pcsx2
pcsx2 copied to clipboard
PCSX2
Cho Aniki: Seinaru Protein Densetsu - Graphic corruption on one particular boss in HW mode
PCSX2 version: PCSX2 v1.7.0-dev-125. My build is slightly customized but the customization doesn't touch anything relevant to this game.
PCSX2 options: The only option that has any impact as far as I can tell is whether gsdx is in software or hardware mode, and there's even a caveat there.
Description of the issue: An odd problem in a very odd game. One boss should be wearing a dress which gets destroyed as you fire at it. If playing in software mode it appears correctly. If playing in hardware mode the dress isn't visible and the boss displays corrupted textures over the underlying model. As mentioned, there's a caveat to this however: what's important appears to be the mode gsdx is in before the boss loads in. If the boss is loaded in software mode but gsdx is then switched to hardware mode once the boss is onscreen, the boss is rendered and graphically behaves correctly. The reverse is also true, and if the corrupted boss is rendered in hardware mode, it's still corrupted on switching to software mode.
How it should appear:
How it appears:
Why not just play in software mode? Because this game has another issue in both hardware and software mode that I will be reporting shortly, and that is possible to mitigate in hardware mode.
How to reproduce the issue: Fight the "Alice" boss while in hardware mode before the boss appears on screen.
PC specifications: Ryzen 3700x, Nvidia GTX 1080, Windows 10
GSDump and save state attached.
ChoAnikiSave.zip ChoAniki.gs.zip
Could be a GS download issue, if the dump was made in SW but HW only breaks when playing the game.
Would be interesting to know if it works now in master since kojin fixed some gs download issues.
I tested this till the savestate was compatible. Kind of hard to test this now without getting a memory card save or save with latest dev build.
I'll take another look at this and if the problem's still there I'll produce a new save state when I get the chance.
I've retested. It is still a problem at default settings, but it now appears fixable. Setting CPU Sprite Render Size to 4 or higher seems to eliminate the issue.