mirror of
https://github.com/shadps4-emu/shadPS4.git
synced 2026-04-25 15:56:00 +03:00
[GH-ISSUE #3322] [GAME BUG]: Driveclub works fine with Nvidia GPU but fails with AMD rdna 3 #1018
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#1018
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 25, 2025).
Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/3322
Checklist (we expect you to perform these steps before opening the issue)
Describe the Bug
AMD rdna3:
In previous versions it worked but now it gets stuck on the loading screen.
Nvidia:
I swapped the Radeon 7800 xt for an Nvidia GTX 1060 6GB, driver 577.00, and I can even complete the introductory race. Everything works fine with this GPU.
AMD log:
AMD shad_log.txt
Nvidia log:
shad_log.txt
Config file:
config_toml.txt
Reproduction Steps
Copy sys_modules to ShadPS4 folder.
Set readbacks=true inside config.toml
Start last ShadPS4
Left all settings by default. Select the ROM and press Play to start emulation process.
The process freezes and gets stuck at loading screen.
Specify OS Version
Windows 11 24H2
CPU
Radeon 7600x
GPU
RDNA3 Rx 7800 XT
Amount of RAM in GB
32GB
Amount of VRAM in GB
16GB
Log File
AMD shad_log.txt
Nvidia shad_log.txt
config_toml.txt
@StevenMiller123 commented on GitHub (Jul 25, 2025):
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.
@StevenMiller123 commented on GitHub (Jul 25, 2025):
Closing as a duplicate of #3315
Please send further information related to this issue there instead.