Kerosyn
Published
Flawless experience, installs and runs
Installing mods also works as expected, no issues to be found, though I don't use reshade so that might take an extra step or two. I don't play online at all either so I also didn't test that.
There are multiple guides on how to actually make this game work on linux on this page already, I'm not going to link to any of them again. There are also a few more on YouTube, the Steam community hub, and other random places. Do I remember where they all are? Absolutely not. Do I even remember what I did? Nope.
What I can tell you is that not a single one of the common guides worked for me... on its own. Trying to set this game up hurt my brain and I waited far too long to post this to be able to remember the specific steps I took aside from using a much older version of Proton just for installation, but I do remember that I had to mix and match different steps from three separate guides.
But once it works, it works. Switched back to a recent Proton GE version and the game runs at full speed, smooth and stable. However, the Proton version MUST NOT be any version of Proton 7, otherwise force feedback does not work. Works fine in 6 and 8.
Works without serious issues, including mods
Exporting to BeamNG isn't a simple one click operation, you have to manually move the exported files to the right location, but it works. Raytracing also doesn't seem to do anything
After ~20 minutes of driving, the game would cause my entire system to crash to a black screen and lock up completely, requiring a power cycle to rescue it. No useful information in any log, temperatures and power draw were well within safe ranges every time. I tried narrowing down the cause myself by unplugging devices one at a time, using different Proton versions, changing graphics settings, and more. Nothing helped.
I picked this up during the summer sale since I have been really looking forward to this game for a long time. Hopefully by the time it goes on such a big sale again, whatever's causing my problem here will have been resolved. Wish I at least knew what the problem even was.
The game runs and mostly works as expected, but is unplayable
There is a constant slight stutter, a slight delay on head movement along with no motion smoothing, a delay on controller movement, occasional major controller jitter, and occaional large hitches. Any one of these things on their own makes the game unplayable at high levels
SteamVR could be the problem, but I don't believe it is. It might be PART of it though
It works normally after enabling a beta branch that should probably be the default branch
Installed libxcrypt-compat
Open the Steam game properties, enter feraldirtsupport in the beta access code box, enable the feral_support_branch beta
The game seems to detect my controller twice, once through Steam input and again through direct input, because when I try to remap my controls, sometimes it gives me Xbox labels and other times it gives me generic numbered button labels.
The game runs slower than I would expect from my hardware, but according to the benchmark, it's still just above my refresh rate of 120hz. Problem is, even though my display is set to that refresh rate, the game only allows me to select 60 or 30, and editing the config file in ~/.local/share/feral-interactive/DiRT Rally/VFS/User/AppData/Roaming/My Games/DiRT Rally/hardwaresettings/ did not help.
Racenet apparently doesn't work for some people, but after enabling the feral_support_branch beta with feraldirtsupport, it works for me. The game also wouldn't launch without that branch enabled, and the Proton version wouldn't even try to launch.
Stable and simple, installs and plays as expected
VR is the only thing I have not tested
The game technically works, but between the random crashing/freezing and the undetectable controller, it is not playable
Deleted GFWL and used patched xlive.dll
While Steam does detect my controller, the game doesn't see it. With the controller mapped to keyboard buttons, it works as an emulated keyboard, but when setting it to xbox inputs, nothing is detected. I only got one chance to look at the steam input configuration though
Game freezes randomly when interacting with menus too quickly, or after playing for over 20 minutes
Opening the Steam overlay freezes the game so hard that I have to kill all processes related to Steam and wine
The game used to simply never launch. Now, it works perfectly
I wish I knew what changed for it to suddenly start working normally, but I can't complain.
"The Steam servers are too busy to handle your request for F1 2014. Error Code (55)"
The game used to simply never launch, no error codes or anything, so I uninstalled it. Now that I've reinstalled it, when I launch the game, it says "Completing installation..." for anywhere from ten seconds to two minutes, then I get that error code.
I think this is progress, because I know what that error code means.
This is one of those games that requires Steam to be installed in its default location, and for the game to be installed into the default library location on Windows (corroborated here: https://steamcommunity.com/app/226580/discussions/0/619568793893846929/)
I don't know how to fix this. Hopefully someone smarter than me has an idea, because with F1 2013 becoming playable, I suspect this game will be as well once this error is worked around.
"The Steam servers are too busy to handle your request for F1 2014. Error Code (55)"
The game used to simply never launch, no error codes or anything, so I uninstalled it. Now that I've reinstalled it, when I launch the game, it says "Completing installation..." for anywhere from ten seconds to two minutes, then I get that error code.
I think this is progress, because I know what that error code means.
This is one of those games that requires Steam to be installed in its default location in Windows. (corroborated here: https://steamcommunity.com/app/226580/discussions/0/619568793893846929/)
However, installing a non-Steam version of this game works perfectly. The problem is exclusive to Steam. Even though I can play the whole game without Steam, hopefully someone can find a solution to this error for Proton.
Does not launch (R6025 pure virtual function call)
Tried manually installing vc 2010-2015 and various dotnet versions. dotnet installs all failed, vc installs didn't help.
I tried every version of Proton available, and every attempt to launch the game either did nothing at all, or showed that error. The native version also does not launch.
Does not launch
Tried manually installing vc 2010-2015 and various dotnet versions. dotnet installs all failed, vc installs didn't help.
I tried every version of Proton available, and every attempt to launch the game either did nothing at all, gave me the r6025 pure virtual function call error, or gives an extremely unhelpful popup that just says "Sorry, something went wrong"
Made it work by disabling SMT in my BIOS, rewarded with performance problems and graphical artifacts
Around the edges of character models and objects in the distance, there are very distracting artifacts, almost like a pixel mosaic filter. Since they don't affect the track or the cars, it's possible to play anyway, but they are always present. There is also occasionally a small but intense vibration across the whole screen, almost like camera shake but a very small amount going incredibly fast, which I'm sure isn't part of the game since it happens seemingly at random and I have camera shake turned off anyway.
My controller simply would not work... but only sometimes. Restart the game once or twice and it works again. Sometimes, it works first try.
The game struggles to reach 120 fps, most often floating around 105, sometimes dipping down as low as 70, and has frequent stutters that drop below 50. Setting the graphics settings to ultra low allows the game to reach 120 more often and to dip less often, but the stuttering does not improve. Rarely, it has a stutter so heavy that it seems to affect the physics and AI in the game. Oddly, vsync has almost no effect on the game, but it does have an effect on OBS if I try recording the game, dropping the OBS capture to 30 fps whenever my actual framerate dips below my refresh rate, or half of it if vsync interval is set to 2.
The game does not launch without disabling simultaneous multithreading in the BIOS. With SMT enabled, it gives error code R6025. I'm assuming this only happens to people with more than an 8c/16t CPU.
By disabling SMT, the R6025 error was solved and the game worked - also true for F1 2015. In my earlier report, I also mentioned the game either simply not doing anything at all or saying "sorry, something went wrong" with no details. Doing nothing at all turned out to be a proton problem, not all versions of proton work with this game. The other error turned out to be denuvo, because every time you change the proton version, denuvo takes that as a new activation, and you can only do that five times a day, so waiting 24 hours solved that. Unfortunately, the performance problems make the game very difficult to play, and I still haven't figured out what's causing those problems for me, because I'm definitely not limited by my hardware, and other linux users with significantly less powerful hardware seem to run the game better than I can.
If you can ignore how it looks, and the occasional hard crash doesn't bother you much, the game works.
gamemoderun %command%
A lot of very distracting square artifacts around the edges of characters and some distant objects. The whole game also looks very oversaturated and overly sharpened, along with some glitched shadows being way too dark, and I don't know if that's a proton problem or the game is just like that.
Occasionally, the controller drops out and needs to be physically reconnected.
If you don't mind the occasional hard crash and a little visual weirdness, everything else is fine.
Square artifacts around the edges of characters. Doesn't affect racing at all though. There is also some ghosting on some things, including your own car, so you see very faint afterimages of yourself as you drive.
With my specs, I see absolutely no reason for this game to struggle to reach 120 fps, but it does. Even on less than max settings. Many tracks only manage 110-115, and some tracks drop as low as 90 in certain sections.
It works exactly as it should ONLY with Proton 8.0
I first tried with Proton 7.0, and while the game pretty much worked, there were some scenes with intense texture and rendering errors that could cause seizures. I moved onto Proton GE 8-3, and not only did the same problem exist, the game also looked visibly worse overall and crashed in the middle of a race. After switching to regular Proton 8.0, it has been flawless.
Seems to work exactly as expected
Poked around in the editor a bit, messing with the stock aircraft, then flew around for a while and encountered no problems at all.
gamemoderun %command%
the game runs, and that's the best thing about it. I did have to use gamemoderun because without doing that, my system couldn't stay awake (just like me) and would dim the display and go to the lock screen while the game was running, which would cause it to crash
With more recent Proton versions, the game simply failed to launch, no errors or anything. With this version, it worked instantly without any trouble.
gamemoderun %command%
Whenever an opponent is close behind me, it sounds like holding a microphone behind a jet engine. It's not distortion or glitchy sound, it could be working as intended, but I find it hard to believe that such a loud and inappropriate sound is really what's supposed to be there
The grass always flickers
Without using gamemoderun, my system would dim the display and go to the lock screen during gameplay.
Confusingly bad performance
All buttons also become unresponsive, often rejecting the first attempt at clicking on them.
After a short time, the game becomes consistently and extremely stuttery, like it's bouncing between 15 and 30 fps rapidly.
Seems to be working normally, aside from the bad performance
At low settings, the game struggles to reach 60 in even the least demanding areas.
Works fine enough
The performance is confusingly bad, but not too bad. It's perfectly playable, it just takes a lot more power to render than I'd expect it to. People on the lower end, nearer to the minimum system requirements probably struggle.
Surprise new update broke the game
1.4.9 worked fine, but 1.4.10 no longer works. There's a new splash screen showing the adobe AIR logo, then the game opens as a solid white 640x480 window that never changes. Tried every Proton version.
Installing OpenPlanet also works perfectly, but does require installing vcrun2022 to work, and launch options WINEDLLOVERRIDES="dinput8=n,b" %command%
Installing OpenPlanet also works perfectly, but does require installing vcrun2022 to work, and launch options WINEDLLOVERRIDES="dinput8=n,b" %command%
Installing OpenPlanet also works perfectly, but does require installing vcrun2022 to work, and launch options WINEDLLOVERRIDES="dinput8=n,b" %command%
gamemoderun %command%
Playing without gamemode enabled leads to frequent stutters on my system, and given the nature of this game, that's practically unplayable. Also, ubisoft connect stays open in the background after quitting the game, but cannot actually be opened to change the settings to make it close itself when the game closes, so the only option is to kill the process manually after playing.
Good news is OpenPlanet also works perfectly.
By default, the game comes with a very old version of Uplay that cannot connect to the Ubisoft servers to update, preventing the game from launching. To fix this, I had to follow the workaround described here: https://github.com/ValveSoftware/Proton/issues/6637
- Download Ubisoft Connect installer
- Place it in steamapps/commmon/Trackmania Turbo/InstallerResources
- Verify integrity of game files
- Edit the install script (steamapps/commmon/Trackmania Turbo/install.vdf)
- Replace "UplayInstaller.exe" with "UbisoftConnectInstaller.exe"
The game now installs the latest version of Ubisoft Connect by default and works normally.
Works perfectly, all issues and fixes are exactly the same as on Windows
Installing OpenPlanet also works perfectly, but does require installing vcrun2022 to work, and launch options WINEDLLOVERRIDES="dinput8=n,b" %command%
