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:

• [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

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?" -> https://github.com/ValveSoftware/Proton/issues/3291#issuecomment-562786062

"That didn't work." -> https://github.com/ValveSoftware/Proton/issues/3291#issuecomment-562662578

[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.

[supersteeeeeeeve]

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/

The Game works fine under Windows, even on my old 2016 Asrock Motherboard. I'm really sure its about cloud saving. It doesnt matter if you enable oder disable it, because when you switch to linux and install it via. Proton it is handled like a fresh install and the launcher will ask again if you want to enable cloud savegames but it crashes beforehand.

[class101]

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.

Interesting analysis but

Making TerminateProcess a noop would be similar to commenting the terminateprocess call as below, and so on, the execution fall in an unexpected chunck of code without even executing runGame because the program is globally known to have a debugger attached

if (debuggerDetected) { //TerminateProcess(); } else { runGame(); }

I would have tested instead to trick the program so runGame() is executed instead (or with anti-debugger plugin capable to hide a debugger)

if (!debuggerDetected) { TerminateProcess(); } else { runGame(); }

[laichiaheng]

It seems like it won't be playable in anytime soon.

[AsciiWolf]

@laichiaheng I really hope it will. The game itself will probably run great (after the current bugs are fixed) since it has Vulkan renderer and having such game running on Linux with a good performance is a big thing, especially if multiplayer will work as well.

[laichiaheng]

@AsciiWolf It seems like all the Rock Star games are dead now, such as GTA5.

It's 20% off now!

[McMarius11]

@AsciiWolf It seems like all the Rock Star games are dead now, such as GTA5.

It's 20% off now!

Why for me GTA 5 runs without any problems (steam version)

[davidjmemmett]

Which version of Proton are you running McMarius11?

Cheers, David

On 14 Dec 2019, at 16:40, McMarius11 notifications@github.com wrote:

 @AsciiWolf It seems like all the Rock Star games are dead now, such as GTA5.

It's 20% off now!

Why for me GTA 5 runs without any problems (steam version)

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[alko89]

I'm unable to install the game through Steam. The install button is disabled for me. Anyone else with this issue on Linux?

[mintylinux]

You can install the game on Steam within Linux, but it just doesn't work.

[mintylinux]

What makes me pissed off about this...is the Stadia version (Linux Version), is obviously running well on the stadia platform, compared to all the issues they are having on the steam release. It makes you wonder if the Linux version is just a way better port, than native windows. Yet they get all this negative feedback about their game not running correctly, and they wont release the Linux desktop version.

[alko89]

@mintylinux I know its broken. I still want to try using Proton. I have only installed one game in Proton up until now and don't remember doing anything to enable the install button.

[kisak-valve]

Hello @Alko89, you should be able to go to the per-game properties in Steam and check Force the use of a specific Steam Play compatibility tool, then select a version of Proton from the list to test.

[alko89]

@kisak-valve thanks! I didn't notice that before, nor do I remember setting this for Stick of Truth. I'm guessing it installs the recommended version of Proton with the game (if it exists).

[davidjmemmett]

There's a new Proton-GE build out, can somebody who owns RDR2 please test it and see if you get any further? https://github.com/GloriousEggroll/proton-ge-custom/releases/tag/4.21-GE-2

[NTMan]

There's a new Proton-GE build out, can somebody who owns RDR2 please test it and see if you get any further? https://github.com/GloriousEggroll/proton-ge-custom/releases/tag/4.21-GE-2

same here

steam-1174180.zip

[mintylinux]

I just tried it with Proton-GE-2, and i get the same crash "Please verify game data"

[McMarius11]

here is my log file with the newest proton-4.11-11 steam-1174180.log

i think @mrpippy is our only hope

[supertin]

Could be cloud save issue... This is where the launcher.log just abruptly ends when using Proton (4.21-GE-2):

[2019-12-21 11:43:29.582] [DISPLAY] [Admin] [external] Ready to attempt a launch.
[2019-12-21 11:43:29.582] [DISPLAY] [Admin] [external] Attempting Steam launch. User is 'tin'
[2019-12-21 11:43:30.255] [DISPLAY] [  255] [gamelaunch] Title has no minimum RGL version.
[2019-12-21 11:43:30.255] [DISPLAY] [  255] [gamelaunch] Title has no minimum RGL version.

And this snippet is from my Windows 10 install "launcher.log" (it has a lot more after this):

[2019-12-20 20:01:12.233] [DISPLAY] [Admin] [external] Ready to attempt a launch.
[2019-12-20 20:01:12.233] [DISPLAY] [Admin] [external] Attempting Steam launch. User is 'tin'
[2019-12-20 20:01:12.256] [DISPLAY] [10804] [gamelaunch] Title has no minimum RGL version.
[2019-12-20 20:01:12.256] [DISPLAY] [10804] [gamelaunch] Title has no minimum RGL version.
[2019-12-20 20:01:18.311] [DISPLAY] [Main ] [cloudsaveop] Cloud Save sync requested for title 'rdr2'
[2019-12-20 20:01:18.328] [DISPLAY] [Main ] [cloudsaveop] Starting cloud save enabled check for title 'rdr2'

[betam4x]

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.

Nt* calls ARE being implemented by wine where documentation is available. That being said, the correct approach that Wine should be taking is to hide the fact that a debugger is attached.

Did anyone run the game with +relay enabled? Preferably after the last GTAV Proton patch dropped.

[kakra]

Nt* calls ARE being implemented by wine where documentation is available. That being said, the correct approach that Wine should be taking is to hide the fact that a debugger is attached.

Which function is that actually? Because according to wine source code, NtQuerySystemInformation already returns FALSE when being queried for an attached debugger.

Looking at the logs, it seems more likely that whatever the launcher tries to launch simply crashes, that's detected by the launcher and thus it tells to verify game files. In the end, it's likely that a crash is caused by damaged game files. But we know, that's most probably not the case here.

It's getting an exception error:

wine: Unhandled exception 0xc0000409 in thread 3c at address 0x18023bf57 (thread 003c), starting debugger...

But all I can see from this thread is:

714499.234:0033:003c:fixme:module:LdrLockLoaderLock flags 1 not supported
714499.393:0033:003c:fixme:module:LdrLockLoaderLock flags 1 not supported
714499.395:0033:003c:fixme:module:LdrLockLoaderLock flags 1 not supported
714499.395:0033:003c:fixme:module:LdrLockLoaderLock flags 1 not supported
714499.395:0033:003c:fixme:module:LdrLockLoaderLock flags 1 not supported
714499.397:0033:003c:fixme:module:LdrLockLoaderLock flags 1 not supported
714499.398:0033:003c:fixme:module:LdrLockLoaderLock flags 1 not supported
714499.398:0033:003c:fixme:module:LdrLockLoaderLock flags 1 not supported
714499.398:0033:003c:fixme:module:LdrLockLoaderLock flags 1 not supported
714499.399:0033:003c:fixme:module:LdrLockLoaderLock flags 1 not supported
714499.399:0033:003c:fixme:module:LdrLockLoaderLock flags 1 not supported
714499.399:0033:003c:fixme:heap:GetPhysicallyInstalledSystemMemory stub: 0x3d1f638
714499.400:0033:003c:fixme:module:LdrLockLoaderLock flags 1 not supported
714499.402:0033:003c:fixme:module:LdrLockLoaderLock flags 1 not supported
714499.402:0033:003c:fixme:module:LdrLockLoaderLock flags 1 not supported
714499.402:0033:003c:fixme:module:LdrLockLoaderLock flags 1 not supported
714499.403:0033:003c:trace:seh:NtRaiseException code=c0000005 flags=0 addr=0x18007e101 ip=18007e101 tid=003c
714499.403:0033:003c:trace:seh:NtRaiseException  info[0]=0000000000000001
714499.403:0033:003c:trace:seh:NtRaiseException  info[1]=000000001319c94d
714499.403:0033:003c:trace:seh:NtRaiseException  rax=0000000000000001 rbx=0000000000000000 rcx=0000000003d1f478 rdx=0000000003d1f480
714499.403:0033:003c:trace:seh:NtRaiseException  rsi=0000000003d1f8d8 rdi=0000000000000000 rbp=0000000003d1f750 rsp=0000000003d1f480
714499.403:0033:003c:trace:seh:NtRaiseException   r8=000000007bceb1c0  r9=0000000000000000 r10=0000000000000008 r11=0000000000000246
714499.403:0033:003c:trace:seh:NtRaiseException  r12=000000000067ff90 r13=000000000067bfa0 r14=000000000067ff90 r15=0000000001704040
714499.403:0033:003c:trace:seh:call_vectored_handlers calling handler at 0x69f63c10 code=c0000005 flags=0
714499.403:0033:003c:trace:seh:call_vectored_handlers handler at 0x69f63c10 returned 0
714499.403:0033:003c:trace:seh:call_vectored_handlers calling handler at 0x6a435200 code=c0000005 flags=0
714499.403:0033:003c:trace:seh:call_vectored_handlers handler at 0x6a435200 returned 0
714499.403:0033:003c:trace:seh:RtlVirtualUnwind type 1 rip 18007e101 rsp 3d1f480
714499.403:0033:003c:trace:seh:dump_unwind_info **** func 7e022-7fca8
714499.403:0033:003c:trace:seh:dump_unwind_info unwind info at 0x1802473f8 flags 4 prolog 0x0 bytes function 0x18007e022-0x18007fca8
714499.403:0033:003c:trace:seh:dump_unwind_info     0x0: movq %r14,0x100(%rsp)
714499.403:0033:003c:trace:seh:dump_unwind_info     0x0: movq %r13,0x108(%rsp)
714499.403:0033:003c:trace:seh:dump_unwind_info     0x0: movq %r12,0x110(%rsp)
714499.403:0033:003c:trace:seh:dump_unwind_info     0x0: movq %rdi,0x118(%rsp)
714499.403:0033:003c:trace:seh:dump_unwind_info     0x0: movq %rsi,0x120(%rsp)
714499.403:0033:003c:trace:seh:dump_unwind_info     0x0: movq %rbp,0x128(%rsp)
714499.403:0033:003c:trace:seh:dump_unwind_info     0x0: movq %rbx,0x150(%rsp)
714499.403:0033:003c:trace:seh:dump_unwind_info     chained to function 0x18007dd40-0x18007dd5e
714499.403:0033:003c:trace:seh:dump_unwind_info unwind info at 0x180247460 flags 3 prolog 0x1e bytes function 0x18007dd40-0x18007dd5e
714499.403:0033:003c:trace:seh:dump_unwind_info     0xc: subq $0x130,%rsp
714499.403:0033:003c:trace:seh:dump_unwind_info     0x5: pushq %r15
714499.403:0033:003c:trace:seh:dump_unwind_info     handler 0x18023bf44 data at 0x180247470
714499.403:0033:003c:trace:seh:call_handler calling handler 0x18023bf44 (rec=0x3d1f340, frame=0x3d1f480 context=0x3d1e810, dispatch=0x3d1e5b0)
714499.403:0033:003c:trace:seh:RtlVirtualUnwind type 0 rip 18023c385 rsp 3d1e460
714499.403:0033:003c:trace:seh:dump_unwind_info **** func 23c368-23c482
714499.403:0033:003c:trace:seh:dump_unwind_info unwind info at 0x18023d958 flags 0 prolog 0x10 bytes function 0x18023c368-0x18023c482
714499.403:0033:003c:trace:seh:dump_unwind_info     0x10: subq $0x80,%rsp
714499.403:0033:003c:trace:seh:dump_unwind_info     0x6: pushq %rbp
714499.404:0033:003c:trace:seh:start_debugger Starting debugger "winedbg --auto 51 964"

The exception indicates a stack overflow. Maybe something is just recursing too deep because of a missing feature in wine? The repeating fixme lines may indicate that.

I'll attach the logs later, my system needs a reboot first.

Update: Attaching logs: https://gist.github.com/kakra/8a374942a24e4aeecf68243e7f994f38

[betam4x]

Nt* calls ARE being implemented by wine where documentation is available. That being said, the correct approach that Wine should be taking is to hide the fact that a debugger is attached.

Which function is that actually? Because according to wine source code, NtQuerySystemInformation already returns FALSE when being queried for an attached debugger.

Looking at the logs, it seems more likely that whatever the launcher tries to launch simply crashes, that's detected by the launcher and thus it tells to verify game files. In the end, it's likely that a crash is caused by damaged game files. But we know, that's most probably not the case here.

It's getting an exception error:

wine: Unhandled exception 0xc0000409 in thread 3c at address 0x18023bf57 (thread 003c), starting debugger...

But all I can see from this thread is:

The exception indicates a stack overflow. Maybe something is just recursing too deep because of a missing feature in wine? The repeating `fixme` lines may indicate that. I'll attach the logs later, my system needs a reboot first.

Sorry that I'm a bit delayed on the reply, between holidays and other stuff I haven't had much time to circle back around. Note that I do not speak for Valve, or for the Wine team, or DXVK or anyone else, My experience stems solely on working on Wine (passively, meaning I was never a core Wine developer) over a decade ago, being an experienced Windows developer, and also having somewhat dated knowledge of a large portion of Windows 7 (and older) internals. That being said, lets stop to address a few things:

• a large majority of Nt syscalls are implemented in ntdll.dl, for example, https://source.winehq.org/git/wine.git/blob/HEAD:/dlls/ntdll/nt.c itself has over 3000 lines of code. Yes some aren't implemented and many more may be incomplete or incorrect. However, progress is being made. I won't venture a guess as to if something is breaking the game here or not because I do not own and cannot debug it. While Rockstar might be using Nt calls, that would be foolish (though after looking into GTA V issues nothing surprises me at this point). They would effectively tie the game to a single version or two of Windows. Nt* calls can change from release to release. Microsoft is pretty adamant about this, for example, see the warning on this page: https://docs.microsoft.com/en-us/windows/win32/api/winternl/nf-winternl-ntquerysysteminformation. This leads me to my other point...

• In order to get a proper trace you need to disable winedbg (winedbg=d) and use +relay along with a few other flags for timestamps, threads, etc. It looks like you are already doing most of that that above, but I noticed winedbg is enabled, that's why I brought it up. We've already seen what GTA V does if it's put in a debugger. RDR2 uses an older, heavily modified fork of the RAGE engine from what I've been able to observe, so I have no reason to think that the game will fair any better than GTAV. Especially as Rockstar is now apparently adamant on stomping out debuggers (I won't even get into the reasons for this, as I'd be borderline trolling).

• I'm sure someone somewhere has taken or is taking a look at this. However nonetheless it's important to have links to good logging. Using GitHub Gists allows you to paste a log in it's entirety, you can then just link to it here. Also of importance is the DXVK logs, if any.

• RDR2 apparently does not completely install for many users under Linux. Your best bet is to attempt to install, then copy a full install over from Windows. If you have a way of capturing any registry or other changes during the install process under Windows that would be helpful as well. Just be aware of Wine's Clean Room Guidelines. I bring this up because I've seen games and applications crash because they don't handle non-existent registry settings properly. There used to be uninstaller packages that tracked all this stuff, but I'm not sure if they exist any longer.

• I can't really be of further help here, as I don't own the game, and I'm not working at the moment so putting down $50-$60 for a game would be a bit foolish (especially since it doesn't work on Linux! :wink:). That being said, hopefully it gets resolved soon. It is a game that I definitely want to eventually pick up once the price drops and I'm in a slightly better situation.

Good luck! A mild disclaimer on spelling and grammar here. I may or may not have had one or many beers prior to writing this and may or may not have written this after being awake for 36 hours straight. Time for bed. :wink: