Have you tried with PROTON_ENABLE_NVAPI=1 and a dxvk.conf file on the folder of the game executable with the line dxgi.nvapiHack = False ?

Yup, after trying that the results weren't any different.

Okay, scratch that. I forgot to delete the "#" in dxvk.conf. I don't get the launch error anymore but the game still crashes after a race.

So, after doing a little more research, I've come to the following conclusions:

• On NVIDIA, you can disable the AMD driver launch error by adding dxvk.conf in the game's install dir, and adding dxgi.nvapiHack = False to it
• On NVIDIA, game crashes after a race when on High or Ultra High graphics presets. When the game is set to Medium or lower, the game doesn't suffer any crashes. So I'm guessing there's some sort of video option that's causing the crash
• Game seems to play well for those who have AMD hardware, albeit for the Steam Deck, according to ProtonDB reports
• Vanilla Proton 7.0-1 is needed to play the game; Proton Experimental and Proton GE don't work (it might just be the Denuvo DRM triggering though)

The game crashes after every race for me on AMD too (Radeon 5600XT). I get to race the initial race and it will crash after the end of the race. Having to race that initial race again next time.

@200Puls try setting the graphics to medium or lower

Hi @linuxgamingcentral ,

thanks for the tip.
That did actically work. Dropping from ulta hight to medium fixed the crashing. Has anybody tried to figure out the single setting that causes this?

I haven't spent the time trying to figure out what setting it is, and I got the game as part of my EA Play subscription. So since my subscription is no longer active I can't test this anymore.

I'm getting a crash on start-up after a long (30+ seconds) black screen. Occasionally I'll get through and then won't have any crashes even after races but I've only managed that once or twice between 10+ attempts.

GPU: AMD Vega 56
CPU: AMD Ryzen 9 5900X
RAM: 32 GiB
Proton version: 7.0-3
OS: Arch Linux, kernel 5.18.6, mesa 22.1.2

Running with PROTON_LOG=1 %command% -dx12, log attached.
steam-1307710.log

System Information

• GPU: AMD RX 480
• Driver/LLVM version: Mesa 22.1.3 / LLVM 14.0.6
• Kernel version: 5.18.9-arch1-1
• Link to full system information report as Gist: Gist
• Proton version: experimental-7.0-20220706 (same with 7.0-3)

Logs: (including Proton and kernel logs)
steam-1307710.zip

Symptoms

Launching the game with high graphics preset (game needs reboot after changing graphics settings!) the game will crash after almost every race, sometimes even causing a full system crash. This happens right when it transitions to the loading screen.

Reproduction

1. Launch game
2. Ensure graphics are at least set to high preset, restart game after changing preset
3. Launch Benchmark from advanced section in graphics settings
4. Wait for benchmark to finish
5. Continue past benchmark results
6. Either game or system crashes/freezes

It is common for the game to crash between loading screens after races. It also has no online connection, and notifies you at startup. I should clarify that I have tested with the Origin version and Proton-GE 7-21 (@GloriousEggroll ) through Lutris.

I too run the Origin version with Lutris-GE-Proton7-19. I don't have the crashing issues, and the game runs surprisingly well with dx12 and on my Nvidia Pascal-generation card.

The biggest issue for me is that I too don't get online connection, and by the looks of it on ProtonDB, other people don't have that too. I assume multiplayer doesn't work because of this.

I realise now that although my Steam deck review on proton-db says it works fine (which it does) I forgot to mention that I'm running the Origin version - not the Steam version. The online thing I can only imagine is an anti-cheat that is not functional. This makes me sad as I imagine online play would be quite fun.

With kernel 5.18.14-arch1-1 and Mesa 22.1.3, I no longer have the very long wait before entering the main menu and no longer have the periodic crashes during that wait.

I do still have crashes after races when graphics settings are set to 'Ultra'.

Just to update on my previous post here, I tried AMDVLK Open (2022.Q3.3-1) today and it runs the game stable and doesn't crash the game or my system in between races. Performance roughly gets cut in half compared to RADV however.

RADV still crashes on loading screens after a race (Kernel 5.19.2-arch1-2 and Mesa 22.1.6-1 on Arch).

Also, online services for the game don't connect either way unfortunately.

Issue is still present on the latest build of Steam Deck. In game mode, game won’t launch because the error is in the background. In desktop mode, error can be bypassed but sometimes game won’t launch.

RX 580 - Steam Flatpak - mesa 22.3.2 keeps crashing after some time.. proton 7.0-5

I tried playing this game with wine-tkg-staging 8.0 + dxvk 2.1 + vkd3d 2.8 and online seems to work as well!
at least when I am playing with the EA app, the game requires shared resources, which is why tkg patches are needed (shared resources are part of proton exp already, so if you are using proton exp, don't worry about it).
no crashes here unless you alt-tab

I still need to do more testing though

with protonGE works

Online working really well

I played for a few hours, I didn't see any crashes (even when online), was a flawless experience with the EA app (unless you alt tab :p)

wine version:
wine 8.0-rc5 tkg staging

Tkg/proton patches are REQUIRED, the game seems to use shared resources

Mesa version:
Mesa-git with rx 6800

found the code responsible for getting rid of the outdated driver popup: https://github.com/ValveSoftware/wine/blob/f497ac98efbb3c924a7ab9630963b88e20385ca4/dlls/amd_ags_x64/amd_ags_x64_main.c#L539

all you have to do in theory is add a DLL override, since normal wine doesn't have this dll, I simply replaced it and the popup is gone!

Hi @linuxgamingcentral ,

thanks for the tip. That did actically work. Dropping from ulta hight to medium fixed the crashing. Has anybody tried to figure out the single setting that causes this?

Did you figure it out by any chance?

Hi @linuxgamingcentral ,
thanks for the tip. That did actically work. Dropping from ulta hight to medium fixed the crashing. Has anybody tried to figure out the single setting that causes this?

Did you figure it out by any chance?

sorry for the ping, I believe the setting is "Texture Quality", set it to Medium or below should solve the after-race crash issue.

However I only have a graphic card with 6GB of VRAM (Nvidia RTX 3060 laptop), is it running out of VRAM then crash?

Replying to https://github.com/ValveSoftware/Proton/issues/5619#issuecomment-2348593438

I spent 3 days and got banned for a day by denuvo crap actually for it (every start of the game == new proton prefix id == new computer, times over 100 crashes I had).

The issue seems to be more complex, to the point it seems like a VRAM allocation issue.

I started with everything set to all-lowest. I was able to reliably complete a race with everything maxed out with exclusion of: AA, XeSS, Textures, Crowds, Shadows, Smoke shadows -- these were set to off/lowest.

And now the fun begins. Setting shadows to high did not let me move textures to even medium (same with smoke shadows or crowds). Having crowds off and shadows to the lowest has once allowed me to have textures high, but crashed next race, and medium reliably for all the time.

AA has also effect on VRAM usage - was making things even less reliable, but I keep it disabled most of the time, as I use XeSS at balanced for most of the time. With crowds off and shadows to low, textures set to medium and everything below that 100% maxed out - I am able to have 90-95% success rate past the race.

Also - fsck denuvo. It blocked me from playing a legally purchased game for a stupid reason.

update: it seems have no more after race crash now even with "Textures Quality" on High. somethings have changed on my setup and I noted them below (updated proton version, system ram, etc.).

by the way, game's XeSS or TAA sometimes leads to wrong camera position. change it to a different presets solves this.

edit a day later: got this error after a hour or so, causing the game crashed when continues to next race session:

2025/2/16 13:50	kernel	NVRM: GPU at PCI:0000:01:00: GPU-c6fe1953-d213-3c07-b94d-6833dab2d3bc
2025/2/16 13:50	kernel	NVRM: Xid (PCI:0000:01:00): 31, pid=52312, name=GridLegends.exe, Ch 0000000f, intr 00000000. MMU Fault: ENGINE GR0_PBDMA0 HUBCLIENT_ESC faulted @ 0x18_8c3eb000. Fault is of type FAULT_PDE ACCESS_TYPE_VIRT_READ

looks like a nvidia bug than game itself (Xid 31, FAULT_PDE ACCESS_TYPE_VIRT_READ). also see: report on nvidia forum

This game's stability is literally everywhere when I tweaks vsync and mangohud frame limiter...

Maxed everything graphic setthings out seems pushed it and gpu to limit, game crashed except set vsync on and monitor refresh rate to 60Hz (but game itself vsynced to 65fps); that means 60Hz+vsync off, 60Hz+mangohud capped 60fps and 144Hz (my laptop monitor's refresh rate)+whatever fps cap crashes.

If I set graphic settings down to everything high, odds even more. 144Hz with vsync on or off the game is fine; 144Hz+mangohud capped 60fps crashed. 60Hz+vsync on or off it's fine; but, 60Hz+mangohud cap sometime it crashed while other times not.

During this whole test these settings kept untouched: bordless fullscreen, xess ultra quality, DRS (dynamic render resolution) 30fps, VRS (variable rate shading) on.

edit: uhhh... after switch my laptop from hybrid to dgpu, those extra 700~1gig vram usage again crashed this game