Ridge Racer Unbounded
System Information gist: https://gist.github.com/MartynHare/dfc6bcccb35c8f28dd5c1399c2db5c71
Attached log with real steam_api.dll to assist in debugging
using "WINEDEBUG": "+timestamp,+pid,+tid,+seh,+debugstr,+module",
"DXVK_LOG_LEVEL": "info",
Attached a log of the results with the "modified" steam_api.dll to assist in debugging.
This includes a playthrough of the very first race using the DLC Ridge Racer car (to show that DLC works).
The "modified" steam_api.dll includes a file called steam_rld.ini, attached for reference.
steam_rld.ini.txt
I have the same problem, but have to Say that someones on protondb reported no crash.
After switching to Proton 3.16-5 i can confirm that Ridge Racer plays like a charm now.
I have played with Proton 7.0 and it works fine.
Game is marked as playable on deck, but ive ran into moments where it looks fine, only for everything to start vertex exploding, making the game more difficult to play. Dunno how to consistently trigger it, just keep doing the first race, restart it here and there if it doesn't happen before the finish and eventually things should start freaking out. I believe from testing and reading reports on protondb and the community hub that this started after 5.0-10 proton
Update, tested it on my framework laptop, can confirm now its a dxvk issue
Testing it out with proton Experimental bleeding edge for a couple of races, seems like the vertex explosions are gone, might need to test some more but I haven't run into any with the latest dxvk fix
I’m still getting it in the default setup from Steam, is there a way to tell which version of DXVK is being used? It looks like versions after this patch should work better.
Proton versions
proton experimentalx1 2025-11proton 7.0x1 2022-02proton 3.16-5x1 2018-12
Launch options
DXVK_LOG_LEVELx1 2018-08WINEDEBUGx1 2018-08
Upstream links
- doitsujin/dxvk/pull/5319x1 2026-04
DLLs
steam_api.dllx3 2018-08
Problem: Game loads as far as saying that the server cannot be contacted, then when pressing Enter or A to continue, the game will exit. At the point of crashing it does appear to show "Saving" in the bottom left, leading me to believe the crash is as a result of a Steam API (SteamWorks?) call.
Expected behaviour: Pressing Enter or A loads main menu and the game otherwise works as usual.
Current, possibly illegal workaround: When using the steam_api.dll which ships with the game, the problem occurs, however, replacing it with a "modified" steam_api.dll, the game works as usual. The SHA-256 of the "modified" steam_api.dll is 90199178b736e1bc7f3e5d3acbf4c8c105b538aa9034d281a1631100b775d463.
I would appreciate it if a Valve developer could assist, as Google doesn't seem to indicate this as being widespread and the problem appears to be related to Steam's DRM more than Wine here. If a Valve developer requires a copy of the DLL or a binary diff needed to make it, please let me know of a private e-mail address to send it to or private ticket to attach it to.
Many Thanks,
Martyn Hare