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.

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.

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

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

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 [email protected] 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 [email protected] 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?

@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 [email protected]
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 [email protected] 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 [email protected] 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 [email protected]
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 [email protected]
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 [email protected] 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 [email protected]
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 [email protected]
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 [email protected] 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

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.

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 [email protected] 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 [email protected] 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 [email protected] 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 [email protected]
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.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?

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.

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

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

Online gives me the same error, hope this can be fixed as well as the resolutions.

For the rest.. Great work to get RDR2 running and even faster then on Windows :+1:

@guustflater How about RADV/ACO? :)

Alright - special thanks to Tk-Glitch!
Tested via RADV/LLVM (will wait for GPU hangup patch to make it upstream before testing ACO), Vega 64. Can support the others in saying it's faster than Windows, though at a lower horizontal resolution so I can't be 100% sure. (In Windows, 2560x1080. In Fedora, 1920x1080). Played for about an hour with no obvious issues and definitely no crashes.

i hope we can have vanilla setup at a point, it's crazy to recompile mesa.

If i'm correct to make it work on AMD cards we current need:

• mesa 20.1.2 (when released)
• custom proton rdr2-4

Right ?

@nerzhul The main loading bar fix is already in mesa-git, so you don't need to recompile. Just add a custom repo for whatever distro you're using, there is more than likely one.

@topsyandpip56 fine, if you know one for archlinux i'm fine :D

@nerzhul Aah of course your AUR mesa-git package is essentially a build script...

@topsyandpip56 fine, if you know one for archlinux i'm fine :D

After all these months I would just wait for another day or 6

https://docs.mesa3d.org/release-calendar.html
Release: 20.1.2
Expected date: 2020-06-24

@guustflater How about RADV/ACO? :)

Good one..! I see while trying to get the game to run I removed the RADV_PERFTEST=llvm steam launch parameter. Will try again, thank you

it's perfect then, i'm fine to wait for 1 more week to prvent my cpu use, thanks all

Is this working with all resolutions yet? I thought it was just 1920x1080 but I'm seeing people above running at 2560x1080 and 1440p. My monitor is 3440x1440.

Is this working with all resolutions yet? I thought it was just 1920x1080 but I'm seeing people above running at 2560x1080 and 1440p. My monitor is 3440x1440.

Good question.. just tried to edit the system.xml file to 3840x1200 but that doesn't work. Hope someone will share how they got 2560x1080.

I understand that the NV Vulkan beta driver is recommended but what exactly happens if someone tries to play it on 440.82? Worse performamce? Black screen, error? I'd like to buy the game but from my experience beta drivers (or AUR/.run drivers in general) have issues with Optimus laptops so I only have 440.82 right now.

Thanks.

You will have poor performance... I did that to update my manjaro nividia driver

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

I use optimus manager on my Gigabyte Aero 15X v8, and it works fine.
https://forum.manjaro.org/t/guide-install-and-configure-optimus-manager-for-hybrid-gpu-setups-intel-nvidia/92196

Hey guys I’m trying to run the steam proton build via terminal, On Manjaro it worked sweet, but the nvidia 440.66.15 was an issue, so I switched to arch cause i had trouble building the AUR nvidia-vulkan package, but now wine throws this error

**
wine: Read access denied for device L”\??\Z:\”, FS volume label and serial are not available.**

I’m like to think it’s not because proton isn’t liking the non steam game, but it’s something Else as On Manjaro, RDR was indeed launching, just really slow and crashing after the smoke effect

Everything should work now with RADV (LLVM or ACO). The GPU hang fix has been pushed yesterday. For people that don't use mesa-git, the next Mesa version (ie. 20.1.2) will contain all required fixes for enjoying RDR2. Have fun!

Anyone getting the game to run with Lutris with the Rockstar launcher?

Anyone getting the game to run with Lutris with the Rockstar launcher?

Yes. Follow Tk-Glitch's instructions to copy the bundled dxvk libraries into the correct place as the script won't do it for you this way.

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.

@topsyandpip56 Could you share your Lutris settings (Runner options/system options) or your methodology for installing RGL? I'm using a NVIDIA GPU so we're a bit different there, but when I hit play in RGL I just get a failed to initialize GPU error.

I'm using rdr2-4's dist folder as my wine version as mentioned by you further up this thread, and set <dxgi=n,b> in the DLL overrides under Runner Options in Lutris. I also have copied the contents of both folders to their respective locations as instructed by Tk-Glitch. I originally installed RGL through Lutris with rdr2-4 as the wine version.

I have yet to update to the beta NVIDIA driver as people have been recommending for performance improvement , but as I understand, it should at least work without it. I'd like to wait til I can launch the game before updating to the beta driver if possible.

Linked HERE is a paste of the Lutris logs from the moment I click play until I hit the OK button on the ERR_GFX_INIT window if that's helpful at all.

@MrSnekyDino
If you've already done those steps I'd just be guessing, but, change DXVK to "manual" in the Lutris options and also add the other dll's as overrides (d3d9.dll, d3d10.dll, etc...) and see if that does anything. From what I understand it won't be at all playable with your current driver but I can understand you want to see something.

I tried it, forced the usage of this build but I'm still getting "Unable to launch game, please verify your game data". I tried validating the game files but to no avail.

Has anyone faced this?

Has anyone been able to successfully run at a higher resolutions than 1920x1080? My monitor is 3440x1440

Story mode runs perfect on my system with the rd2-4 patched proton on manjaro stable and an AMD RX590.
Not using mesa git. (20.0.7.-3).
I had to use amdvlk (open source version).
It still pops up the "driver to old" message, but works fine nevertheless.

Steam launch command:
VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/amd_icd64.json WINEDLLOVERRIDES=dxgi=n,b %command%

@topsyandpip56 Could you share your Lutris settings (Runner options/system options) or your methodology for installing RGL? I'm using a NVIDIA GPU so we're a bit different there, but when I hit play in RGL I just get a failed to initialize GPU error.

I'm using rdr2-4's dist folder as my wine version as mentioned by you further up this thread, and set <dxgi=n,b> in the DLL overrides under Runner Options in Lutris. I also have copied the contents of both folders to their respective locations as instructed by Tk-Glitch. I originally installed RGL through Lutris with rdr2-4 as the wine version.

I have yet to update to the beta NVIDIA driver as people have been recommending for performance improvement , but as I understand, it should at least work without it. I'd like to wait til I can launch the game before updating to the beta driver if possible.

Linked HERE is a paste of the Lutris logs from the moment I click play until I hit the OK button on the ERR_GFX_INIT window if that's helpful at all.

To fix the unable to initialize the GPU error you need to check "Disable Lutris Runtime". It still fails to launch for me but I'm past the error. I get two "doesn't meet minimum requirements" warnings and the game starts for a split second and closes. I am using an NTFS partition for the game and my main ext4 for the prefix (the rockstar launcher in the prefix and game on my NTFS partition) which could be the issue

info:  Game: Launcher.exe
info:  DXVK: v1.7-1-g84bb768a+
info:  Built-in extension providers:
info:    Win32 WSI
info:    OpenVR
warn:  OpenVR: Failed to initialize OpenVR
info:  Enabled instance extensions:
info:    VK_KHR_get_surface_capabilities2
info:    VK_KHR_surface
info:    VK_KHR_win32_surface
info:  AMD RADV NAVI10 (LLVM 10.0.0):
info:    Driver: 20.1.1
info:    Vulkan: 1.2.131
info:    Memory Heap[0]: 
info:      Size: 7936 MiB
info:      Flags: 0x1
info:      Memory Type[0]: Property Flags = 0x1
info:      Memory Type[4]: Property Flags = 0xc1
info:    Memory Heap[1]: 
info:      Size: 8176 MiB
info:      Flags: 0x0
info:      Memory Type[1]: Property Flags = 0x6
info:      Memory Type[3]: Property Flags = 0xe
info:      Memory Type[5]: Property Flags = 0xc6
info:      Memory Type[7]: Property Flags = 0xce
info:    Memory Heap[2]: 
info:      Size: 256 MiB
info:      Flags: 0x1
info:      Memory Type[2]: Property Flags = 0x7
info:      Memory Type[6]: Property Flags = 0xc7
wine: Read access denied for device L"\\??\\D:\\", FS volume label and serial are not available.
wine: Read access denied for device L"\\??\\Z:\\", FS volume label and serial are not available.
info:  Game: RDR2.exe
info:  DXVK: v1.7-1-g84bb768a+
info:  Built-in extension providers:
info:    Win32 WSI
info:    OpenVR
warn:  OpenVR: Failed to initialize OpenVR
info:  Enabled instance extensions:
info:    VK_KHR_get_surface_capabilities2
info:    VK_KHR_surface
info:    VK_KHR_win32_surface
info:  AMD RADV NAVI10 (LLVM 10.0.0):
info:    Driver: 20.1.1
info:    Vulkan: 1.2.131
info:    Memory Heap[0]: 
info:      Size: 7936 MiB
info:      Flags: 0x1
info:      Memory Type[0]: Property Flags = 0x1
info:      Memory Type[4]: Property Flags = 0xc1
info:    Memory Heap[1]: 
info:      Size: 8176 MiB
info:      Flags: 0x0
info:      Memory Type[1]: Property Flags = 0x6
info:      Memory Type[3]: Property Flags = 0xe
info:      Memory Type[5]: Property Flags = 0xc6
info:      Memory Type[7]: Property Flags = 0xce
info:    Memory Heap[2]: 
info:      Size: 256 MiB
info:      Flags: 0x1
info:      Memory Type[2]: Property Flags = 0x7
info:      Memory Type[6]: Property Flags = 0xc7
info:  Adapter LUID 0: 0:40f
info:  Game: RDR2.exe
info:  DXVK: v1.7-1-g84bb768a+
info:  Built-in extension providers:
info:    Win32 WSI
info:    OpenVR
warn:  OpenVR: Failed to initialize OpenVR
info:  Enabled instance extensions:
info:    VK_KHR_get_surface_capabilities2
info:    VK_KHR_surface
info:    VK_KHR_win32_surface
info:  AMD RADV NAVI10 (LLVM 10.0.0):
info:    Driver: 20.1.1
info:    Vulkan: 1.2.131
info:    Memory Heap[0]: 
info:      Size: 7936 MiB
info:      Flags: 0x1
info:      Memory Type[0]: Property Flags = 0x1
info:      Memory Type[4]: Property Flags = 0xc1
info:    Memory Heap[1]: 
info:      Size: 8176 MiB
info:      Flags: 0x0
info:      Memory Type[1]: Property Flags = 0x6
info:      Memory Type[3]: Property Flags = 0xe
info:      Memory Type[5]: Property Flags = 0xc6
info:      Memory Type[7]: Property Flags = 0xce
info:    Memory Heap[2]: 
info:      Size: 256 MiB
info:      Flags: 0x1
info:      Memory Type[2]: Property Flags = 0x7
info:      Memory Type[6]: Property Flags = 0xc7
info:  Adapter LUID 0: 0:410
warn:  CreateDXGIFactory2: Ignoring flags
info:  Game: RDR2.exe
info:  DXVK: v1.7-1-g84bb768a+
info:  Built-in extension providers:
info:    Win32 WSI
info:    OpenVR
warn:  OpenVR: Failed to initialize OpenVR
info:  Enabled instance extensions:
info:    VK_KHR_get_surface_capabilities2
info:    VK_KHR_surface
info:    VK_KHR_win32_surface
info:  AMD RADV NAVI10 (LLVM 10.0.0):
info:    Driver: 20.1.1
info:    Vulkan: 1.2.131
info:    Memory Heap[0]: 
info:      Size: 7936 MiB
info:      Flags: 0x1
info:      Memory Type[0]: Property Flags = 0x1
info:      Memory Type[4]: Property Flags = 0xc1
info:    Memory Heap[1]: 
info:      Size: 8176 MiB
info:      Flags: 0x0
info:      Memory Type[1]: Property Flags = 0x6
info:      Memory Type[3]: Property Flags = 0xe
info:      Memory Type[5]: Property Flags = 0xc6
info:      Memory Type[7]: Property Flags = 0xce
info:    Memory Heap[2]: 
info:      Size: 256 MiB
info:      Flags: 0x1
info:      Memory Type[2]: Property Flags = 0x7
info:      Memory Type[6]: Property Flags = 0xc7
wine: Unhandled page fault on execute access to 0000000000000000 at address 0000000000000000 (thread 0474), starting debugger...
Process of pid=03d8 has terminated
No process loaded, cannot execute 'echo Modules:'
Cannot get info on module while no process is loaded
No process loaded, cannot execute 'echo Threads:'
process  tid      prio (all id:s are in hex)
00000038 services.exe
	00000280    0
	00000204    0
	000001a0    0
	00000080    0
	00000054    0
	00000050    0
	0000004c    0
	00000040    0
	0000003c    0
00000044 plugplay.exe
	0000005c    0
	00000058    0
	00000048    0
00000078 winedevice.exe
	0000008c    0
	00000088    0
	00000084    0
	0000007c    0
00000090 Launcher.exe
	000003d4   15
	000003d0    0
	000003cc    0
	000003c4    0
	000002b8    0
	000002ac    0
	000002a8    0
	00000200    0
	000001fc    0
	000001f8    0
	000001ec    0
	000001e8    0
	000001e4    0
	000001e0    0
	000001dc    0
	000001d8    0
	000001d4    0
	000001d0    0
	000001cc    0
	000001c8    0
	000001c4    0
	000001c0    0
	000001bc    0
	000001b0    0
	00000168    0
	00000164    0
	00000160    0
	0000015c    0
	00000158   -2
	00000154   -2
	00000150   -2
	0000014c   -2
	00000148   -2
	00000144   -2
	00000140   -2
	0000013c   -2
	00000138   -2
	00000134   -2
	000000f8    0
	000000f4    0
	000000f0    0
	000000ec    0
	000000e8    0
	000000e4    0
	000000e0    0
	000000dc    0
	000000d8    0
	000000d4    0
	000000d0    0
	000000cc    0
	000000c8    0
	000000c4    0
	000000c0    0
	000000bc    0
	000000b8   -2
	000000b4   -2
	00000094    0
00000098 explorer.exe
	000000a8    0
	000000a4    0
	000000a0    0
	0000009c    0
00000184 RockstarService.exe
	000001b8    0
	000001b4    0
	000001ac    0
	000001a4    0
	00000188    0
000001f0 SocialClubHelper.exe
	000003ac    0
	000003a8    0
	000003a4    0
	000003a0    0
	00000384    0
	00000380    0
	0000037c    0
	000002a4    0
	0000029c    0
	00000298    0
	00000294    0
	00000290    0
	0000028c    0
	00000288    0
	00000284   -2
	0000027c    0
	00000278    0
	00000274    0
	0000026c    0
	0000025c    0
	00000258    0
	00000254    0
	00000250    0
	0000024c    0
	00000248    0
	00000244    0
	00000240    0
	0000023c   -2
	00000238    0
	00000234    0
	00000230    0
	0000022c   -2
	00000228   -2
	00000224    0
	00000220    0
	0000021c    0
	00000218    0
	00000214    0
	00000210    0
	0000020c    0
	00000208    0
	000001f4    0
00000260 SocialClubHelper.exe
	00000320    0
	0000031c    0
	00000318    0
	00000314    0
	00000310    0
	0000030c    0
	00000308    0
	00000304   -2
	00000300   -2
	000002fc    0
	000002f8    0
	000002f4    0
	00000270    0
	00000264    0
000002b0 SocialClubHelper.exe
	000003bc    0
	000003b8    0
	000003b4    0
	000003b0    0
	00000394    0
	00000390    0
	00000388    0
	00000378    0
	00000374   -2
	00000370    0
	0000036c    0
	00000368    0
	00000364    0
	00000360    0
	0000035c    0
	00000358    0
	00000354    0
	00000350   -2
	0000034c   -2
	00000348    0
	00000344    0
	00000340    0
	0000033c    0
	00000338    0
	00000334    0
	00000330    0
	0000032c    0
	000002b4    0

Arch Linux, 440.66.15, proton_5.0-rdr2-4. I only get a black screen, does anyone have the same problem?

EDIT: By the way I had to set "WINEDLLOVERRIDES=dxgi=n,b %command%" to get to this window, otherwise it just crashes right away.

Arch Linux, 440.66.15, proton_5.0-rdr2-4. I only get a black screen, does anyone have the same problem?

EDIT: By the way I had to set "WINEDLLOVERRIDES=dxgi=n,b %command%" to get to this window, otherwise it just crashes right away.

I get almost the same issue. Mine will show the loading bar, then like 2 secs into the smoke intro, it will freeze, then quickly pop up a second window of the game and within a sec, it completely crashes. Im on Manjaro running the same nvidia driver, and launch options.

Arch Linux, 440.66.15, proton_5.0-rdr2-4. I only get a black screen, does anyone have the same problem?
EDIT: By the way I had to set "WINEDLLOVERRIDES=dxgi=n,b %command%" to get to this window, otherwise it just crashes right away.

I get almost the same issue. Mine will show the loading bar, then like 2 secs into the smoke intro, it will freeze, then quickly pop up a second window of the game and within a sec, it completely crashes. Im on Manjaro running the same nvidia driver, and launch options.

For me, the fix was in the rockstar launcher arguments add this: -width 1920 -height 1080
Idk if it works for everyone but it stopped me from crashing at smoke, still stuck at error code 18 though.

Today I tried the game on Linux Mint 19.3 and it's working fine even without any dll overrides. I can't get it running on Arch though...

I know I'm missing some package but I have no idea.

Arch Linux, 440.66.15, proton_5.0-rdr2-4. I only get a black screen, does anyone have the same problem?
EDIT: By the way I had to set "WINEDLLOVERRIDES=dxgi=n,b %command%" to get to this window, otherwise it just crashes right away.

I get almost the same issue. Mine will show the loading bar, then like 2 secs into the smoke intro, it will freeze, then quickly pop up a second window of the game and within a sec, it completely crashes. Im on Manjaro running the same nvidia driver, and launch options.

For me, the fix was in the rockstar launcher arguments add this: -width 1920 -height 1080
Idk if it works for everyone but it stopped me from crashing at smoke, still stuck at error code 18 though.

Thanks guys for trying to help me, nothing mentioned here helped though. But I was playing around with random launch parameters and finally got the game to run.

What I use is "WINEDLLOVERRIDES=dxgi=n,b %command% -height 720 -width 1280 -vulkan -safemode -ignoreprofile -useMinimumSettings -benchmark -adapter 1"

The "outdated drivers" message changed from "outdated Intel" to "outdated AMD" - maybe because of the "-adapter 1" parameter as I'm on an Optimus laptop.

EDIT: Yes, "-adapter 1" is THE parameter that made the game playable on my Optimus laptop.

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.

<--- comment cropped for readability sake -->

Alright, after installing newly published proton version (5.0-rdr2.4) I was able to launch the game and play in story mode. It's playable, didn't use the benchmark yet (is there a simple way to enable benchmark without installing extra stuff, I saw on some screenshot?). I get however an error (game still launches) about updating my video card drivers. Using Nvidia 440.82 drivers (Ti 1080)

Thank you @mrpippy for the effort you made!

I understand that the NV Vulkan beta driver is recommended but what exactly happens if someone tries to play it on 440.82? Worse performamce? Black screen, error? I'd like to buy the game but from my experience beta drivers (or AUR/.run drivers in general) have issues with Optimus laptops so I only have 440.82 right now.

Thanks.

@headlesscyborg I was able to get there. See my update above (and prev. comments throughout the troubleshooting).

Thank you guys for your work!

I got this running through lutris. Using 5.0-rdr2.4. I had to set the dxgi, dxvk_config and d3d.* dlls as 'n,b', after copying them from proton.

I can play for about 30mins. After that the game crashes to desktop in seemingly uninteresting points. First time was when they were talking to the woman, another while I was interrogating the guy, and the third time when riding in the mountains after those events.

System is Arch Linux, with mesa-git.
AMD FX8350, AMD RX590
Lutris runtime disabled.

I've also enabled proton_log, but I'm not sure where to find it.

Log:

wine: Unhandled privileged instruction at address 0000000142B2A0AC (thread 03b0), starting debugger...
Process of pid=03ac has terminated
No process loaded, cannot execute 'echo Modules:'
Cannot get info on module while no process is loaded
No process loaded, cannot execute 'echo Threads:'
process tid prio (all id:s are in hex)
<--trimmed-->
log.txt

In case anyone is interested what's the performance difference on Nvidia between 440.82 and 440.66.15, it's 19-22 fps vs 40-60 fps on high settings (1660 Ti).

Btw. I'm experiencing random crashes, usually after 30-60 minutes of playing it says something like "Fatal error, please restart the game" (forgot to print screen it, will edit this next time it happens). It might be the 440.66.15 driver because Witcher 3 (perfectly stable before) started freezing after a similar amount of time as well. Does anyone else have the same experience? Is there a log somewhere that I could upload? Right now I have 3 hours played and exactly 3 crashes.

EDIT:

Thank you guys for your work!

I got this running through lutris. Using 5.0-rdr2.4. I had to set the dxgi, dxvk_config and d3d.* dlls as 'n,b', after copying them from proton.

I can play for about 30mins. After that the game crashes to desktop in seemingly uninteresting points. First time was when they were talking to the woman, another while I was interrogating the guy, and the third time when riding in the mountains after those events.

System is Arch Linux, with mesa-git.
AMD FX8350, AMD RX590
Lutris runtime disabled.

I've also enabled proton_log, but I'm not sure where to find it.

Log:

wine: Unhandled privileged instruction at address 0000000142B2A0AC (thread 03b0), starting debugger...
Process of pid=03ac has terminated
No process loaded, cannot execute 'echo Modules:'
Cannot get info on module while no process is loaded
No process loaded, cannot execute 'echo Threads:'
process tid prio (all id:s are in hex)
<--trimmed-->
log.txt

Could you share your Lutris config? What do you mean by setting the dxvk_config and d3d.* dlls as 'n,b'? By setting it in the "DLL overrides" section?

Arch Linux, 440.66.15, proton_5.0-rdr2-4. I only get a black screen, does anyone have the same problem?
EDIT: By the way I had to set "WINEDLLOVERRIDES=dxgi=n,b %command%" to get to this window, otherwise it just crashes right away.

I get almost the same issue. Mine will show the loading bar, then like 2 secs into the smoke intro, it will freeze, then quickly pop up a second window of the game and within a sec, it completely crashes. Im on Manjaro running the same nvidia driver, and launch options.

For me, the fix was in the rockstar launcher arguments add this: -width 1920 -height 1080
Idk if it works for everyone but it stopped me from crashing at smoke, still stuck at error code 18 though.

Thanks guys for trying to help me, nothing mentioned here helped though. But I was playing around with random launch parameters and finally got the game to run.

What I use is "WINEDLLOVERRIDES=dxgi=n,b %command% -height 720 -width 1280 -vulkan -safemode -ignoreprofile -useMinimumSettings -benchmark -adapter 1"

The "outdated drivers" message changed from "outdated Intel" to "outdated AMD" - maybe because of the "-adapter 1" parameter as I'm on an Optimus laptop.

EDIT: Yes, "-adapter 1" is THE parameter that made the game playable on my Optimus laptop.

So i tried to launch it with your extra flags on the launch options, and i got farther. I now get to rock star social club Error 18.

@KermitTheFrogerino

Could you share your Lutris config?

red-dead-redemption-ii-rockstar-games-launc-1592584302.yml.txt

What do you mean by setting the dxvk_config and d3d.* dlls as 'n,b'? By setting it in the "DLL overrides" section?

Yeah.

@KermitTheFrogerino

Could you share your Lutris config?

red-dead-redemption-ii-rockstar-games-launc-1592584302.yml.txt

What do you mean by setting the dxvk_config and d3d.* dlls as 'n,b'? By setting it in the "DLL overrides" section?

Yeah.

@xnick thanks but the game opens for a split second. This is the error:

wine: Unhandled page fault on execute access to 0000000000000000 at address 0000000000000000 (thread 0484), starting debugger...
Process of pid=0420 has terminated
No process loaded, cannot execute 'echo Modules:'
Cannot get info on module while no process is loaded
No process loaded, cannot execute 'echo Threads:'
process  tid      prio (all id:s are in hex)

@KermitTheFrogerino

Did you follow these steps by Tk-Glitch ?

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.

@xnick Yeah... It gives me the same error even without doing anything special like that.
I'm using stock Mesa 20.1.1, Ubuntu 20.04, Ryzen 1700, 5700XT

Hello @KermitTheFrogerino, mesa/radv 20.1.1 is known incompatible with this game. The needed adjustments are queued up for mesa 20.1.2.

@kisak-valve Awesome! I'm pretty new to Linux so how would it handle using a compiled version? I'm guessing that it'll update as usual but just want to make sure :)

@kisak-valve Great! Will try :)

Had anyone been able to get this running at a resolution other than 1920x1080??

Curious if it will run on my 3440x1440 monitor.

Had anyone been able to get this running at a resolution other than 1920x1080??

Curious if it will run on my 3440x1440 monitor.

I have the same issue: how can I play it in 2 2560x1080?

I've got it running and played the first two missions successfully when it suddenly crashed with a ERR_GFX_STATE, music continued to play, I had to force-close the window. But the game runs quite quirky at best. My environment:

• NVIDIA 440.66.15 Vulkan beta, GTX 1660 Ti
• Proton 5.0-rdr2.4 from Codeweavers (fresh pfx, see below)
• I ran with %command% -vulkan
• prefix directory had to be purged before this started working but then it started just fine without any tweaks
• The game says I don't have the correct AMD driver version but clicking OK let's start it just fine, this is probably because some component pretends AMD instead of NVIDIA drivers
• 4k desktop resolution (but the game cannot use it)
• KWin-X11 with KDE Plasma
• Rockstar launcher installed and ran just fine and automatically logged me in through the linked Steam account

So what's quirky?

• The game starts in 1280x720 windows mode, I can only select two resolutions: 1280x720 or 1920x1080
• I can set all settings to at least "high" but not all at once, I need to do this setting by setting until everything is set to "high", otherwise it freezes.
• I cannot make the game fullscreen, it will seemingly freeze and flicker between stretched to full 4k resolution, 1920x1080 is the top-left corner and a black screen every few seconds (Update: Adding launch parameters -width 3840 -height 2160 or similar works around this problem and adds a third resolution)
• The graphics settings neither display any monitors nor graphics adapters, the option is grayed out, maybe this is why I can only select 720p or 1080p
• Switching resolutions can make the game freeze
• mouse raw input mode conflicts with the Xbox game controller: the triggers seem to make the game switch back to keyboard/mouse mode and see the triggers as mouse movement (switching it to "Windows API" fixes that)
• I tried wine virtual desktop mode (as this fixed resolution problems in other games like AC:Odyssey) in both FHD and 4k resolution but it makes no difference, also the game seems to be able to break out of this virtual mode and resizes it to 4k if trying to activate fullscreen mode, probably something is interacting badly with the Vulkan render surface
• The game doesn't render as the topmost surface, it's always behind the plasma taskbar even in full-screen mode (may be a KWin bug but other games, even native Vulkan games, don't show this problem)
• Update: During the first hunting mission, I repeatedly get ERR_GFX_STATE at different progress into the mission, I cannot complete the mission and thus cannot continue the game

So something is really off with display detection, and the game doesn't like to be stretched to higher resolutions at all (at least not how Proton fshack does it). Fullscreen doesn't work but I couldn't test if this is due to being stretched to 4k, or for other reasons. Window mode and border-less window mode both seem to work fine, tho. Switching between those may freeze the game, at least after doing that a few times, seems to work at least once or twice always.

Desktop notifications may become stuck forever on-top of the game content with no way of closing them because the clicks are not passed through to the overlay notification.

The dxgi wine dll override makes no difference for me.

But on the positive side: Loading times were exceptionally fast, although I would had expected the game to do some shader pre-compilation. But even within the game there's absolutely no stutter which I'd usually expect from shader compilation. So big thumbs up on the performance side. I've seen no visual glitches so far except a very rare flicker that looks like a gray triangle right across the complete render surface, barely noticeable. The game seems to run almost constantly at or beyond 60 fps (I'm using vsync, so the benchmark showed 59.something avg fps).

Game runs fine, but on Windows colors are different and game looks more crisp.
My setup:
Arch Linux
DE KDE
Kernel linux-tkg-pds from chaotic
Rockstar launcher via lutris
Proton-5.0-rdr2.4
Driver Vulkan
Rx480
Ryzen 5 2600

@aliendonald @aeikum in terms of colors @doitsujin suspects that there is a bug in Wine https://github.com/doitsujin/dxvk/issues/1668

After about 4 hours of playing, keyboard input slowly became less responsive until it eventually seemed to behave on its own, perhaps delayed terribly or just pressing random keys, I couldn't exactly tell which. May have been related to using the Steam overlay, as I was using it a lot, and it seemed noticeably worse after using it. Either way this only happened once during my 41 hours of playtime with Proton, and unfortunately I have no logs.

@chris-echoz enable logging in Proton so if it happens again you'll have a log.

PROTON_LOG=1 %command% in the launch options.

But yeah, I've got about 1000 hours in the Origin version (which is the same version of the game) and I've never once had that happen.

@aliendonald please take a screenshot of the game so we can see what you're talking about.

Also, when you say "Driver Vulkan," what does that mean? All the drivers you run this game with are going to be Vulkan drivers. Are you using RADV, AMDVLK, or vulkan-amdgpu-pro??

If you're using RADV, I've actually noticed that the game looks nicer with vulkan-amdgpu-pro or AMDVLK. Performance is literally exactly the same (I have benchmarks on flightlessmango.com to prove it), but it just looks a little nicer (unless it's all in my head) with the AMD official drivers (vulkan-amdgpu-pro/amdvlk).

* Adding launch parameters `-width 3840 -height 2160`

The game doesn't render as the topmost surface, it's always behind the plasma taskbar even in full-screen mode (may be a KWin bug but other games, even native Vulkan games, don't show this problem)

Your tip about the resolution works, I am now playing the game in ultrawide 1080p but only as borderless windowed; fullscreen will still force a standard 1080p horizontal resolution. As for KWin bug, I also have this but not in fullscreen mode. In borderless window mode I'm working around this by temporarily setting an autohide setting and toggling compositing off to improve frametimes.

* Adding launch parameters `-width 3840 -height 2160`

The game doesn't render as the topmost surface, it's always behind the plasma taskbar even in full-screen mode (may be a KWin bug but other games, even native Vulkan games, don't show this problem)

Your tip about the resolution works, I am now playing the game in ultrawide 1080p but only as borderless windowed; fullscreen will still force a standard 1080p horizontal resolution. As for KWin bug, I also have this but not in fullscreen mode. In borderless window mode I'm working around this by temporarily setting an autohide setting and toggling compositing off to improve frametimes.

Excellent! I'm going to give it a whirl tonight and try to get it running in 3440x1440

Nice! Finally able to enjoy the game @ 2560x1440
Thanks for the tip

Using Lutris on Arch with latest mesa-git Ryzen3600 + AMD rx 5700 (kernel 5.7)

With 5.0-rdr2.4. I set the dll overrides to every dll of dxvk (dxgi, dxvk_config and d3d.*) as 'n,b', after copying them from proton.
Try every DXVK version or set it to Manual (Not sure what version i need to set)
Disable lutris runtime
Not sure if I need to specify the custom wine exec to dist/bin/wine64 or dist/bin/wine

But I got every time the social club error 18 on amd vulkan icd or black smoke on radv icd

mrpippy said :

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.

So i try to reinstall the launcher/game in a new prefix with 5.0-rdr2.4 but now the game doesn't event load. And there is no error in log. Any clue ?

Strangely enough, I'm now unable to launch the game as well. I just did a system upgrade and rebooted, and it won't start at all.

It's not even creating a log file even though I have PROTON_LOG=1 set.

Setting 2560x1440 with the launch options worked, but in windowed borderless mode the window starts on my secondary monitor and can't be moved either through the gnome overview or through the command line, it's just stuck on the wrong monitor. Using a wine virtual desktop allows it to be moved, but then the game is partly outside of the virtual desktop. Changing the outputIndex in system.xml makes no difference at all.

@chris-echoz it should open on your primary monitor. I've never seen a game open on a non-primary monitor, is the monitor you want to game on set as primary?

Alternatively, you could try launching it from Lutris. It'll just launch Steam (if Steam isn't already running) and launch the game, but if you right-click on the game in your library in Lutris (not Steam) and go to "System Options," you'll see an option that says "Turn off monitors except:" with a drop-down menu. Select which monitor you want to use, click save, and try to run the game. See if that works.

@gardotd426 Yes, it's set as primary, and the vast majority of games open on that monitor, but some applications ignore it and open on the leftmost monitor (my secondary). It's been a very rare occurrence the last 5 years or so, though.

Does this Lutris option actually disable the monitor? In that case I may as well just switch them around or just deal with 1080p, as that kind of defeats the purpose of having two monitors.

Only while playing the game. If you need the second monitor while gaming,
then yeah I suppose it would defeat the purpose.

On Tue, Jun 23, 2020 at 5:29 PM Echoz [email protected] wrote:

@gardotd426 https://github.com/gardotd426 Yes, it's set as primary, and
the vast majority of games open on that monitor, but some applications
ignore it and open on the leftmost monitor (my secondary). It's been a very
rare occurrence the last 5 years or so, though.

Does this Lutris option actually disable the monitor? In that case I may
as well just switch them around or just deal with 1080p, as that kind of
defeats the purpose of having two monitors.

—
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-648438031,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM5Y333JMERXZH2J5HFIAOLRYENC5ANCNFSM4JV54AXQ
.

Someone tried the online mode ?
It works or not ?

Thanks :D

@Odelpasso It doesn't yet.

It seems the monitor issue has nothing to do with which monitor is to the left or right, but probably happens this way because my secondary monitor happens to have a lower index in my graphics card. Switching them around still resulted in it launching on the wrong monitor.

Setting 2560x1440 with the launch options worked, but in windowed borderless mode the window starts on my secondary monitor and can't be moved either through the gnome overview or through the command line, it's just stuck on the wrong monitor. Using a wine virtual desktop allows it to be moved, but then the game is partly outside of the virtual desktop. Changing the outputIndex in system.xml makes no difference at all.

Does gnome have a feature like KDE where holding alt and dragging the window works regardless of how the app feels about it?

@topsyandpip56 Technically, yes, but no matter how I try to move the window it refuses to do so. I'm assuming it moves itself there constantly, and that this is why nothing actually causes it to move.
@gardotd426 Yup, I tried using those shortcuts, nothing happened at all.
I've just switched the cables around and I'll see if that works. To my surprise HDMI was able to run the monitor at 2560x1440@144hz, so if this works it'll be my solution.
I'm sure the Lutris option would work, as the game would have to end up on the right monitor if there's only one. I'm mostly looking for a way to avoid disabling the other monitor.

Switching the cables didn't work, so the game has either tapped into my brain and decided to work against my will, or this is related to refresh rate, causing it to always go to the monitor with a 60 Hz refresh rate. I'll see what happens if I set them both to 60 Hz.

Well yeah I know, I just meant that you might be able to tweak whatever
Lutris is doing in order to get the same result but without having to
disable the other monitor. But if switching the cables around works, I
would just do that as well (I've also found switching cables has fixed
weird monitor arrangement issues)

On Tue, Jun 23, 2020 at 5:48 PM Echoz [email protected] wrote:

@topsyandpip56 https://github.com/topsyandpip56 Technically, yes, but
no matter how I try to move the window it refuses to do so. I'm assuming it
moves itself there constantly, and that this is why nothing actually causes
it to move.
@gardotd426 https://github.com/gardotd426 Yup, I tried using those
shortcuts, nothing happened at all.
I've just switched the cables around and I'll see if that works. To my
surprise HDMI was able to run the monitor at 2560x1440@144hz, so if this
works it'll be my solution.
I'm sure the Lutris option would work, as the game would have to end up on
the right monitor if there's only one. I'm mostly looking for a way to
avoid disabling the other monitor.

—
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-648445700,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM5Y33Y2SE4F5QDLSDFMPVDRYEPKJANCNFSM4JV54AXQ
.

Switching cables, switching their arrangement and setting both to 60 Hz did nothing. However setting my secondary monitor as primary did the trick. Of course this is not desirable and I don't at all understand why the game would start on my secondary display purely based on the fact that it's not my primary.

This also worked with the original arrangement of my monitors, having the (original) primary set to 144 Hz.

Performance is terrible unless the WM actually sees it as a full screen window, so the convoluted way I managed to make it perform well and display in 2560x1440 was to disable the secondary monitor, switch it to full screen through the WM and then enable the secondary again. Now it performs well and displays on the right monitor.

@chris-echoz it should open on your primary monitor. I've never seen a game open on a non-primary monitor, is the monitor you want to game on set as primary?

Alternatively, you could try launching it from Lutris. It'll just launch Steam (if Steam isn't already running) and launch the game, but if you right-click on the game in your library in Lutris (not Steam) and go to "System Options," you'll see an option that says "Turn off monitors except:" with a drop-down menu. Select which monitor you want to use, click save, and try to run the game. See if that works.

Try holding "Alt" while left-clicking somewhere in the window and dragging it. It works with kwin but it should be standard x11 behavior: alt+left-click = drag, alt+right-click = resize

It's not standard X11 behavior. If that were the case, it would work in i3
as well. In GNOME it's Super+left click to move any window. And like I
said, I'm pretty certain it's Super+Shift+Left/Right Arrow to move
monitors. It's something like that. Chris already said he'd tried that,
presumably because that is indeed the way it works in GNOME.

On Tue, Jun 23, 2020 at 7:03 PM Kai Krakow [email protected] wrote:

@chris-echoz https://github.com/chris-echoz it should open on your
primary monitor. I've never seen a game open on a non-primary monitor, is
the monitor you want to game on set as primary?

Alternatively, you could try launching it from Lutris. It'll just launch
Steam (if Steam isn't already running) and launch the game, but if you
right-click on the game in your library in Lutris (not Steam) and go to
"System Options," you'll see an option that says "Turn off monitors
except:" with a drop-down menu. Select which monitor you want to use, click
save, and try to run the game. See if that works.

Try holding "Alt" while left-clicking somewhere in the window and dragging
it. It works with kwin but it should be standard x11 behavior:
alt+left-click = drag, alt+right-click = resize

—
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-648472034,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM5Y3357P3DV5AMOMY3C25DRYEYD5ANCNFSM4JV54AXQ
.

It's not standard X11 behavior. If that were the case, it would work in i3 as well. In GNOME it's Super+left click to move any window. And like I said, I'm pretty certain it's Super+Shift+Left/Right Arrow to move monitors. It's something like that. Chris already said he'd tried that, presumably because that is indeed the way it works in GNOME.

Okay, maybe. But I worked with twm (and fluxbox, and other WMs) like 20 years ago, and that was the way to move windows around there and resize them. So, I'm guessing, Gnome is just deviating from established standards - as always ;-)

i3 is a tiling window manager, can you even resize windows with the mouse there? Maybe floating... But I'm just using i3 for emergency/recovery scenarios currently (maybe more often in the future). Thus, I'm not very used to it yet.

Yeah, floating mode windows are resized with Mod+right-click. They're moved
with Mod+Left-click.

On Tue, Jun 23, 2020 at 7:13 PM Kai Krakow [email protected] wrote:

It's not standard X11 behavior. If that were the case, it would work in i3
as well. In GNOME it's Super+left click to move any window. And like I
said, I'm pretty certain it's Super+Shift+Left/Right Arrow to move
monitors. It's something like that. Chris already said he'd tried that,
presumably because that is indeed the way it works in GNOME.

Okay, maybe. But I worked with twm (and fluxbox, and other WMs) like 20
years ago, and that was the way to move windows around there and resize
them. So, I'm guessing, Gnome is just deviating from established standards

• as always ;-)

i3 is a tiling window manager, can you even resize windows with the mouse
there? Maybe floating... But I'm just using i3 for emergency/recovery
scenarios currently (maybe more often in the future). Thus, I'm not very
used to it yet.

—
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-648475275,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM5Y334PPS5FUJ7QVFLSKKDRYEZIBANCNFSM4JV54AXQ
.

Seems that since I've done this sysupgrade, nvidia-vulkan has upgraded to 440.66.17. Starting the game is hit or miss for me now, and when it DOES start I get Social Club Error 18, unable to initialize graphics device blah blah.

I've tried a new prefix and all. Not sure what's up but.. It's frustrating.

Yeah you might have to file that with Nvidia, it sounds like the driver
update has broken the game for Nvidia users.

They've fixed stuff quickly in the past, when people have reported it to
them. They did with Doom Eternal, actually released a beta driver just so
people could play. But nothing can get fixed if no one reports it.

On Tue, Jun 23, 2020 at 9:30 PM Joe Knockenhauer [email protected]
wrote:

Seems that since I've done this sysupgrade, nvidia-vulkan has upgraded to
440.66.17. Starting the game is hit or miss for me now, and when it DOES
start I get Social Club Error 18, unable to initialize graphics device blah
blah.

I've tried a new prefix and all. Not sure what's up but.. It's frustrating.

—
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-648528756,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM5Y337QMMMQLJPQXT76X73RYFJJ5ANCNFSM4JV54AXQ
.

Starting the game worked just as before for me with 440.66.17. All my testing yesterday was done with that driver, and it didn't at all seem less reliable than with 440.66.15.

Mine has been giving me the Social Club Error 18 as well. running Nvidia 440.66.15. Tried everything. I cant get past it.

I ended up rolling back to 440.66.15 and recreated the prefix. Working again for me.

@aliendonald please take a screenshot of the game so we can see what you're talking about.

Also, when you say "Driver Vulkan," what does that mean? All the drivers you run this game with are going to be Vulkan drivers. Are you using RADV, AMDVLK, or vulkan-amdgpu-pro??

If you're using RADV, I've actually noticed that the game looks nicer with vulkan-amdgpu-pro or AMDVLK. Performance is literally exactly the same (I have benchmarks on flightlessmango.com to prove it), but it just looks a little nicer (unless it's all in my head) with the AMD official drivers (vulkan-amdgpu-pro/amdvlk).

Sorry for late answer. I set amd_icd64.json in lutris so it's probably amdvlk, right? Today was an update of mesa-tkg-git and game looks fine now.

@topsyandpip56 Could you share your Lutris settings (Runner options/system options) or your methodology for installing RGL? I'm using a NVIDIA GPU so we're a bit different there, but when I hit play in RGL I just get a failed to initialize GPU error.
I'm using rdr2-4's dist folder as my wine version as mentioned by you further up this thread, and set <dxgi=n,b> in the DLL overrides under Runner Options in Lutris. I also have copied the contents of both folders to their respective locations as instructed by Tk-Glitch. I originally installed RGL through Lutris with rdr2-4 as the wine version.
I have yet to update to the beta NVIDIA driver as people have been recommending for performance improvement , but as I understand, it should at least work without it. I'd like to wait til I can launch the game before updating to the beta driver if possible.
Linked HERE is a paste of the Lutris logs from the moment I click play until I hit the OK button on the ERR_GFX_INIT window if that's helpful at all.

To fix the unable to initialize the GPU error you need to check "Disable Lutris Runtime". It still fails to launch for me but I'm past the error. I get two "doesn't meet minimum requirements" warnings and the game starts for a split second and closes. I am using an NTFS partition for the game and my main ext4 for the prefix (the rockstar launcher in the prefix and game on my NTFS partition) which could be the issue
log

Thanks, I quickly discovered that! Still getting a 'Please update your driver to 20.2.2 or newer' error (even though I'm using a NVIDIA GPU). Pressing OK on the window gets me a split second of a black screen and then the game quits itself. Not sure where to go from here, I have all the recommended DLL overrides, I'm using the same lutris settings as posted elsewhere, I've moved the .dll files to their correct windows folders, and I installed the launcher with the rdr2-4 wine version.

For AMD users: Mesa 20.1.2 has been released and it contains all fixes for RDR2!

@aliendonald if you have VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/amd_icd64.json set, then you're not using Mesa, you're using AMDVLK. RADV is Mesa's vulkan driver.

@aliendonald if you have VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/amd_icd64.json set, then you're not using Mesa, you're using AMDVLK. RADV is Mesa's vulkan driver.

Oh, my mistake. I'm not new in linux but gaming stuff and graphics drivers it's mystery for me ;-). Amdvlk was also updated, so that was the point I think.

No worries it took me 6 months of trying before I figured out amdgpu, mesa, RADV, AMDVLK, vulkan-amdgpu-pro, etc. It's a mess. But also it's cool because you get three different vulkan drivers so if one is being dumb you can try another, which is like, unfathomable on Windows.

Glad you got it working!
Sent from Mailspring (https://getmailspring.com/), the best free email app for work
On Jun 25 2020, at 2:43 am, aliendonald [email protected] wrote:

@aliendonald (https://github.com/aliendonald) if you have VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/amd_icd64.json set, then you're not using Mesa, you're using AMDVLK. RADV is Mesa's vulkan driver.
Oh, my mistake. I'm not new in linux but gaming stuff and graphics drivers it's mystery for me ;-). Amdvlk was also updated, so that was the point I think.

—
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-649265555), or unsubscribe (https://github.com/notifications/unsubscribe-auth/AM5Y332S5KLOCSQF5UA3W33RYLWZJANCNFSM4JV54AXQ).

@hakzsam great news, cannot wait to have it on archlinux.
We need this custom build and mesa, and it works out of the box ?

@nerzhul Yes.

thanks for your return, that will quiet this topic. Can we expect some/all your proton patches to be upstreamed ?

Oh yeah packages are on arch

lib32-libva-mesa-driver-20.1.2-1  lib32-mesa-20.1.2-1  lib32-mesa-vdpau-20.1.2-1  lib32-opencl-mesa-20.1.2-1  lib32-vulkan-radeon-20.1.2-1
             libva-mesa-driver-20.1.2-1  mesa-20.1.2-1  mesa-vdpau-20.1.2-1  opencl-mesa-20.1.2-1  vulkan-radeon-20.1.2-1

The game doesn't startup unless i put WINEDLLOVERRIDES="dxgi=n,b" %command%, but i confirm with mesa 20.1.2 it launches on vanilla archlinux :)

great job guys !

i played 2 hours without problem, very fine

i played 2 hours without problem, very fine

Has the mainline WINE and Proton supported this?

Anyone got multiplayer working?

Hey everyone involved,

I've been quietly watching this thread since early Spring 2020 & let me pause for a standing ovation for this magnificent piece of work you've done here! Very well done!

However, I'm not really into heavy tinkering of my trusty Manjaro setup, even though I sport probably optimal combo of Intel CPU + Nvidia GPU. So my question is as noobish as it gets: do you assume we can expect new version of Proton & Nvidia drivers with RDR2 fixes included anytime soon in Manjaro repositories? I've been waiting for so long that a few weeks longer is definitelly worth it to have almost out-of-box working game experience, considering I've just purchased Ultimate Edition of RDR2 via Steam :-)

Basically what is the reason for delay when it comes to implementing these RDR2 fixed into official Proton release? Is it reasonable to expect these fixes implemented first in Glorious Eggroll Proton release? And finally, is there any kind of "how to get it working" for Nvidia GPU rigs, especially for Arch Linux (Manjaro)?

Thanks a bunch to all of you and enjoy this one-of-a-kind masterpiece of game!

Also, sorry for another post with question, but I cannot download any of Brendan's custom Proton builds, can anyone confirm? The links above simply point to empty folder it seems, I wonder what is the reason behind it... Thanks for clarification if possible!

@TKCZ https://www.codeweavers.com/xfer/bshanks/public/proton-5.0-rdr2-4.tar.gz works just fine for me

Hi all
RDR2 ran well on my PC, so I started playing the game. But I stuck on a mission called "Magicians for Sport". At some point my companion stops doing anything and I can't interact with him. Here is my short video with the mission
https://www.youtube.com/watch?v=x4UjgN18agY

Info:
Radeon rx480
Clear Linux (also tested with Fedora)
Proton rdr2-4
Mesa git (ACO)

Can anyone check how the mission works on your PC? I have no idea it's wine bug or mesa bug or I do something wrong.
Here are my saves and proton logs
https://gist.github.com/IShashkin/fec1b7919f9e92374107b2a2bc0f43d7/raw/56d8d7dc3fd5a1a64bef18ae9bed84ef4c401a61/rdr2%2520logs%2520and%2520save.zip
On my PC location of saves was /steamapps/compatdata/1174180/pfx/drive_c/users/steamuser/My Documents/Rockstar Games/Red Dead Redemption 2/Profiles/461B8BAB

@IShashkin This didn't happen when I did this mission. Maybe try waiting before you inspect the tub, at least I took a little longer to do that, and Charles already walked outside by the time I inspected it.

So.. I've tried it out with the latest mesa 20.1.2 and the suggested proton version and my game crashed so hard after ~half an hour that my bios wouldn't even boot. I had to plug off the power supply for 2-3 mins for it to reset I guess. To be sure that this isn't some error in the latest mesa driver or an overheating issue, I've been playing jedi fallen order for ~1.5 hours without any hitch. Might need to test a vulkan windows-only game to be certain though

First time since 2 years (where I started using linux for gaming) that this ever happened so severe. Maybe it's an upcoming hardware failure, though then I'd expect this in other games as well.

CPU: Ryzen 5 3600
GPU: AMD 5700XT
Distro: Manjaro KDE
Kernel: 5.7.6-1

Will test it with rage 2 (another windows-only vulkan game) and update this, if that also happens there

EDIT: Played Rage 2 now for over an hour, not a single problem. So most likely a rdr2 problem.

Someone has an error during the launch ?
I have this :
"Social Club Error
Failed to initialize Social Club : Error Code 0
...."

I don't know how to fix that

Hello All!

Thank you for kicking ass and trying to make this gem playable on linux.

I have a question about MESA.. I am running Manjaro linux. I am in the bauh package manager... I do not see the current version of Mesa y'all are using. I am capped at 20.0.7-3. I suppose I need to manually install 20.1.2? I find it odd because that package manager sources from Arch as well.

Hello All!

Thank you for kicking ass and trying to make this gem playable on linux.

I have a question about MESA.. I am running Manjaro linux. I am in the bauh package manager... I do not see the current version of Mesa y'all are using. I am capped at 20.0.7-3. I suppose I need to manually install 20.1.2? I find it odd because that package manager sources from Arch as well.

Manjaro uses multiple branches.. stable, testing, unstable. Each with different stages of testing basically. Mesa 20.1.2 is only available on testing atm, though it should be released to stable in a couple of days I assume. There is usually not a huge delay.

So you either build/add it yourself, change to testing branch or wait till it gets released to stable

Hello All!
Thank you for kicking ass and trying to make this gem playable on linux.
I have a question about MESA.. I am running Manjaro linux. I am in the bauh package manager... I do not see the current version of Mesa y'all are using. I am capped at 20.0.7-3. I suppose I need to manually install 20.1.2? I find it odd because that package manager sources from Arch as well.

Manjaro uses multiple branches.. stable, testing, unstable. Each with different stages of testing basically. Mesa 20.1.2 is only available on testing atm, though it should be released to stable in a couple of days I assume. There is usually not a huge delay.

Oh, I see. I will change to testing then! That's sort of the reason why I moved over to Manjaro from Ubuntu.

I did not want to mess up the mesa / bauh relationship. (If) that's a thing by manually installing.

Running on Ubuntu 20.04 with nvidia 440.100 driver. Stability is surprisingly good with the proton-5.0-rdr2-4, installed fine and the game was able to load.
Performance is lacking though, choppy framerates at only 1080p with 2080ti and 6700K on lowest settings. Must be a driver bug on 440.100 as the GPU is only 30-40% utilised. Game works for the most part but ALT+TAB requires that the game be switched from fullscreen to windowed and back again otherwise the game shows on only a portion of the screen. ALT+ENTER twice achieves that.

@chris-echoz thanks for the answer but the reason was MSAA... After disabling it the mission works like a charm. I rechecked it a few times and it stably repeated. With x2 MSAA companion stucks in an animation, without MSAA all is good.
@hakzsam I'm not sure the bug on mesa side but maybe it's interesting for you. More info you can find in my comment https://github.com/ValveSoftware/Proton/issues/3291#issuecomment-650534543

I've found a critical bug using both AMDVLK and Mesa/ACO. On the Jim Boy Calloway mission with Emmet Granger, (spoiler) Arthur sticks some dynamite in Emmet's manure pile and sets it off. On both of these drivers, just before the explosion effect there will be a total lockup.
On Mesa/ACO, the game will turn into complete colour corruption but the system will remain responsive and it's possible to recover from TTY.
On AMDVLK, this causes the exact same full screen corruption but also a total system hang requiring hard reboot.

I wish I had more useful information than a description of events but hopefully someone else can test and gain useful info. This is on Vega 64 with kernel 5.6.19-300.fc32.x86_64. It might be an issue with the core amdgpu driver?

Game worked yesterday and launched several times but today I have an activation error saying that my account is not entitled to the game... Is this an error due to Rockstar's servers or Proton?
Launching standard Steam copy of the game with Proton build listed here.

You have to try several times. It's a known problem.

Hello Everyone,

i wanna share my progress so far:

Setup 1:
Pop OS 20.04
GTX 960 2GB
Proton-rdr2.4

The game startet with resolution 1280×720 and the outdated Mesa driver Warning pops up. After skiping the warning the game started quit nicely. On the first launch the game stucked for like 10s on the smoking intro, but recovered afterwards. The Game was still not playable because of the poor performance from the nvidia driver 440.82 and the small RAM of my graphic cards. I still tested this setup with the beta driver (440.66.15) and got really good FPS on 1280×720 and low settings (average ~70FPS). Conclusion: If you have a GTX 960 with 4GB it is playable on low - medium settings and 1920×1080 resolution with the nvidia beta driver (440.66.15).

Setup 2:
Pop OS 20.04
RTX 2060 Super 8GB
Proton-rdr2.4

Game started with 1920x1080 resolution. Still got the outdated mesa warning, but runs nicely after skipping it. Still not playable because of the poor performance of nvidia driver 440.82. Average FPS was around 20 on low settings. After i installed the beta nvidia driver 440.66.15 (quite a mess on Pop OS) i got a average FPS around 50 on medium settings with ultra textures. Conclusion: To play the game smoothly you need to install the nvidia beta driver. I recommend version 440.66.15, because people reported here unstability with the newer 440.66.17 release.

Further remarks:

• Audio crackle sometimes. Maybe a problem on the pulseaudio side
• While setup RDR2 multiple times during my tests i got the activation error. My workaround was to delete the compdata folder again. (@howels maybe that works for you too. )

I've found a critical bug using both AMDVLK and Mesa/ACO. On the Jim Boy Calloway mission with Emmet Granger, (spoiler) Arthur sticks some dynamite in Emmet's manure pile and sets it off. On both of these drivers, just before the explosion effect there will be a total lockup.
On Mesa/ACO, the game will turn into complete colour corruption but the system will remain responsive and it's possible to recover from TTY.
On AMDVLK, this causes the exact same full screen corruption but also a total system hang requiring hard reboot.

I wish I had more useful information than a description of events but hopefully someone else can test and gain useful info. This is on Vega 64 with kernel 5.6.19-300.fc32.x86_64. It might be an issue with the core amdgpu driver?

If it helps, here is a video of the issue occurring in real time:
https://gfycat.com/famousfearlessbunting

@topsyandpip56 try the vulkan-amdgpu-pro driver.

What distribution are you using?

@Nocccer Yes, deleting the compatdata/1174180 does solve this but it's quite an extreme step as all local settings are lost when this folder is removed, so keybindings etc need to be recreated.

@gee-oh I wouldn't bother with dual-booting just yet.

Far, far too often people are like "well, this game doesn't run as well as I'd like, guess I'm stuck with Windows," and go through all this trouble to dual-boot and oftentimes even go back to Windows full-time, when like, 3 weeks later the game is running better on Linux than on Windows.

RDR2 has already been shown to run faster on Linux than Windows with some setups (articles have been written about it and everything). But this game JUST started working, after literally over half a year of time, effort, and work by a few people behind the scenes.

I've somewhat fallen into this trap myself (though not enough to dual-boot). When Doom Eternal came out and didn't work right out of the box, I legitimately was crushed and thought about dual-booting, and told everyone "well it's not gonna work on Linux, that sucks." A week and a half later it was running as good or better than on Windows. Just give it a couple weeks.

Regarding music or CAD, this isn't the place for any real discussion on that, but there are a bunch of subreddits and other forums that can help you out, you can probably find something satisfactory on both counts.

@topsyandpip56 try the vulkan-amdgpu-pro driver.

What distribution are you using?

Fedora 32 which doesn't have any official amdgpu-pro support. That being said I will test it with VK_ICD_FILENAMES method and report back. I'll also test a custom kernel with the newest amdgpu base driver.

@topsyandpip56 well yeah, neither does Arch, but I use it, that's one of the perks of the vulkan amd pro driver, is that it's standalone and can live alongside RADV (and AMDVLK).

I'd be surprised if there isn't a COPR or some such stuff for it. But either way, you just need the amdvlk32.so and amdvlk64.so files (and you need to put them in /opt/ so they don't conflict with AMDVLK's files of the same name), and then put the .json files in /etc/vulkan/icd.d/amd_pro_icd32.json and /etc/vulkan/icd.d/amd_pro_icd64.json.

@TKCZ https://www.codeweavers.com/xfer/bshanks/public/proton-5.0-rdr2-4.tar.gz works just fine for me

Sorry, but the directory you are currently trying to access is locked. You either need to login to our website to access it. Or enter the key provided to you in the field below.

@TKCZ https://www.codeweavers.com/xfer/bshanks/public/proton-5.0-rdr2-4.tar.gz works just fine for me

Sorry, but the directory you are currently trying to access is locked. You either need to login to our website to access it. Or enter the key provided to you in the field below.

So... You did enter the key public like described here above, right? 😀

@TKCZ https://www.codeweavers.com/xfer/bshanks/public/proton-5.0-rdr2-4.tar.gz works just fine for me

Sorry, but the directory you are currently trying to access is locked. You either need to login to our website to access it. Or enter the key provided to you in the field below.

So... You did enter the key public like described here above, right? grinning

no, just click link...

I tried out NVIDIA's 450.51 beta driver, and it has the same poor performance as 440.82. For now the "Vulkan beta" drivers still need to be used, either 440.66.15 or 440.66.17

@sinaflan well that's your problem. You have to enter the key. It's "public"

@TKCZ https://www.codeweavers.com/xfer/bshanks/public/proton-5.0-rdr2-4.tar.gz works just fine for me

Is it the only version of Proton that supports Red Dead Redemption 2? Haven't GE Proton supported it yet?
By the way, it is locked.

Is it the only version of Proton that supports Red Dead Redemption 2? Haven't GE Proton supported it yet?

GE don't mention Red Dead on their releases page, so it appears at this stage we only have one build that works. But it shouldn't be too long before the various fixes are merged into either GE or the official builds.

By the way, it is locked.

You have to enter the password as described in the original posts announcing these custom builds. If it doesn't offer to let you enter a password, try reloading the page. I had to do that one time.

Is it the only version of Proton that supports Red Dead Redemption 2? Haven't GE Proton supported it yet?

GE don't mention Red Dead on their releases page, so it appears at this stage we only have one build that works. But it shouldn't be too long before the various fixes are merged into either GE or the official builds.

By the way, it is locked.

You have to enter the password as described in the original posts announcing these custom builds. If it doesn't offer to let you enter a password, try reloading the page. I had to do that one time.

Where do you get this?

@laichiaheng You click the link, and it downloads the tarball.

@laichiaheng You click the link, and it downloads the tarball.

I mean the password.

It's "public"

But that link above doesn't even ask for a password.

This one:

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

But that might be because I'd already downloaded it and given the password.

So if that's the case, and you do need it, it's "public"

Is it the only version of Proton that supports Red Dead Redemption 2? Haven't GE Proton supported it yet?

GE don't mention Red Dead on their releases page, so it appears at this stage we only have one build that works. But it shouldn't be too long before the various fixes are merged into either GE or the official builds.

There's maybe more to it than just the patches published otherwise I don't see why those patches haven't been included yet in some custom build. It could very well be that the patches are hacky enough to not apply or work cleanly on newer wine versions. I'm currently thinking about reviving my own Proton branch and playing around with those patches. It could also be possible that the binary build has patches with unresolved licensing issues, and until that's resolved, there won't be published patches, and this binary build is more like a beta test to see if the general idea of the patches works. But who knows, in the end it may just be a pandemic thing which steals time from working on publishing the final patchwork.

So it may be a good idea to use what's published and build on that, and try to get the game running with a custom build that not too far away from the official Proton version. GE and Tk are way closer to upstream Wine and the patches may just not work there.

@sinaflan well that's your problem. You have to enter the key. It's "public"

Thx, work.

How to bypass the reCAPTCHA? I can't see the description in it.
It doesn't allow me to log in, either.

How to bypass the reCAPTCHA? I can't see the description in it.
It doesn't allow me to log in, either.

I see now, it is English only.

The rockstar launcher closed itself when I try to open the game with proton-5.0-rdr2-4

I just can't get into the game, help! I have removed the compatdata for many times.
I'm on Manjaro Unstable Branch, so I should've had the latest packages.
CPU: AMD Ryzen7 3700X
GPU: AMD RX580 8GB
RAM: 32GB DDR4 3600

It shoud not open Rockstar Launcher at all. It happens for me too on Arch and I can't play. I can play on Mint without problems.

It shoud not open Rockstar Launcher at all. It happens for me too on Arch and I can't play. I can play on Mint without problems.

Arch is too new to play this game?

Rock Star Launcher can launcher correctly on Lutris, but not on Steam with this custom version of Proton.

It shoud not open Rockstar Launcher at all. It happens for me too on Arch and I can't play. I can play on Mint without problems.

Arch is too new to play this game?

I don't think so. It's a missing package or setting, I don't know.

@laichiaheng Am on manjaro stable with the same GPU and the previous generation of that CPU.

I needed amdvlk to run it. After installing amdvlk VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/amd_icd64.json WINEDLLOVERRIDES=dxgi=n,b %command% worked fine for me. (Except sometimes it fails to connect to the server, but just try again in that case)

@laichiaheng Am on manjaro stable with the same GPU and the previous generation of that CPU.

I needed amdvlk to run it. After installing amdvlk VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/amd_icd64.json WINEDLLOVERRIDES=dxgi=n,b %command% worked fine for me. (Except sometimes it fails to connect to the server, but just try again in that case)

Is this all you did, or were there other requisites (custom Proton, driver patch)? I've been looking through this thread as a noob trying to understand how I can get the game working on my AMD system on Steam with the least chance of messing things up.

@myahenochs I used the custom proton build linked somewhere in this thread. But besides that no change except forcing amdvlk and the WINEDLLOVERRIDES
(Mesa is 20.0.7-3 btw, but i think that doesn't matter at all when using amdvlk .?)

@kisak-valve Thanks for the reply! I knew about that proton build, but the patch was where I was lost (which isn't mentioned in the comment you linked, I know, but the author links it). I've been looking at if there was any breakthrough that doesn't rely on the patch, or if I'm better off waiting. Seems like @SleepProgger has done that? I'm not at my PC for a few days, just here to make a plan of attack :) Thank you both, I appreciate your patience with me.

Hi guys. Can you play on UltraWide resulutions, 21:9?
I can't set it here, even using -width argument..

Hi guys. Can you play on UltraWide resulutions, 21:9?
I can't set it here, even using -width argument..

• Switch to borderless windowed in game's settings
• Use -width AND -height arguments, e.g. WINEDLLOVERRIDES="dxgi=n,b" %command% -width 2560 -height 1080

Hello @myahenochs, there's a one-off dev preview build of Proton in [#3291 (comment)](https://github.com/ValveSoftware/Proton/issues/3291#issuecomment-644542391) that you can try, which should be paired with mesa 20.1.2 for mesa/radv support or nVidia 440.66.15 (vulkan dev branch).

@SleepProgger, until Manjaro updates to mesa 20.1.2+, their mesa build is too old.

I am on Unstable Branch, the mesa version is already 20.1.2

@laichiaheng Am on manjaro stable with the same GPU and the previous generation of that CPU.

I needed amdvlk to run it. After installing amdvlk VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/amd_icd64.json WINEDLLOVERRIDES=dxgi=n,b %command% worked fine for me. (Except sometimes it fails to connect to the server, but just try again in that case)

Thanks! It works!
Why doesn't it detect my controller?

Hi guys. Can you play on UltraWide resulutions, 21:9?
I can't set it here, even using -width argument..

• Switch to borderless windowed in game's settings
• Use -width AND -height arguments, e.g. WINEDLLOVERRIDES="dxgi=n,b" %command% -width 2560 -height 1080

Hi @artemyto! The game launch with correct resolution, but taskbar continue visible. If I use ALT+ENTER to try to restore full screen, it changes back to 1920. But as I can hide taskbar before starting the game, I can now play in my native resolution. Thank you for your help!!!

Hello @myahenochs, there's a one-off dev preview build of Proton in [#3291 (comment)](https://github.com/ValveSoftware/Proton/issues/3291#issuecomment-644542391) that you can try, which should be paired with mesa 20.1.2 for mesa/radv support or nVidia 440.66.15 (vulkan dev branch).
@SleepProgger, until Manjaro updates to mesa 20.1.2+, their mesa build is too old.

I am on Unstable Branch, the mesa version is already 20.1.2

@laichiaheng Am on manjaro stable with the same GPU and the previous generation of that CPU.
I needed amdvlk to run it. After installing amdvlk VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/amd_icd64.json WINEDLLOVERRIDES=dxgi=n,b %command% worked fine for me. (Except sometimes it fails to connect to the server, but just try again in that case)

Thanks! It works!
Why doesn't it detect my controller?

It detects my controller after I restart the game, it works fine with RADV, but the WINEDLLOVERRIDES=dxgi=n,b is still needed.

Did someone manage to play it with 2k resolution?

Add -width 2560 -height 1440 after %command% in the launch options.

Did someone manage to play it with 2k resolution?

Someone managed to play it in 21:9 ratio but I think that it's still 1080p, just extended. Correct me if I'm wrong -- I'd also like to see 2k working.

Edit: Wow, someone gave the right answer right before I posted this. Thanks @joeknock90

It actually works in 2k with -width 2560 -height 1440 and not just extended 1080p but I have 3 monitros, on the left one it shows correctly when I have it on my middle one which is the main it shows some of the game on the left screen and the rest on the middle screen, wow that's a progress

Did someone manage to play it with 2k resolution?

lol, got a 1440p/144hz monitor off craigslist today.. was just about to ask the same question. CHEERS!

Add -width 2560 -height 1440 after %command% in the launch options.

Duh moment... Thank you.

It actually works in 2k with -width 2560 -height 1440 and not just extended 1080p but I have 3 monitros, on the left one it shows correctly when I have it on my middle one which is the main it shows some of the game on the left screen and the rest on the middle screen, wow that's a progress

Add -width 2560 -height 1440 after %command% in the launch options.

Question for you two.. Does it show up as 2560 x 1440 in the game? Or does it show up as 1920 x 1080 still?

It shows 2560 x 1440 but you have to be in window mode if you put it to fullscreen you get to 1080p again, and I still didnt manage to remove the taskbar above and position it properly on my main screen but honestly, I didn't have the time to try more than 5 minutes

It actually works in 2k with -width 2560 -height 1440 and not just extended 1080p but I have 3 monitros, on the left one it shows correctly when I have it on my middle one which is the main it shows some of the game on the left screen and the rest on the middle screen, wow that's a progress

Add -width 2560 -height 1440 after %command% in the launch options.

Question for you two.. Does it show up as 2560 x 1440 in the game? Or does it show up as 1920 x 1080 still?

For me it shows 3840x1200 like it should, only it's not in the center of my screen, so useless since I can't see a third of rdr2 now :(

Does anyone know if a fullscreen fix will come anytime soon?
Also, is online being worked on?

It shows 2560 x 1440 but you have to be in window mode if you put it to fullscreen you get to 1080p again, and I still didnt manage to remove the taskbar above and position it properly on my main screen but honestly, I didn't have the time to try more than 5 minutes

Aww damn! I like playing in full screen. I'll try it as you explained though.

It actually works in 2k with -width 2560 -height 1440 and not just extended 1080p but I have 3 monitros, on the left one it shows correctly when I have it on my middle one which is the main it shows some of the game on the left screen and the rest on the middle screen, wow that's a progress

Add -width 2560 -height 1440 after %command% in the launch options.

Question for you two.. Does it show up as 2560 x 1440 in the game? Or does it show up as 1920 x 1080 still?

For me it shows 3840x1200 like it should, only it's not in the center of my screen, so useless since I can't see a third of rdr2 now :(

Does anyone know if a fullscreen fix will come anytime soon?
Also, is online being worked on?

Damn that doesn't sound fun.

@guustflater In case that you are running Gnome-Shell, installing the "Hide Top Bar" Gnome extension ( https://extensions.gnome.org/extension/545/hide-top-bar/ ) fixed the window placement with borderless fullscreen with my native resolution (3440x1440) for me.

Edit: I have set my launch options like this to enable this extension just for RDR2:

gnome-extensions enable [email protected] && gamemoderun %command% -width 3440 -height 1440 && gnome-extensions disable [email protected]

(you'll need to have gnome-extensions installed for that, using gnome-shell-extension-tool might be an alternative if that is not available.)

Second edit: I got a bit annoyed with the Wine Task Tray that always pops up in Gnome-Shell when the launcher starts. With this https://github.com/jp7677/hide-tray-icons I could get rid of it. Might not be the best solution, but it does the job for me.

That sounds promising because In one of my screens it works perfectly and on the other the positioning is bad and the only difference between the two is the gnome top bar. I will try it in the afternoon after I finish work and also I will have the time to test it extensively in the weekend and I will post results for Fedora 32 with nvidia 2060

Why does it need WINEDLLOVERRIDES=dxgi=n,b? Is it a DXVK bug?

You guys are very luck. I can’t even run this game :(
I don’t own the steam version though so I still don’t know where I should
put the overrides settings

On Fri, Jul 3, 2020 at 1:06 AM 小亨 [email protected] wrote:

Why does it need WINEDLLOVERRIDES=dxgi=n,b? Is it a DXVK bug?

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

--
Rafael Monteiro
84 9833-3150

@rafmonteiro use the Lutris install script for whatever version you have, there's an Epic one and a Rockstar one.

After it does it's thing, right click on it in Lutris and click "Configure". You'll see 4 tabs, go to "System Options," the last tab on the right. Go down until you see the "Environment Variables" field. That's where you enter the WINEDLLOVERRIDES variable. You enter WINEDLLOVERRIDES on the left, and dxgi=n,b on the right (when you go to add, there are two fields). Click "Save."

For resolution, you go to the "Game Options" tab in that same configure menu, and in "Arguments`, you put whatever the width and height are. Click Save again, and exit.

You also need the proton build from here, extracted into ~/.steam/root/compatibilitytools.d. Then run ln -s ~/.steam/root/compatibilitytools.d/proton-5.0-rdr2-4/dist ~/.local/share/lutris/runners/wine/proton-5.0-rdr2-4. Then restart Lutris (you have to exit lutris and relaunch it for this to show up) and reopen that same Configure menu (right-click on RDR2 in your library, click Configure), and go to "Runner options," and in the runner version dropdown menu you'll see proton-5.0-rdr2-4, select that and click "Save." And that's it.

Whether or not it will work, that's another question, but that's how you get all the same tricks people here are using in Steam.

AHA! While the game still locks up after a while (even past the cutscene that caused that severe crash), I was able to retrieve the kernel log for that crash (last time it either didn't show or I couldn't find it). So I'll attach it here with the content I think is most important (basically the red lines with a bit before and after). Hopefully this helps (might not even be relevant to proton, though my knowledge in that regard is way too small.. to not say nonexistent).

The "Reboot" is basically when I hard-reset my pc. Didn't want another severe crash where I had to plug the power supply for several minutes.
Hopefully that helps!

EDIT: Might actually be a GPU issue.. 5700XT drivers still had issues iirc

rdr2_gamecrash.log

EDIT: Might actually be a GPU issue.. 5700XT drivers still had issues iirc

rdr2_gamecrash.log

If it means anything I've played the game for over 50 hours on LInux and never had any crash that required me to reboot my computer or even restart my desktop environment. I'm on Nvidia.

EDIT: Might actually be a GPU issue.. 5700XT drivers still had issues iirc
rdr2_gamecrash.log

If it means anything I've played the game for over 50 hours on LInux and never had any crash that required me to reboot my computer or even restart my desktop environment. I'm on Nvidia.

I also have a 5700. Sounds real nice :(
I only crash during games though, and certain games more than others. Dunno tbh.

Game is installing right now. I'll report back with the crashing situation too if I get some hours in.

@FurbyonSteroid that's a driver crash that's commonly seen by people with Navi cards. Some people seemingly have an actual hardware-level defect that causes those crashes to happen all the time (3-5 times a day, even when just on the desktop and doing nothing), but also there are mesa bugs that cause crashes in specific games.

For example, RADV with ACO enable causes these driver crashes on Navi in Titanfall 2 Multiplayer, but only from 20.1.1 and onward, there's an open bug report for it right now. This might be something similar. Try using AMDVLK or vulkan-amdgpu-pro

I can confirm that the standalone (not steam) version of Rockstar Launcher is working on Arch with mesa-git from AUR using the proton version @mrpippy released :+1:

Obs.: Didn't needed to patch the mesa driver. Just installed directly the mesa-git from AUR, and worked.
Obs.: Applied the WINEDLLOVERRIDES environment as well.

Can't get online working:

Why does it need WINEDLLOVERRIDES=dxgi=n,b? Is it a DXVK bug?

Proton uses wine's dxgi by default to provide better compatibility with vkd3d. WINEDLLOVERRIDES=dxgi=n,b argument activates dxvk's dxgi instead of wine's. So the problem is not dxvk, but wine's dxgi implementation.

after the latest update of nvidia drivers (Fedora 32 440.100) it gives me a second warning that I have to update intel graphics and just hangs there

Can't get online working:

Online doesn’t work on wine/proton.

Why did you mark my question as off-topic?
If the answer is yes, you will no longer have to set WINEDLLOVERRIDES=dxgi=n,b to run the game.

Hello guys

After a fresh reinstall of rdr2 with the modified proton builds, mesa from oibiaf and trying to launch with amdvlk or radv aco, and with environement variable for dxgi
I'm getting this error in the terminal

Someon has an idea ?

Alright so I have a few hours in now. I'm playing directly from Steam with the rdr2 Proton build from this comment.

• Installed amdvlk
• Launch options: WINEDLLOVERRIDES="dxgi=n,b" VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/amd_icd32.json:/usr/share/vulkan/icd.d/amd_icd64.json %command% -width 2560 -height 1440 with the VK_ICD_FILENAMES added as per @gardotd426 with an explanation here.
• Mesa version 20.0.7-3 (I've been told this is not necessary but keeping it here anyway)

Works like a charm with no crashing from the 5700XT bug (so far).

Started up with the custom Proton with no problems except the outdated driver message. Clicked past and I was able to play. I had to restart to use my headphones, but booting back in gave me the Social Club account error. Restarted with Proton 5.0-9, let it crash, and went back in with the custom build again and was able to get to playing without even the driver message that time.

Messed around for 20 minutes trying to get fullscreen 1440p through in-game settings, nothing would work out.
Performance is alright. 50-60fps on mostly high settings. Snow slows it down as to be expected but I'm still in mid 50s, steady 60fps in areas with few particles. I assume there are things I could do to improve performance but I'm happy with what I have for now.

I know that this is mostly rewriting what other people have said/done, but this thread is getting passed around frequently so I figured I'd write up what exactly I did with my results in hopes that this is easier to find than the 5 different comments I got all of this information from.

Updated to keep this all in one comment for those who like that. I've had a single crash to desktop in my 6 hours of play since then. I also had another instance of the Social Club error, switching Proton versions and switching back worked again (and again, I've been told that this is not necessary lol).

@myahenochs If you've installed AMDVLK and are using AMDVLK, then it doesn't matter what Mesa version you're using. If you're using AMDVLK (or vulkan-amdgpu-pro), you're not using Mesa.

@myahenochs If you've installed AMDVLK and are using AMDVLK, then it doesn't matter what Mesa version you're using. If you're using AMDVLK (or vulkan-amdgpu-pro), you're not using Mesa.

Ah okay, sorry, that makes sense. I'm not terribly knowledgeable here.

@myahenochs no worries, just make sure you're aware that you're generally going to be using RADV (Mesa) unless you specifically tell the game/application to use AMDVLK with the VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/amd_icd32.json:/usr/share/vulkan/icd.d/amd_icd64.json environment variable, just installing amdvlk isn't usually enough (though for some reason certain Steam games will use AMDVLK by default if its installed, like Resident Evil 7 and 2).

Well it's nice to have the solution in one comment. Mine seems to work fine too. I just get a message that my driver needs to be updated. From the aur package i got Mesa 20.2.0-devel, the message says i need 20.2.2 or newer. So how would you get it working with something like amdvlk since that is more performant?

@muisje you'd do what I said in my above comment. That's how you use AMDVLK.

@gardotd426 Steam processes the shaders before the game starts and it specifically says "Vulkan shaders," so is it using AMDVLK?

No, the game itself is vulkan. RADV stands for vulkan-radeon, it's the Mesa vulkan driver, and RDR2 is using Vulkan no matter what (because even DirectX games get translated to Vulkan on Linux).

RADV is mesa's vulkan driver.

AMDVLK is the open-source vulkan driver developed BY AMD.

vulkan-amdgpu-pro is the proprietary vulkan driver developed by AMD.

They're all three vulkan drivers.

You need to open your launch options for the game, and add VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/amd_icd32.json:/usr/share/vulkan/icd.d/amd_icd64.json to the launch options. To the left of %command%, the same place where the WINEDLLOVERRIDES option is.

Before that, you need to make sure you have both amdvlk and lib32-amdvlk installed. I don't know what distro you're on, but on Arch/Manjaro, it's just sudo pacman -S amdvlk lib32-amdvlk.

On Ubuntu and other distros, it might put the .json files in /etc/vulkan/icd.d instead of /usr/share/vulkan/icd.d. Just use that instead, if that's where it puts them. There's a .deb package for Ubuntu and it's derivatives here: https://github.com/GPUOpen-Drivers/AMDVLK/releases

Thanks! I did that and did some benchmarks. Should I be noticing a big performance difference? Either I didn't do something correctly or I'm getting only a few more fps at best.

My launch options: WINEDLLOVERRIDES="dxgi=n,b" VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/amd_icd32.json:/usr/share/vulkan/icd.d/amd_icd64.json %command% -width 2560 -height 1440

I really appreciate your explanations. I'm still learning. I'm indeed on Manjaro, by the way.

@myahenochs nope, that's about right.

Flightlessmango's benchmarks showed about a 3-4 percent performance bump over ACO.

There are other games that swing way more in one direction or another (like Doom Eternal, which is like 40% faster on vulkan-amdgpu-pro and 25% faster on AMDVLK), some games perform way better on RADV, that's why you do it on a case-by-case basis.

The main reason AMDVLK was mentioned here is because unless you have mesa-git installed, you can't even use RADV and have to use AMDVLK or vulkan-amdgpu-pro. Not because it was that much more performant. And you have mesa-git, so it doesn't really matter in your case.

@gardotd426 Thank you! I'll remember this for other games. I fixed all of this in my other comment.

@myahenochs nope, that's about right.

Flightlessmango's benchmarks showed about a 3-4 percent performance bump over ACO.

There are other games that swing way more in one direction or another (like Doom Eternal, which is like 40% faster on vulkan-amdgpu-pro and 25% faster on AMDVLK), some games perform way better on RADV, that's why you do it on a case-by-case basis.

The main reason AMDVLK was mentioned here is because unless you have mesa-git installed, you can't even use RADV and have to use AMDVLK or vulkan-amdgpu-pro. Not because it was that much more performant. And you have mesa-git, so it doesn't really matter in your case.

It runs on RADV in Manjaro Unstable Branch perfectly

@laichiaheng yeah, because that's the minimum working version. But that's not available as stable anywhere else (not even vanilla Arch, which I'm typing this from). So what. Most people (actually very few people) are running Manjaro Unstable branch. 20.2 is needed, right now that's only available on mesa-git/mesa master, except for Manjaro Unstable branch (and maybe Solus, I don't know).

Just picked up the game and was really happy to find this thread to help get things running. You are all amazing!

I had a generic "game failed to launch" kind of error initially. But after following the advice to change to Proton 5.0-9, opting out of cloud saves, then switching back to proton_5.0-rdr2-3 I was able to get the game running!
At the moment I am sitting at a rather sluggish 20fps, but I have not changed my nvidia drivers to the recommended beta version yet.

I have no particular launch options, just PROTON_LOG=1 %command%. I have tried WINEDLLOVERRIDES="dxgi=n,b" but it hasn't made any noticeable effect for me.

Kernel: 5.7.1-050701-generic, current nvidia driver: 440.100
Is it worth me changing to the nvidia 440.66.15 driver if my current version is higher?
Cheers
EDIT: I have seen there is a proton_5.0-rdr2-4 which I am now using but seeing similar performance.

@mattlennon3 mrpippy advised to use the dev beta driver especially regarding performance.
https://developer.nvidia.com/vulkan-driver

I have no particular launch options, just PROTON_LOG=1 %command%.

@mattlennon3 PROTON_LOG=1 enables log, which may decrease performance, don't use it to game. You still need 440.66.15 or 440.66.17 to have good performance.

I have no particular launch options, just PROTON_LOG=1 %command%.

@mattlennon3 PROTON_LOG=1 enables log, which may decrease performance, don't use it to game.

Based on my testing (~50 hrs), basic logging barely if at all affects performance, however the vulkan and/or dxvk logging options if manually enabled in user_settings.py decimate performance. Playing with the basic logging on might be useful if you experience some odd bug you want to report.

I have no particular launch options, just PROTON_LOG=1 %command%.

@mattlennon3 PROTON_LOG=1 enables log, which may decrease performance, don't use it to game. You still need 440.66.15 or 440.66.17 to have good performance.

Is that still beta? RPMfusion on Fedora just installed for me 440.100

Arch is on 440.100 too. I don't use Nvidia though so I'm not sure, I know
their versioning numbers get jacked up sometimes.

On Mon, Jul 6, 2020 at 9:56 AM didentifier [email protected] wrote:

I have no particular launch options, just PROTON_LOG=1 %command%.

@mattlennon3 https://github.com/mattlennon3 PROTON_LOG=1 enables log,
which may decrease performance, don't use it to game. You still need
440.66.15 or 440.66.17 to have good performance.

Is that still beta? RPMfusion on Fedora just installed for me 440.100

—
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-654254420,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM5Y3372KLFAH67WWJB2ELLR2HJXXANCNFSM4JV54AXQ
.

Yes 440.66.17 is the vulkan beta driver. 440.100 is not a beta driver but doesn’t have the features required to get acceptable performance.

Just an FYI for anyone who is having trouble with the nvidia driver required:

I have been having trouble getting this 440.66.15/17 driver to build on my machine. This version of the Nvidia driver apparently doesn't build on the 5.6.X or 5.7.X kernels. I have found this recent thread which offers a fix, I followed the patch instructions and then I could successfully build the driver, but afterwards I got a black screen on system boot & had to revert it.
Tempted to roll back to a 5.5.X kernel or earlier and try again without the patches, but it is quite late now. Will try tomorrow.

Thanks so very much for all the work you put into getting RDR2 working @mrpippy.

The Proton build worked out of the box for me on Elementary OS 5.1.6 kernel 5.4.10-asco once I reinstalled the OS as the only way to get rid of the outdated MESA 20.0.0 drivers I installed from the Mesa Graphics Stable Padoka PPA last year.
Installed the Mesa 20.1.99 drivers (RADV/ACO) from the Oibaf PPA and RDR2 booted up just fine.

Ran several benchmarks at 4K (WINEDLLOVERRIDES="dxgi=n,b" %command% -width 3840 -height 2160) on a Radeon VII at stock clocks and settled on:

1. Ultra textures,
2. High settings,
3. all anti-aliasing and Anisotropic filtering turned off except TAA sharpening, (all Anisotropic and AA settings seemed to be really detrimental to performance)
4. unlocked volumetric ray marching resolutions, and
5. resolution scaling at 14/15 x0.933

got an average of 38.7964fps Min of 20.1193 and Max of 62.4376fps

Based on other cinematic style games I play, e.g. Star Citizen, Tomb Raider, Resident Evil 2/3 Remake, etc, performance wise these frame rates are about what I would expect from my Radeon VII. I was able to get an average 49fps, 27fps min and 79fps max at the default low settings running at 4K without resolution scaling.

That said, I will do actual game play testing tomorrow.

It doesn't allow me to open the game the 2nd time I open this game.
Why?

Game crashes after selecting the story mode

Tried it with both the nvidia drivers 440.100 and 440.60.17 drivers(Using 1060 6GB). And I am using custom proton build proton_5.0-rdr2-4 provided by Brandon (@mrpippy).

Also tried with WINEDLLOVERRIDES=dxgi=n,b %command% and WINEDLLOVERRIDES="dxgi=n,b" taskset -c 0-7 %command% and PROTON_USE_WINED3D=1 %command%

Haven't seen this issue on rest of comments hence attaching the log generated with PROTON_LOG=1. steam-1174180.log.gz

Tried heavy steam runtime as well. No luck!

This game crashes a lot!

It doesn't allow me to open the game the 2nd time I open this game.
Why?

When you see this just exit the game and start it again, most of the times it will be fine.

How did you add the gpu information on the left corner? What software are you using?

Almost works.

Problem: Social Club Error 18 (Social Club's Vulkan overlay appears to be unable to inject)
Notes: Before the game launches, this window opens:

Minimum Recommended Hardware Check Failure: Please update your driver. Game requires version 20.2.2 or newer. Please visit [AMD's website] for the latest display driver

My system has an NVIDIA video card, not AMD. Being a laptop, there may be Optimus issues taking place, although I tried the workaround suggested by @headlesscyborg here which unfortunately didn't work.
I tried this suggestion by @nono031 too, but couldn't configure it correctly, so that didn't work either.

Launch:
STEAM_COMPAT_DATA_PATH=<prefix_path> WINEDLLOVERRIDES="dxgi=n,b" <proton_path> run <path_to_LauncherPatcher.exe>
Game launch options (commandline.txt):
-width 1920 -height 1080 -fullscreen

Specifications:
NVIDIA drivers: 440.66.17
Proton: proton-5.0-rdr2-4
Game flavour: Rockstar Games Launcher

Notes and tips:

• If you don't want to redownload the game and your main partition has insufficient space, before logging into the launcher, symlink your game to <prefix_path>/pfx/drive_c/Program\ Files/Rockstar\ Games/. Then, immediately after logging into the launcher, select the game in the panel, press Pre-Load and confirm. Your game should be ready to play.
  Remember not to press Uninstall if it fails. If it does, reinstall the launcher and delete My Documents/Rockstar Games in your Proton prefix.
• If you wipe your Proton prefix often and use the RGL version, create commandline.txt in the game directory and insert your launch commands there instead of inside launcher settings.

With AMDVLK it's working fine with Manjaro Linux.
Audio is also cracking for you?

It doesn't allow me to open the game the 2nd time I open this game.
Why?

Did you try again after you got that error?
I had the same thing a few times, but after closing the game and restarting it again from Steam it worked. It is probably something triggering a timeout or something like that when the game is connecting to social club before it boots to the main menu.

Thought I should have taken a screenshot of the issue when it happened but didn't think much of it when it was happening. However, it would probably be better to initiating logging in the game/WINE/Proton and try to find the point in the log file where the connection failure happens and see what triggers the connection failure between the game client and the Social Club servers.

With AMDVLK it's working fine with Manjaro Linux.
Audio is also cracking for you?

Didn't have any audio issues yesterday when I was running benchmarks and I could be having a separate issue to you, but the cracking audio may be a driver or GPU issue like driver not talking properly to the GPU. In my case at least, I have had it for sometime. Since September/October last year to be precise. It is mainly an issue with my Radeon VII but strangely not on my other rig with a Vega 64. I thought it was the HDMI cable or the optical audio out cable from my TV to my A/V receiver, but I have gone through a number of optical cables, and HDMI cables. Now using an HDMI 2.1 cable but it does pop up here and there even when watching YouTube videos. Haven't done a lot of digging into it though.

With AMDVLK it's working fine with Manjaro Linux.
Audio is also cracking for you?

I take back my previous reply, there was some noticeable cracking when the music was playing in the 2hrs play through I test just did. Not sure if it was just that I had the volume set too high for the music in the game and it was screwing with my speakers or if it is a bigger problem. Will keep tabs as I continue playing over the coming days and weeks.

[EDIT: watching the play back of the game capture, I can confirm that there is a lot more cracking of the audio than I noticed during the play through. Seems to be speech and music]

If you watch the video you can ignore the echo during speech in the cut scenes, this happened because I had my mic volume/sensitivity too high and it was too close to the rear speakers and it was picking up the audio. I have not had the chance to reconfigure the mic and a couple of other things since I reinstalled the OS.

[EDIT: Video is still uploading to YouTube, but just realised that the echo was not the mic but me recording 2 identical audio sources in OBS. One audio source coming from my Decklink Quad HDMI Recorder and the second audio source being the Desktop audio itself. Must have forgotten I usually turn one of them off]

Aside from the audio game play is perfectly fine, though the key bindings do take some getting used to; especially on horse back in first person view.

Actually not really. AMDVLK updates about once a month it seems, same for
Mesa. It's just that AMDVLK are developed BY AMD, meanwhile Mesa isn't and
also has to develop for AMD, Intel AND the open-source Nvidia drivers all
simultaneously. Before, AMD paid little attention to Linux so their drivers
were bleh, but now they're at least marginally trying, and AMDVLK and
vulkan-amdgpu-pro have gotten quite good (especially with Navi). For
pre-Navi GPUs, RADV+ACO is pretty much always the way to go, but with Navi,
it's a back and forth. Mesa's having a lot of struggles with Navi GPUs.

On Wed, Jul 8, 2020 at 1:02 AM Timár Csaba [email protected] wrote:

@myahenochs https://github.com/myahenochs nope, that's about right.

Flightlessmango's benchmarks showed about a 3-4 percent performance bump
over ACO.

There are other games that swing way more in one direction or another
(like Doom Eternal, which is like 40% faster on vulkan-amdgpu-pro and 25%
faster on AMDVLK), some games perform way better on RADV, that's why you do
it on a case-by-case basis.

The main reason AMDVLK was mentioned here is because unless you have
mesa-git installed, you can't even use RADV and have to use AMDVLK or
vulkan-amdgpu-pro. Not because it was that much more performant. And you
have mesa-git, so it doesn't really matter in your case.

Mesa upgrades are so slow compared to amdvlk.

—
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-655285408,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM5Y333I5PLLGRRJ2PRIHL3R2P4WBANCNFSM4JV54AXQ
.

Almost works.

Problem: Social Club Error 18 (Social Club's Vulkan overlay appears to be unable to inject)
Notes: Before the game launches, this window opens:

Minimum Recommended Hardware Check Failure: Please update your driver. Game requires version 20.2.2 or newer. Please visit [AMD's website] for the latest display driver

My system has an NVIDIA video card, not AMD. Being a laptop, there may be Optimus issues taking place, although I tried the workaround suggested by @headlesscyborg here which unfortunately didn't work.
I tried this suggestion by @nono031 too, but couldn't configure it correctly, so that didn't work either.

Launch:
STEAM_COMPAT_DATA_PATH=<prefix_path> WINEDLLOVERRIDES="dxgi=n,b" <proton_path> run <path_to_LauncherPatcher.exe>
Game launch options (commandline.txt):
-width 1920 -height 1080 -fullscreen

Specifications:
NVIDIA drivers: 440.66.17
Proton: proton-5.0-rdr2-4
Game flavour: Rockstar Games Launcher

Notes and tips:

* If you don't want to redownload the game and your main partition has insufficient space, before logging into the launcher, symlink your game to `<prefix_path>/pfx/drive_c/Program\ Files/Rockstar\ Games/`. Then, immediately after logging into the launcher, select the game in the panel, press Pre-Load and confirm. Your game should be ready to play.
  Remember not to press Uninstall if it fails. If it does, reinstall the launcher and delete `My Documents/Rockstar Games` in your Proton prefix.

* If you wipe your Proton prefix often and use the RGL version, create commandline.txt in the game directory and insert your launch commands there instead of inside launcher settings.

Anyways. What does it mean dxgi n, b? Is it something common with Wine?

@rtrevinnoc @xcom169 can you try it again with the nvidia vulkan beta driver 440.66.15. Someone reported that the 440.66.17 makes the game unstable again. @rtrevinnoc besides the crashes you need vulkan beta driver 440.66.15 else the performance is terrible.

Anyways. What does it mean dxgi n, b? Is it something common with Wine?

@xcom169 According to Wine's documentation (edited):

Try to load dxgi as native Windows DLL first and try the builtin version if the native load fails.

I.e. it supposedly overrides Proton's dxgi.dll with the native one.

@rtrevinnoc you need nvidia driver 440.66.15 or 440.66.17 - I also tried with 440.100 but it does not have the beta features you need. You can download it from nvidia as a .run file. I have a comment above which says if you are using the latest 5.6 or 5.7 kernels there are patches to apply to the nvidia driver. Read up through the thread. Good luck.

This game crashes a lot!

If you are referring to the ERR_GFX_STATE crash, that seems to be specific to Vulkan and not Proton as people on windows get the same error. Rockstar's official "fix" is to just use DX12 but there are several other suggested fixes you can find out there. One that seems to improve stability for me is disabling steam overlay and adding -ignorepipelinecache as a launch option (only tested for a few hours today but had no crashes during that time).

My Fedora 32 just wouldn't boot with 440.66.17 even with the patches, from my experience whenever I installed "custom" driver on Fedora it broke, I leave that to RPMfusion, I guess I will have to wait for the beta features to go live. The custom driver is NOT recommended :p

Yeah, beta drivers are too much trouble, waiting for RDR working on stable ones.

On Thu, Jul 9, 2020 at 9:32 AM didentifier [email protected] wrote:

My Fedora 32 just wouldn't boot with 440.66.17 even with the patches, from my experience whenever I installed "custom" driver on Fedora it broke, I leave that to RPMfusion, I guess I will have to wait for the beta features to go live. The custom driver is NOT recommended :p

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

On Amd its working fine..

On Thu, 9 Jul 2020, 11:20 Sergey Lapin, [email protected] wrote:

Yeah, beta drivers are too much trouble, waiting for RDR working on stable
ones.

On Thu, Jul 9, 2020 at 9:32 AM didentifier [email protected]
wrote:

My Fedora 32 just wouldn't boot with 440.66.17 even with the patches,
from my experience whenever I installed "custom" driver on Fedora it broke,
I leave that to RPMfusion, I guess I will have to wait for the beta
features to go live. The custom driver is NOT recommended :p

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

—
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-656014807,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEH2G2QKX6NJODJZAZJUPADR2WDUHANCNFSM4JV54AXQ
.

I just installed this game this morning, played around 1 hour and everything worked really well. I'm getting constant 60fps (vsync) and very playable.

Setup:

• Kernel version: 5.7.7-zen1-1-zen
• Mesa 20.1.2 (Sapphire Radeon RX5600XT)
• proton-5.0-rdr2-4

Launch options: RADV_PERFTEST=aco WINEDLLOVERRIDES=dxgi=n,b %command% -width 2560 -height 1440 -fullscreen

Couple of minor problems I noticed:

• I got the activation error once randomly
• I'm getting the "Minimum Recommended Hardware Check Failure" popup which goes away by clicking ok.
• Benchmark got "stuck" on the first try. On the last scene the character just waited behind the tree and the "police cart" never arrived. The benchmark was running all of this time and did not crash. I have never played this game before so not sure if it's an actual bug in the game. On the second try everything worked.

On Thursday, July 9, 2020, Timár Csaba [email protected] wrote:

On Amd its working fine..

It was all about nvidia.

On Thu, 9 Jul 2020, 11:20 Sergey Lapin, [email protected] wrote:

Yeah, beta drivers are too much trouble, waiting for RDR working on
stable
ones.

On Thu, Jul 9, 2020 at 9:32 AM didentifier [email protected]
wrote:

My Fedora 32 just wouldn't boot with 440.66.17 even with the patches,
from my experience whenever I installed "custom" driver on Fedora it
broke,
I leave that to RPMfusion, I guess I will have to wait for the beta
features to go live. The custom driver is NOT recommended :p

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

—
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-656014807>,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AEH2G2QKX6NJODJZAZJUPADR2WDUHANCNFSM4JV54AXQ

.

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

I just tested out the released 450.57 NVIDIA driver, it has the same performance problems as previous versions.

The Vulkan beta drivers 440.66.15 or 440.66.17 still need to be used.