codeYeTi
Published
WINEDLLOVERRIDES="$WINEDLLOVERRIDES,msvcr100=n' %command% -showScriptErrors -noLauncher -skipintro -nosplash -noPause -noPauseAudio -world=empty -hugepages
Game jumps out of fullscreen if you have multiple fullscreen instances running, but this won't effect most users.
BattlEye runtime broke for ~1 week once, but hasn't happened since.
Version 2.14 breaks compatibility with Linux due to mistake with case-insensitive file systems.
-showScriptErrors -noLauncher -skipintro -nosplash -noPause -noPauseAudio -world=empty -hugepages
Ridiculous that despite reporting this quite early in the testing cycle, this problem still reached live environments, completely breaking the ability to play the game on Linux
-showScriptErrors -noLauncher -skipintro -nosplash -noPause -noPauseAudio -world=empty -hugepages
Despite a brief breakage at the 2.14 update, the developer has been nothing short of fantastically responsive, and had a build out to me within 24 hours that worked again.
If you can get your controller working, this should work out of the box for you. I had isssues with my specific wheel though.
github.com/berama/ffbtools
Force Feedback on the Logitech G920 wheel updates too fast for the kernel, and causes issues after ~1min of playtime, causing me to have to disconnect the wheel, since the problem persists even after closing the game.
Video decoding is broken, but skipping them with Enter works fine
https://github.com/berarma/ffbtools/ with FFBTOOLS_THROTTLING=3 + https://github.com/mcoffin/proton/tree/acc to fix menus rendering in SteamVR + https://github.com/DadSchoorse/vkbasalt with smaa:cas filter to get better image quality
Requires https://github.com/berarma/ffbtools with FFBTOOLS_THROTTLING=3 to prevent overloading the logetech FFB driver in the kernel
Videos don't play, but you can just hit enter to skip them so it's a non-factor completely
Turn off Temporal Anti-aliasing and KTAA (Kunos' version of temporal AA) if you're having performance issues. They're awful, cause some "ghosting" in the image, and slam your VRAM. This problem is also prevelant on Windows, but for those coming here to improve performance, this may be a useful tweak.
In VR, I had to set my headset to 144Hz, letting the game use async reprojection to render at 72fps, as I couldn't hold the native 80fps required for 80Hz at any sort of reasonable resolution. This is different from windows, but the differences in the experience are almost imperceptible, partially due the ACC's VR implementation not being the best on the planet.
Check out https://github.com/mcoffin/proton/tree/acc for my branch that contains Proton fixes required for the game to start, and display menus properly in VR. These changes are submitted for upstream here - https://github.com/ValveSoftware/Proton/pull/4163
With a Logitech wheel, I had to use https://github.com/berarma/ffbtools with FFBTOOLS_THROTTLING=3 to avoid filling the device's FFB message queue.
With Fanatec ClubSport V2.5 wheel, I use https://github.com/gotzl/hid-fanatecff as a force-feedback driver. This worked "out of the box".
For Fanatec load cell pedals (CSL LC and ClubSport V3, etc), you will likely want to use the sysfs interface from hid-fanatecff above to also adjust the sensitivity of the load cell. This will have to be done @ every boot, so I scheduled some udev rules to do it for me.
Videos still don't seem to work, but that doesn't really impact the important gameplay aspects, though it does detract from the tutorial/singleplayer experience, but that probably isn't the most common use case for this game.
Turn off Temporal Anti-aliasing and KTAA (Kunos' version of temporal AA) if you're having performance issues. They're awful, cause some "ghosting" in the image, and really tax your VRAM. This problem is also prevelant on Windows, but for those coming here to improve performance, this may be a useful tweak.
This game also works "fine" in VR (about as well as it does on Windows, which is... "fine"). You'll need a modern (5.9? +) that has my OpenVR overlay patches in order to see menus, but all the 6.x proton series will work fine. This is a very demanding title in VR, so I'd recommend either running the headset at a low framerate (80, maybe 90 in singleplayer), or running the headset at as high as it will go, and trying to trust the async reprojection (not recommended).
In VR, I also found it useful to use the sysfs interface for amdgpu to set the minimum clock speeds of my 6900XT to ~50% of the maximum. This significantly improved "hitches" in the VR experience as the card no longer went in to it's lower power states, causing lag on the next frame as it clocked back up.
If you're having issues with the FFB message queue for any device (logitech, fanatec, etc.) filling up, then I suggest lowering your FFB messaging rate in the in game settings to 111Hz down from the default (333Hz).
Rumble on the Fanatec V3 pedals is supported in the driver, but will not work with the game due to missing translation layers in proton, and a very limited userspace sysfs API that is currently the only way to control them. This is not a big loss, and only affects Fanatec ecosystem users.
Enjoyable, but with a quirk in the settings menu
Single-player seems fine, but once you add in AI, this thing CHUGS
The settings menu is quite buggy, but if you set a setting, then re-start the game, it will work as expected. It gets annoying during initial setup, but it's livable.
Force feedback being largely non-ideal, though it initially appears to work, render this game much less enjoyable for anyone using a wheel.
Force feedback seems to be quite broken, though it attempts to work. This was tried on the following devices.
- Logitech G920 wheel with mainline drivers
- Fanatec ClubSport V2.5 w/ hid-fanatecff
Both exibited similar behavior, indicating unsupported "effects" in the force-feedback API(s)
Seems to have some issues with Xwayland in the past, but I can no longer replicate this.
Probably fine for kicking around w/ a controller, but useless right now with a wheel.
Fantasic game, with fantastic modding community
Seems a little stutter-y, and FreeSync causes issues, but that's likely on the driver side
Very in-frequent crashes. Not reproducable or predictable
If you have it, you'll likely want to disable G-Sync/FreeSync if you experience any screen flashing. This game chugs with super large cities, and your FPS will drop out of your adaptive range. Just something to keep in mind as your city grows.
Needed to add root CA certificate codemasters.pem from other posts to my trust anchors in order to be able to get to the online segment of the game. It's just an SSL issue when it fails to communicate with the servers.
Audio stutters on 5.6, and crackles on 5.4-amd-staging-drm-next. Was not able to fix given the other reports.
FPS stutter due to shader recompilation
Seems to work perfectly, though with some slight stuttering at times that I didn't experience on Windows, likely due to shader recompilation, so that might even out over more playtime
Works fantastically on X11. Minor quirks with Xwayland, but it's getting better with proton 5.0+
On 4.X proton versions, leaving the window under Xwayland can cause you to no longer be able to give input to the game, and a restart will be required. This seems to only be applicable to running the game in Xwayland
Works great, and the diegetic menu controls offer one of the better VR menu experiences that I've encountered
I had one crash in the middle of the second tutorial job, but that may have been a fluke as it looked like the fault of my graphics driver.
Not related to Linux compatibility, but the controls are sort-of finicky, meaning you have to get very close to objects to interact with them, so this game would be more playable with a larger playspace than the tiny one I'm working with right now.
Everything works so long as you keep your focus on the game without switching windows. It's unfortunate, but everything else is 100%
Alt-tabbing or switching windows away from Project CARS causes it to turn black and the game must be restarted.
I don't know why the native Linux port is missing the VR support, but Proton can get it back for you!
Only running with Proton because the native version is (for some dumb reason), missing VR support.
