mirror of
https://github.com/shadps4-emu/shadPS4.git
synced 2026-04-26 16:25:58 +03:00
[GH-ISSUE #3315] [GAME BUG]: DriveClub gets stuck on loading screen. #1019
Labels
No labels
Bloodborne
bug
contributor wanted
documentation
enhancement
frontend
good first issue
help wanted
linux
pull-request
question
release
verification progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/shadPS4#1019
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @bulumbala on GitHub (Jul 24, 2025).
Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/3315
Checklist
Describe the Bug
In previous versions it was running at a stable 30 fps with ctds in middle running.
eg: Now in 'DriveClub' has stopped working from the begining at loading screen.
There is something that has broken compatibility.
Sure it will be fixed in the next versions.
Specs: Win11-24h2, ryzen 7600x, radeon 7800xt, SSD, 32Gb DDR5.
ShadPS4: Default settings, no patches applied, Readbacks=on, ( CUSA00093 v1.28 ).
Regards.
Reproduction Steps
Copy sys_modules to ShadPS4 folder.
Set readbacks=true inside config.toml
Start last ShadPS4 Pre-release:
fb5ac91Left all settings by default. Select the ROM and press Play to start emulation process.
The process freees and hangs at loading screen.
Wait in a black screen for a while. Try to close all the processes and restart system.
Expected Behavior
In previous versions it was running at a stable 30 fps with some ctds situations that could be resolved.
Now it doesn't even start.
Specify OS Version
Windows 11 24H2
CPU
ryzen 7600X
GPU
Radeon 7800 XT
Amount of RAM in GB
32 GB
@Missake212 commented on GitHub (Jul 24, 2025):
You chose the wrong template since this is a game bug issue, could you send a log ?
@bulumbala commented on GitHub (Jul 24, 2025):
Sorry, i changed the topic to GAME.
I´ll sending to you, thanks. ( error: [Debug] vk_scheduler.cpp:175 operator(): Assertion Failed!... )
shad_log.txt
@bulumbala commented on GitHub (Jul 25, 2025):
QUOTE:
"Could you specify the newest "previous version" that worked in DRIVECLUB?
Having a timeframe for when the regression could've occurred will make it easier for developers to debug"
ANSWER:
Since the build #8511 it starts to fail.
-Build #8510 works fine: shad_log Build 8510.txt
-Build #8511 no longer starts: shad_log_Build 8511.txt
-Configuration file: config_toml.txt
Regards.
@StevenMiller123 commented on GitHub (Jul 25, 2025):
Based on that, it's a regression from #3306.
Thanks for the additional information.
@bulumbala commented on GitHub (Jul 25, 2025):
Yes, it´s from: https://github.com/shadps4-emu/shadPS4/actions/runs/16478196302
@ctrlinsert commented on GitHub (Jul 25, 2025):
Stephen, it’s worth noting that this is likely an issue with the user’s setup or configuration as I’ve not seen anyone complain in either the shad or Driveclub servers about this being an issue.
@StevenMiller123 commented on GitHub (Jul 25, 2025):
I'm leaning towards this being specific to RDNA3 graphics cards on Windows, that particular generation has really bad driver issues on Windows (and this is a driver crash, as the log shows a device lost error).
If you can find someone with an RDNA3 GPU, testing this game on Windows, and they don't have this issue, please comment that here @ctrlinsert
@raphaelthegreat commented on GitHub (Jul 25, 2025):
Please enable validation the log is useless without it, since it's a device loss
@Solitair69 commented on GitHub (Jul 25, 2025):
for me it never passed that first loading screen neither with noir without readbacks
in the meantime i also updated to 377.00
RTX3070 AMD Ryzen 9 3900X
tested like the last 10 nightlies
shad_log.txt
@bulumbala commented on GitHub (Jul 25, 2025):
I hope it helps, since build 8511 It gets stuck on the loading screen:
Build 8511: shad_log.txt
Build 8666: shad_log.txt
Config file: config_toml.txt
@bulumbala commented on GitHub (Jul 25, 2025):
With the same system configuration and driver version, 25.6.3, it continued to work until build 8010.
Nothing changed on my system. It only stopped working since build 8011.
Regards.
@Missake212 commented on GitHub (Jul 25, 2025):
@bulumbala You're missing the Vulkan SDK so the log with Validation layers enabled you sent is the same as the one from before, you need to install the Vulkan SDK.
@bulumbala commented on GitHub (Jul 25, 2025):
Thanks for the guidance. I'll install the development kit and report back on the results.
https://vulkan.lunarg.com/sdk/home#windows vulkansdk-windows-X64-1.4.321.1.exe
@bulumbala commented on GitHub (Jul 25, 2025):
Now it doesn't even start, do I need to configure something within the SDK?
shad_log.txt
config-toml.txt
@RP32WEC commented on GitHub (Jul 26, 2025):
I have this exact same issue using 7800XT
@Missake212 commented on GitHub (Jul 26, 2025):
@bulumbala it should work as is, I also don't think you can mess up the Vulkan SDK install so I'm not sure what happened, you should disable all those other settings in the debug tab though.
@bulumbala commented on GitHub (Jul 26, 2025):
Hi, ok, the reliability after any change is very finicky. As soon as something is updated, it's like starting over.
,Thanks for your help.