Unknown
Works great out of the box.
gamemoderun mangohud gamescope -w 2560 -h 1440 -f --sharpness 0.6 --force-grab-cursor -- %command%
gamemoderun → Enables GameMode (performance optimizations)
gamescope → Runs the game in a nested Wayland session
-w 2560 → Sets width to 2560 (upscales from 1080p to 1440p)
-h 1440 → Sets height to 1440 (upscales from 1080p to 1440p)
-f → Enables fullscreen
--sharpness 0.6 → Applies 0.6 sharpness to scaling
--force-grab-cursor → Forces the game to grab the mouse cursor
-- %command% → Executes the game with these options
Game does start and the menu works, but when choosing a map the game freezes and crashes.
No idea why this game is listed as unsupported! It runs perfectly at an unbreakable 60 fps limit, though the only framerate limiter the game provides is vsync. It seems as if you can push the settings a little bit too if you want without threatening your fps limit; the most important one to turn off on all platforms seems to be crowds. I played on low settings simply to preserve battery life and for the security of knowing my framerate limit will never break
SWITCH TO LINUX NOW! It is the future of gaming
Single player campaign is online only, and any online features are at the mercy of Codemaster's server, which would randomly goes down.
So far, at this time of writing, EA hasn't implemented their own anti-cheat which is known to not work in Linux in DR2.0. So online services would work as long as nothing is burning in Codemasters RaceNet's server room.
Crashes desktop environment on launch (proton experimental) or loading into a race (proton 8)
Similar to the last report, I'm no longer able to play the game on my system. I don't know what has changed. I have tried both X and wayland, same issue.
Game freezes around 2 minutes in, you're forced to restart the whole pc by long pressing the power button
It's weird seeing this game running (or I should say not running) when I used to play it perfectly on the same pc with absolutely no tinkering.
The game does start up, everything work correctly as soon as it doesn't. I get a game freeze around 2 minutes after launching the game and trying to start a race, that leads into a black screen (I can still hear the game though) and I'm forced to force-restart my pc by long pressing the power button. I tried switching from experimental to stable 9.4 to GE, but the issue was the same around every version I tried. Kinda sad, I was expecting a chill night on Dirt :(
Before thinkering: Audio pops.
Before thinkering: Worst performance when in full-screen.
Was having connection issues when using a G29 wheel (with shifter). Fixed it by changing it to PS3 mode.
Before thinkering: Awful performance.
Had rough performance issues first. Had to thinker with the proton version at the 'Compatibility' menu and install the mesa driver.
Graphical performance issues initially
Full screen had performance issues initially
Playing with G29 wheel and shift was fine for most part. However, the device disconnected once (has't happen since thinkering with the proton and drivers)
20 FPS, unplayable
In menus: 60 fps; In game: 20-30 fps
The game runs at 60 fps in the menus, but in races it runs around 20-30fps, which makes it unplayable. I have tried everything: changing the Proton version, graphics drivers, launch parameters, I have even changed my OS from pure Arch to CachyOS (very good distro, by the way). When I made this last change it worked fine, but it went wrong again as soon as I restarted the PC.
mangohud %command%
Works fine out of the box. Thurstmaster T300RS is fully functional with hid-tmff2 drivers.
Like a native game... that's it!
Smooth experience, no problems and even better performance than on Windows.
Works well
Some cars have a weird audio issue, where the engine audio cuts for miliseconds and if feels like its turning on and off multiple times a second, but only some cars, and changes everytime I launch the game, seems to be random
Aside from some very small (but annoying) audio bugs, works perfectly well
Game launches but maps doesn't start. Immediatly closes and gives an error.
gamemoderun %command%
Access violation at address 0x408fa87f in module 'dirtrally2.exe' + 0x8fa87f. dirtrally2.exe
its rlly the only rally game that is great on dirt, richard burns is the king but this comes close and runs well + looks great
/home/pollux/ffbtools/bin/ffbwrap --throttling --throttling-time 21 /dev/input/by-id/usb-Logitech_G920_Driving_Force_Racing_Wheel_for_Xbox_One_000092fa4b58ed30-event-joystick mangohud -- %command%
my g920 wheel feedback is extremely delayed which requires ffbtools to throttle the feedback so my wheel feels great in the game, with a controller there is no issues
if you have a wheel look into ffbtools for fixing feedback problems as it can throttle the wheel like on my g920 wheel
runs perfectly, controller, keyboard and mouse, wheel, all work perfectly.
The game runs almost perfectly out of the box. On KDE Plasma a minor tweak is required when using a steering wheel.
gamemoderun %command%
On KDE Plasma add "gamemoderun %command%" to prevent it from going to sleep while using your steering wheel.
DXVK_ASYNC=1 RADV_PERFTEST=aco,gpl gamemoderun %command%
Game seems to run around 25% slower compared to Windows on ultra settings, while lower settings seem to be running as good as Windows.
Newer versions of Proton have some issues which cause the framerate to basically halve, so you should switch to 8.0-5, though since the game is pretty well optimized, you still might be getting over 60 fps on experimental if you lower your settings or have beefy hardware, that's why I classified it as playable without tinkering.
Other than that, the performance on ultra is noticably slower than on Windows given my hardware, since it goes from 70 to below 30 fps in heavier scenarios. I'm getting over 100fps on high though, which is about what you would expect from this game on Windows. Probably related to Vulkan having lower performance rendering certain stuff compared to DX.
Works out of the box without issues that prohibits you from playing the game. Some minor issues but nothing too bad.
Some stuttering, but when I clicked on the game window it dissapeared (same with the crackeling noise). It did come back a couple times though, haven't debugged the issue yet.
Worked flawless with the valve index vr, no issues at all.
Decent performance
Minor sound issues
gamemoderun mangohud %command%
After a few minutes of playing, the game freezes.
Functioned fine a couple months back, now crashes 2 ish minutes into a map. That alone makes it quite hard to play.
DXVK_ASYNC=1 PROTON_ENABLE_NVAPI=1 PROTON_LOG=1 mangohud gamemoderun %command%
Game crashes 1-2 minutes into a stage
Tried upgrading and downgrading proton, changing around launch options and messing with graphics options — doesn't seem to help much. Downgrading to 8.0-5 made it stable for around one minute longer.
Runs perfectly out of the box, Steam Deck locked at 40fps but no other adjustments made to deck or in game.
DXVK_ASYNC=1 DXVK_FRAME_RATE_LIMIT=60 RADV_PERFTEST=aco,gpl PULSE_LATENCY_MSEC=90 PROTON_LOG=1 gamemoderun %command%
I only used these initialization options because I saw people on ProtonDB recommending.
I believe there is not need for any tricks, I only used the initialization options because people recommended. The game runs with a lot of FPS, normally more than 100fps and graphics are beatiful. It was one of the best experiences playing on Linux.
You can just install it and play.
On KDE Plasma, system crashes a few seconds after loading into a stage
Not a plasma issue, so I am filing bug to MESA developers. NOTE: Game runs file on GNOME, probably implementation differences but confirmed its a MESA bug by KDE developers.
