Kingdom Hearts Birth By Sleep

[[Unknown]]

Well, unfortunately many Windows 10 drivers seem to still have bugs. The fact that this persists beyond PPSSPP closing definitely means it's a driver bug, and it may be fixed in a future version of the driver. So I'd recommend staying tuned for updates from AMD.

That doesn't mean it's not ALSO a bug in PPSSPP. We made 109 changes between v1.0.0 and v1.1.1, so that's already pretty helpful.

A few things to try / clarify:

You're for sure using "OpenGL" as the rendering backend, right?

You're using a 64-bit version of PPSSPP (PPSSPPWindows64.exe), right?

Try changing the following options:
1. Change "Simulate block transfer" to off.
2. Change "Rendering mode" to "Buffered rendering".
3. Change "Vertex cache" to off.
4. Change "Disable slow framebuffer effects" to ON.
5. Make sure nothing under "Hacks" at the bottom is selected.
6. Change "Fast memory" under System to off.
7. Disable any post-shader you're using (if you don't know what this means, you're probably not using one.. options are e.g. "Natural Colors", etc.)

Note that 1 and 4 will potentially cause graphical glitches in the game. But, disabling those things may avoid triggering the bug - it can at least help is narrow down that the bug IS in those features.

From the regression range (https://github.com/hrydgard/ppsspp/compa.....v1.0.1), the most likely candidates to me seem to be:

https://github.com/hrydgard/ppsspp/pull/7458 / https://github.com/hrydgard/ppsspp/issues/7457
https://github.com/hrydgard/ppsspp/pull/7520

But I'm not sure. If you want to help narrow it down, it'd be great if you could test a git build in between (like v1.0-53-g6f0ea8f) v1.0.0 and v1.0.1. If you can test a couple, go by halves - 4-5 tries would narrow it down a lot, but I imagine you have to restart in between each one.

-[Unknown]