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.

[Leopard1907]

I don't know how or why this happens but game is busted on audio department.

When game does positional audio changes ( one channel being louder than other or completely silent ) it doesn't go back to being stereo again as one would expect. It sticks like that.

More over, when that happens and one quits the game; that behaviour sticks through other apps that are not involving Proton usage. So ( as weird as it sounds ) the way Proton interacts with underlaying sound mechanisms causes them to stick with references Proton set for them. Unplugging and plugging the device that was affected fixes the problem.

So far only managed to get that behaviour on RDR 2. Configuration is set to Headphones in game.

Arch Linux, pipewire, fully up to date system, Proton Experimental.

Not a special sound chip is used either, just the one that is on motherboard, which is a midrange B650 board called B650M-DS3H.

[kisak-valve]

Hello @Leopard1907, that's a rather bizarre snafu. You should also mention it to the pipewire dev(s) as Proton shouldn't be capable of influencing other audio clients.

[kisak-valve]

Red Dead Redemption 2 on Framework 13 AMD 7840U

Issue transferred from #7887.
@Spaht posted on 2024-07-11T15:49:10:

Compatibility Report

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

System Information

• GPU: AMD Ryzen™ 7 7840U w/ Radeon™ 780M Graphics × 16
• Video driver version:
• Kernel version: Linux 6.9.7-200.fc40.x86_64
• Link to full system information report as Gist:
• Proton version:

I confirm:

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

steam-1174180.log

Log attached to this report

Symptoms

Once loaded, the game runs at 1-2 FPS and is unplayable. System is Fedora 40 running GNOME under Wayland

Reproduction

Red Dead Redemption 2 AppID 1174180

AMD Ryzen™ 7 7840U w/ Radeon™ 780M Graphics × 16
Driver= amdgpu

https://gist.github.com/Spaht/de82829d8ad87b86d75009a9d848b4f0#file-gistfile1-txt

https://gist.github.com/Spaht/416c40b1b8f0894bb0c6cba35864b2a3#file-gistfile1-txt

---

@Spaht commented on 2024-07-11T15:51:30:

I am trying to run Red Dead Redemption 2 on a Framework 13 laptop with an AMD7840 APU (integrated Radeon 780M) with 16 GB of RAM. The game is slow to launch and gets terrible FPS in the 1-2 per second range. My system is running Fedora 40 with GNOME and Wayland.

[ghost]

Replying to #3291 (comment)

I finally found the answer in a ProtonDB post. This system uses an iGPU. You have to edit the settings of the game to use it.

You need to edit: /home/USERNAME/.local/share/Steam/steamapps/compatdata/1174180/pfx/drive_c/users/steamuser/Documents/Rockstar Games/Red Dead Redemption 2/Settings/system.xml so that adapterIndex value = 0 instead of 1.

I made that edit and it is working fine as can be expected on this hardware. My issue can be closed. Thanks for all that you do.

[DekosAnjo]

Does anyone have flickering lights or other flickering textures with "Screen Space Ambient Occlusion" set to medium?

I can have it on all settings, but with medium there seems to be some Z fighting. I know this should probably goto Rockstar Support instead, but I just wanted to know if anyone else can replicate this. You can see it in the house with the party, the lights flicker and the windows go completely nuts! Same with the first camp windows and the broken mirror between the cabinets.

Same here! However, I've noticed that in any configuration, the lights flicker on both the stores and the bar. To be honest, I'm not sure why this happens because it seems like nobody else has experienced the same issue.

[kisak-valve]

[Red Dead Redemption 2] Frame spikes / stutter when using keybord

Issue transferred from #8116.
@geludwig posted on 2024-09-21T18:38:11:

Compatibility Report

• Name of the game with compatibility issues: Red_Dead_Redemption_2
• Steam AppID of the game: 1174180

System Information

• GPU: AMD Radeon RX 7900 XTX
• Video driver version: Mesa 24.0.3-1pop1171163555922.04~7a9f319
• Kernel version: 6.9.3-76060903-generic
• Link to full system information report as Gist: https://gist.github.com/geludwig/7bc5e67726a1957ef2a687dd218816d6
• Proton version: Experimental, 9.0-3, 8.0-5

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.

Symptoms

Frame spikes / stutter when using Keyboard since around 19/09/2024. No updates to system, only to game and Rockstar launcher (BattleEye update).
No issues when using gamepad.
Capping framerate to 60Hz mitigates this issue to an extend.
Game options: 3440x1440, 144Hz, Borderless Window, Ultra

Reproduction

Press or hold any key when ingame.

Issue might be connected to:
7510.164:0550:0600:fixme:keyboard:NtUserActivateKeyboardLayout flags 40000000 not supported
7510.164:0550:0600:fixme:keyboard:X11DRV_ActivateKeyboardLayout 0x4090409, 40000000: semi-stub!

steam-1174180.log
Gamepad:

Keyboard:

[xpander69]

Can confirm the input issue with keyboard+mouse
for me it happens when i hold at least 2 keys on keyboard and turn with mouse. when i hold just 1 key from keyboard like "W" and move the mouse then frametimes are fine. as soon as i touch more keys from keyboard it starts to cause issues.

Quick video about it:
https://drive.google.com/file/d/1oIou1FgiE4E2BW-qMRC4QRRvO1A3VVLn/view?usp=sharing

Distro: Arch Linux
DE: MATE desktop, X11
CPU: AMD Ryzen 5800X3D
GPU: Nvidia RTX 3080
Video driver version: 560.35.03
Kernel version: 6.11.0-1-cachyos
Proton version: Experimental

[ODeadlock]

I can also reproduce this same stuttering issue on keyboard+mouse.

Distro: Gentoo Linux
DE: KDE 6.2 Beta
CPU: AMD Ryzen 5950X
GPU: Nvidia RTX 4090
Video driver version: 560.35.03
Kernel version: 6.11.0-melatonin
Proton version: GE-Proton9-14

[geludwig]

Did some additional troubleshooting without any success.

• Reinstalled game
• Changed graphics driver to kisak-turtle
• Changed graphic settings (including refresh rate, fullscreen/window etc, settings ...)
• different keyboard (and layout)

What I noticed!
I mapped my game controller inputs to keyboard keys using AntiMicroX (for example left stick forward to "W"). And the same problem occurs as using the keyboard directly. So likely not a polling-rate related issue.

[ODeadlock]

@geludwig Your original report highlights
7510.164:0550:0600:fixme:keyboard:X11DRV_ActivateKeyboardLayout 0x4090409, 40000000: semi-stub!
Which makes me curious if forcing native wayland for wine might resolve this issue. I havent been able to test this thoroughly because when using alternative builds such as wine-tkg-git with native wayland forced on, I am unable to interact with any steam game whatsoever (despite the game running fine at the menu). However this seems to be an unrelated proton/steam issue and not a wine issue as playing non-steam games with wine wayland forced on works fine.

[ODeadlock]

Out of curiosity, I wrote a patch for wine and did a quick build of proton to prevent the large number of calls to NtUserActivateKeyboardLayout, and this has still not resolved the stuttering issue for me. However, I no longer see 7510.164:0550:0600:fixme:keyboard:X11DRV_ActivateKeyboardLayout 0x4090409, 40000000: semi-stub!
flooding my log.

Ive recorded the games behavior with both keyboard and controller alongside the proton log.

[xpander69]

7510.164:0550:0600:fixme:keyboard:X11DRV_ActivateKeyboardLayout 0x4090409, 40000000: semi-stub!

Yeah those messages are spammed with other games also in the proton logs. games that dont suffer from any frametime stutters.
so i think thats unrelated to the RDR2 issue

[geludwig]

Quick video of the issue.

Yes, I can freez the whole game when spamming my keyboard... And only RD2 has this issue, not seen this in every other game in my libary.

[gofman]

The severe fps drop when holding a key should be fixed in the just updated Proton Experimental (bleeding-edge branch, https://github.com/ValveSoftware/Proton/wiki/Proton-Versions ). It might happen some minor drop is still there (like 1-2 fps at ~110fps) but should be nothing like it was.

[ODeadlock]

Do you have a link for the commit that solved this issue? I have built a few different configurations of proton experimental bleeding edge and I havent seen any improvement.

[gofman]

Proton Experimental bleeding-edge build is available through Steam, see the link above for details. There is a tag in github public repo which corresponds to it, but it is probably interesting to try the official build first to exclude potential issues with custom builds.

[ODeadlock]

Per your previous response, it seems that wine @ de12886 does indeed solve this issue. Both my custom build of experimental bleeding edge as well as the official build no longer stutter with simultaneous key presses and mouse input.

[geludwig]

Tested it with a complete fresh install of Pop!OS 22.04 on my second disk. Nothing but Steam, MangoHud and RD2 (Proton Experimental). Same exact issue. Im giving up.

[Blisto91]

@geludwig have you tried giving Bleeding Edge a try? It's a beta for regular experimental

[geludwig]

@Blisto91 I knew I forgot something, thanks. Beta fixed it. Now I can use my non-existent free time again ; )

[nail1203]

Replying to #3291 (comment)

You'll be shocked but this error mostly occurs when your vram is full. I have 16 gb of vram and this game uses only 5-6 of it at start but it raises slowly and reaches 16 gigs about 2 hours. If you often fast travel, it raises quicker.

So the problem is, this game cannot remove of the vram it uses when it's not necessary. And only works on vulkan selected in the settings, otherwise game wont run at all on dx12.

[polluxau]

Replying to #3291 (comment)

You'll be shocked but this error mostly occurs when your vram is full. I have 16 gb of vram and this game uses only 5-6 of it at start but it raises slowly and reaches 16 gigs about 2 hours. If you often fast travel, it raises quicker.

So the problem is, this game cannot remove of the vram it uses when it's not necessary. And only works on vulkan selected in the settings, otherwise game wont run at all on dx12.

yes i noticed that also, my vram would be touching 10gb, does this happen on windows tho? if it doesnt then could it be a proton or driver problem on the linux side?

I would like to play longer then 2 hours lol and wouldnt this affect steamdeck owners also?

[GnomeBeans]

Looks like your issue is being discussed in other places
https://www.reddit.com/r/linux_gaming/comments/1gbwd28/rdr2_stacking_vram_like_a_slices_of_bread_other/
https://steamcommunity.com/app/1174180/discussions/0/7073555028225775075/

[nail1203]

Replying to #3291 (comment)

I was using dx12 api of the game on windows. There was no issue but also i didnt try the vulkan version while using windows

[polluxau]

Replying to #3291 (comment)

Yeah can't use dx12, has graphical problems and some Vulkan extension errors appear when launching

I reset the graphics settings, it hasn't crashed since and I was able to complete Arthur's story :)

[Buggem]

[2024-12-26 08:08:26.890] [DISPLAY] [ 1456] [gamelaunch] Launching game...
[2024-12-26 08:08:26.890] [DISPLAY] [ 1456] [gamelaunch]  Path: F:\SteamLibrary\steamapps\common\Red Dead Redemption 2\RDR2.exe
[2024-12-26 08:08:26.890] [DISPLAY] [ 1456] [gamelaunch]  Command Line: "F:\SteamLibrary\steamapps\common\Red Dead Redemption 2\RDR2.exe" -skipPatcherCheck -steamLocation "F:\SteamLibrary\steamapps\common\Red Dead Redemption 2" -vulkan -width 1920 -height 1080 @args.txt -enableCrashpad -useSteam -steamAppId=1174180 -scCommerceProvider=4 @commandline.txt -fromRGL -rglLanguage=en-US
[2024-12-26 08:08:26.890] [DISPLAY] [ 1456] [gamelaunch]  Working Directory: F:\SteamLibrary\steamapps\common\Red Dead Redemption 2
[2024-12-26 08:08:27.196] [DISPLAY] [ 1456] [gamelaunch] Game exited with code 0xc0000135 (3221225781)
[2024-12-26 08:08:27.203] [DISPLAY] [ 1456] [crashdetection] Game left no exit file.
[2024-12-26 08:08:27.203] [ ERROR ] [ 1456] [crashdetection] Exit code 0xc0000135 indicates a fatal game exit (reason: STATUS_DLL_NOT_FOUND)
[2024-12-26 08:08:27.203] [ ERROR ] [ 1456] [gamelaunch] Game did not create a window and exited with code 0xc0000135, which likely indicates a fatal game exit during startup
[2024-12-26 08:08:56.175] [DISPLAY] [Main ] [cloudsaveop] Cloud Save sync requested for app 'rdr2'
[2024-12-26 08:08:56.192] [DISPLAY] [Main ] [cloudsaveop] Starting cloud save enabled check for app 'rdr2'
[2024-12-26 08:08:56.192] [DISPLAY] [Main ] [cloudsaveop] Received cloud saves enabled state for app 'rdr2' = disabled
[2024-12-26 08:08:56.192] [DISPLAY] [Main ] [cloudsaveop] Finished syncing cloud saves for app 'rdr2'

[polluxau]

[2024-12-26 08:08:26.890] [DISPLAY] [ 1456] [gamelaunch] Launching game...
[2024-12-26 08:08:26.890] [DISPLAY] [ 1456] [gamelaunch]  Path: F:\SteamLibrary\steamapps\common\Red Dead Redemption 2\RDR2.exe
[2024-12-26 08:08:26.890] [DISPLAY] [ 1456] [gamelaunch]  Command Line: "F:\SteamLibrary\steamapps\common\Red Dead Redemption 2\RDR2.exe" -skipPatcherCheck -steamLocation "F:\SteamLibrary\steamapps\common\Red Dead Redemption 2" -vulkan -width 1920 -height 1080 @args.txt -enableCrashpad -useSteam -steamAppId=1174180 -scCommerceProvider=4 @commandline.txt -fromRGL -rglLanguage=en-US
[2024-12-26 08:08:26.890] [DISPLAY] [ 1456] [gamelaunch]  Working Directory: F:\SteamLibrary\steamapps\common\Red Dead Redemption 2
[2024-12-26 08:08:27.196] [DISPLAY] [ 1456] [gamelaunch] Game exited with code 0xc0000135 (3221225781)
[2024-12-26 08:08:27.203] [DISPLAY] [ 1456] [crashdetection] Game left no exit file.
[2024-12-26 08:08:27.203] [ ERROR ] [ 1456] [crashdetection] Exit code 0xc0000135 indicates a fatal game exit (reason: STATUS_DLL_NOT_FOUND)
[2024-12-26 08:08:27.203] [ ERROR ] [ 1456] [gamelaunch] Game did not create a window and exited with code 0xc0000135, which likely indicates a fatal game exit during startup
[2024-12-26 08:08:56.175] [DISPLAY] [Main ] [cloudsaveop] Cloud Save sync requested for app 'rdr2'
[2024-12-26 08:08:56.192] [DISPLAY] [Main ] [cloudsaveop] Starting cloud save enabled check for app 'rdr2'
[2024-12-26 08:08:56.192] [DISPLAY] [Main ] [cloudsaveop] Received cloud saves enabled state for app 'rdr2' = disabled
[2024-12-26 08:08:56.192] [DISPLAY] [Main ] [cloudsaveop] Finished syncing cloud saves for app 'rdr2'

Distro, hardware, drivers, kernel, what proton runner are using, have you cleared the wine prefix, is this game on a ext4 or btrfs partition?

[Buggem]

This game is on an Exfat partition. I cannot move it over to my main hard drive for space reasons.
Fedora 41
AMD Ryzen 9
Gigabyte RTX 4070 Ti
Proton Experimental
I'll try clearing the wineprefix. It wont help I think though