Fakeman Pretendname
Published
Running on Proton 6.3-5 without any tweaks, appears to work completely and entirely.
Both career and free drive modes have been tested for several hours each, and it appears to be generally up and running using default proton, and certainly works to a perfectly playable level.
I've used it with keyboard and with a Logotech G920, which is mostly working fine. The pedals needed remapping in the controls section, but otherwise work properly. Keyboard remapping is not detecting my UK Laptop keyboard layout, so when it asks for "" I have to press "#", for example, but otherwise works properly.
Force Feedback is inconstent i.e. when you start driving it's sometimes there and sometimes not - then if you retry a lesson, or return to menu, it might be working/not working next time. Audio and radio is working, though I've not so far managed to get any custom radio stations to work. No graphical issues seen on default settings.
Note that before running it, I have to run "sudo vulkaninfo" in terminal, as Vulkan is not initialising correctly without this (I think this is a general issue, rather than specific to this game).
There are occasional in game crashes, though I believe they're part of the original program and not specifically Proton issues. I've not tested multiple monitor setups.
All fine in all modes, after approx 20 hours of play. Working with Logitech G920, with occasional Force Feedback (It is sometimes on or off after returning to menu). G920 pedals needed remapping, but fine afterwards. Radio and custom stations all fine (navigate to the compatdata folder of the game, then through to Steam user's My Documents folder to edit radio.ini).
After 50 hours in game, all seems fine. I've had no language problems - it's all in English.
On my laptop (Ubuntu 18.04), no launch options were necessary, but on my desktop (also Ubuntu 18.04), PROTON_NO_ESYNC was needed to use the "Free Driving Mode".
Without the launch option, the learning/tests worked, but "Free Driving" would crash with "eventfd: Too many open files" and "13786.033:0035:0036:err:winediag:FILE_CreateFile Too many open files, ulimit -n probably needs to be increased".
With the launch option, everything seems to be working as expected.
I had to remap the brake and clutch on my Logitech G920, then it worked correctly.
Without Media Foundation, it ran without videos, and you'd have to press ESC to get to the main menu, and SPACEBAR to skip cutscenes in game. I used the mf-install off github.
With it, it still seems to need a little nudge (ESC) to get to the main menu, but runs fine after - about 5 hours in, no further problems.
After playing about 50 hours, I have had no problems whatsoever. Appears to run perfectly.
Appears to run perfectly out of the box, with the exception of Force Feedback on G920 wheel working inconsistently.
FFB on Logitech G920 Wheel works perfectly for ~5 minutes, then suddenly cuts off. When you start/stop the car, it starts working again. May be an issue with the game anyway.
Seems to run fine out of the box.
Would not detect G920 wheel at all - though most of the game is playable on mouse & keyboard anyway.
Still has problem with mouse drifting down-right every mouse click, or mousewheel scroll. Still has no support for controllers. Otherwise is roughly playable with Keyboard and Mouse.
Under Proton 3.16-8, the mouse pointer drifting down-right has gone, and the game is now even recognising an XBox 360 Controller, and roughly playable with it - though it won't currently recognise my Logitech G920 Wheel at all (Running the game in Linux with a swapped Unity Executable will recognise the wheel, and other Proton games have recognised it fine, so I'm not sure what the issue is yet).
As far as I can tell, this works completely and perfectly out of the box. It's a mouse & keyboard only game, so no controllers to test. I haven't tested its response to multiple monitors.
Having played ~50 hours, and many seasons of the game I have had no problems at all, runs perfectly out of the box. As a mouse and keyboard only game, I haven't tested controllers or multiple monitors.
Using proton-5.0-rdr2-4 (Custom Proton from Proton Github)
I both installed and ran with proton-5.0-rdr2-4.
WINEDLLOVERRIDES=dxgi=n,b %command%
Stuck on a black window
WINEDLLOVERRIDES=dxgi=n,b %command% -width 1920 -height 1080
Failed graphics adapter
VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/nvidia_icd.json WINEDLLOVERRIDES=dxgi=n,b %command% -width 1920 -height 1080
Worked
This got me into the launcher to register.
Every time I want to run it:
After a minute or so, the small square launcher box is replaced by a larger rectangular box. After a couple of minutes, this 2nd box has disappeared, and I run this in a terminal:
PID=$(pgrep RDR2.exe); kill -s SIGSTOP $PID; kill -s SIGCONT $PID
I sometimes have to put it in twice. After a few seconds, it tells me to update my AMD drivers (a work around from the custom proton). I just click OK, then the game starts.
Once it's actually running, everything appears fine for single player (>130 hours). No problems with audio, graphics, speed etc. I've not tried the online mode yet.
Flashes a black screen and immediately closes. Tried all variations of Proton startup options with no success so far. Note that on the Steam Forums and RLL3 forums, it seems that a lot of Windows users have (from time to time) the same problem with it refusing to start.
Since Proton 4.11-7, runs perfectly without any tweaks. Controller is required for game and a wired XBox 360 Controller works fine. Played a few seasons in Career Mode without any problems.
Appeared to run fine out of the box. Slight issue with clutch pedal/gear changing on G920
Clutch on G920 not working correctly. Had to switch to auto-clutch to be able to change gears. May be an issue with the game instead of Proton/Linux.
