

Games work fine out of the box, some tinkering is needed if playing with mods but other than that, runs fine.
Game crashes if attempting to set fullscreen, either via launch options or in-game
Initially, there were instabilities when attempting to apply fullscreen configuration and set the game to the correct resolution, primarily because of the dual monitor setup. However, after making adjustments to the settings, these issues were resolved.

Works flawlessly. No tinkering needed at all in my case, and no command line arguments. Runs smooth like butter and rarely drops below 100 FPS maxed out @ 1440p.
Definitely a great experience.

Constant game crashes after every hour or so into the game, only really happens when you get to saint denis or any large cities
Fullscreen doesn't work, switches to borderless mode when switched to fullscreen
Game crashes every hour of gameplay or so, I turned off Smart Access Memory (SAM) and that didn't do anything
I don't know how to fix these crashes, seems like an issue with the game and vulkan - DX12 just makes the game unlaunchable

awful frame times, playable but rough
awful frame times, felt bad to play
Some people running similar hardware were able to fix by forcing experimental - rockstar launcher didn't launch with experimental for me :(

Attempting to run the game on my system just didn't work. I tried with a variety of Proton versions (official and GE).
Refused to launch on Bazzite

Unfortunately not stable for me, haven't found a fix from tinkering.
Game Crashes after a few minutes of runtime. Screen freezes and the windows closes after a second.

Game works great OOTB but if you are using mods, you have to pass the following launch options
WINEDLLOVERRIDES=vulkan-1,dinput8,version,ScriptHookRDR2,OutfitChanger,EasyHook,EasyHook64,EasyHookPatch,EasyLoad64,NativeInterop,SimpleHook=n,b %command%
10/10. Mix of high/ultra settings at 1440p with FSR set to quality mode and I'm able to get ~60 fps.
gamescope --mangoapp -b --force-grab-cursor -w 1920 -h 1080 -f --adaptive-sync -- %command%

LD_PRELOAD="" %command%
LD_PRELOAD="" fixed the mouse stutter problem
Disable 4g decoding and resizable bar

Err_gfx_state
MANGOHUD=1 MANGOHUD_CONFIG="fps_limit=30,vsync=1,fps_limit_method=early,vram,ram,cpu_temp,gpu_temp,fps,frame_timing=1" PROTON_NO_FSYNC=1 PROTON_NO_ESYNC=1 DXVK_CONFIG="dxgi.maxFrameLatency=4" %command% -fullscreen -width 1920 -height 1080 -safe
No he sido capaz de jugar más de 5 minutos, el juego crashea con ese error, he probado a hacer downclock de la grafica y de la ram, a ejecutarlo con dx12, a cambiar la versión de los drivers de Nvidia, pero nada. Con los parametros actuales he conseguido que me dure un poco más.

If you try to play this game using HDR through gamescope, the rockstar launcher instantly crashes, closing the game, making it unplayable.
ENABLE_HDR_WSI=0 gamescope -f -w 3840 -h 2160 --hdr-enabled --force-grab-cursor -- %command%
Only playable if I don't launch through game scope, which limits the game to SDR and 1440p even though I have a 4K monitor.

Ohne HDR ist es perfekt mit jeder proton version über 9+, jedoch mit WaylandHDR=1 oder Gamescoupe funktioniert es seit neuesten nicht mehr.
Warten auf Patches, um HDR wieder benutzen zu können.
40+ hour in game so far, the game run well without any problem.

Occasional crashes in Saint Denis Area, 1 crash in Rhodes with FFFFFF error with Vulkan API. But mostly it ran fine, around 6 crashes in whole playthrough

MANGOHUD=1 gamescope -h 1440 -H 1440 -- %command%
Protontricks not required, launched fine out of the box. Mod support is very easy, effectively the same as windows except for having to add dinput8 to your libraries in winecfg (via protontricks)
Occasionally in Red Dead Online you will get an Error #FFFFFF crashing the game, I dont know what causes this.
Outside of RDOs problems itself, linux didnt change anything

Mantener los graficos predefinidos basta, pero puedes hacer ajustes leves en cuanto a resolución y escalado para mejorar un poco el rendimiento o duración de la batería
Tal vez pueda ser tedioso para algunos tener que instalar Rockstar launcher en el proceso.
Si estas jugando con joystick, al volver de una suspensión, el juego dejará de detectarlo y te pondrá por default teclado y ratón (aplica lo mismo al jugar en modo portatil)
Ola Bb

Rockstar Launcher did give issues when trying to log in, I was presented with the error: "Sorry, we are unable to handle your request at this time"
To fix it, I had to do the following:
(NB: Make sure you are starting on a clean state, if you tried running the game before, use ProtonTricks to enter the RDR2 default wineprefix, and clear all the data so you start on a clean state, Proton tricks can be found at: https://github.com/Matoking/protontricks)
Download the Litrus Rockstar installer from their host: https://dl-eu.opendataapi.net/lutris/games/GTA/rockstar-games-launcher-1-0-36-344.exe
Then go to your local install/download of RDR2 and enter its redistributables folder, usually located in "SteamLibrary/steamapps/common/Red Dead Redemption 2/Redistributables/"
In that folder, delete the "Rockstar-Games-Launcher" and the "Rockstar Social Club" installers. Then copy the Litrus installer into that folder and rename it to the original "Rockstar-Games-Launcher"
Once copied, Launch RDR2 from steam using Proton 8.0-5, You should then get a prompt to install the launcher, follow the normal procedings and when at the login screen use your rockstar credentials and the error should be gone.

Had zero issues

Does not get past registration window
Every time I try to create a Rockstar Games Account I get the error: Sorry, we are unable to handle your request at this time. Without this step I cannot continue. Internet connection works fine.

__GL_SHADER_DISK_CACHE_SKIP_CLEANUP=1 game-performance %command%
Nothing to do just don't change the API in the main menu and leave Vulkan API. DirectX 12 API will crash the game. If you did the step to change the API, here where you need to go :
/SteamLibrary/steamapps/compatdata/1174180/pfx/drive_c/users/steamuser/Documents/Rockstar Games/Red Dead Redemption 2/Settings/
Search the API section inside the file "system.xml" and change : kSettingAPI_DX12 to kSettingAPI_Vulkan. Saving and relaunch the game.

after ~1hr my mouse input begun to stutter everytime (only in the Game)
sadly it started to crash when i was around 10 hrs in when pressed "m" to open my map (now it wont start at all) (sound was still playing but i couldnt make any input)

gamemoderun %command% -vulkan -height 1440 -width 2560
game crash when trying to leave windowed mode
It defaulted to a 720p window

occasional crackling, not sure what makes it occur. Very inconsistent
Had to go into games's settings and set correct screen resolution on first play. Now the game auto opens to full screen, windowless.
see long end notes
For dual boot, Linux Mint and Windows 10, or for using external game storage devices, the RD2 steam files needed to be on an EXT4 formatted drive/partition to work. Steam/proton refused to load the game for me otherwise. The "Play" button would turn blue, then quickly back to Play.
I used Steam to move the game files, then had to verify the integrity of the game files and the Steam Runtime files. Steam needs all three Linux Runtime programs (scout, soldier, sniper) to work. Set forced compatibility, Proton Experimental.
Wine was installed, with the 32-bit libraries, over the course of trouble-shooting the above issue, so not sure if it has an effect on the final result.
To access the save files from both Windows and LM, this requires messing around with the "My Documents" folder. Open Windows and find a program to mount EXT4 in windows. I used Ext4Fsd. Use the program to mount the EXT4 partition/drive in windows. Then in file explorer, right click "My Documents" folder, go to "properties", then "location". Change the TARGET path to "(EXT4 partition/drive)/yourpath/steamapps/compatdata/1174180 (game#)/pfx/drive_c/users/steamuser/documents". I copied all my files to the new path, but copying just the game files might work. I was able to access my saves from LM after rebooting.
Will likely mess up your other uses of the Documents folder when using Windows.

gamescope -W 1920 -H 1080 -f -- %command%
probably because i'm playing under Hyprland. using gamescope fixed the issue
rockstar launcher handles save games slightly weirdly between devices, lost some progress moving from steam deck to pc

Unplayable - Game doesn't start on a laptop with hybrid graphics
I tried multiple Proton versions and launch options. I was only able to play once, for a while it worked flawlessly until it crashed. From that point, I never got it to work. It's always stuck on loading screen. Maybe it'd start after disabling iGPU. I'm not going to do it though, it'd be really unconvinient for me to disable it only for RDR2. Not worth it.

The game runs very well under normal Proton with no settings changed. I had one crash in about six hours of gameplay so far, which I believe was due to running out of RAM while compiling something in Rust in the background (lol). I plan to complete the full game if I don't get burnt out.
Overall, the game runs completely fine just as it would on Windows.

Symlinked Red Dead Redemption to the proton folder, triggered verification then clicked play.
Slight input delay, but went away with turning on DLSS
Used: GE-Proton10-3
Tried multiple Proton versions and launch options. Game doesn't start
gamemoderun %command%

it works out of the box. There are some issues that are resolved with a quick restart if you dont want add launch options.
LD_PRELOAD="" %command%
Noticiable crackling during gameplay.
Game does not like to stay in fullscreen, changes to windowed every start.
Game slows down after around 40 mins of gamemplay, fixed with restart but inconvenient.

Ran quite honestly perfectly throughout my full story playthrough of 46 hours, absolutely zero issues faced.

Runs excellently when it finally starts. Possible "fix" for "A game is currently running" issue?
Takes slightly longer to open than you might think. Like a few others on this forum, I had Rockstar Games Launcher telling me the game is already open. My "fix" for this was found entirely by accident, simply waiting. Yes, really. When the warning window popped up that the game was already running, I started checking my phone for something related to the issue. Around 30-45 seconds later, the game suddenly started without any further input from me. From now on, even though the game says it's already running and won't launch a second copy, I just have to be patient and wait for it to appear. I'd guess it should take no less than two minutes on slower systems, but I don't have any way to test or confirm this.

In having an equal experience on Linux as I did with Windows.
Given my hardware, and after watching a lot of the benchmark videos, I was expecting a 20-30% hit in performance but there's a 0% hit.