Red Dead Redemption 2 (1174180)

[NTMan]

Compatibility Report

• Name of the game with compatibility issues: Red Dead Redemption 2
• Steam AppID of the game: 1174180

System Information

• GPU: AMD Radeon VII
• Driver/LLVM version: Mesa 20.0/10.0.0
• Kernel version: 5.4
• Link to full system information report as Gist
• Proton version: 4.11-9

I confirm:

• that I haven't found an existing compatibility report for this game.
• that I have checked whether there are updates for my system available.

steam-1174180.log

Symptoms

Rockstar Game Launcher said that unable to launch the game and recommend verify game data, but the game data successfully validated by steam.

Reproduction

Just launch the game.

[McMarius11]

i have the exact same issue:
Proton 4.11-9 steam-1174180.log
Proton 4-20-1-GE does not work either
i hope someone could fix it for us <3

[echozio]

I've not been able to get past the infinite splash screen in the launcher (1st screenshot in OP). Tried 4.11.9, 4.21-1-GE and a version of 4.11.5 I built to get the launcher running for GTA V back when it came out. All with fresh compatdata directories.

[mrpippy]

This error is due to the launcher crashing before it's able to launch the game, it's not actually related to the files being corrupted. I experienced the same crash when using vanilla Wine (and -staging) to launch RDR2 from the launcher outside of Steam as well. It's a weird crash and I wasn't able to make much progress troubleshooting it, unfortunately I won't be able to work on it for the next few weeks.

[laichiaheng]

This error is due to the launcher crashing before it's able to launch the game, it's not actually related to the files being corrupted. I experienced the same crash when using vanilla Wine (and -staging) to launch RDR2 from the launcher outside of Steam as well. It's a weird crash and I wasn't able to make much progress troubleshooting it, unfortunately I won't be able to work on it for the next few weeks.

Any good way to bypass the launcher?

[KuJo-Ger]

Same with me. Starts up to the launcher and loads infinitely.

The strange thing is that RDR2 is not shown in my Social Club account (website). But my other games (GTA V and GTA IV) are. Somehow the communication between Steam and the SC doesn't seem to have worked.

BTW - GTA V with the R-Launcher via Steam Play still works for me with the newest Proton.

I have now requested a refund and will buy it from Google Stadia.

[jas0n098]

This error is due to the launcher crashing before it's able to launch the game, it's not actually related to the files being corrupted. I experienced the same crash when using vanilla Wine (and -staging) to launch RDR2 from the launcher outside of Steam as well. It's a weird crash and I wasn't able to make much progress troubleshooting it, unfortunately I won't be able to work on it for the next few weeks.

Any good way to bypass the launcher?

When I tried launching the RDR2 exe directly, nothing happend. It's normally supposed to say ERR_NO_LAUNCHER which it does on Windows but not on Wine. Can anyone else confirm this?

[KuJo-Ger]

I've got an idea. Unfortunately, my request for a refund has already been approved. Therefore I can't try it for myself anymore. But maybe there can be another try here?

I have a working GTA V with Rockstar Launcher and Proton running. I can always start the game with the latest Proton 4.11-9.

It would be interesting to see if you copied the prefix folder from GTA V

/steam/steamapps/compatdata/271590/"
(-> this is the Proton prefix-path for GTA V)

and made it a prefix folder for RDR2
/steam/steamapps/compatdata/1174180/
(-> this is the Proton prefix-path for RDR2)

Maybe RDR2 will start with the working R-Launcher of GTA V?

[KuJo-Ger]

Maybe it'll help someone. I got the 4 log-files of the launcher from my folder
/home/kai/MyDocuments/Rockstar Games/Launcher
and I've attached it here.

Looks like he didn't realize I had the game on the record:

[2019-12-06 12:13:35.286] [DISPLAY] [Main ] [titlemanager] - Title rdr2 : Not installed

launcher.01.log
launcher.02.log
launcher.03.log
launcher.log

[wofferl]

Maybe RDR2 will start with the working R-Launcher of GTA V?

That didn't work.

Maybe the problem is the cloud save. This is the log from a launch on windows. With linux the launcher stops right before the cloud save request.

[2019-12-05 21:21:09.113] [DISPLAY] [Admin] [external] Ready to attempt a launch.
[2019-12-05 21:21:09.113] [DISPLAY] [Admin] [external] Attempting Steam launch. User is 'Wofferl'
[2019-12-05 21:21:09.250] [DISPLAY] [10968] [gamelaunch] Title has no minimum RGL version.
[2019-12-05 21:21:09.250] [DISPLAY] [10968] [gamelaunch] Title has no minimum RGL version.
[2019-12-05 21:21:13.694] [DISPLAY] [Main ] [cloudsaveop] Cloud Save sync requested for title 'rdr2'
[2019-12-05 21:21:13.711] [DISPLAY] [Main ] [cloudsaveop] Starting cloud save enabled check for title 'rdr2'
[2019-12-05 21:21:17.039] [DISPLAY] [Main ] [cloudsaveop] Received cloud saves enabled state for title 'rdr2' = disabled
[2019-12-05 21:21:17.040] [DISPLAY] [Main ] [cloudsaveop] Finished syncing cloud saves for title 'rdr2'
[2019-12-05 21:21:17.089] [DISPLAY] [ 1180] [audio] Valid Audio Device: true
[2019-12-05 21:21:18.059] [DISPLAY] [10968] [gamelaunch] Launching game...
[2019-12-05 21:21:18.059] [DISPLAY] [10968] [gamelaunch]  Path: E:\SteamLibrary\steamapps\common\Red Dead Redemption 2\RDR2.exe
[2019-12-05 21:21:18.059] [DISPLAY] [10968] [gamelaunch]  Command Line: "E:\SteamLibrary\steamapps\common\Red Dead Redemption 2\RDR2.exe" -skipPatcherCheck @args.txt @commandline.txt -useSteam
[2019-12-05 21:21:18.059] [DISPLAY] [10968] [gamelaunch]  Working Directory: E:\SteamLibrary\steamapps\common\Red Dead Redemption 2
[2019-12-05 22:11:06.667] [DISPLAY] [10968] [gamelaunch] Game exited with code 0x0 (0)

[McMarius11]

i think the problem is not this :D / GTA 5 has the same and still works

[2019-12-06 18:46:07.481] [DISPLAY] [Main ] [minmode] Location: Z:\home\mcmarius11.local\share\Steam\steamapps\common\Red Dead Redemption 2
[2019-12-06 18:46:07.481] [DISPLAY] [Main ] [launcher] Opening log file.
[2019-12-06 18:46:07.498] [WARNING] [Main ] [title] No default branch for title rdr2
[2019-12-06 18:46:07.498] [DISPLAY] [Main ] [titlemanager] Installation status:
[2019-12-06 18:46:07.498] [DISPLAY] [Main ] [titlemanager] - Title rdr2 : Not installed

GTA 5 launcher.log working
RDR2 launcher.log not working

i hope @mrpippy can fix it when he's back :)

[ByCybernetik]

This error is due to the launcher crashing before it's able to launch the game, it's not actually related to the files being corrupted. I experienced the same crash when using vanilla Wine (and -staging) to launch RDR2 from the launcher outside of Steam as well. It's a weird crash and I wasn't able to make much progress troubleshooting it, unfortunately I won't be able to work on it for the next few weeks.

Any good way to bypass the launcher?

When I tried launching the RDR2 exe directly, nothing happend. It's normally supposed to say ERR_NO_LAUNCHER which it does on Windows but not on Wine. Can anyone else confirm this?

Same problem

[mintylinux]

I have an idea. Not sure if it would work, but could we possibly use the launcher from GTAV to load Red Dead Redemption 2? Just thinking if this is maybe a launcher version solution. We know the launcher for GTAV loads and runs the game, even though it's horrible.

[KuJo-Ger]

I have an idea. Not sure if it would work, but could we possibly use the launcher from GTAV to load Red Dead Redemption 2? Just thinking if this is maybe a launcher version solution. We know the launcher for GTAV loads and runs the game, even though it's horrible.

Ehm ... look some comments above ...

"... Maybe RDR2 will start with the working R-Launcher of GTA V?"
-> #3291 (comment)

"That didn't work."
-> #3291 (comment)

[shiznix]

That didn't work.

Maybe the problem is the cloud save. This is the log from a launch on windows. With linux the launcher stops right before the cloud save request.

[2019-12-05 21:21:09.113] [DISPLAY] [Admin] [external] Ready to attempt a launch.
[2019-12-05 21:21:09.113] [DISPLAY] [Admin] [external] Attempting Steam launch. User is 'Wofferl'
[2019-12-05 21:21:09.250] [DISPLAY] [10968] [gamelaunch] Title has no minimum RGL version.
[2019-12-05 21:21:09.250] [DISPLAY] [10968] [gamelaunch] Title has no minimum RGL version.
[2019-12-05 21:21:13.694] [DISPLAY] [Main ] [cloudsaveop] Cloud Save sync requested for title 'rdr2'
[2019-12-05 21:21:13.711] [DISPLAY] [Main ] [cloudsaveop] Starting cloud save enabled check for title 'rdr2'
[2019-12-05 21:21:17.039] [DISPLAY] [Main ] [cloudsaveop] Received cloud saves enabled state for title 'rdr2' = disabled
[2019-12-05 21:21:17.040] [DISPLAY] [Main ] [cloudsaveop] Finished syncing cloud saves for title 'rdr2'
[2019-12-05 21:21:17.089] [DISPLAY] [ 1180] [audio] Valid Audio Device: true
[2019-12-05 21:21:18.059] [DISPLAY] [10968] [gamelaunch] Launching game...
[2019-12-05 21:21:18.059] [DISPLAY] [10968] [gamelaunch]  Path: E:\SteamLibrary\steamapps\common\Red Dead Redemption 2\RDR2.exe
[2019-12-05 21:21:18.059] [DISPLAY] [10968] [gamelaunch]  Command Line: "E:\SteamLibrary\steamapps\common\Red Dead Redemption 2\RDR2.exe" -skipPatcherCheck @args.txt @commandline.txt -useSteam
[2019-12-05 21:21:18.059] [DISPLAY] [10968] [gamelaunch]  Working Directory: E:\SteamLibrary\steamapps\common\Red Dead Redemption 2
[2019-12-05 22:11:06.667] [DISPLAY] [10968] [gamelaunch] Game exited with code 0x0 (0)

In Linux have you tried disabling cloud saves prior to launching the game?

[KuJo-Ger]

Interesting watching.

Since I gave the game back I can't test it anymore. Maybe someone else here?

[shiznix]

Interesting watching.

Since I gave the game back I can't test it anymore. Maybe someone else here?

Posting debug logs after you returned the game had me thinking you'd maybe repurchased it again, oh well 😕

[ByCybernetik]

The reason why the game does not start lies in the file rdr2.exe

[ByCybernetik]

Doesn’t even show an error

[jas0n098]

The reason why the game does not start lies in the file rdr2.exe

Doesn’t even show an error

What should WINEDEBUG be set to in this case?

[ByCybernetik]

Even in the terminal didn't show anything

[ghost]

Maybe the problem can be discovered using the +relay in WINEDEBUG

[jas0n098]

log of RDR2 with +relay

[KuJo-Ger]

Interesting watching.
Since I gave the game back I can't test it anymore. Maybe someone else here?

Posting debug logs after you returned the game had me thinking you'd maybe repurchased it again, oh well confused

When refunding a game the files are not deleted. So I was able to attach the files that were created before refunding.

BTW - has someone tested it with diasbling the cloud-saves function?

[mintylinux]

american.txt
This is what my errorcodes file says in /Read Dead Redemption 2/x64/data/errorcodes/ I wonder if it's something we could fix with protontricks.

[mintylinux]

Wow, alot of people are saying the game crashes because their motherboard BIOS isn't up to date. https://www.reddit.com/r/reddeadredemption/comments/drzrdf/rdr2_launch_issues_megathread/

[wofferl]

BTW - has someone tested it with diasbling the cloud-saves function?

The launcher dies before you were asked if you want to enable cloud saves.
I tried with the My Documents/Rockstar Games/Launcher/Profiles/XXXXXXX/settings_account.dat
from my windows installation where I have cloud saves disabled and it did not work, but don't know if this info is stored there.

[KuJo-Ger]

The launcher dies before you were asked if you want to enable cloud saves.
I tried with the My Documents/Rockstar Games/Launcher/Profiles/XXXXXXX/settings_account.dat
from my windows installation where I have cloud saves disabled and it did not work, but don't know if this info aren't stored there.

Oh, that's true, I forgot. I meant disabling it in the general Steam options. But the logs of the Steam function islstored in the R*-Launcher logs.

[shiznix]

Wow, alot of people are saying the game crashes because their motherboard BIOS isn't up to date. https://www.reddit.com/r/reddeadredemption/comments/drzrdf/rdr2_launch_issues_megathread/

Just a theory, but maybe the launcher checks for CPU microcode exploits as an anti-cheat method.
Microcode exploits are patched in BIOS updates and so the checks pass.
It may also be why it fails in Linux, microcode exploit check might be using Windows APIs not implemented in Wine/Proton.

[mrpippy]

This error is due to the launcher crashing before it's able to launch the game, it's not actually related to the files being corrupted. I experienced the same crash when using vanilla Wine (and -staging) to launch RDR2 from the launcher outside of Steam as well. It's a weird crash and I wasn't able to make much progress troubleshooting it, unfortunately I won't be able to work on it for the next few weeks.

Any good way to bypass the launcher?

When I tried launching the RDR2 exe directly, nothing happend. It's normally supposed to say ERR_NO_LAUNCHER which it does on Windows but not on Wine. Can anyone else confirm this?

RDR2.exe has its own issue where it exits very early because it tries to detect a debugger with a crazy method (direct NT syscalls) that’s not supported by Wine. It thinks a debugger is attached, and then calls TerminateProcess() to exit.

It’s fairly easy to bypass by making TerminateProcess() a no-op, but even with that, RDR2.exe just launches the launcher (which crashes because of the main bug) and then exits. Makes it a moot point until the launcher bug is figured out.

[Quentin-ctrL]

I'm unable to play RDR2

I switch to the latest proton 8.0-3 running on Debian 12 / 6.1.0-11-amd64 / NVIDIA 525.125.06. I tested previous version of proton but no differences

The game loads and have the error 'ERR_GFX_INIT'
The only way to enter the menu is to add "%command% -adapter 1"
That way I can enter the parameters, I can switch between video adapters:

• Adapter 1 have only 2G of Vram
• Adapter 0 have 12Go of Vram

Using adapter 1 is unplayable. The settings are the lowest and the game crash
Using adapter 0 gives me 'ERR_GFX_INIT'

I tried several options listed on https://www.protondb.com/app/1174180 but none works

steam.txt

[Zeemlapje]

I'm having the same problem with the game not launching because the Rockstar launcher/Social Club is in a log-in loop/error and kills the process before reaching the intro/splash screen.

OS: EndeavourOS Linux
KERNEL: 6.5.3-zen1-1-zen
CPU: AMD Ryzen 9 5900X 12-Core
GPU: AMD Radeon (gfx1101, LLVM 16.0.6, DRM 3.54, 6.5.3-zen1-1-zen)
GPU DRIVER: 4.6 Mesa 23.1.7-arch1.1
RAM: 32 GB

I've tried multiple Proton version (8.0-3/Experimental/Glorious Eggroll)
I've tried verifying game files
I've tried launching a bunch of Rockstar launcher/Social Club .exe files to see if I can fix it from there but it'll ask for an install

I'll try a fresh install but this is not a practical solution (I'm on ADSL)

Maybe a launch option to remove any 3rd party launchers (Rockstar's in this case) + their saved credentials to allow for a fresh install & log in?

[dklementowski]

Replying to #3291 (comment)

Try to renew your prefix by removing directory in compatdata ~/.local/share/Steam/steamapps/compatdata/1174180 and launching the game again. Rockstar app should then reinstall.

[LumpyArbuckle]

Replying to #3291 (comment)

I more or less have the same setup with the same problem, did you ever find a solution?

[LumpyArbuckle]

I was told to post a log here, basically when starting the game it freezes on the first loading screen right before the main menu.

I have tried two different distros, two different DEs, and both Wayland and X.11 but nothing worked. The Proton version also appears to make no difference either. The only thing that did get the game to start was Steam Big Picture Mode however it would usually only start once and was quite buggy. The graphics settings didn't work right and once I closed the game there was a solid chance it wouldn't open again unless I deleted the compatdata folder.

OS - EndeavourOS
Kernel - 6.5.7-arch1-1
CPU - Ryzen 5 3600
GPU - RX 6600XT
Driver - 23.2.1-arch1.2
RAM - 16GB DDR4

steam-1174180.log

[kisak-valve]

Hello @LumpyArbuckle, skimming through your Proton log, apparently your issue is audio related. Thread 0548 hits an access violation (c0000005) and has a bad time. This thread was renamed "winealsa_midi_notify."

[LumpyArbuckle]

Hello @LumpyArbuckle, skimming through your Proton log, apparently your issue is audio related. Thread 0548 hits an access violation (c0000005) and has a bad time. This thread was renamed "winealsa_midi_notify."

Is there a solution to this problem? I do have occasional audio glitches since switching to AMD (maybe more than when I used Nvidia) so it makes sense that it's possibly audio-related, it could just be me imagining things though.

[AQDuck97]

The game freezes during the initial loading screen on Nvidia GPUs but works fine on AMD.
Both 535 driver and 545 driver tested

steam-1174180.log

[kisak-valve]

Red dead redemption 2 is currently running

Issue transferred from #7239.
@Gimuck posted on 2023-11-05T23:40:10:

After Rockstarr starts up in RDR2 the box comes up as above 'A GAME IS CURRENTLY RUNNING' 'Red dead redemption 2 is currently running. By choosing to exit Red Dead Redempetion 2 will be quit and any unsaved access will be lost. RDR2 then crashes if quit or not quit. I am running proton8.0-4 on Mint 21.2 Victoria - Kernel: 5.15.0-88-generic x86_64.
Graphics:
Device-1: NVIDIA TU116M [GeForce GTX 1660 Ti Mobile] vendor: ASUSTeK
driver: nvidia v: 470.223.02 bus-ID: 01:00.0
Device-2: AMD Renoir vendor: ASUSTeK driver: amdgpu v: kernel
bus-ID: 06:00.0
Device-3: IMC Networks USB2.0 HD UVC WebCam type: USB driver: uvcvideo
bus-ID: 3-4:3
Display: x11 server: X.Org v: 1.21.1.4 driver: X:
loaded: amdgpu,ati,nvidia unloaded: fbdev,modesetting,nouveau,vesa
gpu: amdgpu resolution: 1920x1080~144Hz
OpenGL: renderer: RENOIR (renoir LLVM 15.0.7 DRM 3.42 5.15.0-88-generic)
v: 4.6 Mesa 23.2.1 - kisak-mesa PPA direct render: Yes
Thanks,

[kisak-valve]

Hello @Gimuck, if the game is running your AMD APU, than your video driver is new enough, but if it's running on your NVIDIA GPU, the NVIDIA 470 series video driver provides Vulkan 1.2, but Proton 8.0 (and newer) requires the video driver to provide Vulkan 1.3.

Please update your NVIDIA video driver install to a newer driver series and retest.

[Gimuck]

Yes that worked thanks..

[AQDuck97]

Steam Overlay causes the game to freeze on the loading screen, killing the gameoverlayui process immediately unfreezes the game and gets you to the menu at the cost of no Steam overlay (Mangohud works fine).
Can personally confirm it happens on both AMD and Nvidia cards.

Thanks to Kuta GreyApe on ProtonDB for pointing this out.

[Leopard1907]

Just a heads up for AMD gpu users:

AMDVLK performs vastly better with this game compared to RADV. So if one has a choice,using it with this game is recommended.

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

[GalacticalEdge]

https://www.protondb.com/app/1174180?device=pc

Recent Proton reports have talked about mild artifacts that appear in the game on AMD GPUs (such as occasional flickering objects and blurry textures). I have experienced this behavior on both my PC (RX 6600 XT with Mesa 23.2.1) and Steam Deck. Can this be looked into?

[dantob]

I've run in to a gpu reset, with RADV 6600XT (-vulkan game launch option) 100% reproduceable with mesa 23.1.9 -> 23.3.1, the Emmet Granger side quest triggers it every time, when the TNT explosion happens (otherwise I've managed 50 hours without crashes).

How can I get a useful trace of this, it obviously takes down my graphical session, how can I setup a trace from a separate vt (is gfx reconstruct the right tool?)

[drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=3210036, emitted seq=3210038
[drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process RDR2.exe pid 26646 thread RDR2.exe:cs0 pid 26681
amdgpu 0000:03:00.0: amdgpu: GPU reset begin!

[kisak-valve]

Hello @dantob, please copy the contents of Steam Runtime Diagnostics from Steam (Steam -> Help -> Steam Runtime Diagnostics) and put it in a gist, then include a link to the gist in this issue report. Also, are you able to share a save near the crash for a video driver dev to ponder?

[dantob]

@kisak-valve as requested

Steps: You have to start the Emmet Granger side quest (white circle with EG on the map), grab the pitchfork, scoop the 4 pig manure piles into the wheelbarrow, a cutscene plays. you now have tnt in hand, place tnt on manure storage, another cutscene plays (GPU resets during tnt explosion) should be 3-5 mins game time.

Edit: launch options gamescope -W 2560 -H 1440 -r 60 -f -- %command% -vulkan

steam runtime info
rdr2 save.zip

[jeisoncp]

I having flicker issue when using the Nvidia driver and Wayland. Anyone knows someway to fix it?:

flickering.mp4

system.txt

[kakra]

I having flicker issue when using the Nvidia driver and Wayland. Anyone knows someway to fix it?:

This looks like the out-of-order presentation bug I was seeing in other games when using gamescope with NVIDIA. If using no vsync but force full composition pipeline in the driver (maybe an option in X11 only), I did no longer see it - without gamescope at least. I'm not sure if gamescope still would have this issue for me, since it is wayland-based, using wayland may be a problem, too, because it forces vsync by default. If you experience stutter with composition pipeline and vsync off, try using mangohud to limit the fps to your monitor refresh: it should result in smooth gameplay without tearing.

I'd wait for driver 555 (probably, if they keep their versioning) before trying wayland, it may bring a lot of fixes. It's currently in beta as driver 550, so it should become stable soonish.

[jeisoncp]

I already using Mangohud to limit FPS at 60 fps, what is in the video. Changing limit to 30 fps makes it worst. I tryed to use gamescope, but even this couldn't solve the problem.

[kakra]

I already using Mangohud to limit FPS at 60 fps, what is in the video

Try early limiter instead of late limiter (MANGOHUD_CONFIG="fps_limit=60+30+0,fps_limit_method=early" %command%), it should avoid stutter at the cost of higher input latency. 60+30+0 configures three limits: 60fps, 30fps and unlimited, switchable via hotkey. Disable v-sync inside the game, it works exceptionally bad with multi-monitor NVIDIA.

I reported a similar issue here: ValveSoftware/gamescope#495

[jeisoncp]

I tried to but, there wasn't any changes. The flickering remains.

[luca0N]

Just in case this helps someone: the Rockstar Launcher refuses to launch RDR2 if you're using firejail, despite the "game executable not found" error.

[deadrubberboy]

Been working great. Update to Rockstar Launcher in January/February 2024 killed it. Will not launch. Get errors like "steam not running" when I launch it via steam! Madness.

[deviantsemicolon]

can't run it on nixos. probably a launcher issue. disappointed because rdr2 was one of my favorite games on the xbox, but i've since switched to PC gaming