Can confirm the same wine error:

GPU: Vega 64
Driver/LLVM version: RADV 19.1, 9.0.0 LLVM and tried too: AMDVLK Q2019.Q2.2 
Kernel version: 5.0.15-liquorix
Proton version: 4.2-3

I sometimes get an error dialog about unknown graphics drivers, yet it appears randomly. Tried installing vcrun2015 via winetricks and did it manually, but didnt change the wine error.

but didnt change the wine error.

Nothing you do should change that error. The flaw with Wine is that if a game comes out that uses something Wine doesn't already implement to some degree, then it crashes and can't be used until its implemented to the needed degree.

On the other side of the coin is that there are errors that do not keep games from working to the game's end but could still introduce various problems.

So if this error is what's keeping the game from working and it very much appears to be then you can't do squat to fix it unless you want to do the programming yourself. So you can wait until someone does instead.

Maybe though if you can get it the .dll and it accepts it as a workaround. You have to make sure its not taking in the Wine dll version and if still not working then its a most likely a done deal.

In this case it looks like its only finding "C:\windows\system32\api-ms-win-crt-math-l1-1-0.dll" is a fake Wine dll https://github.com/wine-mirror/wine/tree/master/dlls/api-ms-win-crt-math-l1-1-0 > stub fmaf

And Valve decided to add in a fix https://github.com/ValveSoftware/Proton/releases/tag/proton-4.2-4 though possibly not totally fixed. It looks like there may be other problems too.

random crashes going to map

Can get in game now but sometimes it still hangs on the loading screen.
Overall 25 fps more on AMDVLK than on RADV.
Thx for the fix so far :)

Hey Kisak, in my case its not launching, despite the update to 4.2-4. Captured the information as you requested in your response to trenton.

steam-548570.log

Steam system information : https://gist.github.com/BoldyPlays/d1139dcfdb9c3f7fe9f557d2e5b472fa

Hey @kisak-valve good shout, I'll take care of that immediately - Appreciated!

Tried to use something a little more recent @kisak-valve to no avail, same result. I've refunded the game for now, maybe revisit it when AMD drivers are not a total cluster**** - cheers for getting back to me man!

https://gist.github.com/BoldyPlays/d1139dcfdb9c3f7fe9f557d2e5b472fa

https://gist.github.com/trenton4k/300c294e4d8b13988b81c5e45f73fe2a

Hello @trenton4k, please add PROTON_LOG=1 %command% to the game's launch options, reproduce the crash, and drag and drop the generated $HOME/steam-$APPID.log into the comment box. Also, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.

https://gist.github.com/trenton4k/300c294e4d8b13988b81c5e45f73fe2a

steam-548570.log

I have the same issues on AMD, on RADV the game crashes on the epilepsy warning screen, on AMDVLK it does run every other try or crashes when the Bethesda Logo starts to show. After 3.5 hours of play I got a random crash to desktop midgame.
I will post my sys infos later, am at work right no and log the game. If I can catch a midgame exit, I will post the proton log.
https://gist.github.com/enthalpie/a336f437376b7912305fa381d91d3b7e
P.S.: its working now pretty good on AMDVLK

The game works with RADV too, but crashes every time when I change resolution from FHD to UHD.

steam-548570.log
steam-548570.log

$ inxi -bM
System:    Host: localhost.localdomain Kernel: 5.1.0-1.fc31.x86_64 x86_64 bits: 64 Desktop: Gnome 3.33.1 
           Distro: Fedora release 31 (Rawhide) 
Machine:   Type: Desktop Mobo: ASUSTeK model: ROG STRIX X470-I GAMING v: Rev 1.xx serial: <root required> 
           UEFI: American Megatrends v: 2202 date: 04/11/2019 
CPU:       8-Core: AMD Ryzen 7 2700X type: MT MCP speed: 2195 MHz min/max: 2200/3700 MHz 
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Vega 20 [Radeon VII] driver: amdgpu v: kernel 
           Display: wayland server: Fedora Project X.org 1.20.4 driver: amdgpu resolution: 3840x2160~60Hz 
           OpenGL: renderer: AMD Radeon VII (VEGA20 DRM 3.30.0 5.1.0-1.fc31.x86_64 LLVM 8.0.0) v: 4.5 Mesa 19.1.0-rc2 
Network:   Device-1: Intel I211 Gigabit Network driver: igb 
           Device-2: Realtek RTL8822BE 802.11a/b/g/n/ac WiFi adapter driver: r8822be 
Drives:    Local Storage: total: 11.57 TiB used: 8.02 TiB (69.3%) 
Info:      Processes: 456 Uptime: 21m Memory: 31.40 GiB used: 14.75 GiB (47.0%) Shell: bash inxi: 3.0.34 

Game will Freeze with nvidia from time to time, when opening tab menu or esc menu. Having vsync enabled makes it happening less, but still happens from time to time.

• GPU: GTX 1080 Ti
• Driver/LLVM version: Nvidia 430.14
• Kernel version: 5.1.4-zen
• Link to full system information report as Gist: https://gist.github.com/xpander69/8c756b27f6f28037072c2e8adaf2216d
• Proton version: 4.2-5
• Proton log: steam-548570.log

edit: Turned off Async Compute from ~/SteamLibrary/steamapps/compatdata/548570/pfx/drive_c/users/steamuser/Saved Games/id Software/Rage 2/settings.ini

2+ hours without a freeze now. If anyone else can also confirm it? might be just luck though :)

edit2: 8+ hours in a row without issues, when Async Compute is disabled.

Confirmed on another 1080 Ti - AsyncCompute=0 fixes triple-tab crash. Thank you!

Confirmed on a GTX 1060 AsyncCompute=0 fixes the crash related with the tab menu.

Still randomly crashes for me when opening the Tab menu with AsyncCompute=0 in settings.ini on RTX 2080 with physical copy activated on bethesda.net with Lutris and Proton 4.2-7.

The new patch seems to break the game. It fails to launch and a "RAGE2 has stopped working" window appears every time I launch the game.

EDIT: Reinstalling the game after the patch seemed to fix the issue. I think it was an issue with an environment variable.

Works fine for me, without reinstall. Only thing was that the resolution and graphical settings were all reset. So i had to configure them again to disable the stupid blur, chromatic aberration and the washed out AA this game has.

Is anyone else getting microstuttering on mouse movement? When I move only with the keyboard it is silky smooth. Same test area moving only the mouse slowly exhibits a consistent stutter like twice a second. I may try to get a video to show it but I'm not sure if my camera is fast enough that it will be visible.

I'm getting 70+ FPS constantly and I'm on a gsync display so I'm fairly sure it's not an actual framerate drop, just feels like something is being presented out of order or twice or something.

Stuttering solved - disabling the chroma effects option above resolved the issue completely (it's on by default). It's smooth as butter now. Not sure if that would be enough for whitelisting as you have to change a setting but I doubt Chroma is a dealbreaker for many people.

A quick update:

Setting the key 'AsyncComputeDisable' to 1 on settings.ini seemed to have fixed it!
Will run some more tests late today to make sure.

Setting the key 'AsyncComputeDisable' to 1 on settings.ini indeed solved the issue for me.
Played for a long time (died many times) and it did not crash anymore. Could not reproduce the error.
Hope that helps someone else with the same issue I had.

@NTMan Are you still able to reproduce the crash when you change the resolution with Mesa 20.1?

I have just pushed a workaround for a game bug (the white circles issue). Please give it a new try. Thanks!

@NTMan Are you still able to reproduce the crash when you change the resolution with Mesa 20.1?

I am was able to reproduce the game crash when switch from fullscreen mode to borderless with mesa 20.1.99 (900bf50).

@NTMan Are you also able to reproduce with AMDLVK or AMDGPU-PRO? I tried again and it didn't happen.

Some observations

Relevant specs:

• i7-4790k
• Radeon VII
• 32GB RAM
• Disp 1 - 2560x1440@144hz+0x0, Disp 2 - 2560x1440@60hz+2560x0
• Kernel 5.6.0-pf4-torvalds-git (pf-kernel)
• Proton: 5.11-GE-1

Game issues/quirks:

• RADV performance is not idea (40fps at 1440p compared to 75+fps with AMDVLK), AMDVLK/xgl performance is excellent.
• The game somewhat predictably crashes after an hour to several hours of gameplay, and I cannot find any specific trigger.
• AsyncComputeDisable does not appear to mitigate the instability I am seeing, rather it significantly impacts performance and causes extreme stuttering.
• The overlay can permanently steal mouse input some small percentage of the time.

Same bug as NTMan reported (Rage 2 stopped, DX Diag...) with AsyncComputeDisable or not, Fullscreen or borderless.
It crashes every time whithin an hour of play (often under 15 mins). Game is unplayable, atm.

Ryzen 5 3600 with GTX 1660 Super on 440.100 driver.
Linux Mint 20

Thanks for your support!

Been trying this lately, things I observed with MESA20 and 21 on 6800XT

1. Stuttering whenever vsync was enabled.
2. ACO compiler corrupts some graphics (menus and maybe some shaders in game).

As for stability, still testing.

https://gist.github.com/jarrard/09d53558bb135408994bf85250d09415

In-game shadows and transparencies seem off (not blending right). Main menus have black blocks all over the place and some animated icons and videos.

This issue is duplicate of link below, and is apparently fixed in future MESA versions, which will one day appear in mainline mesa (I just use stable arch/manjaro atm, tried the mesa-git and it didn't resolve the issue so must be older git).

https://gitlab.freedesktop.org/mesa/mesa/-/issues/4163

I normally turn off vkbasalt etc but forgot this time around. I would test again if there wasn't already a bug report about this issue so will just wait for the next mesa release.

For AMD users, you can set Fullscreen=1 in steamapps/compatdata/548570/pfx/drive_c/users/steamuser/Saved Games/id Software/Rage 2/settings.ini to use the borderless window mode to avoid crashes on focus loss.

For AMD users, you can set Fullscreen=1 in steamapps/compatdata/548570/pfx/drive_c/users/steamuser/Saved Games/id Software/Rage 2/settings.ini to use the borderless window mode to avoid crashes on focus loss.

tried this on proton 8 and proton experimental with no luck, still crashes at start

Is anyone else having severe performance issues in general? Specifically on nvidia?

You'll need to provide more information. When do the performance issues start? main menu, when you go ingame, or after playing for a while? system information? game settings?

I don't have a nvidia card, but after playing for a few minutes with both low and ultra graphics presets with proton 9.0-4 and comparing against windows I got comparable performance. Also couldn't get the game to crash on my side with the tab menu.

It's Ingame. Works fine on Windows. I have an Nvidia RTX 4060. Tried Arch, Fedora, other Linux Distros all the same. Does it on any setting Fullscreen, Borderless, Vsync on and off.

Also to quote this guy from proton db (Copy and Pasted section)

Begin-

Instability:Frequently

Unless I disabled Show Hud, frequent crash every time a Hud element was displayed, especially early game with all the tutorial prompts (each would cause a crash when Hud was enabled).

TLDR: -Something in this games HUD is broken when trying to play on LINUX for me (constant crash) -Show HUD = Off (ran fine and perfectly smooth without crashes)

End-

(Possibly the culprit and apparently on AMD Cards there are no problems on any Linux Distro)

Hope this helps!

So nvidia users if you are eager to play this. There's a way:

Latest patch from 17th sept 2024 made the game unplayable on nvidia. Hangs when opening tab/map menu. AsyncComputeDisable=1 doesnt work anymore. to work around it we need to download the patch before that.

open steam with:
steam steam://open/console

paste it to the steam console tab:
download_depot 548570 548572 1826443442961353435

then copy and replace the depot downloaded files into the actual game directory

Create a steam_appid.txt file with 548570 into the game folder in order to not let the game update.

Change AsyncComputeDisable to 1 in
~/SteamLibrary/steamapps/compatdata/548570/pfx/drive_c/users/steamuser/Saved Games/id Software/Rage 2/settings.ini

edit: you also have to cap the fps to 120 either via mangohud or libstrangle. otherwise the map screen loads and hangs if FPS is too high.

Nvidia issue report here:
https://forums.developer.nvidia.com/t/rage-2-native-vulkan-windows-game-hangs-on-nv-linux-drivers-works-on-amd-radv-and-nv-windows-drivers/169083/10

Ok RAGE 2 is finally fixed on nvidia 580.105.08
no more hangs on tab menu

Hello. Rage 2 for me has stuttering if using mangohud or libstrangle to cap the frame rate.
It stops being a problem around 120 fps but 90fps shows issues.
Enabling vsync seems to smooth it out a little. Still suboptimal. Seems to elude mangohud why the stuttering is occuring. Seems to be from the input side.

Latest nvidia driver 580.105.08
de: kde plasma - wayland
proton versions seem to not change this.

Hello. Rage 2 for me has stuttering if using mangohud or libstrangle to cap the frame rate. It stops being a problem around 120 fps but 90fps shows issues. Enabling vsync seems to smooth it out a little. Still suboptimal. Seems to elude mangohud why the stuttering is occuring. Seems to be from the input side.

Does this happen with
fps_limit_method late or early?
in mangohud? maybe difference there. I just recently uninstalled the game to make some free space. no idea what method libstrangle uses though.

Hello. Rage 2 for me has stuttering if using mangohud or libstrangle to cap the frame rate. It stops being a problem around 120 fps but 90fps shows issues. Enabling vsync seems to smooth it out a little. Still suboptimal. Seems to elude mangohud why the stuttering is occuring. Seems to be from the input side.

Does this happen with fps_limit_method late or early? in mangohud? maybe difference there. I just recently uninstalled the game to make some free space. no idea what method libstrangle uses though.

I tried both. Same result.

So nvidia users if you are eager to play this. There's a way:

Thank you! The bug is still present and this worked for me in 2026.