protonscr

Ridge Racer Unbounded: Vertex explosion issues

dxvkclosed d3d9
doitsujin/dxvk#5318 · opened 2025-11-09 by waspennator · updated 2025-11-10 · 4 comments · github
Wwaspennator 2025-11-09 github

Game is marked as steam deck playable and it seems to work fine on deck and windows with dxvk at first, however every so often during races, there will be these random vertex explosions that will occur, sometimes they last for a few seconds, other times they go on for longer.

Image

If you use Windows, please check the following page: https://github.com/doitsujin/dxvk/wiki/Windows

Software information

Ridge Racer Unbounded

System information

  • GPU: AMD Van Gogh, RX 7700s
  • Driver: Mesa 24.3.4, 32.0.21025.10016
  • Wine version: 9.0
  • DXVK version: [d3d11,util] Add GPU execution cost heuristic for submissions

Apitrace file(s)

  • I tried getting an Apitrace file on my Framework 16 laptop, but when I tried running it without dxvk, it took way too long to even get in game to get an Apitrace.

For instructions on how to use apitrace, see: https://github.com/doitsujin/dxvk/wiki/Using-Apitrace

Log files

Please attach Proton or Wine logs as a text file:

  • When using Proton, set the Steam launch options for your game to PROTON_LOG=1 %command% and attach the corresponding steam-xxxxx.log file in your home directory.
  • When using regular Wine, use wine game.exe > game.log 2>&1 and attach the resulting game.log file.
  • On Windows, log files will usually appear next to the games exe or in its base folder.

steam-202310.log.txt

KK0bin maintainer 2025-11-09 github
Mmbriar 2025-11-09 github

I tried getting an Apitrace file on my Framework 16 laptop, but when I tried running it without dxvk, it took way too long to even get in game to get an Apitrace.

Despite what the wiki says, usually it's no problem to record the apitrace with DXVK enabled, and it's also usually way faster.

Wwaspennator 2025-11-09 github

Sorry for the delay, turns out for some reason, apitrace did not like it when I ran the game on my rx 7700s so I had to drop to my Ryzen 9 7940hs and the trace went through normally without taking an eternity now. Did a trace of one lap, but again I do not know how to consistently get the vertex explosions to trigger.

https://www.mediafire.com/file/jllod56gjp1u7rc/RRU.zip/file

BBlisto91 2025-11-10 github

The PR above should work around the issue.

We've also updated the apitrace guide so to better explain tracing with dxvk versus wined3d

Launch options