
strikekat
Published
~/.local/share/Steam/steamapps/common/Proton\ 7.0/proton waitforexitandrun ~/.local/share/Steam/steamapps/common/assettocorsa/Content\ Manager\ Safe.exe; PROTON_USE_DXVK=1 echo %command%
Used a combination of the guides here: https://gist.github.com/ANBAL534/4f1693536f17b75ebcc8016e0d4cc071 https://gist.github.com/raphaelbruno/609a61bbad8ef011ff9c9c82ef200e17
Force Proton to version 5.0 (required for .net install needed by AC launcher + CM) and try to start the game at least once to create prefix, then run:protontricks --no-background-wineserver 244210 -q dotnet48
The --no-background-wineserver
is critical, otherwise protontricks would hang forever on certain install steps.
From here, you can change Proton back to higher version (I did 7.0). Stock AC ran for me at this point.
To run Content Manager, I followed the steps in the first linked guide and renamed the executable to "Content Manager Safe.exe" and modified launch options as noted.
From here I was able to launch it and install CSP, but CSP did not work until I ran winecfg
and set "dwrite.dll" override to "native, builtin" (also noted in guide).
Have only tried CSP + the NSX car mod so far. Works fine with the Dualshock 4 over Steam Input, but will try a wheel (G29) soon. Hopefully works as per other reports.
Note that CSP's WeatherFX completely tanked my FPS until I disabled it, in case you are chasing performance issues.
~/.local/share/Steam/steamapps/common/Proton\ 6.3/proton waitforexitandrun ~/.local/share/Steam/steamapps/common/assettocorsa/Content\ Manager\ Safe.exe; PROTON_USE_DXVK=1 echo %command%
Update on my prior report that I figured was important enough to post since I can't edit.
I've had a chance to try with a Logitech G29, and Proton 7.0 (and experimental at the moment) do NOT work with force feedback for me. This has been encountered by a few other people
I ended up nuking the prefix, then rerunning my steps with 6.3 instead of 7.0.
I also installed the updated driver new-lg4ff and the GUI config tool oversteer.
After this, FFB worked out of the box in at least AC, ACC, and AMS2.
I did have to remap the steering + pedals in every game.
It also never seems to be mentioned, but at least on the G29 specifically you need to have it set to PS3 mode, NOT PS4 (wasted a fair amount of time on that).
Hopefully the force feedback issue gets fixed in future Proton/Wine revisions.
Just to recap, my prior report but using 6.3 instead of 7.0, then installing the updated lg4ff drivers and everything seems to work out of the box with my G29 now.
Sorry for any frustrations if anybody was trying to get it running with 7.0.
IMO not worth the effort unless you're ready to tinker with it. I couldn't get running from the deck alone, and it's already a pain on desktop.
Following my previous report(s), I couldn't even get the .net install to complete with protontricks on the deck, getting some generic error each time.
That said - I ended up copying my prefix from my working install on my computer, and it actually works, at a smooth 60FPS with many AI drivers. Only thing so far I've noticed is rumble seems very weak/broken.
Have not tried Content Manager, but CSP actually seems to work too (forgot the CSP DLL was copied over too).
You'll want to set trackpad to mouse mode for the launcher and remap some keys for in-game menus.
Only classifying as borked because I could not complete from start to finish on the Deck itself, and I believe that should be a minimum for a "working" classification.
However, ran better than I expected when using my desktop prefix. Hopefully the .net install is fixed or people have better luck with that (I could've just been doing something wrong/stupid).
This game ran way better than I expected, with one exception. Rumble seems to cause the game to slow down (braking, driving offroad). If you turn controller vibration completely off in control settings, the issue goes away.
This is unfortunately also a problem on desktop, and in Project Cars 2 (same engine).
As stated, copy over the SDL2.dll from another KEX game such as Quake Remastered. Before I did that, it ran but majorly hitched and slowed down when using the joystick. Unfortunately I don't know another source for that "better" SDL2 library if you don't have another KEX engine game, but it might be online/uploaded somewhere.
Built-in deck controls glitchy until SDL2.dll was replaced.
"./Cities.x64" %command%
Lots of slowdown when zooming in and out
I had to change the compatibility tool to "Steam Linux Runtime" to get the game to launch.
Use the command above to launch the game directly and skip the useless launcher.
I had no immediate issues loading and playing a medium-ish sized city for ~20-30 min or so.
Performance is.. spotty, but it's playable for being portable and not the Switch version. You'll probably have to tweak the controls to get something really workable.
PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 %command%
Needed both FSYNC and ESYNC variables otherwise I got the blank white screen.
You can set the resolution to 1280x800 but it doesn't seem to support 16:10 aspect ratio as it still letterboxes. A couple minor hitches at start but otherwise arcade mode seems to run fine.
Did not try story mode or online (Since I'm garbage - although it did notify me about online opponents being available i.e. throwdowns)
Since it exhibits the same problem as Blood Fresh Supply where joystick movement causes the game to stutter/lock up, I did the same fix and copied over the SDL2.dll from Quake Remastered and it fixed it here as well.
Significant freezing and stuttering with joystick controllers if not using an updated SDL2 lib.
Nightdive should really update at least this and Blood with the version of SDL2 used in Quake Remastered. There might be other games that exhibit this same issue.
I've tried installing dotnet40 to the prefix, but never was able to get the original launcher to run.
As others have noted, the hwrc-proton-launcher
script works for the most part.
I had to make a few changes for mine:
- I had to just comment out the lines that check if Steam is running. Even after making the changes from an earlier report. Maybe a Fedora issue? pgrep kept throwing an error about libgpg.
- I had to modify all the paths at the bottom of the script to have
bin
instead ofBin
.
After that, works great so far. Performance at 4K easily on-par with my Windows install.
Lastly, the Steam overlay would not appear by just running the script, but adding it as the launch option allowed the overlay to appear fine:
/bin/sh `~/src/hwrc-proton-launcher/hwrc-proton-launcher hwmp`
Just like AMS2, this game runs surprisingly good on the deck with one exception - rumble seems to cause the game to slow down (braking, driving offroad). If you turn controller vibration completely off in control settings, the issue goes away. This is also a problem on desktop, and in Automobilista 2 (same engine).
I haven't personally gotten the drifting/stuttering issues others have noted, unless it's related to that same slowdown issue. If you already own AMS2, I'd say test that first if you were considering buying PCars 2.
Ran once, now crashes or gets stuck every time
Easily the must frustrating Proton experience I've had. I've followed every guide out there exactly, reinstalled the game, and reset the prefix numerous times. This is with Proton 4.11 - 5.0 and 4.3 crash at start.
After a day or so of following those guides, it actually started perfectly. Got through 2-3 hours of gameplay. Next day, changed nothing - just crashes every single time now. It always crashes right after the "discovering DLC" dialog is done. If I remove the savedata, it gets up to letting me start a new game, then crashes immediately where the "car driving" video is supposed to start. If I just don't use the mfinstallcab script, it sits forever loading, if using it - above crash.
The issue is mfreadwrite.dll (tried several versions of it.) The stack trace points to that, and if I put the original Wine DLL back in system32 after mfinstall script, it goes back to being stuck loading. No clue what else to try at this point.
Ran fine for me at 60 FPS as well as functional videos. Only annoying thing was getting letterboxing in both original and widescreen (4:3 and 16:9) modes. Might be fixable with some config file tweaking.
Runs fine on the deck for me, including videos. The video options let me set 1280x800, but the game still seems to play in 720.
%command% -CustomResolution:enabled -r1280x800x32 -Intro:off
Lot of slowdown when moving around the map. Framerate likes to drop to 30 (and below) constantly.
Use the command line options to set the deck native 1280x800 resolution.
As some other reports have noted, the performance in the game is worse than expected on modern hardware. There are a few proposed solutions but I've only tried various command line options so far. I'll post a new report if I try anything else and it runs more smoothly.
I'd say it's probably playable, but I also haven't tried huge cities.
Some of the community control layouts aren't bad, but you'll probably want to tweak them for the deck.
You might need to use the touchscreen to open the options and actually enable controller input. However it worked perfectly after I did that.
%command% -v
Without the -v
, the game would sit on a blank screen at startup.
Please note that I removed that argument when writing this report to double-check, and it actually plays the video now, so either it's been possibly fixed or it's only needed for the initial run.
As noted, installed needed dependencies with protontricks 882710 dotnet20 dotnet461 xact gdiplus allfonts
. (Takes a while to install).
Did not work with 5.13, had to use 5.0.