How do you make the game crashed? i think that crash is an important issue to be fixed

How do you make the game crashed? i think that crash is an important issue to be fixed

Simply abuse any ingame mechanic (such as starting 2 different missions) to cause the game to crash.

For this screenshot and dump, I changed the player handle to an invalid value (such as 0 or -1) with Cheat Engine in order to intentionally cause a crash with the "Resume" button appearing on the crash screen. The "Resume" button is important so that the game can be continued from a previous savestate. Otherwise we would have to quit to the main menu of PPSSPP and load the game again from the startup screen.

The crash is the game's fault. That is not the problem. The problem is the emulator producing the above visual glitch after loading a savestate from a crash screen, and then using the ingame pause feature.

I see, if it crashed because you intentionally tampering the memory i guess it wasn't an issue.

Regarding the resume button, i also noticed it a while back while testing some games that had in-game crash issue (blue screen), and as i remembered an alternative way to resume it (if the resume button didn't shows up or grayed out) is by pressing ESC (or Back button) and then click "Continue", this will resume the emulation.
But, yeah, this "Resume" button and the visual glitches need to be fixed.

Can't reproduce this in v1.12.3.

Okay, it may be this was fixed then. I know we changed some things in shaders.

I'm going to mark this as closed, in that case. Thanks for the update.

-[Unknown]

I've encountered the same rendering glitch again. No game crash involved this time.

Is this using Vulkan and MSAA? Seems slightly like the Jeanne d'Arc issue.

-[Unknown]

It's using OpenGL and I don't see an option for MSAA anywhere.

This isn't the same as #13529? We all know sometimes savestate can cause glitches 🤔

This isn't the same as #13529? We all know sometimes savestate can cause glitches 🤔

Could be related, but if this trick still worked:

6. Launching GE Debugger gets rid of the visual glitch

and able to fix the glitch, that mean there is a way to prevent it from glitching after loading from savestate.

I wondered why simply bringing out GE Debugger could fix the glitch 🤔 did it flushed the cache or something?

The GE debugger will change a few things when it's active:

• It prevents the multiple prim calls in a row optimization.
• It skips "fast load" bone matrix optimizations.
• It prevents the matrix skip-load optimizations.
• It uses the slow run-loop which should be the same but is technically different code than the fast run-loop.

So mostly it turns off optimizations that interfere with stepping. If it affects the game here in current versions, either we're misdetecting a fast-load matrix situation, or something about reading the prims all in a row is going wrong, I guess.

-[Unknown]

I'm not sure how to feel about this issue.
I am noticing that sometimes I have the same problem with other apps that use GPU acceleration, with a similar pattern of the exact same visual artifact. The difference is that the artifacts only appear in other apps while switching tasks to them, and they automatically disappear like half a second later.
I have updated my driver several times since I'd opened the issue (new OBS Studio releases force me to update it from time to time)