Zolleriux
Published
Got the demo to run but crashes after about 10 seconds into the main menu
On installation, you're asked to install 'Microsoft Visual C++ Runtime', which leads to a UE4 installer which fails. This can be worked around with a method listed for Medieval Dynasty, more about that here: https://www.protondb.com/app/1129580/
Basically, you have to manually get the 'VR_redist.x64.exe' runtime and replace its name with the UE4 installer provided in the games directory. After that, you can proceed through the Visual C++ runtime installation and you can get the game to start. I also used 'protontricks 1620610 vcrun2019', but this appid should be for the demo only.
I was unable to continue playing but hopefully somebody else will find this useful.
Nothing, just a quick black window then nothing.
An update to my old report. The game now works tinker-free and flawlessly without a single issue.
Tried just about everything to run this. Consistently freezes before the main menu, right at "Waiting for system assets to initialize..".
Tried all listed versions of Proton (including GE8-6), vcrun20**-packages, game config changes, verifying, re-installing, moving the game to different drives, proton launch option overrides, unplugging all USB-devices, and many other things.
Game runs well on the Windows drive. Proton 6.3-8 does launch the game, most other versions of Proton just gives a Unity error for me, but no matter what I do I can't get into the main menu. I don't know what I'm missing in case of software or potential hardware conflicts on my system, maybe I need to something like dotnet45 (tried but failed to install with protontricks).
Here's a screenshot of where exactly it freezes (after holding to skip intro): https://i.imgur.com/t2HvBil.jpg
From startup, I am able to get about half-an-hour of good frame rate. Then all of a sudden it drops and becomes very low and inconsistent. Also risks crashing on map change.
Can crash on map change once the aforementioned stuttering begins.
As previously mentioned, add -w and -h to launch options for your desired resolution. I can play a campaign at a time, and then I need to restart the game to avoid stuttering and low frame-rate.
An update to my previous report, the game now works really well with Proton Experimental. No other tweaks.
Played around 5 online races without any issues.
At the time of writing, default Proton version is 9.0-4 but the game fails to launch with that. Proton Experimental works flawlessly as I have not encountered a single issue.
Unable to launch (DirectX Error)
PROTON_USE_WINED3D = 1% command%
Tried different Proton versions until I got Origin to properly launch with GE 7.35. The game window is being launched but then crashes with the following DirectX Error:
"Failed to initialize display adapter. Please ensure your video card is compatible and the drivers for it installed. Usually this is a result of missing vendor specific drivers."
Without "PROTON_USE_WINED3D = 1% command%", Origin would not launch at all.
Works perfectly out of the box, never had a single issue. It even works well with enhancement mods such as Dash Faction and Pure Faction.
From flawless to completely broken
The game worked perfectly fine (almost like native) until the 5.5.0 patch which caused massive performance drops. The 5.6.0 patch broke the game completely as you can't even get into the main menu.
Refuses to launch since update 6.1 added a Kernel Level Anti-Cheat
The game has been running well without any issues in the last few months until now. Now it crashes on startup, regardless of Proton version. Went to the store page and sure enough, there's now a disclaimer that the game is using Kernel Level Anti-Cheat.
Had to edit the config file because of the fps cap. Also had graphical artifacts, could annoy some people but I was able to ignore them.
Crashes at the loading screen (the one with the bear and the fox) consistently with a DirectX error message. Tried e-sync, vcrun2015 and the other tweaks, no luck so far. Managed to run this on the GTX 760 so hopefully new Mesa drivers will do it.
Did not run until either a new mesa update or Steam Cloud settings from Windows version was transferred over. Don't know which, but could be the 'Medium' setting that was carried over, much like the previous poster noted. Game now runs without any issues.
