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

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.

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.

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?

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.

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?

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?

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

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)

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 :)

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

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.

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

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?

Interesting watching.

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

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 😕

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

Doesn’t even show an error

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?

Even in the terminal didn't show anything

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

log of RDR2 with +relay

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?

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.

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/

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.

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.

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.

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.

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.

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(); }

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

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

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

It's 20% off now!

@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)

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.

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

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

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.

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

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.

@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).

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

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

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

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

i think @mrpippy is our only hope

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'

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.

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

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:

@betam4x Thanks for the update - it reminded me of something... ;-) I managed to miss that I wanted to upload the logs after reboot. The logs are huge, I've managed to squeeze them into a gist (post above updated): https://gist.github.com/kakra/8a374942a24e4aeecf68243e7f994f38

I happily update the logs if you give instruction how to create them.

As far as I know, you should be able to switch the graphics engine to Vulkan after successfully launching into the game: https://www.youtube.com/watch?v=xnatU6Uhz48

So I'd expect the graphics engine itself running pretty well after we fixed the startup issues (and maybe editing some config file).

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?

@laichiaheng There's this handy command line snippet to bypass launchers in Steam, it simply replaces the command that Steam wants to launch with a command you want to launch. Just put it in your game launch options:

bash -c 'exec "${@/PlayRDR2.exe/RDR2.exe}"' -- %command%

It works the same with other games, simply adjust the file names. I.e., the Borderlands GOTY launcher won't properly run with Proton, I'm using such a launch option to skip it.

For RDR2, tho, it doesn't work. The game will just silently exit after a few seconds of Proton thinking it's running.

Same result as the OP, "please verify game data". GTA V runs flawlessly on this system.

GTAV and RDR2 do not work with the same error "please verify game data"

GTAV and RDR2 do not work with the same error "please verify game data"

GTAV has always worked flawlessly for me. Make sure your distro is up to date.

no problem with GTA 5 for me on archlinux, just RDR 2

Has anyone been able to get past the "please verify your game data" error?

Has anyone been able to get past the "please verify your game data" error?

Do not believe so, bypassing that seems to be the only obstacle to get this game to work currently.

Shame because the game is indeed Vulkan, it would probably run great if it wasn't for that

New Proton-GE release. Anybody available to do a quick test?

Cheers,
David

On 19 Jan 2020, at 14:45, Evernow notifications@github.com wrote:


Has anyone been able to get past the "please verify your game data" error?

Do not believe so, bypassing that seems to be the only obstacle to get this game to work currently.

Shame because the game is indeed Vulkan, it would probably run great if it wasn't for that

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

@davidjmemmett

New Proton-GE release. Anybody available to do a quick test? Cheers, David

Unfortunately no luck, tried re validating the files as well, nothing.

Further discussion about direct NT syscall can be seen here: https://bugs.winehq.org/show_bug.cgi?id=48291

Further discussion about direct NT syscall can be seen here: https://bugs.winehq.org/show_bug.cgi?id=48291

From the looks of things.. this game isn't gonna work for a long long time... shit...

I have been writing to Rockstar support and feedback to try and get some help for Valve team for porting the game with obviously not much luck.
Maybe if more people would write to their feedback suggestion we could get some help from their team.

I have been writing to Rockstar support and feedback to try and get some help for Valve team for porting the game with obviously not much luck.
Maybe if more people would write to their feedback suggestion we could get some help from their team.

And don't forget to put it on your wishlist:
https://steamcommunity.com/games/221410/announcements/detail/1475356649450732547

work via Proton 5.0-1 ?

work via Proton 5.0-1 ?

Nope. Still gives the same "unable to launch game" error as the OP has a screenshot of.

I have been working on it, there’s a lot of issues to figure out but I’ve been making steady progress. I fixed the launcher crash (working on an upstream patch for that), and the direct syscalls are pretty easy to work around.
Getting audio and video working correctly is the challenge right now, hopefully I’ll have something to show you all soon.

That is great news, thanks a lot for your work!

On Sat, Feb 8, 2020 at 9:01 AM Brendan Shanks notifications@github.com wrote:
>

I have been working on it, there’s a lot of issues to figure out but I’ve been making steady progress. I fixed the launcher crash (working on an upstream patch for that), and the direct syscalls are pretty easy to work around.
Getting audio and video working correctly is the challenge right now, hopefully I’ll have something to show you all soon.

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

I have been working on it, there’s a lot of issues to figure out but I’ve been making steady progress. I fixed the launcher crash (working on an upstream patch for that), and the direct syscalls are pretty easy to work around.
Getting audio and video working correctly is the challenge right now, hopefully I’ll have something to show you all soon.

great! we 💓 u

I have been working on it, there’s a lot of issues to figure out but I’ve been making steady progress. I fixed the launcher crash (working on an upstream patch for that), and the direct syscalls are pretty easy to work around.
Getting audio and video working correctly is the challenge right now, hopefully I’ll have something to show you all soon.

wow, man !!!! thats awesome

sorry for ping.. but any update?

still waiting

still waiting

Must be valve time 😀

I have been working on it, there’s a lot of issues to figure out but I’ve been making steady progress. I fixed the launcher crash (working on an upstream patch for that), and the direct syscalls are pretty easy to work around.
Getting audio and video working correctly is the challenge right now, hopefully I’ll have something to show you all soon.

so we can assume you were trolling by now?

I have been working on it, there’s a lot of issues to figure out but I’ve been making steady progress. I fixed the launcher crash (working on an upstream patch for that), and the direct syscalls are pretty easy to work around.
Getting audio and video working correctly is the challenge right now, hopefully I’ll have something to show you all soon.

so we can assume you were trolling by now?

This is the patch (or one of the patches) for RDR2 that he sent to the WineHQ mailing list: https://source.winehq.org/patches/data/180360

Hello, thanks for your patch, i just tested it, and currently i'm failing to launch the Rockstar launcher on wine staging 5.3 (arch based). I have a stack overflow. Here is the beginning output (which is repeated and overflow it seems)

info:  Game: Launcher.exe
info:  DXVK: v1.4
warn:  OpenVR: Failed to locate module
info:  Enabled instance extensions:
info:    VK_KHR_get_physical_device_properties2
info:    VK_KHR_surface
info:    VK_KHR_win32_surface
info:  Game: Launcher.exe
info:  DXVK: v1.4
warn:  OpenVR: Failed to locate module
info:  Enabled instance extensions:
info:    VK_KHR_get_physical_device_properties2
info:    VK_KHR_surface
info:    VK_KHR_win32_surface
info:  Game: Launcher.exe
info:  DXVK: v1.4
warn:  OpenVR: Failed to locate module
info:  Enabled instance extensions:
info:    VK_KHR_get_physical_device_properties2
info:    VK_KHR_surface
info:    VK_KHR_win32_surface
info:  Game: Launcher.exe
info:  DXVK: v1.4
warn:  OpenVR: Failed to locate module
info:  Enabled instance extensions:
info:    VK_KHR_get_physical_device_properties2
info:    VK_KHR_surface
info:    VK_KHR_win32_surface
info:  Game: Launcher.exe
info:  DXVK: v1.4
warn:  OpenVR: Failed to locate module
info:  Enabled instance extensions:
info:    VK_KHR_get_physical_device_properties2
info:    VK_KHR_surface
info:    VK_KHR_win32_surface
info:  Game: Launcher.exe
info:  DXVK: v1.4
warn:  OpenVR: Failed to locate module
info:  Enabled instance extensions:
info:    VK_KHR_get_physical_device_properties2
info:    VK_KHR_surface
info:    VK_KHR_win32_surface
002c:err:seh:setup_exception stack overflow 1680 bytes in thread 002c eip 000000007bc696a5 esp 0000000000130f80 stack 0x130000-0x131000-0x230000

using regular wine-staging package without your patch permits to launch the launcher (it blocks on the update but it's launched)

Is there anything a user with some decent Linux and programming knowledge (as well as the game in their Steam library) can do to help?

Any news?

@mrpippy has a branch for RDR2 related commits located here https://github.com/mrpippy/wine/tree/rdr2
you can also keep up to date with submitted wine patches here, also useful if you're interested in seeing progress on mfplat stuff

Sorry guys, still working on it but making good progress. I was able to get a hack working with seccomp-bpf to trap and emulate the direct syscalls, this fixed audio. Work is ongoing for the various Vulkan extensions and Windows display functions that are needed.

any update in this topic?

I'm playing this game, way too much, and would love to not have to run Windows for it. Can I help? What needs doing?

Tested running it under:

• Proton 4.11-13
• Proton 5.0.6
• Steam native Linux

None of the options worked. I even tried bypassing Rockstar Launcher through these launch options (but this launches RDR2.exe and silently crashes):

bash -c 'exec "${@/PlayRDR2.exe/RDR2.exe}"' -- %command%

GTA IV and GTA V both work fine, just not RDR2.

Tested running it under:

* Proton 4.11-13

* Proton 5.0.6

* Steam native Linux

None of the options worked. I even tried bypassing Rockstar Launcher through these launch options (but this launches RDR2.exe and silently crashes):

bash -c 'exec "${@/PlayRDR2.exe/RDR2.exe}"' -- %command%

GTA IV and GTA V both work fine, just not RDR2.

You should be testing with upstream wine if you wanted to test if the game works or not as that is the place where those patches land.

@mrpippy Any progress update?

Has any one who owns this game tried PROTON_USE_SECCOMP=1 yet?

Has any one who owns this game tried PROTON_USE_SECCOMP=1 yet?

Yes, does not work yet. I tried Proton GE 5.6 because it should also have all the wine upstream commits up to and including wine 5.6. While the Rockstar launcher looks fine now visually, the game still silently crashes or exits. At least as of 5.6 the seccomp patches are either yet incomplete or only part of the solution.

Has any one who owns this game tried PROTON_USE_SECCOMP=1 yet?

Yes, does not work yet. I tried Proton GE 5.6 because it should also have all the wine upstream commits up to and including wine 5.6. While the Rockstar launcher looks fine now visually, the game still silently crashes or exits. At least as of 5.6 the seccomp patches are either yet incomplete or only part of the solution.

Hey, you had anymore luck? This is one of those games keeping me on Windows sadly.

It seems to be hopeless. Has anyone tried the latest Proton-5.8-GE2-MF build?

The game does not work for me as well. However, I am not experiencing crashes or anything, it's just stuck on the Rockstar Launcher forever like this:

Has anyone else experienced this? I will try to debug anyway, and will let you know what the results are. Also, let me know if more system specs or logs are needed from my side.

Specs:
Operating system: Pop!_OS 20.04
Proton Version: 5.0-7
Graphics Card: Nvidia 1050 Ti 4GB

@nushkovg you're not alone :smile: I noticed the same thing around a week ago.

Pretty new to Proton (I've been using Linux for a few weeks now, though), but maybe I can help by sending specs, logs, or things like that.

Thank you for your hard work, everyone!

I had been having some luck with Brendan's patches from https://github.com/mrpippy/wine/tree/rdr2 although I would often get stuck at an "Activation Failed" error after displaying the splash screen. However I was able to get into the game a few times. Unscientifically, probably around once per five attempts.

Unfortunately, it seems that a recent update to either the game or the launcher is preventing me from even getting that far. Now when I click "Play" the game exits before displaying anything at all.

With WINEDEBUG=+relay, I notice that the following snippet is printed 8 times, about once per second, before KERNEL32.TerminateProcess gets called. I'm not sure if that might be significant? Maybe like it's waiting for something, times out, and decides to give up?

00b0:Ret ntdll.NtWaitForMultipleObjects() retval=00000000 ret=7b082743 00b0:Ret winex11.drv.MsgWaitForMultipleObjectsEx() retval=00000000 ret=7f090b495edf 00b0:Call window proc 0x7f090ac59da0 (hwnd=0x1002c,msg=WM_TIMER,wp=00000001,lp=00000000) 00b0:Ret window proc 0x7f090ac59da0 (hwnd=0x1002c,msg=WM_TIMER,wp=00000001,lp=00000000) retval=00000000 00b0:Call winex11.drv.MsgWaitForMultipleObjectsEx(00000001,00abf7f8,ffffffff,000004ff,00000000) ret=7f090b495edf

Let me know if there's any other info that might be helpful, I'm somewhat new to wine debugging.

Trying with Proton-5.8-GE-2-MF and looking at the kernel log, it appears that something is trying (and failing) to access my optical disc drive (/dev/sr0) repeatedly (see attached).

Eventually the game terminates after throwing the error "Invalid address (0x000000007b44dfb1 EntryPoint+0x37fe1) for breakpoint 0, disabling it".

rdr2_dmesg.log

Sorry for the delay, in the past few days I've made really good progress and figured out the last two issues (the recent launcher crash and the activation error). The task now is to clean up the many hacks I've got and hopefully have something ready for testing in the next few weeks

Sorry for the delay, in the past few days I've made really good progress and figured out the last two issues (the recent launcher crash and the activation error). The task now is to clean up the many hacks I've got and hopefully have something ready for testing in the next few weeks

Good work Brendan, Congratulations!

Sorry for the delay, in the past few days I've made really good progress and figured out the last two issues (the recent launcher crash and the activation error). The task now is to clean up the many hacks I've got and hopefully have something ready for testing in the next few weeks

Thanks, I wish you good luck on that. It would be great to play rdr2 on Linux. Could that script/hack be used for other rockstar games?

Sorry for the delay, in the past few days I've made really good progress and figured out the last two issues (the recent launcher crash and the activation error). The task now is to clean up the many hacks I've got and hopefully have something ready for testing in the next few weeks

Does that mean that you have the game running ? If so then these are great news!

Does anyone know what makes rdr2 different from gta and other rockstar games in terms of running it in Linux. People get gta working fine, just not rdr2. That was always strange to me.

I guess they employ much better protection. Also I don't know anybody who
successfully
run GTA V after launcher update, the best result I had was with saves
disabled from start, but that
currently won't run either. I managed to downgrade the game back to
pre-launcher state and that fixed GTAV.
But RDR2 has all the modern protection nastiness in there so I guess it
will be quite nontrivial to run
it if that ever happens. My PC is quite old though, I7 2600K + GTX1060.

On Sat, May 16, 2020 at 7:51 PM AmericanGamer13 notifications@github.com
wrote:

Does anyone know what makes rdr2 different from gta and other rockstar
games in terms of running it in Linux. People get gta working fine, just
not rdr2. That was always strange to me.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/3291#issuecomment-629674853,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAABPUZFATVEAJWGT3MZWWTRR3ACNANCNFSM4JV54AXQ
.

Sorry for the delay, in the past few days I've made really good progress and figured out the last two issues (the recent launcher crash and the activation error). The task now is to clean up the many hacks I've got and hopefully have something ready for testing in the next few weeks

I want to make my only post ever on Github to say thank you so much for your persistence/dedication in getting this to work. Bless you.

I want to make my only post ever on Github to say thank you so much for your persistence/dedication in getting this to work. Bless you.

I also made an account for this thread. I just bought the game and will start testing soon.

@mrpippy Thanks for your hard work on this project. Can't wait to test it out when you're ready!

I can’t wait to test that script/hack out I literally got a github account just for this thread!

@mrpippy happy to test on Arch/Manjaro as well. Do you need any second pair of eyes to clean-up/merge? :) Virtual session with eager users + beers, in somewhat a hackathon! Much more fun and we may fix it within X hours alltogether?

Thinking out loud.

I bought RDR 2 on steam just after I finished Jedi (which runs very well under Linux) and I am disappointed that I cannot play it ...

@mrpippy Thanks for your hard work on this project. Can't wait to test it out when you're ready!

Just tested the recent Proton 5.0-8, game doesn't complain about corrupted game files, but doesn't start :)
Launcher is fine

Just tested the recent Proton 5.0-8, game doesn't complain about corrupted game files, but doesn't start :)
Launcher is fine

Wait if the launcher is fine then what is stopping the game from launching? I don’t know much about coding or proton so please excuse my bad knowledge of it.

@AmericanGamer13 If I understood correctly, the game uses low-level syscalls into the NTOS kernel (the Windows kernel), and this doesn't work for the Linux kernel. That's probably part of the copy protection or some anti-cheat system. Work is currently done to trap those syscalls and redirect them to the NTOS kernel emulation/implementation of Wine instead of letting them pass to the Linux kernel (where they really don't belong).

Did anyone test the game with Brendan's wine branch?

I'm going for it:
https://github.com/davidjmemmett/Proton/tree/proton_5.0-next_with_mrpippy-wine

It's building now, I'll let you know how it goes.

Cheers,
David JM Emmett

On Sun, 7 Jun 2020 at 04:29, Esdras Tarsis notifications@github.com wrote:

Did anyone test the game with Brendan's wine branch
https://github.com/mrpippy/wine/tree/rdr2-2?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/3291#issuecomment-640151446,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABUBTNYT5E45DYVWCKEH3DRVMCSJANCNFSM4JV54AXQ
.

You got further than me, the SECCOMP changes wouldn't compile, so I gave up.

Cheers,

David JM Emmett

On Sun, 7 Jun 2020 at 19:37, topsyandpip56 notifications@github.com wrote:

Using mrpippy's rdr2-2 branch on Fedora 32 + amdgpu, the game crashes
shortly into the initial shader load. I don't know if the backtrace offers
anything useful. It might be due to not compiling 32-bit support into the
wine build?

wine: Unhandled page fault on read access to 0000000000000128 at address 00007FA34C798872 (thread 0408), starting debugger...
Unhandled exception: page fault on read access to 0x00000128 in 64-bit code (0x00007fa34c798872).
Register dump:
rip:00007fa34c798872 rsp:00000000341ebb20 rbp:00007f9c30012850 eflags:00010202 ( R- -- I - - - )
rax:00000000341ebbc0 rbx:0000000000000000 rcx:0000000000000002 rdx:00007fa34c863ba0
rsi:0000000000000008 rdi:0000000000000000 r8:00007f9bd37626e0 r9:00007f9c30012850 r10:00000000341eab84
r11:0000000000000000 r12:0000000000000000 r13:0000000000000000 r14:00000000341ebbc0 r15:0000000000000000
Stack dump:
0x00000000341ebb20: 00007f9bd3a4b0d0 0100000000000000
0x00000000341ebb30: 00000000341ebb2f 0000000000000002
0x00000000341ebb40: 0000000000000000 0000000000000000
0x00000000341ebb50: 00007f9c30012850 0000000000000000
0x00000000341ebb60: 00007f9c30012850 0000000000000000
0x00000000341ebb70: 0000000000000000 00000000341ebbc0
0x00000000341ebb80: 0000000000000000 00007fa34c64bf4f
0x00000000341ebb90: 0000000000000000 00007f9bd6c97490
0x00000000341ebba0: 0000000000000000 0000000000000000
0x00000000341ebbb0: 0000000000000000 0000000000000000
0x00000000341ebbc0: 0000010100000000 0101010101010000
0x00000000341ebbd0: 0101010101000001 0101000000010101
Backtrace:
=>0 0x00007fa34c798872 (0x00007f9c30012850)
0x00007fa34c798872: movq 0x0000000000000128(%rdi),%rbx
Modules:
Module Address Debug info Name (55 modules)
PE 220000- 24d000 Deferred amd_ags_x64
PE 250000- 2cb000 Deferred bink2w64
PE 960000- 96e000 Deferred api-ms-win-core-localization-l1-2-1
PE 33fd0000- 33fde000 Deferred api-ms-win-core-sysinfo-l1-2-1
PE 61900000- 6199d000 Deferred sechost
PE 62140000- 621cd000 Deferred uxtheme
PE 62540000- 625e4000 Deferred wintrust
PE 62600000- 626d8000 Deferred usp10
PE 637c0000- 63931000 Deferred winmm
PE 64940000- 64986000 Deferred shcore
PE 64b80000- 64bab000 Deferred hid
PE 64d40000- 64d59000 Deferred vulkan-1
PE 65000000- 65597000 Deferred ole32
PE 65680000- 656af000 Deferred rtworkq
PE 65780000- 6579c000 Deferred version
PE 66440000- 664a2000 Deferred msacm32
PE 67500000- 67527000 Deferred xinput9_1_0
PE 67740000- 6786c000 Deferred wbemprox
PE 68140000- 68265000 Deferred msctf
PE 68a40000- 68b67000 Deferred shlwapi
PE 69c80000- 69cf8000 Deferred propsys
PE 6a100000- 6a502000 Deferred oleaut32
PE 6a700000- 6a8b3000 Deferred setupapi
PE 6aa00000- 6ab83000 Deferred mf
PE 6b880000- 6b88d000 Deferred api-ms-win-core-fibers-l1-1-1
PE 6bec0000- 6bf09000 Deferred imm32
PE 6cd80000- 6ce1d000 Deferred mfreadwrite
PE 6d3c0000- 6d54c000 Deferred dsound
PE 6e340000- 6e34e000 Deferred api-ms-win-core-synch-l1-2-0
PE 6e6c0000- 6eac5000 Deferred comctl32
PE 6fbc0000- 6fdde000 Deferred rpcrt4
PE 70140000- 701c3000 Deferred mmdevapi
PE 71200000- 7135c000 Deferred mfplat
PE 7a850000- 7a858000 Deferred opengl32
PE 7b000000- 7b339000 Deferred kernelbase
PE 7b410000- 7b5db000 Deferred kernel32
PE 7bc20000- 7bc35000 Deferred ntdll
PE 140000000- 1473b6200 Deferred rdr2
PE 180000000- 1800e9000 Deferred oo2core_5_win64
PE 7fa374020000- 7fa374027000 Deferred winevulkan
PE 7fa37c020000- 7fa37c024000 Deferred winepulse
PE 7fa37c160000- 7fa37c16d000 Deferred winspool
PE 7fa3846a0000- 7fa3846a9000 Deferred wined3d
PE 7fa384b90000- 7fa384b95000 Deferred dxgi
PE 7fa384dd0000- 7fa384dd5000 Deferred winex11
PE 7fa385720000- 7fa385ffd000 Deferred shell32
PE 7fa386150000- 7fa38615c000 Deferred dinput8
PE 7fa3861b0000- 7fa3861b5000 Deferred bcrypt
PE 7fa3861e0000- 7fa386227000 Deferred crypt32
PE 7fa3862e0000- 7fa3862e6000 Deferred ws2_32
PE 7fa386340000- 7fa386346000 Deferred iphlpapi
PE 7fa386380000- 7fa38638c000 Deferred gdi32
PE 7fa386550000- 7fa38656e000 Deferred ucrtbase
PE 7fa386660000- 7fa38666b000 Deferred advapi32
PE 7fa3867f0000- 7fa3868e1000 Deferred user32
Threads:
process tid prio (all id:s are in hex)
00000020 Launcher.exe
000003b8 15
000003b4 0
000003a8 0
00000288 0
0000027c 0
00000278 0
000001d4 0
000001c8 0
000001c4 0
000001c0 0
000001bc 0
000001b8 0
000001b4 0
000001b0 0
000001ac 0
000001a8 0
000001a4 0
000001a0 0
0000019c 0
00000198 0
0000018c 0
00000184 0
00000180 0
0000017c 0
00000178 0
00000174 -2
00000170 -2
00000114 0
00000110 0
0000010c 0
00000108 0
00000104 0
00000100 0
000000fc 0
000000f8 0
000000f4 0
000000f0 0
000000ec 0
000000e8 0
000000e4 0
000000e0 0
000000dc 0
000000d8 0
000000d4 -2
000000d0 -2
00000024 0
00000038 services.exe
00000160 0
000000a4 0
00000090 0
0000006c 0
0000004c 0
00000040 0
0000003c 0
00000044 plugplay.exe
00000250 0
00000248 0
0000007c 0
00000060 0
0000005c 0
00000058 0
00000048 0
00000064 winedevice.exe
00000098 0
00000094 0
0000008c 0
00000078 0
00000074 0
00000070 0
00000068 0
0000009c winedevice.exe
000000b0 0
000000ac 0
000000a8 0
000000a0 0
000000b4 explorer.exe
000000c4 0
000000c0 0
000000bc 0
000000b8 0
0000012c RockstarService.exe
00000194 0
00000190 0
0000016c 0
00000164 0
00000130 0
000001cc SocialClubHelper.exe
000003a0 0
0000039c 0
00000398 0
00000384 0
00000380 0
0000037c 0
00000274 0
00000270 0
0000026c 0
00000268 0
00000264 0
00000260 0
0000025c 0
00000258 0
00000254 -2
00000244 0
00000240 0
0000023c 0
00000238 0
0000022c 0
00000224 0
00000220 0
0000021c 0
00000218 0
00000214 0
00000210 -2
0000020c 0
00000208 0
00000204 0
00000200 0
000001fc -2
000001f8 -2
000001f4 0
000001f0 0
000001ec 0
000001e8 0
000001e4 0
000001e0 0
000001dc 0
000001d8 0
000001d0 0
00000280 SocialClubHelper.exe
00000390 0
00000388 0
00000378 0
000002d4 -2
000002d0 0
000002cc 0
000002c8 0
000002c4 0
000002c0 0
000002bc 0
000002b8 -2
000002b4 -2
000002b0 0
000002ac 0
000002a8 0
000002a4 0
000002a0 0
0000029c 0
00000298 0
00000294 0
00000284 0
00000330 SocialClubHelper.exe
00000374 0
0000036c 0
00000364 0
00000360 0
0000035c 0
00000358 0
00000354 0
00000350 -2
0000034c -2
00000348 0
00000344 0
00000340 0
00000338 0
00000334 0
000003c4 (D) C:\Program Files\Rockstar Games\Red Dead Redemption 2\RDR2.exe
00000490 -2
0000048c -2
00000488 -2
00000480 15
0000047c 15
00000478 15
00000474 0
00000470 -1
0000046c 15
00000468 15
00000464 15
00000460 15
0000045c 1
00000458 0
00000454 -1
00000450 -1
0000044c 0
00000448 1
00000444 0
00000440 0
0000043c 0
00000438 0
00000434 0
00000430 0
0000042c 15
00000424 0
00000420 0
0000041c 0
00000418 0
00000414 -1
00000410 2
0000040c 2
00000408 2 <==
00000404 2
000003c8 15
System information:
Wine build: wine-5.8
Platform: x86_64
Version: Windows 10
Host system: Linux
Host version: 5.6.15-300.fc32.x86_64

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/3291#issuecomment-640260996,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABUBTKVLLE6PQK6C5EH3X3RVPM5LANCNFSM4JV54AXQ
.

That's super weird. I haven't had any compilation errors at all. What are
you trying to build on?

On Sun, 7 Jun 2020 at 20:39, David JM Emmett notifications@github.com
wrote:

You got further than me, the SECCOMP changes wouldn't compile, so I gave
up.

Cheers,

David JM Emmett

On Sun, 7 Jun 2020 at 19:37, topsyandpip56 notifications@github.com
wrote:

Using mrpippy's rdr2-2 branch on Fedora 32 + amdgpu, the game crashes
shortly into the initial shader load. I don't know if the backtrace
offers
anything useful. It might be due to not compiling 32-bit support into the
wine build?

wine: Unhandled page fault on read access to 0000000000000128 at address
00007FA34C798872 (thread 0408), starting debugger...
Unhandled exception: page fault on read access to 0x00000128 in 64-bit
code (0x00007fa34c798872).
Register dump:
rip:00007fa34c798872 rsp:00000000341ebb20 rbp:00007f9c30012850
eflags:00010202 ( R- -- I - - - )
rax:00000000341ebbc0 rbx:0000000000000000 rcx:0000000000000002
rdx:00007fa34c863ba0
rsi:0000000000000008 rdi:0000000000000000 r8:00007f9bd37626e0
r9:00007f9c30012850 r10:00000000341eab84
r11:0000000000000000 r12:0000000000000000 r13:0000000000000000
r14:00000000341ebbc0 r15:0000000000000000
Stack dump:
0x00000000341ebb20: 00007f9bd3a4b0d0 0100000000000000
0x00000000341ebb30: 00000000341ebb2f 0000000000000002
0x00000000341ebb40: 0000000000000000 0000000000000000
0x00000000341ebb50: 00007f9c30012850 0000000000000000
0x00000000341ebb60: 00007f9c30012850 0000000000000000
0x00000000341ebb70: 0000000000000000 00000000341ebbc0
0x00000000341ebb80: 0000000000000000 00007fa34c64bf4f
0x00000000341ebb90: 0000000000000000 00007f9bd6c97490
0x00000000341ebba0: 0000000000000000 0000000000000000
0x00000000341ebbb0: 0000000000000000 0000000000000000
0x00000000341ebbc0: 0000010100000000 0101010101010000
0x00000000341ebbd0: 0101010101000001 0101000000010101
Backtrace:
=>0 0x00007fa34c798872 (0x00007f9c30012850)
0x00007fa34c798872: movq 0x0000000000000128(%rdi),%rbx
Modules:
Module Address Debug info Name (55 modules)
PE 220000- 24d000 Deferred amd_ags_x64
PE 250000- 2cb000 Deferred bink2w64
PE 960000- 96e000 Deferred api-ms-win-core-localization-l1-2-1
PE 33fd0000- 33fde000 Deferred api-ms-win-core-sysinfo-l1-2-1
PE 61900000- 6199d000 Deferred sechost
PE 62140000- 621cd000 Deferred uxtheme
PE 62540000- 625e4000 Deferred wintrust
PE 62600000- 626d8000 Deferred usp10
PE 637c0000- 63931000 Deferred winmm
PE 64940000- 64986000 Deferred shcore
PE 64b80000- 64bab000 Deferred hid
PE 64d40000- 64d59000 Deferred vulkan-1
PE 65000000- 65597000 Deferred ole32
PE 65680000- 656af000 Deferred rtworkq
PE 65780000- 6579c000 Deferred version
PE 66440000- 664a2000 Deferred msacm32
PE 67500000- 67527000 Deferred xinput9_1_0
PE 67740000- 6786c000 Deferred wbemprox
PE 68140000- 68265000 Deferred msctf
PE 68a40000- 68b67000 Deferred shlwapi
PE 69c80000- 69cf8000 Deferred propsys
PE 6a100000- 6a502000 Deferred oleaut32
PE 6a700000- 6a8b3000 Deferred setupapi
PE 6aa00000- 6ab83000 Deferred mf
PE 6b880000- 6b88d000 Deferred api-ms-win-core-fibers-l1-1-1
PE 6bec0000- 6bf09000 Deferred imm32
PE 6cd80000- 6ce1d000 Deferred mfreadwrite
PE 6d3c0000- 6d54c000 Deferred dsound
PE 6e340000- 6e34e000 Deferred api-ms-win-core-synch-l1-2-0
PE 6e6c0000- 6eac5000 Deferred comctl32
PE 6fbc0000- 6fdde000 Deferred rpcrt4
PE 70140000- 701c3000 Deferred mmdevapi
PE 71200000- 7135c000 Deferred mfplat
PE 7a850000- 7a858000 Deferred opengl32
PE 7b000000- 7b339000 Deferred kernelbase
PE 7b410000- 7b5db000 Deferred kernel32
PE 7bc20000- 7bc35000 Deferred ntdll
PE 140000000- 1473b6200 Deferred rdr2
PE 180000000- 1800e9000 Deferred oo2core_5_win64
PE 7fa374020000- 7fa374027000 Deferred winevulkan
PE 7fa37c020000- 7fa37c024000 Deferred winepulse
PE 7fa37c160000- 7fa37c16d000 Deferred winspool
PE 7fa3846a0000- 7fa3846a9000 Deferred wined3d
PE 7fa384b90000- 7fa384b95000 Deferred dxgi
PE 7fa384dd0000- 7fa384dd5000 Deferred winex11
PE 7fa385720000- 7fa385ffd000 Deferred shell32
PE 7fa386150000- 7fa38615c000 Deferred dinput8
PE 7fa3861b0000- 7fa3861b5000 Deferred bcrypt
PE 7fa3861e0000- 7fa386227000 Deferred crypt32
PE 7fa3862e0000- 7fa3862e6000 Deferred ws2_32
PE 7fa386340000- 7fa386346000 Deferred iphlpapi
PE 7fa386380000- 7fa38638c000 Deferred gdi32
PE 7fa386550000- 7fa38656e000 Deferred ucrtbase
PE 7fa386660000- 7fa38666b000 Deferred advapi32
PE 7fa3867f0000- 7fa3868e1000 Deferred user32
Threads:
process tid prio (all id:s are in hex)
00000020 Launcher.exe
000003b8 15
000003b4 0
000003a8 0
00000288 0
0000027c 0
00000278 0
000001d4 0
000001c8 0
000001c4 0
000001c0 0
000001bc 0
000001b8 0
000001b4 0
000001b0 0
000001ac 0
000001a8 0
000001a4 0
000001a0 0
0000019c 0
00000198 0
0000018c 0
00000184 0
00000180 0
0000017c 0
00000178 0
00000174 -2
00000170 -2
00000114 0
00000110 0
0000010c 0
00000108 0
00000104 0
00000100 0
000000fc 0
000000f8 0
000000f4 0
000000f0 0
000000ec 0
000000e8 0
000000e4 0
000000e0 0
000000dc 0
000000d8 0
000000d4 -2
000000d0 -2
00000024 0
00000038 services.exe
00000160 0
000000a4 0
00000090 0
0000006c 0
0000004c 0
00000040 0
0000003c 0
00000044 plugplay.exe
00000250 0
00000248 0
0000007c 0
00000060 0
0000005c 0
00000058 0
00000048 0
00000064 winedevice.exe
00000098 0
00000094 0
0000008c 0
00000078 0
00000074 0
00000070 0
00000068 0
0000009c winedevice.exe
000000b0 0
000000ac 0
000000a8 0
000000a0 0
000000b4 explorer.exe
000000c4 0
000000c0 0
000000bc 0
000000b8 0
0000012c RockstarService.exe
00000194 0
00000190 0
0000016c 0
00000164 0
00000130 0
000001cc SocialClubHelper.exe
000003a0 0
0000039c 0
00000398 0
00000384 0
00000380 0
0000037c 0
00000274 0
00000270 0
0000026c 0
00000268 0
00000264 0
00000260 0
0000025c 0
00000258 0
00000254 -2
00000244 0
00000240 0
0000023c 0
00000238 0
0000022c 0
00000224 0
00000220 0
0000021c 0
00000218 0
00000214 0
00000210 -2
0000020c 0
00000208 0
00000204 0
00000200 0
000001fc -2
000001f8 -2
000001f4 0
000001f0 0
000001ec 0
000001e8 0
000001e4 0
000001e0 0
000001dc 0
000001d8 0
000001d0 0
00000280 SocialClubHelper.exe
00000390 0
00000388 0
00000378 0
000002d4 -2
000002d0 0
000002cc 0
000002c8 0
000002c4 0
000002c0 0
000002bc 0
000002b8 -2
000002b4 -2
000002b0 0
000002ac 0
000002a8 0
000002a4 0
000002a0 0
0000029c 0
00000298 0
00000294 0
00000284 0
00000330 SocialClubHelper.exe
00000374 0
0000036c 0
00000364 0
00000360 0
0000035c 0
00000358 0
00000354 0
00000350 -2
0000034c -2
00000348 0
00000344 0
00000340 0
00000338 0
00000334 0
000003c4 (D) C:\Program Files\Rockstar Games\Red Dead Redemption
2\RDR2.exe
00000490 -2
0000048c -2
00000488 -2
00000480 15
0000047c 15
00000478 15
00000474 0
00000470 -1
0000046c 15
00000468 15
00000464 15
00000460 15
0000045c 1
00000458 0
00000454 -1
00000450 -1
0000044c 0
00000448 1
00000444 0
00000440 0
0000043c 0
00000438 0
00000434 0
00000430 0
0000042c 15
00000424 0
00000420 0
0000041c 0
00000418 0
00000414 -1
00000410 2
0000040c 2
00000408 2 <==
00000404 2
000003c8 15
System information:
Wine build: wine-5.8
Platform: x86_64
Version: Windows 10
Host system: Linux
Host version: 5.6.15-300.fc32.x86_64

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<
https://github.com/ValveSoftware/Proton/issues/3291#issuecomment-640260996
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AABUBTKVLLE6PQK6C5EH3X3RVPM5LANCNFSM4JV54AXQ

.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/3291#issuecomment-640268973,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABTLIYYYM4MJEPAFWHLUV2TRVPUGDANCNFSM4JV54AXQ
.

I’ve been using the standard docker builder. Works for all other branches except mrpippy/rdr2-2.

Cheers,
David

On 8 Jun 2020, at 14:37, topsyandpip56 notifications@github.com wrote:


That's super weird. I haven't had any compilation errors at all. What are
you trying to build on?

On Sun, 7 Jun 2020 at 20:39, David JM Emmett notifications@github.com
wrote:

You got further than me, the SECCOMP changes wouldn't compile, so I gave
up.

Cheers,

David JM Emmett

On Sun, 7 Jun 2020 at 19:37, topsyandpip56 notifications@github.com
wrote:

Using mrpippy's rdr2-2 branch on Fedora 32 + amdgpu, the game crashes
shortly into the initial shader load. I don't know if the backtrace
offers
anything useful. It might be due to not compiling 32-bit support into the
wine build?

wine: Unhandled page fault on read access to 0000000000000128 at address
00007FA34C798872 (thread 0408), starting debugger...
Unhandled exception: page fault on read access to 0x00000128 in 64-bit
code (0x00007fa34c798872).
Register dump:
rip:00007fa34c798872 rsp:00000000341ebb20 rbp:00007f9c30012850
eflags:00010202 ( R- -- I - - - )
rax:00000000341ebbc0 rbx:0000000000000000 rcx:0000000000000002
rdx:00007fa34c863ba0
rsi:0000000000000008 rdi:0000000000000000 r8:00007f9bd37626e0
r9:00007f9c30012850 r10:00000000341eab84
r11:0000000000000000 r12:0000000000000000 r13:0000000000000000
r14:00000000341ebbc0 r15:0000000000000000
Stack dump:
0x00000000341ebb20: 00007f9bd3a4b0d0 0100000000000000
0x00000000341ebb30: 00000000341ebb2f 0000000000000002
0x00000000341ebb40: 0000000000000000 0000000000000000
0x00000000341ebb50: 00007f9c30012850 0000000000000000
0x00000000341ebb60: 00007f9c30012850 0000000000000000
0x00000000341ebb70: 0000000000000000 00000000341ebbc0
0x00000000341ebb80: 0000000000000000 00007fa34c64bf4f
0x00000000341ebb90: 0000000000000000 00007f9bd6c97490
0x00000000341ebba0: 0000000000000000 0000000000000000
0x00000000341ebbb0: 0000000000000000 0000000000000000
0x00000000341ebbc0: 0000010100000000 0101010101010000
0x00000000341ebbd0: 0101010101000001 0101000000010101
Backtrace:
=>0 0x00007fa34c798872 (0x00007f9c30012850)
0x00007fa34c798872: movq 0x0000000000000128(%rdi),%rbx
Modules:
Module Address Debug info Name (55 modules)
PE 220000- 24d000 Deferred amd_ags_x64
PE 250000- 2cb000 Deferred bink2w64
PE 960000- 96e000 Deferred api-ms-win-core-localization-l1-2-1
PE 33fd0000- 33fde000 Deferred api-ms-win-core-sysinfo-l1-2-1
PE 61900000- 6199d000 Deferred sechost
PE 62140000- 621cd000 Deferred uxtheme
PE 62540000- 625e4000 Deferred wintrust
PE 62600000- 626d8000 Deferred usp10
PE 637c0000- 63931000 Deferred winmm
PE 64940000- 64986000 Deferred shcore
PE 64b80000- 64bab000 Deferred hid
PE 64d40000- 64d59000 Deferred vulkan-1
PE 65000000- 65597000 Deferred ole32
PE 65680000- 656af000 Deferred rtworkq
PE 65780000- 6579c000 Deferred version
PE 66440000- 664a2000 Deferred msacm32
PE 67500000- 67527000 Deferred xinput9_1_0
PE 67740000- 6786c000 Deferred wbemprox
PE 68140000- 68265000 Deferred msctf
PE 68a40000- 68b67000 Deferred shlwapi
PE 69c80000- 69cf8000 Deferred propsys
PE 6a100000- 6a502000 Deferred oleaut32
PE 6a700000- 6a8b3000 Deferred setupapi
PE 6aa00000- 6ab83000 Deferred mf
PE 6b880000- 6b88d000 Deferred api-ms-win-core-fibers-l1-1-1
PE 6bec0000- 6bf09000 Deferred imm32
PE 6cd80000- 6ce1d000 Deferred mfreadwrite
PE 6d3c0000- 6d54c000 Deferred dsound
PE 6e340000- 6e34e000 Deferred api-ms-win-core-synch-l1-2-0
PE 6e6c0000- 6eac5000 Deferred comctl32
PE 6fbc0000- 6fdde000 Deferred rpcrt4
PE 70140000- 701c3000 Deferred mmdevapi
PE 71200000- 7135c000 Deferred mfplat
PE 7a850000- 7a858000 Deferred opengl32
PE 7b000000- 7b339000 Deferred kernelbase
PE 7b410000- 7b5db000 Deferred kernel32
PE 7bc20000- 7bc35000 Deferred ntdll
PE 140000000- 1473b6200 Deferred rdr2
PE 180000000- 1800e9000 Deferred oo2core_5_win64
PE 7fa374020000- 7fa374027000 Deferred winevulkan
PE 7fa37c020000- 7fa37c024000 Deferred winepulse
PE 7fa37c160000- 7fa37c16d000 Deferred winspool
PE 7fa3846a0000- 7fa3846a9000 Deferred wined3d
PE 7fa384b90000- 7fa384b95000 Deferred dxgi
PE 7fa384dd0000- 7fa384dd5000 Deferred winex11
PE 7fa385720000- 7fa385ffd000 Deferred shell32
PE 7fa386150000- 7fa38615c000 Deferred dinput8
PE 7fa3861b0000- 7fa3861b5000 Deferred bcrypt
PE 7fa3861e0000- 7fa386227000 Deferred crypt32
PE 7fa3862e0000- 7fa3862e6000 Deferred ws2_32
PE 7fa386340000- 7fa386346000 Deferred iphlpapi
PE 7fa386380000- 7fa38638c000 Deferred gdi32
PE 7fa386550000- 7fa38656e000 Deferred ucrtbase
PE 7fa386660000- 7fa38666b000 Deferred advapi32
PE 7fa3867f0000- 7fa3868e1000 Deferred user32
Threads:
process tid prio (all id:s are in hex)
00000020 Launcher.exe
000003b8 15
000003b4 0
000003a8 0
00000288 0
0000027c 0
00000278 0
000001d4 0
000001c8 0
000001c4 0
000001c0 0
000001bc 0
000001b8 0
000001b4 0
000001b0 0
000001ac 0
000001a8 0
000001a4 0
000001a0 0
0000019c 0
00000198 0
0000018c 0
00000184 0
00000180 0
0000017c 0
00000178 0
00000174 -2
00000170 -2
00000114 0
00000110 0
0000010c 0
00000108 0
00000104 0
00000100 0
000000fc 0
000000f8 0
000000f4 0
000000f0 0
000000ec 0
000000e8 0
000000e4 0
000000e0 0
000000dc 0
000000d8 0
000000d4 -2
000000d0 -2
00000024 0
00000038 services.exe
00000160 0
000000a4 0
00000090 0
0000006c 0
0000004c 0
00000040 0
0000003c 0
00000044 plugplay.exe
00000250 0
00000248 0
0000007c 0
00000060 0
0000005c 0
00000058 0
00000048 0
00000064 winedevice.exe
00000098 0
00000094 0
0000008c 0
00000078 0
00000074 0
00000070 0
00000068 0
0000009c winedevice.exe
000000b0 0
000000ac 0
000000a8 0
000000a0 0
000000b4 explorer.exe
000000c4 0
000000c0 0
000000bc 0
000000b8 0
0000012c RockstarService.exe
00000194 0
00000190 0
0000016c 0
00000164 0
00000130 0
000001cc SocialClubHelper.exe
000003a0 0
0000039c 0
00000398 0
00000384 0
00000380 0
0000037c 0
00000274 0
00000270 0
0000026c 0
00000268 0
00000264 0
00000260 0
0000025c 0
00000258 0
00000254 -2
00000244 0
00000240 0
0000023c 0
00000238 0
0000022c 0
00000224 0
00000220 0
0000021c 0
00000218 0
00000214 0
00000210 -2
0000020c 0
00000208 0
00000204 0
00000200 0
000001fc -2
000001f8 -2
000001f4 0
000001f0 0
000001ec 0
000001e8 0
000001e4 0
000001e0 0
000001dc 0
000001d8 0
000001d0 0
00000280 SocialClubHelper.exe
00000390 0
00000388 0
00000378 0
000002d4 -2
000002d0 0
000002cc 0
000002c8 0
000002c4 0
000002c0 0
000002bc 0
000002b8 -2
000002b4 -2
000002b0 0
000002ac 0
000002a8 0
000002a4 0
000002a0 0
0000029c 0
00000298 0
00000294 0
00000284 0
00000330 SocialClubHelper.exe
00000374 0
0000036c 0
00000364 0
00000360 0
0000035c 0
00000358 0
00000354 0
00000350 -2
0000034c -2
00000348 0
00000344 0
00000340 0
00000338 0
00000334 0
000003c4 (D) C:\Program Files\Rockstar Games\Red Dead Redemption
2\RDR2.exe
00000490 -2
0000048c -2
00000488 -2
00000480 15
0000047c 15
00000478 15
00000474 0
00000470 -1
0000046c 15
00000468 15
00000464 15
00000460 15
0000045c 1
00000458 0
00000454 -1
00000450 -1
0000044c 0
00000448 1
00000444 0
00000440 0
0000043c 0
00000438 0
00000434 0
00000430 0
0000042c 15
00000424 0
00000420 0
0000041c 0
00000418 0
00000414 -1
00000410 2
0000040c 2
00000408 2 <==
00000404 2
000003c8 15
System information:
Wine build: wine-5.8
Platform: x86_64
Version: Windows 10
Host system: Linux
Host version: 5.6.15-300.fc32.x86_64

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<
https://github.com/ValveSoftware/Proton/issues/3291#issuecomment-640260996
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AABUBTKVLLE6PQK6C5EH3X3RVPM5LANCNFSM4JV54AXQ

.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/3291#issuecomment-640268973,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABTLIYYYM4MJEPAFWHLUV2TRVPUGDANCNFSM4JV54AXQ
.

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

My testing resulted in the following, about two weeks ago:

Someone suggested that I try skipping the introduction, which supposedly is done just by feeding the game a save after the so called introduction, but it didn't help. Some external hacks are supposedly still needed, so let's wait for Brendan :)

Similarly I can show the absolute furthest it gets before terminating, on the latest 1231.61 patch of today.

Here's another log. I don't know if it will help, but here it is anyway.
steam-1174180.log

This was how far I managed to get on May 25th. I put in a game settings file with everything set to low and Vulkan. Really bad performance in the into logo animation, felt like software rendering, but idk.

This was how far I managed to get on May 25th. I put in a game settings file with everything set to low and Vulkan. Really bad performance in the into logo animation, felt like software rendering, but idk.

Well that's really interesting. Are you using an nvidia card by any chance?

Thanks everyone for your patience, I'm impressed by the sleuthing and I've got a Proton build for you to try out! 🎉 🎉 🎉

https://www.codeweavers.com/xfer/bshanks/public/proton-5.0-rdr2-3.tar.gz
password: public

Download the file and uncompress it in your compatibilitytools.d directory, likely ~/.steam/steam/compatibilitytools.d/
Then force it to be used for RDR2 in Steam, with "Force the use of a specific Steam Play compatibility tool"

In addition, before launching with this Proton build, delete any previous compatdata for the game. This would usually be at ~/.steam/steam/steamapps/compatdata/1174180/

Drivers

• NVIDIA: you will need to run the beta 440.66.15 driver to avoid very poor performance
• AMD Mesa/RADV: you will need to rebuild Mesa with this patch applied, otherwise it will crash halfway through the progress bar. Mesa/RADV has not gotten much testing, there may be other issues.

Known issues

• only 720p and 1080p resolutions are available
• you may get an Activation Error on the first launch or two, but it should go away after a relaunch
• you will get a Minimum Hardware Requirements Check dialog on launch, click OK to ignore it
• I haven't tried Online play at all

I can confirm it works. Thanks Brendan!

@Tk-Glitch Did you have to do anything at all other than clean compatdata, have the right drivers and run it with the proton build? I tried and got the same game file verification errors I had earlier.
I'm in the process of reinstalling the game and giving it another shot, but would appreciate to know if you were using any special launch options, or other workarounds that I've seen mentioned here.

Reinstall did nothing. Still fails with "Unable to launch game, please verify your game data."
Log file: https://gist.github.com/chris-echoz/a0bca3b860feb6a8d01729fb36e128f9
I'm on Debian Sid, running kernel 5.6.0-2 with proprietary 440.66.15 drivers.

@chris-echoz Your log reports proton-5.0-8, while it should report proton_5.0-rdr2-3 when using the correct build above.
My setup is pretty convoluted tbh but it shouldn't matter much here. Having WINEDLLOVERRIDES="dxgi=n,b" in your launch parameters might be needed as I had some child window error without it, but I'm not entirely sure.
Outside of this, clean prefix, tested successfully on both latest amdgpu-pro and mesa-git (with the patch linked above applied).

@Tk-Glitch I noticed that it said 5.0-8, too, but I checked multiple times that steam says proton_5.0-rdr2-3. I'm not sure exactly where it gets this string from, but 5.0-8 is consistent with the "version" file in the tarball, so I don't believe I'm running the wrong version of Proton.
I'll try running with those overrides to see if it makes any difference.

@Tk-Glitch I noticed that it said 5.0-8, too, but I checked multiple times that steam says proton_5.0-rdr2-3. I'm not sure exactly where it gets this string from, but 5.0-8 is consistent with the "version" file in the tarball, so I don't believe I'm running the wrong version of Proton.

Yeah that’s the right version, it does say 5.0-8 but the wine: enabling seccomp syscall filters for RDR2. line is the tip-off.

You’re not the first person to have that crash, but I still don’t know what’s causing it. Can you try using wined3d instead of dxvk? (PROTON_USE_WINED3D)

Oh my bad 😅 That'll teach me for having a convoluted setup to report stuff with :frog:

@mrpippy Running with launch options PROTON_LOG=1 PROTON_USE_WINED3D=1 %command% got me through the launcher, gave me an error telling me I had an old driver:

Then the game launched and I saw a black window for about a second or so before it terminated.
The log file is considerably larger this time (62.4 MB), and gist timed out while I was uploading it. I've uploaded it on my server instead: https://cloud.echoz.io/s/p8NcHZqF5d7Nkcj

In addition to this I also tried with Tk-Glitch's override for dxgi, which did in contrast to my attempts without special launch options actually allow me to see the launcher, but in the end gave me the same error as before.

@mrpippy Running with launch options PROTON_LOG=1 PROTON_USE_WINED3D=1 %command% got me through the launcher, gave me an error telling me I had an old driver:

Then the game launched and I saw a black window for about a second or so before it terminated.

Interesting, looks like it's trying to use D3D12 and then crashes. Could you add +dxgi,+vulkan to your log? Also, try it with PROTON_USE_WINED3D=1 and WINEDLLOVERRIDES=d3d12.dll=d. What card do you have?

@mrpippy Running with launch options PROTON_LOG=1 PROTON_USE_WINED3D=1 %command% got me through the launcher, gave me an error telling me I had an old driver:

Then the game launched and I saw a black window for about a second or so before it terminated.

Interesting, looks like it's trying to use D3D12 and then crashes. Could you add +dxgi,+vulkan to your log? Also, try it with PROTON_USE_WINED3D=1 and WINEDLLOVERRIDES=d3d12.dll=d. What card do you have?

By adding +dxgi,+vulkan do you mean add it to PROTON_LOG or WINEDEBUG?
Adding it to user_settings.py, I'm assuming that's what you meant anyway.
I'll give all these things a shot and get back to you.

My GPU is a GTX 1060 6GB.

By adding +dxgi,+vulkan do you mean add it to PROTON_LOG or WINEDEBUG?

Add those to WINEDEBUG, in user_settings.py

@chris-echoz maybe you can try to force Vulkan in game config file?

https://www.pcgamingwiki.com/wiki/Red_Dead_Redemption_2 states you need to open settings.xml which is located somewhere in game's prefix, locate kSettingAPI_DX12 and change it to kSettingAPI_Vulkan

I don't have the game and can't try it myself.

@chris-echoz maybe you can try to force Vulkan in game config file?

https://www.pcgamingwiki.com/wiki/Red_Dead_Redemption_2 states you need to open settings.xml which is located somewhere in game's prefix, locate kSettingAPI_DX12 and change it to kSettingAPI_Vulkan

I don't have the game and can't try it myself.

I managed to find someone else's config file, and tried this with an array of different options and workarounds, but to no avail. I believe the game even with Vulkan uses a lot of D3D components.

@mrpippy All of these logs are with +dxgi,+vulkan, each in a new compatdata directory.

With PROTON_LOG=1 WINEDLLOVERRIDES=d3d12.dll=d PROTON_USE_WINED3D=1 %command%:
Launcher went through fine, got the same message regarding AMD drivers. Game window popped up briefly and crashed. Second attempt went the same way.
Log: https://cloud.echoz.io/s/WQjCGXeMNi6otbT

With PROTON_LOG=1 WINEDLLOVERRIDES=d3d12.dll=d %command%:
I don't even see the launcher, I just get the game file verification error.
Tried another 4 or 5 with the same compatdata, but results were consistent.
Log: https://cloud.echoz.io/s/fTF6pSbRdeic4Xc

With PROTON_LOG=1 PROTON_USE_WINED3D=1 %command%:
Appears the same as what happened on the first run happened here.
Log: https://cloud.echoz.io/s/SRSF962DiZpyyqj

Finally, with only PROTON_LOG=1 %command%:
Appears to run just the same as running with only the d3d12 override.
Log: https://cloud.echoz.io/s/saGobE86g7T6K2K

I'm seeing the same as Echoz. Using latest NVIDIA DKMS package on Ubuntu
19.10 (440.82-0ubuntu0~0.19.10.1) with GTX 1060.

A quick grep of the logs show an error being thrown:
wine: Unhandled exception 0x20474343 in thread cc at address
000000007B00FC3E (thread 00cc), starting debugger...

Cheers,
David JM Emmett

On Sat, 13 Jun 2020 at 08:50, Echoz notifications@github.com wrote:

@mrpippy https://github.com/mrpippy All of these logs are with
+dxgi,+vulkan, each in a new compatdata directory.

With PROTON_LOG=1 WINEDLLOVERRIDES=d3d12.dll=d PROTON_USE_WINED3D=1
%command%:
Launcher went through fine, got the same message regarding AMD drivers.
Game window popped up briefly and crashed. Second attempt went the same way.
Log: https://cloud.echoz.io/s/WQjCGXeMNi6otbT

With PROTON_LOG=1 WINEDLLOVERRIDES=d3d12.dll=d %command%:
I don't even see the launcher, I just get the game file verification error.
Tried another 4 or 5 with the same compatdata, but results were consistent.
Log: https://cloud.echoz.io/s/fTF6pSbRdeic4Xc

With PROTON_LOG=1 PROTON_USE_WINED3D=1 %command%:
Appears the same as what happened on the first run happened here.
Log: https://cloud.echoz.io/s/SRSF962DiZpyyqj

Finally, with only PROTON_LOG=1 %command%:
Appears to run just the same as running with only the d3d12 override.
Log: https://cloud.echoz.io/s/saGobE86g7T6K2K

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/3291#issuecomment-643586914,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABUBTJPLNY6ISA6CUDN3KTRWMVSTANCNFSM4JV54AXQ
.

Don't know if this helps anyone, but I kept getting the verify files error when I used a clean prefix and rdr2-3. If I let 5.0-9 create the prefix, then switch to rdr2-3, this error goes away.

That said, I get a freeze during the logo video, and no menu comes up... Haven't got time to figure out why. Just wanted to note the prefix thing in case it helps anyone.

Thanks everyone for your patience, I'm impressed by the sleuthing and I've got a Proton build for you to try out! tada tada tada

https://www.codeweavers.com/xfer/bshanks/public/proton-5.0-rdr2-3.tar.gz
password: public

Download the file and uncompress it in your compatibilitytools.d directory, likely ~/.steam/steam/compatibilitytools.d/
Then force it to be used for RDR2 in Steam, with "Force the use of a specific Steam Play compatibility tool"

In addition, before launching with this Proton build, delete any previous compatdata for the game. This would usually be at ~/.steam/steam/steamapps/compatdata/1174180/

Drivers

* NVIDIA: you will need to run the [beta 440.66.15 driver](https://developer.nvidia.com/vulkan-driver) to avoid very poor performance

* AMD Mesa/RADV: you will need to rebuild Mesa with [this patch](https://gitlab.freedesktop.org/hakzsam/mesa/-/commit/d044a4476a828f15298336f66404892682cfcfb7) applied, otherwise it will crash halfway through the progress bar. Mesa/RADV has not gotten much testing, there may be other issues.

Known issues

* only 720p and 1080p resolutions are available

* you may get an Activation Error on the first launch or two, but it should go away after a relaunch

* you will get a Minimum Hardware Requirements Check dialog on launch, click OK to ignore it

* I haven't tried Online play at all

Anyone know how to get this driver for Manjaro 64 bit? im running a Nvidia gtx 980

hello, it seems better than before, but in my case it crashed after launcher.
I'm on latest arch with Linux 5.7 & mesa 20.1.1 and AMD RX580

Anyone know how to get this driver for Manjaro 64 bit? im running a Nvidia gtx 980

On AUR or with Tk-Glitch PKGBUILDS.

Thanks!

Anyone know how to get this driver for Manjaro 64 bit? im running a Nvidia gtx 980

On AUR or with Tk-Glitch PKGBUILDS.

loading packages...
resolving dependencies...
looking for conflicting packages...
:: nvidia-dev-dkms-tkg and linux56-nvidia-440xx are in conflict (nvidia). Remove linux56-nvidia-440xx? [y/N] y
:: nvidia-dev-utils-tkg and nvidia-440xx-utils are in conflict (nvidia-utils). Remove nvidia-440xx-utils? [y/N] y
error: failed to prepare transaction (could not satisfy dependencies)
:: removing linux56-nvidia-440xx breaks dependency 'linux56-nvidia-440xx' required by linux-latest-nvidia-440xx
==> WARNING: Failed to install built package(s).
-> exit cleanup done

git clone https://github.com/Frogging-Family/nvidia-all.git
cd nvidia-all
makepkg -si
sudo mkinitcpio -P

The new wine build throws up an error before launching:
wine: Unhandled page fault on read access to 0000000000000010 at address 000000007B00FC3E (thread 053c), starting debugger...
After this the seccomp syscall filters open and fail because the process doesn't exist. Possibly important to note that I'm not using Proton via Steam. I am using the wine build extracted from Proton_dist via Lutris due to owning the RGS version of the game. The older rdr2-2 build hits a page fault just after the intro video. This is with the patched AMD Mesa being used.

Update: I can confirm the same page fault when using Proton via Steam.

So exciting! I've tried it on my machine and I'm getting the same error as chris-echoz, Failed to verify game files, and when I set it to use wined3d I get the dialog about outdated amd graphics drivers, then a black window for a second and then it crashes. I'm using a TR 2950 and Nvidia turing.

Log is here:
rdr2.log.zip

Launch parameters : PROTON_LOG=1 WINEDLLOVERRIDES=d3d12.dll=d PROTON_USE_WINED3D=1 %command%

user_settings.py :
"WINEDEBUG": "+timestamp,+pid,+tid,+seh,+debugstr,+loaddll,+mscoree,+dxgi,+vulkan",
"DXVK_LOG_LEVEL": "info",
"VKD3D_DEBUG": "warn",
"WINE_MONO_TRACE": "E:System.NotImplementedException",

Rockstar launcher loads for a while, then I get the same error as https://github.com/ValveSoftware/Proton/issues/3291#issuecomment-643572027 about outdated AMD drivers, which is strange because I'm on Nvidia 440.66.15...

log :
steam-1174180.log

Hello @ah-, blind guess, does taskset -c 0-15 %command% have an effect on your system?

if i run it with Brendan's Proton
i get Unable to launch game, please verify your game data.

then i change it to 5.0-9 the launcher appears, i get cloud save conflict, i skip it. then it closes itself.
then i change it back to Brendan's, i get cloud sync error, skip. and it launches.
i get activation error, i quit the game.
after that the cloud override from Rockstar Launcher will appear i choose the right one.
after that it runs just with the AMD driver pop-up but it runs :)!

thanks for the hard work Brendan!

i run manjaro and im on stable Nvidia, i did not change the driver to beta yet

Well how about that, If doing it exactly as McMarius11 says I got it working.
Running on Arch Kernel 5.6.15
Nvidia RTX 2060 Super driver 440.82
No specific launch options just running "gamemoderun %command%" as per usual.

So the game runs, but not sure that I would play it just yet. Got pretty bad stuttering both graphic and sound. Needed to turn it down pretty far to look somewhat playable, so with everything on Medium in the benchmark i got Min fps: 5, Average: 44, max 270.
That in window mode 1920x1080.

So this is looking really promising. Thanks for all your work @mrpippy

WINED3D did not work for me, however the game does work with the tweak that @Tk-Glitch recommended: WINEDLLOVERRIDES="dxgi=n,b" as a launch option.

Without this, seems that when winex11drv has a brainfart: 7891.284:03e4:03e8:fixme:vulkan:X11DRV_vkCreateWin32SurfaceKHR Application requires child window rendering, which is not implemented yet!, this results in a E_NOTIMPL - 0x80004001 error on the application level, which is what ends up spiraling into the write that causes a fault at 0x7B00FC3E. (That is in kernelbase.dll:"RaiseException", right after calling into RtlRaiseException)

This seems to be a known wine issue: https://bugs.winehq.org/show_bug.cgi?id=45277
Which I did initially get blocked by, despite running the latest nvidia vulkan beta drivers: 440.66.15-1

@topsyandpip56 I think this is the same issue as what you are having.

Impressive work Brendan (@mrpippy ), thank you :smiley:

Small heads up for people using mesa/RADV: at least on Navi, ACO has issues with LOD transitions and irrecoverable hangs. Using llvm instead has been - so far - flawless.

Small heads up for people using mesa/RADV: at least on Navi, ACO has issues with LOD transitions and irrecoverable hangs. Using llvm instead has been - so far - flawless.

I'm surprised you can even get that far. On Vega10/llvm there's the earlier referenced pagefault in the current proton rdr2 build. With the older rdr2-2 build, I had some better progress but always hit the same "social club failed to initialize graphics device" in-game.

With just WINEDLLOVERRIDES="dxgi=n,b" as a launch option it works, thank you @dt-zero

Performance is really bad on Nvidia 440.66.15, around 15 FPS in the benchmark, but it seems the GPU is only working at about 45%. It's the same kind of thing that was happening with Doom Eternal.

No luck yet for me even with PROTON_LOG=1 WINEDLLOVERRIDES="dxgi=n,b" taskset -c 0-7 %command% I'm getting the unable to launch game crash. Interestingly, before I see this as well:

Log:
rdr2.log.zip

if i run it with Brendan's Proton
i get Unable to launch game, please verify your game data.

then i change it to 5.0-9 the launcher appears, i get cloud save conflict, i skip it. then it closes itself.
then i change it back to Brendan's, i get cloud sync error, skip. and it launches.
i get activation error, i quit the game.
after that the cloud override from Rockstar Launcher will appear i choose the right one.
after that it runs just with the AMD driver pop-up but it runs :)!

thanks for the hard work Brendan!

i run manjaro and im on stable Nvidia, i did not change the driver to beta yet

I did exactly this, but in the end the game still didn't start.
Then after doing this, I added the WINEDLLOVERRIDES=dxgi=n,b launch option, and now I'm currently on the brightness calibration, in-game.
I will try to play and update my post.

I was able to get in-game, change settings, everything seems to work as it should. However, the frame rate I got in-game was only 14, so it's not really playable for me at this point, but it does work. The menus on the other hand were very smooth, same with the video at the start of the story.

It seems to be borked on nvidia regarding performance. I also got 14fps on my geforce.
No problem on my radeon (5700XT) though, even maxed out:

1080p is pretty limiting (also vsync was enabled which sets a 60fps framerate cap due to Brendan's hack, even though my display is 144Hz 🐸 ).

if i run it with Brendan's Proton
i get Unable to launch game, please verify your game data.

I can reproduce that if I disable native d3d11. Weird.

Oh, so now with a prefix created with Proton 5.0-9, and then running with rdr-3 proton and WINEDLLOVERRIDES="dxgi=n,b" I get a bit further!

I get the initial loading screen (with the bar at the bottom of the window) and then see a second of the intro video (with smoke etc.), and then the rdr2 window closes, reopens as a black window for a second and then it exits.

Log:
rdr2.log.zip

Also tried taskset, but sadly no difference there.

Looking at the benchmark output, the game really thinks I'm using an AMD GPU, it's strange :
GPU: AMD GeForce RTX 2080

@jalabb That's part of Brendan's hack: https://github.com/mrpippy/wine/commit/911cdd53a1bf7b569bebaadc1bb6ecf616586804
So most likely expected.

git clone https://github.com/Frogging-Family/nvidia-all.git
cd nvidia-all
makepkg -si
sudo mkinitcpio -P

Tried this, but DKMS will never build for me correctly. I dont know what it is. I have the kernel headers installed.

@mintylinux If you have a 5.6 kernel it might not be compatible. There's a patch here https://gitlab.com/snippets/1945940 that you can use on the kernel module sources to make it work with 5.6

@mintylinux If you have a 5.6 kernel it might not be compatible. There's a patch here https://gitlab.com/snippets/1945940 that you can use on the kernel module sources to make it work with 5.6

Thanks! i patched the nvidia files with the kernel patch, and it installed fine...but now it seems like the progress for trying to run RDR2 on my computer has back tracked. Last night i could get it to load the window and the loading bar, then it would show the smoke on the screen for a second or two and freeze. Now i cant even get the window to open.

@mintylinux You should probably try to follow the procedures that @McMarius11 suggested on a fresh compatdata and use WINEDLLOVERRIDES=dxgi=n,b in the launch options. That's at least how I was able to get it running, any other way I tried I would experience some sort of variation of what you just described is happening now.

@mintylinux You should probably try to follow the procedures that @McMarius11 suggested on a fresh compatdata and use WINEDLLOVERRIDES=dxgi=n,b in the launch options. That's at least how I was able to get it running, any other way I tried I would experience some sort of variation of what you just described is happening now.

so what do you mean by fresh compatdata? i tried running the game with a different version of proton, and then switched back to the rdr2 proton, and i did add this to my launch options.

Hmm, I can't Sign in:

Someone with similar problem?

@mintylinux You should probably try to follow the procedures that @McMarius11 suggested on a fresh compatdata and use WINEDLLOVERRIDES=dxgi=n,b in the launch options. That's at least how I was able to get it running, any other way I tried I would experience some sort of variation of what you just described is happening now.

so what do you mean by fresh compatdata? i tried running the game with a different version of proton, and then switched back to the rdr2 proton, and i did add this to my launch options.

He means this

In addition, before launching with this Proton build, delete any previous compatdata for the game. This would usually be at ~/.steam/steam/steamapps/compatdata/1174180/

Hmm, I can't Sign in:

Someone with similar problem?

No, never had this problem

@mintylinux You should probably try to follow the procedures that @McMarius11 suggested on a fresh compatdata and use WINEDLLOVERRIDES=dxgi=n,b in the launch options. That's at least how I was able to get it running, any other way I tried I would experience some sort of variation of what you just described is happening now.

so what do you mean by fresh compatdata? i tried running the game with a different version of proton, and then switched back to the rdr2 proton, and i did add this to my launch options.

He means this

In addition, before launching with this Proton build, delete any previous compatdata for the game. This would usually be at ~/.steam/steam/steamapps/compatdata/1174180/

will try that, thanks!

@mintylinux You should probably try to follow the procedures that @McMarius11 suggested on a fresh compatdata and use WINEDLLOVERRIDES=dxgi=n,b in the launch options. That's at least how I was able to get it running, any other way I tried I would experience some sort of variation of what you just described is happening now.

so what do you mean by fresh compatdata? i tried running the game with a different version of proton, and then switched back to the rdr2 proton, and i did add this to my launch options.

He means this

In addition, before launching with this Proton build, delete any previous compatdata for the game. This would usually be at ~/.steam/steam/steamapps/compatdata/1174180/

Ok, well i keep trying to start it now, but it keeps saying please verify game data. over and over and over again.

Hmm, I can't Sign in:

Someone with similar problem?

No, never had this problem

I tried over 5 times to no avail...

@mintylinux You should probably try to follow the procedures that @McMarius11 suggested on a fresh compatdata and use WINEDLLOVERRIDES=dxgi=n,b in the launch options. That's at least how I was able to get it running, any other way I tried I would experience some sort of variation of what you just described is happening now.

so what do you mean by fresh compatdata? i tried running the game with a different version of proton, and then switched back to the rdr2 proton, and i did add this to my launch options.

He means this
In addition, before launching with this Proton build, delete any previous compatdata for the game. This would usually be at ~/.steam/steam/steamapps/compatdata/1174180/

Ok, well i keep trying to start it now, but it keeps saying please verify game data. over and over and over again.

If you prefix is cleared, start the game with
Proton 5.0-9 continue the dialog until it crashes.
Use Brendon's Proton after that.

@mintylinux You should probably try to follow the procedures that @McMarius11 suggested on a fresh compatdata and use WINEDLLOVERRIDES=dxgi=n,b in the launch options. That's at least how I was able to get it running, any other way I tried I would experience some sort of variation of what you just described is happening now.

so what do you mean by fresh compatdata? i tried running the game with a different version of proton, and then switched back to the rdr2 proton, and i did add this to my launch options.

He means this
In addition, before launching with this Proton build, delete any previous compatdata for the game. This would usually be at ~/.steam/steam/steamapps/compatdata/1174180/

Ok, well i keep trying to start it now, but it keeps saying please verify game data. over and over and over again.

If you prefix is cleared, start the game with
Proton 5.0-9 continue the dialog until it crashes.
Use Brendon's Proton after that.

Trying now

@mintylinux You should probably try to follow the procedures that @McMarius11 suggested on a fresh compatdata and use WINEDLLOVERRIDES=dxgi=n,b in the launch options. That's at least how I was able to get it running, any other way I tried I would experience some sort of variation of what you just described is happening now.

so what do you mean by fresh compatdata? i tried running the game with a different version of proton, and then switched back to the rdr2 proton, and i did add this to my launch options.

He means this
In addition, before launching with this Proton build, delete any previous compatdata for the game. This would usually be at ~/.steam/steam/steamapps/compatdata/1174180/

Ok, well i keep trying to start it now, but it keeps saying please verify game data. over and over and over again.

If you prefix is cleared, start the game with
Proton 5.0-9 continue the dialog until it crashes.
Use Brendon's Proton after that.

Yeah that's a no go for me. Keeps crashing after the social club window.

In my case, doesn't work (using rdr2-3). The game doesn't start (no launcher even). Strangely, the proton log is empty.

````

... cat ~/steam-1174180.log

Proton: 1591829148 proton-5.0-8
SteamGameId: 1174180
Command: ['/media/storage/games/steamapps/common/Red Dead Redemption 2/PlayRDR2.exe']

Options: {'forcelgadd'}

````

My system is:
Manjaro Linux 20.0.3 Nvidia driver 440.82

I have the game working
GPU: Radeon RX590
OS: Arch Linux
DE: KDE Plasma 5

Test results via AMDVLK-PRO

Test results via AMDVLK-LLVM

Message when trying to log in to an online game

<Responding to the immediately previous comment>

The frame rate looks so low, is it because of the GPU?
By the way, shouldn't you use ACO instead of LLVM?

It seems to work on my ManjaroLinux 20.0.3 (Lysia), Kernel 5.4.43-1-MANJARO, nvidia 440.82, but...
It wants to use my laptop integrated intel graphic card...

Any tips ?
(For fun: I "love" to see steam tell me I played 120min on RDR2 even if I never saw a single frame of the game except the rockstar launcher :) )

Just click on OK. I get the same message but on my pc (ryzen 2600 paired with a 6gb GTX 1060 and I get an average on 20 fps at 720p with mid to low details. On windows I was getting around 50 fps at 1080p with high to ultra details.

launching steam like this:
STEAM_RUNTIME_HEAVY=1 __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia steam
I have the AMD driver warning even if I have no AMD card...

I'm starting to see smoke (intro video not my laptop) few seconds and crash... :(

I repaired the installation, cleaned the compatdata/1174180
I got this error:

Restarted immedially, activation error
Switched back to Proton 5.0-9, crash after launcher
Switched back to Brendon's Proton and I get the welcome screen !
I make some benchmarks, thanks for your work !

With Brendan's Proton I get Unable to launch game, please verify your game
data.
Then I switch to 5.0-9 and get post-launcher where game silently exits.
Then I switch back to Brendan's Proton, this gets me a short glimpse of red
Rockstar logo and then game
window closes and game silently exits. Looks like 16GB RAM is not enough
for the game to run.

On Sat, Jun 13, 2020 at 9:38 PM Echoz notifications@github.com wrote:

if i run it with Brendan's Proton
i get Unable to launch game, please verify your game data.

then i change it to 5.0-9 the launcher appears, i get cloud save conflict,
i skip it. then it closes itself.
then i change it back to Brendan's, i get cloud sync error, skip. and it
launches.
i get activation error, i quit the game.
after that the cloud override from Rockstar Launcher will appear i choose
the right one.
after that it runs just with the AMD driver pop-up but it runs :)!

thanks for the hard work Brendan!

i run manjaro and im on stable Nvidia, i did not change the driver to beta
yet

I did exactly this, but in the end the game still didn't start.
Then after doing this, I added the WINEDLLOVERRIDES=dxgi=n,b launch
option, and now I'm currently on the brightness calibration, in-game.
I will try to play and update my post.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/3291#issuecomment-643661443,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAABPUZXQIELOHJ64Z2VP4LRWPBTPANCNFSM4JV54AXQ
.

WINEDLLOVERRIDES=dxgi=n,b does help getting to a progressbar but then the
game hangs without any activity consuming all CPU.

On Sun, Jun 14, 2020 at 1:01 PM Sergey Lapin slapinid@gmail.com wrote:

With Brendan's Proton I get Unable to launch game, please verify your
game data.
Then I switch to 5.0-9 and get post-launcher where game silently exits.
Then I switch back to Brendan's Proton, this gets me a short glimpse of
red Rockstar logo and then game
window closes and game silently exits. Looks like 16GB RAM is not enough
for the game to run.

On Sat, Jun 13, 2020 at 9:38 PM Echoz notifications@github.com wrote:

if i run it with Brendan's Proton
i get Unable to launch game, please verify your game data.

then i change it to 5.0-9 the launcher appears, i get cloud save
conflict, i skip it. then it closes itself.
then i change it back to Brendan's, i get cloud sync error, skip. and it
launches.
i get activation error, i quit the game.
after that the cloud override from Rockstar Launcher will appear i choose
the right one.
after that it runs just with the AMD driver pop-up but it runs :)!

thanks for the hard work Brendan!

i run manjaro and im on stable Nvidia, i did not change the driver to
beta yet

I did exactly this, but in the end the game still didn't start.
Then after doing this, I added the WINEDLLOVERRIDES=dxgi=n,b launch
option, and now I'm currently on the brightness calibration, in-game.
I will try to play and update my post.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/3291#issuecomment-643661443,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAABPUZXQIELOHJ64Z2VP4LRWPBTPANCNFSM4JV54AXQ
.

Without WINEDLLOVERRIDES=dxgi=n,b %command%, the game silently dies

Getting this message after the graphics driver error

Flightlessmango is getting decent performance on Nvidia somehow...
https://youtu.be/5DTxEr9CaHI

I still get this error:

I cleared download cache, validated the game files, tried to launch the game with different startup options and without any options at all, cleared compatdata to no avail. Is this step mandatory? I never tried the game on Windows and I don't know.

@mozo78 have you linked your Steam account to you Rockstar Social Club account? If you do it should log you in automatically when you launch the game.

Using the older rdr2-2 wine build with patched Mesa (used via LD_LIBRARY_PATH, LIBGL_DRIVERS_PATH and VK_ICD_FILENAMES) it is impossible to get SocialClubVulkanLayer.dll to successfully inject which always causes Error 18 in game due to drm. The most annoying part is that the game has clearly successfully launched using Vulkan to get to this point; it just refuses to go any further because the overlay won't inject.

Trying to use the newer proton build is a non-starter as I have referenced here earlier, it hits a pagefault before even launching the game, I don't know why.

I repaired the installation, cleaned the compatdata/1174180
I got this error:

Restarted immedially, activation error
Switched back to Proton 5.0-9, crash after launcher
Switched back to Brendon's Proton and I get the welcome screen !
I make some benchmarks, thanks for your work !

Game was crashing for me at the smoke/gunshot intro, but running steam with the heavy runtime gets through it. Thanks!

I am able to play the game by using WINEDLLOVERRIDES=dxgi=n,b %command% and switching between Proton 5.0-9 and the custom proton version:

https://www.codeweavers.com/xfer/bshanks/public/proton-5.0-rdr2-3.tar.gz
password: public

Manjaro 64bit on Kernel 5.7

Edit: Download the NVIDIA Beta drivers or the performance will be inadequate.

In my case, doesn't work (using rdr2-3). The game doesn't start (no launcher even). Strangely, the proton log is empty.

... cat ~/steam-1174180.log 
======================
Proton: 1591829148 proton-5.0-8
SteamGameId: 1174180
Command: ['/media/storage/games/steamapps/common/Red Dead Redemption 2/PlayRDR2.exe']
Options: {'forcelgadd'}
======================

My system is:

Manjaro Linux 20.0.3
Nvidia driver 440.82

Still didn't get it working... However some progress is there.

1. Reformatted my HDD where I installed the game to ext4 (was NTFS)
2. Ran the game (with WINEDLLOVERRIDES=dxgi=n,b %command%) option -> it immediately went to launching social club
3. Signed in
4. Error window popped up (screenshot No. 1)
5. Meanwhile immediately R launcher started (small squared, with yellow R logo) - progress bar went to the end
6. Launcher is gone. One more runtime error pop-up (screenshot No. 2)
7. Immediately R launcher started (the bigger one, with animated logo)
8. Launcher is gone
9. Error pop-up: Unable to launch game, please verify your game data (the compatdata was cleaned before launch) (screenshot No. 3)
10. Any ideas?

Log:
steam-1174180.log.zip
(FYI: steamdata is in ~/.steam, but the game is stored at /media/storage/steamapps/..)

Screenshots:

I was able to install the game flawlessly with Proton 5.0-9 in a clean prefix. Then upon startup it will crash. Then I switched to the custom wine rdr3 build and the game will launch, tho then crash at the intro video when the smoke is coming. Steam Heavy Runtime nor taskset nor mf libraries did help.

Patched my mesa and tried it on both kernel 5.7 and 5.6 works both up until the intro.

R9 3900X, Vega 64

Any recommendations for users who own the game through Rockstar Games Launcher instead of Steam?

Any recommendations for users who own the game through Rockstar Games Launcher instead of Steam?

Try Lutris with the custom Proton version.

I have tested the custom Proton version through Lutris extensively and
unfortunately myself and one other person so far that I have contacted are
met with a pagefault as the seccomp filters don't quite operate correctly
this way. The issue is the same if adding the launcher as a non-steam game
and using it via steam itself.

On Sun, 14 Jun 2020 at 19:07, derbrachialist notifications@github.com
wrote:

Any recommendations for users who own the game through Rockstar Games
Launcher instead of Steam?

Try Lutris with the custom Proton version.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/3291#issuecomment-643801373,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABTLIYYHYSKYPTT4LVZTYVLRWUGXHANCNFSM4JV54AXQ
.

Sorry, I guess my question should be how do I achieve that?

I've got the proton version downloaded, both in the steam compatibilitytools.d directory, as well as in the Lutris runners directory. Lutris does not automatically detect this version of proton (however it does automatically detect 5.9 GE which is also in compatibilitytools.d). Lutris does give the option to chose a custom path to the runner, but I'm not sure which file to choose.

Sorry, I guess my question should be how do I achieve that?

I've got the proton version downloaded, both in the steam compatibilitytools.d directory, as well as in the Lutris runners directory. Lutris does not automatically detect this version of proton (however it does automatically detect 5.9 GE which is also in compatibilitytools.d). Lutris does give the option to chose a custom path to the runner, but I'm not sure which file to choose.

Symlink or copy the 'dist' folder inside the proton config to ~/.local/share/lutris/runners/.
I don't expect it to work but you are welcome to try.

Had to go through this process (https://github.com/ValveSoftware/Proton/issues/3291#issuecomment-643661443 ) to get the game running, with an rx5700 xt.

Framerate is very low but isn't stuttery (frametimes are pretty much a flat line for the most part), CPU usage never hits over 80 percent on any or the cores( they're normally running between 50-70%), GPU is always on low usage and overclocking ram doesn't seem to do any difference.

Tried some possible fixes with @Tk-Glitch 's help but only swapping between proton versions seemed to get the game running for me. I also just noticed on my last couple benchmarks that the GPU core clock seems to be stuck at 800MHz.

On a side note, it seems like Cloud Saves work fine (at least importing them).

@topsyandpip56

try disabling the lutris runtime under system options if it doesn't work with custom proton version.

@fsyy
Thanks for the tip, but it's not a runtime issue. It makes no difference. There's some kind of sequencing error when using that Proton wine build without the official steam version of the game, even as a non-steam game in steam.

wine: Unhandled page fault on read access to 0000000000000010 at address 000000007B00FC3E (thread 03dc), starting debugger... wine: enabling seccomp syscall filters for RDR2. SIGSYS, rax 19 r10 ffffffffffffffff rdx 7 r8 3495dd90 r9 8 rdi 140000000 rsi 2 rip 0x142da201b

I'm gonna make myself look stupid to maybe help the others who experienced atrocious performance (even with the latest Nvidia beta drivers).
Turn off logging, especially if you had +vulkan,+dxgi in user_settings.py. If you got the game running just delete that file. I went from about 10-20 FPS to a much more playable average of 60.

@chris-echoz Sorry what file are you talking about? I have removed the launch option for logging. But is there more then that? I only find user_settings_sample.py.
Still running somewhere in between 5fps and 250fps

@chris-echoz That did it! Thank you so much!

@Spunkt user_settings.py. If you don't have it that isn't the problem. Me and probably a few others had enabled the log options to help out with debugging.
If you're experiencing bad peformance anyway, make sure you have 440.66.15 and not the stable 440.82 driver.

Okey, that made it a lot better, with 440.66.15 I got a pretty stable 60 fps. Not really sure why tho, shouldn't 440.82 be a later driver then 440.66?

@Spunkt 440.82 technically is a higher version number, but it's a stable driver, where as 440.66.15 is a beta driver that contains more experimental optimizations for vulkan, and is also more recent.

Works beautifully with FX-8300 and RX 590 with AMDGPU-PRO drivers. Haven't tested with mesa yet because I'm too lazy to patch it.

Thank you for your hard work!

It's working for me both on RADV/mesa-aco and amdgpu-pro 20 up until the smoke starts in the beginning of the game. Then the window quits and another one opens that is black just to quit again. After that the game quits.

Mangohud works as well, at least for the brief moment I am in.

Do you have any other extraordinary stuff installed? I run a pretty clean Manjaro Budgie install with mesa 20.2.0.

This is the moment it crashes.

Interesting, you're on Zen as well. Maybe this has to do with the CPU? I have the same crash with a Threadripper. But with nvidia here, so likely not due to the GPU.

@ntropy83 I have pretty much the same hardware as you, did you patch mesa? did you set this WINEDLLOVERRIDES=dxgi=n,b in the launch commands?

@ntropy83 I have pretty much the same hardware as you, did you patch mesa? did you set this WINEDLLOVERRIDES=dxgi=n,b in the launch commands?

Yes and yes, without the dll override it wont launch at all. Mesa I patched within pamac. Added the patch command in the pkgfile under prepare() and during compilation it says the patch applied.

I tried running the game with taskset and also tried to install media foundation libs, since I know this crash behaviour with intro movies from the Unreal engine, but that didnt do the trick.

@ntropy83
Try placing a config.xml file which has 1920x1080 and Vulkan specifically set.

@ntropy83
Try placing a config.xml file which has 1920x1080 and Vulkan specifically set.

This was a good idea, I think something happened:

It says "Social Club could not initialize graphics adapter" and from here you can only quit the game.

I have done two things, I created a settings.xml in:
../SteamLibrary/steamapps/compatdata/1174180/pfx/drive_c/users/steamuser/My Documents/Rockstar Games/Red Dead Redemption 2/Settings/settings.xml
It has this content:
https://pastebin.com/75duK5U2
Here may be already be the problem, since there are options enabled that prolly wont work in Linux.

The second thing I did was starting steam with
STEAM_RUNTIME=0 steam
To get steam to work this way, I searched for missing libs with and installed them:
$ cd ~/.steam/root/ubuntu12_32

$ file * | grep ELF | cut -d: -f1 | LD_LIBRARY_PATH=. xargs ldd | grep 'not found' | sort | uniq

I have to start the game with these options:
RADV_PERFTEST=aco PROTON_LOG=1 MANGOHUD=1 WINEDLLOVERRIDES=dxgi=n,b %command%
If I remove only one, even PROTON_LOG it will crash again at the smoke screen. So does the change to llvm or amdgpu-pro.

Very strange, not sure if this is an improvement now or not.

@ntropy83 Well this is now very interesting because you have the exact same issue that I had on the older wine-rdr2-2 build. In my investigation I found that this code 18 error was being caused because SocialClubVulkanOverlay.dll was not injecting, so the game's DRM was hitting that error 18. Unfortunately I really can't help you anymore because we're on the exact same page.

Perhaps we patched our mesa's wrong?

Edit: Incidentally I also notice we are both using Vega 64 cards. Might be pertinent information.

@ntropy83 Well this is now very interesting because you have the exact same issue that I had on the older wine-rdr2-2 build. In my investigation I found that this code 18 error was being caused because SocialClubVulkanOverlay.dll was not injecting, so the game's DRM was hitting that error 18. Unfortunately I really can't help you anymore because we're on the exact same page.

Perhaps we patched our mesa's wrong?

Edit: Incidentally I also notice we are both using Vega 64 cards. Might be pertinent information.

OK that is good to know at least I am not alone with my problem :).

The social club vulkan overlay would be probably the popup showing up in the upper right corner, telling that your nickname is logged in. That is missing for me, so here could be the problem.

I have done two things, I created a settings.xml in:
../SteamLibrary/steamapps/compatdata/1174180/pfx/drive_c/users/steamuser/My Documents/Rockstar Games/Red Dead Redemption 2/Settings/settings.xml
It has this content:
https://pastebin.com/75duK5U2
Here may be already be the problem, since there are options enabled that prolly wont work in Linux.

Interesting, I've tried to do the same (PROTON_LOG=1 WINEDLLOVERRIDES=dxgi=n,b, create that settings.xml) but no luck so far. Would you mind sharing a log of a working run, ideally with +vulkan wine logs?

Mine crashes right around QueryDisplayConfig:
1241.413:04bc:0560:trace:vulkan:wine_vkDestroyImage 0x3b44c8d0, 0x7f35de98e2c8, (nil) 1241.515:0658:065c:fixme:system:GetDisplayConfigBufferSizes (0x2 0x22e6d4 0x22e6d0): stub SIGSYS, rax 19 r10 ffffffffffffffff rdx 7 r8 462eed50 r9 8 rdi 140000000 rsi 3 rip 0x142da201b NtQueryInformationProcess class 7 SIGSYS, rax 19 r10 ffffffffffffffff rdx 1e r8 462eed50 r9 8 rdi 140000000 rsi 3 rip 0x142da201b NtQueryInformationProcess class 1e SIGSYS, rax 19 r10 ffffffffffffffff rdx 1f r8 462eed50 r9 4 rdi 140000000 rsi 3 rip 0x142da201b NtQueryInformationProcess class 1f SIGSYS, rax 36 r10 23 rdx 462eed50 r8 2 r9 0 rdi 140000000 rsi 3 rip 0x142da1fc3 NtQuerySystemInformation class 23 SIGSYS, rax eb r10 fffffffffffffffe rdx 462eed70 r8 a0042ee r9 0 rdi 140000000 rsi 3 rip 0x142da215a NtGetContextThread: ContextFlags 100010 rcx 0x142da215a 1245.545:04bc:0560:fixme:system:QueryDisplayConfig (00000002 0x365cfbf8 0x365cb3b0 0x365cfc00 0x365c73b0 (nil)) 1245.552:04bc:0560:trace:vulkan:wine_vkDestroyImageView 0x3b44c8d0, 0x7f35dce52fa8, (nil)

rdr2.log.zip

How did you determine <videoCardDescription>AMD AMD RADV VEGA10 (ACO)</videoCardDescription>? I tried a few variations with my gpu name (via vulkaninfo) plus NVIDIA/AMD in front of that, but no luck.

Thanks to everyone for testing, I've got a new build that should fix the main issue that required switching Proton builds.

https://www.codeweavers.com/xfer/bshanks/public/proton-5.0-rdr2-4.tar.gz
password: public

Download the file, quit Steam, and uncompress it in your compatibilitytools.d directory, likely ~/.steam/steam/compatibilitytools.d/
Then force it to be used for RDR2 in Steam, with "Force the use of a specific Steam Play compatibility tool"

Before launching with this Proton build, delete any previous compatdata for the game. This would usually be at ~/.steam/steam/steamapps/compatdata/1174180/

Also there shouldn't be a need for any WINEDLLOVERRIDES. If things aren't working though, WINEDLLOVERRIDES=dxgi=n,b might be worth trying.

There's more info about required graphics drivers and known issues on my original post

The problem with rdr2-3 is that the default prefix wasn't getting the winevulkan.json file needed for the official Vulkan loader (which installs as a prerequisite with RDR2), so once the loader installed, Vulkan (including dxvk for the launcher) wouldn't work.

Installing the game under 5.0-9 actually doesn't install the official loader correctly (there's a vulkan-1.dll version change needed). And without the official loader installed, RDR2 either hangs during the smoke or gets stuck at the Social Club graphics adapter error.

I pushed the Mesa/RADV fix yesterday, the game should no longer crash during shaders compilation. The fix will be backported to next Mesa 20.1.2.

Removed the pfx folder and tried run the new build. Installed fine, intro sequence was a bit slow loading but got past it. But now I never get past an Activation error. Also needed the WINEDLLOVERRIDES=dxgi=n,b to be able to start at all.

Did the same thing once more and now I was able to get into the game and everything seems to be running fine. Well.. as well as it did yesterday

Runs great for me now with rdr2-4! Just worked the first try. I also still need WINEDLLOVERRIDES=dxgi=n,b or it doesn't start.

I'm just getting 30-40fps though in the benchmark at 1920x1080, looks like nvidia irqs are a bit slow? At medium/low settings, and taskset to cpus 1,3,5,7 to stop it from switching the process around all the time.

Edit: Oh, I think I'm a driver version behind, testing 440.66.15 now.

Edit2: And it runs great with latest nvidia vulkan beta driver, I was just on 440.66.14 before, from 440.66.15 onwards it runs with 56 FPS on highest settings. Pretty amazing!

Any chance we could get a version with support for 2560x1440 and 3840x2160? That'd make it run perfectly for most people I think.

How did you determine <videoCardDescription>AMD AMD RADV VEGA10 (ACO)</videoCardDescription>? I tried a few variations with my gpu name (via vulkaninfo) plus NVIDIA/AMD in front of that, but no luck.

I found a webpage online that creates a default settings.xml for RDR2 and that got my GPU info. (https://rdr2.forceflow.be/)

rdr2-4 works for me too !! Many many thanks @mrpippy, you are a genius !!! :)

I reinstalled the prefix and it went smooth now, pretty quick install with loading bars this time. Then the game hangs again at the smoke screen, but continues after 5 seconds and loads normally. On first launch I got the activation error, second launch worked then.

I briefly started the first chapter and had ingame around 60 fps constantly at half the gpu freq speed. I only remote login into my home gaming PC from work on a bad internet connection and then it crashed. Now I have to call my mother-in-law to turn the PC off at home :D.

Will give it a more extensive testing this evening.

https://www.codeweavers.com/xfer/bshanks/public/proton-5.0-rdr2-4.tar.gz
password: public

Also there shouldn't be a need for any WINEDLLOVERRIDES. If things aren't working though, WINEDLLOVERRIDES=dxgi=n,b might be worth trying.

It works with clearing the compatdata directory and the "WINEDLLOVERRIDES=dxgi=n,b %command%" launch parameters! Great work, thanks!

Without dll override, the launcher works, but the game silently crashes.

Thanks for the update Brendan.
Sadly the new proton build is still not working on non-Steam versions of the game.
wine: Unhandled page fault on read access to 0000000000000010 at address 000000007B00FC3E (thread 03f0), starting debugger...

Thanks to everyone for testing, I've got a new build that should fix the main issue that required switching Proton builds.

https://www.codeweavers.com/xfer/bshanks/public/proton-5.0-rdr2-4.tar.gz

password: public

Download the file, quit Steam, and uncompress it in your compatibilitytools.d directory, likely ~/.steam/steam/compatibilitytools.d/

Then force it to be used for RDR2 in Steam, with "Force the use of a specific Steam Play compatibility tool"

Before launching with this Proton build, delete any previous compatdata for the game. This would usually be at ~/.steam/steam/steamapps/compatdata/1174180/

Also there shouldn't be a need for any WINEDLLOVERRIDES. If things aren't working though, WINEDLLOVERRIDES=dxgi=n,b might be worth trying.

There's more info about required graphics drivers and known issues on my original post

---

The problem with rdr2-3 is that the default prefix wasn't getting the winevulkan.json file needed for the official Vulkan loader (which installs as a prerequisite with RDR2), so once the loader installed, Vulkan (including dxvk for the launcher) wouldn't work.

Installing the game under 5.0-9 actually doesn't install the official loader correctly (there's a vulkan-1.dll version change needed). And without the official loader installed, RDR2 either hangs during the smoke or gets stuck at the Social Club graphics adapter error.

Do we specifically need the driver version 440.66.15 or does a newer version works aswell?(440.82)

Sorry if this is a stupid question, I just switched to Linux 3 days ago

Do we specifically need the driver version 440.66.15 or does a newer version works aswell?(440.82)

Sorry if this is a stupid question, I just switched to Linux 3 days ago

Not a stupid question, Nvidias driver naming scheme is a bit confusing and higher numbers don't always mean newer. You do need 440.66.15 specifically, it has some changes that are not yet in the 440.82 driver.

New proton version worked right away and https://github.com/ValveSoftware/Proton/issues/3291#issuecomment-644193811 was spot on, the Winedebug flags were eating my performance away

@CrazyHater 440.66.15 is actually almost two months newer than 440.82. As ah- said, it's just Nvidia's confusing versioning schemes. I'm sure it's very clear to them internally 🐸

The new build from Brendan works just as good as the previous version on my end, thanks! I'll be patiently waiting for other resolutions support, and for the changes to be available either in proton's or mrpippy's wine repos.

thanks for the new version, the cloud conflict takes some retries till if finally works

WINED3D did not work for me, however the game does work with the tweak that @Tk-Glitch recommended: WINEDLLOVERRIDES="dxgi=n,b" as a launch option.

Without this, seems that when winex11drv has a brainfart: 7891.284:03e4:03e8:fixme:vulkan:X11DRV_vkCreateWin32SurfaceKHR Application requires child window rendering, which is not implemented yet!, this results in a E_NOTIMPL - 0x80004001 error on the application level, which is what ends up spiraling into the write that causes a fault at 0x7B00FC3E. (That is in kernelbase.dll:"RaiseException", right after calling into RtlRaiseException)

This seems to be a known wine issue: https://bugs.winehq.org/show_bug.cgi?id=45277
Which I did initially get blocked by, despite running the latest nvidia vulkan beta drivers: 440.66.15-1

@topsyandpip56 I think this is the same issue as what you are having.

Impressive work Brendan (@mrpippy ), thank you smiley

Damn, can't believe I didn't notice this days ago. You are right, this is the exact error I'm having even in the current proton 4 build. However, for me, the dxgi n,b override doesn't seem to do anything. Obviously declaring "n" only stops even the launcher being able to open. Anything obvious that I'm missing?

Running the game worked on my first attempt with rdr2-4 in a clean prefix and launch options: WINEDLLOVERRIDES="dxgi=n,b" %command%.
I did get an activation error, but this seems to occur randomly anyway. Next attempt I got to the menu.

Some issues I've experienced playing the game for a few hours with, mostly rdr2-3, but also rdr2-4:

• Windowed borderless does not stretch to the full resolution of the monitor, but rather creates a 1920x1080 window without a border.
• Fullscreen mode works initially, and stretches up to 2560x1440, but if I switch out of the game it returns to a borderless window with the size of 1920x1080. If I return focus to the game, it stretches back to 2560x1440, however the viewport stays the same (see screenshot below).
  
  The solution to this for me has been to first switch the game out of fullscreen (alt+enter), and then back, however one caveat with this is that the game is highly likely to crash while doing this. When it crashes from switching I get this error (to clarify I am running the game with Vulkan):
  
• I attempted to solve this by setting proton to use a virtual desktop at 2560x1440 in winecfg, however this had some peculiar results. Initially the launcher displays perfectly fine in a full screen virtual wine desktop, but as soon as I dismiss the minimum system requirements warning and the game actually opens, the virtual desktop changes its size to 5120x1440, spanning across both of my monitors and instead displaying as a window with a border. I'm not sure if this is a bug in wine or behavior that is supposed to happen, but my understanding was that applications running in wine would not be allowed to modify the size of the virtual desktop. Nonetheless, the game displays as if it were run in windowed borderless in this mode, i.e. not stretching at all.
• After a while of playing the game simply crashes with an error, I'm not entirely sure if there is any correlation, but this seemed to happen more often after I increased the graphics from low to medium, same with the crash while switching in and out of full screen. I just now got this error while trying to load into the game.
  

Aside from crashing the game while switching in and out of full screen, I've confirmed all of these issues on rdr2-4. I've enabled logging, although not +vulkan,+dxgi, as they make the game unplayable, and will upload logs if it crashes.

Log for the full-screen (DX12) error: https://cloud.echoz.io/s/LdSHBmEKGREkb9a

If you are experimenting GPU hangs with RADV/ACO, you might want to try this potential fix https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5498

It does fix the hangs, but the LOD transitions are still broken. Far less critical of course.

@Tk-Glitch How do I reproduce these broken LOD transitions? It seems like I didn't spot them in the benchmark.

In my case if i add WINEDLLOVERRIDES="dxgi=n,b" %command% with the new shiny build the game starts up in windowed mode, i have a loading bar, then it crashes.
Before starting the game says that my amd drivers are not up to date (i'm using mesa 20.1.1-1 on archlinux)

Regarding the attached log it seems to be a stack overflow (i compressed it)

steam-1174180.log.gz

@hakzsam It seems to only affect some very specific objects, mostly vegetation/bushes. In the benchmark it can be observed in the first scene in the snow for example, where the bush on the left will initially look fine, then past a certain point getting closer to it, it'll become a weird blurry ball of alpha textures. This is on Navi10.
Switching to LLVM fixes it and the bush looks correct at all distances.

I have everything ready but I dont know how to install this patch https://gitlab.freedesktop.org/hakzsam/mesa/-/commit/d044a4476a828f15298336f66404892682cfcfb7

Somebody can help to install that mesa patch?

I have everything ready but I dont know how to install this patch https://gitlab.freedesktop.org/hakzsam/mesa/-/commit/d044a4476a828f15298336f66404892682cfcfb7

Somebody can help to install that mesa patch?

it's been added to mesa-git, no need to patch it yourself anymore https://github.com/ValveSoftware/Proton/issues/3291#issuecomment-644558726

I tested the game on radeon rx480 with mesa-git + https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5498 First 30 minutes of gameplay works with good fps and without visible glitches.

I got all the way in, but I still get stuck at the following screen. I believe I have put the system.xml in the correct location, but I can't be for sure.

@Siigada
According to Brendan that is something to do with the vulkan-1.dll requiring a change (something I tried to do with the only build that will get in-game for me, wine-rdr2-2) and it made no difference. Are you having that same issue with the current proton rdr2-4 build?

Yea, just updated to rdr2-4. Mesa is patched as well

Ok I tried the game. It works insanely amazing and is real fun. Tho I normally only like space games, I think this game will be fun to play :).

The game hard crashes every time for me on mesa-aco. First scene when you start riding on the horse, it hard crashes the whole machine. So I applied the patch by @hakzsam

If you are experimenting GPU hangs with RADV/ACO, you might want to try this potential fix https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5498

I dont know if that worked tho, it seems like it was already applied in mesa-devel, the process at least returned no message that the patch was applied successfully.
I did another thing: the original mesa-patch by @mrpippy gave an error on Hunk 1. So I deleted Hunk 1 and only went with Hunk 2.

Rest of the settings are only rdr2-4 and WINEDLLOVERRIDES=dxgi=n,b

It runs insanely good, utilizes the Vega to its full potential^^. 70 - 90 fps around 10 - 12 ms.
I made a video:

https://www.youtube.com/watch?v=u2SefPhwSgQ

This hack will be implemented into proton by default?

Some success. Thank you, @mrpippy and @hakzsam.

I had an identical situation to @nerzhul's comment where I'd see a loading bar. It would reach near halfway before the window simply disappeared.

After I installed mesa-git from the AUR it started working. The game seemed flawless, though after a few minutes X restarted and I have not yet had an opportunity to check the logs as to why. I will check again tomorrow.

@hakzsam It seems to only affect some very specific objects, mostly vegetation/bushes. In the benchmark it can be observed in the first scene in the snow for example, where the bush on the left will initially look fine, then past a certain point getting closer to it, it'll become a weird blurry ball of alpha textures. This is on Navi10.
Switching to LLVM fixes it and the bush looks correct at all distances.

I recorded short video with this bug https://www.youtube.com/watch?v=uEkk2n972ws&feature=youtu.be It's on aco.

So my issue is the same as one mentioned before..i updated to the rdr2-4, and i am running the launch option WINEDLLOVERRIDES=dxgi=n,b %command%...but my window opens up to the smoke intro, then freezes as it did before, then it generates another window of the game after that, and it crashes.

I am running a Nvidia GTX980, video driver ver 440.66.15. If i run the game without the launch options i dont even get a game window..it just silently crashes.

rdr2-4 worked straight away for me using whatever Nvidia driver is currently on the semi-official Ubuntu PPA (440.64 I think) and my existing 5.0-9 -> rdr2-3 prefix. Quite low framerate though.
Progress :+1:
Switched to the recommended beta driver. Game no longer starts (just closes without error). :facepalm:

Several more attempts at cleaning the prefix and trying different command line options have all resulted in the verify game files error. Good to see it's working for others, but apparently it's not my time yet :smile:

Edit: Turns out I'm an idiot... It wasn't working with the updated driver because the driver hadn't actually installed properly and I was actually running the Nouveau driver as a fallback. Fixed the beta driver and it seems to work quite well.

So my issue is the same as one mentioned before..i updated to the rdr2-4, and i am running the launch option WINEDLLOVERRIDES=dxgi=n,b %command%...but my window opens up to the smoke intro, then freezes as it did before, then it generates another window of the game after that, and it crashes.

I am running a Nvidia GTX980, video driver ver 440.66.15. If i run the game without the launch options i dont even get a game window..it just silently crashes.

Have you tried deleting the compatdata/1174180 directory?

I can confirm the "sporadically crashes after a while with ERR_GFX_STATE" mentioned on https://github.com/ValveSoftware/Proton/issues/3291#issuecomment-644836348
There is no obvious pattern, it seems to happen pretty randomly, sometimes after 30 minutes, sometimes never, sometimes just after launching.

Besides that it runs fine on my manjaro 20.0.3 with rd2-3 and and rd2-4 patch and latest nvidia.

@Tk-Glitch You might want to try https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5525 for the LOD issue, make sure to also apply the GPU hang fix which has been superseded by https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5518

Anyone might know why I still get social club error 18? I've done everything I think I can, anyone else having the problem?

A follow-up re the issue I'm having is that it is possibly hardware or driver-related. No issues with other games but it could still be a red herring. Relevant messages in kernel logs at the time. Note that this was about 45 minutes ago SAST:

Jun 17 19:27:41 <hostname> kernel: [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out!
Jun 17 19:27:41 <hostname> kernel: [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out!
Jun 17 19:27:46 <hostname> kernel: [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out!
Jun 17 19:27:46 <hostname> kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=31675444, emitted seq=31675446
Jun 17 19:27:46 <hostname> kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process RDR2.exe pid 1377969 thread RDR2.exe pid 1378230
Jun 17 19:27:46 <hostname> kernel: amdgpu 0000:0c:00.0: GPU reset begin!

$ uname -a
Linux <hostname> 5.7.2-arch1-1 #1 SMP PREEMPT Wed, 10 Jun 2020 20:36:24 +0000 x86_64 GNU/Linux

If relevant:

AMD Ryzen 9 3900x
AMD RX 5700 XT

I'll follow up again another time. :)

Thank you for the good work, all.

So my issue is the same as one mentioned before..i updated to the rdr2-4, and i am running the launch option WINEDLLOVERRIDES=dxgi=n,b %command%...but my window opens up to the smoke intro, then freezes as it did before, then it generates another window of the game after that, and it crashes.
I am running a Nvidia GTX980, video driver ver 440.66.15. If i run the game without the launch options i dont even get a game window..it just silently crashes.

Have you tried deleting the compatdata/1174180 directory?

Yes i have done that many times...always ending up at the same dead end.

@mintylinux Just a shot in the dark, but maybe you should try deleting the shader cache as well

@hakzsam I can confirm that fixes the issue. Thanks again Samuel!

Played around 1 hour
Proton Version: rdr2-4
Steam Launch options: WINEDLLOVERRIDES=dxgi=n,b %command%
20-40FPS on ultra 1080p
GFX drivers:
lib32-nvidia-utils-full-vulkan-all 440.66.15-1
nvidia-full-vulkan-all 440.66.15-1
nvidia-settings-full-vulkan-all 440.66.15-1
nvidia-utils-full-vulkan-all 440.66.15-1

I had to patch nvidia 440.66 to install on kernel 5.7 as per:
https://forums.developer.nvidia.com/t/nvidia-440-82-kernel-5-7-patch/125815

Getting the Social Club Error, but works after second try.

OS: Arch Linux x86_64 
Kernel: 5.7.2-arch1-1 
Uptime: 6 hours, 29 mins 
Packages: 651 (pacman) 
Shell: bash 5.0.17 
Resolution: 2560x1440, 2560x1440 
WM: i3 
Theme: Adwaita [GTK2/3] 
Icons: Adwaita [GTK2/3] 
Terminal: urxvt 
CPU: AMD Ryzen 9 3900X (24) @ 3.800GHz 
GPU: NVIDIA GeForce RTX 2080 SUPER 
Memory: 3706MiB / 64310MiB 

Those of you able to launch the game in the proton rdr2-4 build with WINEDLLOVERRIDES=dxgi=n,b, which native dll is your Wine actually loading? From where? For me, this option makes no difference. The same fixme:vulkan:X11DRV_vkCreateWin32SurfaceKHR Application requires child window rendering, which is not implemented yet! error is tripped with or without this override option. Declaring dxgi=n only stops the launcher being able to open at all, because there is no native file to load - hence my interest in where your installations are loading the dll from.

@topsyandpip56 You're running the wine binary directly, right?
The dxgi override works when running the proton script due to this:

            #if the user asked for dxvk's dxgi (dxgi=n), then copy it into place
            if "WINEDLLOVERRIDES" in os.environ and "dxgi=n" in os.environ["WINEDLLOVERRIDES"]:
                dxvkfiles.append("dxgi")
            else:
                wined3dfiles.append("dxgi")

To reproduce the same behavior when running the wine binary as is and not the proton script, you'll want to copy the content of dist/lib64/wine/dxvk to your prefix's drive_c/windows/system32 & dist/lib/wine/dxvk's content to your prefix's drive_c/windows/syswow64, respectively (and yes, the names are misleading, but it's not a typo).

After doing so, WINEDLLOVERRIDES=dxgi=n,b will load DXVK's dxgi (and friends, if you want to), in a similar fashion to running the proton script.

@Tk-Glitch The LOD fix is upsteam now, it will be backported to next Mesa 20.1.2 release as well as the previous fix. The GPU hang is still under reviews but should be merged soon.

How can I use this WINEDLLOVERRIDES="dxgi=n,b"? where should I put this on? I'm not using steam tho, The game won't start complaining about mesa version ( I use NVIDIA) and then 2 other pop-ups saying that I don't met the hardware requirements...

Thanks @Tk-Glitch for explaining that. I had noticed and thought about that extra dxvk folder put didn't put the numbers together... After having done exactly as you say though, and retaining the native override, now we arrive here:
wine: Call from 0x7bc8bf1c to unimplemented function dxgi.dll.DXGID3D10CreateDevice, aborting wine: Unimplemented function dxgi.dll.DXGID3D10CreateDevice called at address 000000007BC8BF1C (thread 009c), starting debugger... Unhandled exception: unimplemented function dxgi.dll.DXGID3D10CreateDevice called in 64-bit code (0x000000007bc8bf1c).
Dammit.

Update: Simply mark the extra dxvk libraries as natives, d3d9, d3d10, d3d11, etc...