starred/shadPS4

Fork 0

mirror of https://github.com/shadps4-emu/shadPS4.git synced 2026-04-25 15:56:00 +03:00

[GH-ISSUE #1373] GFD Engine games enter a weird softlock state due to GPU Buffer Cache stuff #455

New issue

Closed

opened 2026-02-27 21:06:23 +03:00 by kerem · 6 comments

kerem commented

2026-02-27 21:06:23 +03:00

Owner

Originally created by @Da-nu on GitHub (Oct 14, 2024).
Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/1373

Originally assigned to: @polybiusproxy on GitHub.

My earlier issue (#590 ) mentioned this softlock when I first discovered it in P5D and thinking its only an issue there. As more GFD games started running, the softlock happened in all of them. ShadPS4 logs don't seem to show anything about whats causing them.
The earlier issue was focused on P5D, but I made this new one for GFD games in general.

Originally created by @Da-nu on GitHub (Oct 14, 2024). Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/1373 Originally assigned to: @polybiusproxy on GitHub. My earlier issue (#590 ) mentioned this softlock when I first discovered it in P5D and thinking its only an issue there. As more GFD games started running, the softlock happened in all of them. ShadPS4 logs don't seem to show anything about whats causing them. The earlier issue was focused on P5D, but I made this new one for GFD games in general.

kerem

2026-02-27 21:06:23 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-27 21:06:23 +03:00

Author

Owner

@polybiusproxy commented on GitHub (Oct 15, 2024):

This appears to be present in all GFD Engine games.
The game gets on a loop reading the same file offset on the CriWare filesystem thread, over and over again. I suspect the cause is deep within the emulator's threading emulation.

I must also add that this issue apparently was not present in older versions, so this appears to be some sort of regression.

@polybiusproxy commented on GitHub (Oct 15, 2024): This appears to be present in all GFD Engine games. The game gets on a loop reading the same file offset on the CriWare filesystem thread, over and over again. I suspect the cause is deep within the emulator's threading emulation. I must also add that this issue apparently was not present in older versions, so this appears to be some sort of regression.

kerem commented

2026-02-27 21:06:23 +03:00

Author

Owner

@Da-nu commented on GitHub (Oct 18, 2024):

I would like to note the issue seems to be more common when in PS4 Pro mode.

@Da-nu commented on GitHub (Oct 18, 2024): I would like to note the issue seems to be more common when in PS4 Pro mode.

kerem commented

2026-02-27 21:06:23 +03:00

Author

Owner

@polybiusproxy commented on GitHub (Oct 19, 2024):

I don't think PS4 Pro mode would do something, considering all it does is mostly raise the maximum of available memory to the game.
What you experienced is most likely a race condition which would check out with what there's reported already, that makes me more confident that this is a threading issue.

@polybiusproxy commented on GitHub (Oct 19, 2024): I don't think PS4 Pro mode would do something, considering all it does is mostly raise the maximum of available memory to the game. What you experienced is most likely a race condition which would check out with what there's reported already, that makes me more confident that this is a threading issue.

kerem commented

2026-02-27 21:06:23 +03:00

Author

Owner

@Da-nu commented on GitHub (Nov 3, 2024):

The cause of the issue has been found and there are 2 working workarounds. One of them is Linux only and breaks sound and the other seems to be multiplatform. Both lead to some sort of slowdown in performance. Poly is free to give a more in-depth explanation of what's happening because I am not the best at explaining how this issue works.

@Da-nu commented on GitHub (Nov 3, 2024): The cause of the issue has been found and there are 2 working workarounds. One of them is Linux only and breaks sound and the other seems to be multiplatform. Both lead to some sort of slowdown in performance. Poly is free to give a more in-depth explanation of what's happening because I am not the best at explaining how this issue works.

kerem commented

2026-02-27 21:06:23 +03:00

Author

Owner

@Da-nu commented on GitHub (Dec 10, 2024):

https://github.com/shadps4-emu/shadPS4/pull/1726 appears to have fixed this. Someone has confirmed to have P3D and P5 running. I will test P4D, P5D, and P5R later to confirm.

@Da-nu commented on GitHub (Dec 10, 2024): https://github.com/shadps4-emu/shadPS4/pull/1726 appears to have fixed this. Someone has confirmed to have P3D and P5 running. I will test P4D, P5D, and P5R later to confirm.

kerem commented

2026-02-27 21:06:23 +03:00

Author

Owner

@Da-nu commented on GitHub (Dec 11, 2024):

Can confirm it just works now. The framerate issues seem unrelated to this and P5R has some extra issues unrelated to this.

@Da-nu commented on GitHub (Dec 11, 2024): Can confirm it just works now. The framerate issues seem unrelated to this and P5R has some extra issues unrelated to this.

kerem referenced this issue

2026-02-27 21:13:08 +03:00

[PR #455] [MERGED] Qt-GUI: Improvements (Part 2) #1575