[XCX] FPS++ Crash Behavior at 120fps Cap

[MacreadyX]

Describe the issue
See https://bugs.cemu.info/issues/693 for a description.

To Reproduce
Steps to reproduce the behavior:

1. Boot game up
2. Load attached save with FPS++ active and set to 120fps cap. Take a left, then a left again to run down Armory Alley. You will crash before reaching the far end.

Expected behavior
No crashing.

Desktop (please complete the following information):

• OS: [Windows 11]
• GPU: [Nvidia 4080]
• Renderer [Vulkan]
• Version [Cemu 2.0-86; latest FPS++]

Additional context
Crash doesn't happen at 60fps mod default. Crash does happen at 120fps cap.

These crashes only happen (sometimes) immediately after loading. The attached save was created after 3 uninterrupted hours of rock-solid play. Only after saving/reloading does the potential for this crash behavior seem to exist.

Further, the crash behavior can be cleared by leaving the problem area. I'm still trying to determine how far you need to go / how long you need to wait before returning / etc. But in the case of the attached save, if you load, immediately run to the transport (taking the route away from Armory Alley), head to Industrial District, then exit via the west gate and go as far as the first stream, by that point (if you make it without a crash), whatever was causing the Armory Alley crash has cleared - you can double back and have no problem. Speaking more generally (and not just about this save example), once you get out from under the shadow of a problematic game load, the game will be completely stable. The crashes happen in the first minutes right around where you loaded in, or they don't happen at all.

This error can usually be found in the log immediately post-crash:
[00:04:19.281] GLSL parsing failed for ffef00f9c1d0e51d_00000000fffff301: "ERROR: 0:31: 'textureUnitPS1' : identifier not previously declared
ERROR: 1 compilation errors. No code generated.

CrashSaveXCX.zip