pcsx2
pcsx2 copied to clipboard
PCSX2
[BUG]: SLUS-20937 Wild ARMs Alter Code F - GPU Palette Conversion broken in 2.2.0
Describe the Bug
I noticed once upgrading from 2.0.2 to 2.2.0 that Wild ARMs Alter Code F's rendering looked way different: textures would disappear or be replaced, triangles would completely disappear, etc. I started messing around with the settings and checked the Manual Hardware Renderer Fixes which seemed to resolve the issue. The display said that this changed gpuPaletteConversion = 2 (not sure how that aligns with a checkbox but okay).
That's the best I can give you at the moment. Not sure what could have caused it, but there appears to be a workaround, which is good.
Reproduction Steps
Enable or disable GPU Palette Conversion. I had to manually restart the game to see the broken state, as enabling it fixed it at runtime.
Expected Behavior
No response
PCSX2 Revision
v2.2.0
Operating System
Windows 11
If Linux - Specify Distro
No response
CPU
i5-1035G4
GPU
Intel Iris Plus Graphics (Surface built-in card)
GS Settings
No response
Emulation Settings
No response
GS Window Screenshots
No response
Logs & Dumps
No response
@rbrettj I don't see a difference between the two releases? Can you post a gs dump where it shows the issue?
I don't think I'm understanding what you mean; there's only the single dump and screenshot, both with the issue. Did you want me to post two dumps, one with and one without the issue? I followed the instructions on how to generate the dumps from on here but there's a chance I didn't do it right. I just want to make sure I get you what you're asking for. My apologies for the confusion.
I mean I don't see any issue on the dump you posted, or am I missing something?
I'm not sure where you got that image, but here is the one included within the zip that shows the issue:
I'm not sure where you got that image
It's from the gs dump you provided when replaying it I can't spot any issue, are you running any non default settings?
As I mentioned in the description, the issue appears for me with default settings, whereas enabling manual hardware fixes and checking GPU Palette Conversion fixes the issue. Not sure what else to mention. I find it odd that the gs dump does not appear to show the issue, but I'm not privy to how it works so that might be expected depending on what the issue is.
Is the game fine on software renderer? Can you upload a block dump with a savestate of the game?
I'm not sure how to check that. I also don't see any documentation on how to create a block dump. Can you point me to some documentation for those and I'm happy to oblige. Thanks.
To clarify one of your points, the reason it notes that the fix gpuPaletteConversion = 2 is not applied is because, when you turn Manual Hardware Renderer Fixes on, it sets all of the settings in the Hardware Fixes and Upscaling Fixes tabs to default (since the assumption is that, if you're using this setting, you want to start from a clean slate). This means that settings which are automatically applied via the GameDB (we test for per-game settings that fix issues, place them in a YAML file, and apply these settings automatically) are no longer applied.
I must be confused because what you describe is almost the opposite of what I saw, and when I try it now without running the game (just clicking properties of the game but not starting it) it seems to behave as you describe. I'm not sure how I would have guessed to turn that setting on. Can you confirm in the GameDB that the YAML file has that setting checked? Can you point me to somewhere I can check that myself?
Is there a possibility of a race condition or something where me turning on manual hardware fixes could have not cleared the board as normal but exposed the settings as defined in that YAML file? It certainly is a possibility that I inadvertently got myself into this situation and there is no bug, but as a software engineer myself with plenty of experience using software, I cannot see myself making such a simple mistake, lol.
