VerifiedShow Details
Unknown
The game plays perfectly and performance is identical as when I've played it on Windows 10.
PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 OBS_VKCAPTURE=1 obs-gamecapture gamemoderun %command%
I would recommend using the Windows version via proton than the native build. I had some issues with it, namely it wouldn't pick up my monitor resolution for some reason, forcing me to play at a stretched out 1920x1080.
Works natively out of the box but I highly recommend using proton compatibility layer for better even greater stability!
mangohud gamemoderun %command%
The game is pretty much the same as EuroTruck Simulator 2. It works natively with OpenGL, but for me the performance was a little stuttery, with a little too low fps. I highly recommend you using a version of proton such as: proton 9.0-4. If you still encounter some issues, you can try running with proton-experimental, proton hotfix, or a custom version of proton-GE.
-openvr
ALVR with Quest 2 gets the best performance with the -openvr launch option.
Minor crackling, very rare.
Although the game runs native on Linux, running the Proton version gives me much better performance. Either way, the game works very well, it recognizes my G29 no problem, shifter included.
DX11 version through Proton has better performance than native OpenGL
OpenGL version of the game runs worse both on Windows and as native in Linux, so I recommend running the game in DirectX11 mode trough any Proton version. Doing so will also have better controller suppor (i.e. button icons instead of codes in Xinput mode).
The only launch parameters I use is -nointro and -homedir to make proton installation use the same game folder as native version (in ~/.local/share/).
I do recommend, but only if you are willing to take the time and have the patience to set up any wheels that are not Logitech.
The game itself is Linux native, but getting actual wheels and pedals to work is a pain, unless you have an older Logitech wheel (G29 and alike).
There were several issues I encountered when trying to set up my Fanatec DD wheel and separate Thrustmaster pedals. For the Fanatec wheel, I had to use hid-fanatecff driver found on github. The Thrustmaster pedals have to have an udev rule set so that they are detected as a joystick, not an accelerometer.
Your experience will be greatly varied depending on the sim setup you own. It is much better to have a single vendor for all hardware. It is not the fault of the game itself, hence the recommendation. It is the issue with hardware vendors supporting their hardware on Linux.
It is fine however if you plan on playing on a gamepad, Steam Deck or keyboard.
removed joystick deadzones
Roadsigns illegible at nearly any distance >100ft, UI text perfectly legible
Playing at such a low resolution makes some portions of ATS more difficult, namely reading roadsigns indicating speedlimits and warnings. ultimatly performance isn't much of an issue, some minor slowdowns depending on traffic dencity and environment complexity but all about 30fps at any given time on medium settings.
Forcing Proton Experimental allowed me to use my Logitech G29 wheel. Otherwise, no issues.
Use Proton Experimental on multi-monitor setups. Otherwise will have issues with full screen and Alt+Tab'ing from the game.
For the smaller writing it can be hard to see using the deck screen
Ran out of box
Ran fine after install
No issues
mangohud %command% -openxr
Framerate capped at 45fps despite GPU not maxed out for seemingly no reason (in VR)
Menus do not display in VR, requiring you to check your monitor when paused or starting the game (game view freezes in headset when paused, take caution if you get motion sick easily)
With a Quest 2 using ALVR, VR is also doable for this game, but it'll be a bit bumpy. (in fairness, I don't remember it being flawless on Windows either). Remember to change the beta track to Oculus
This game gave me splitting headache for two days
Whatever I do, most of my keyboard (letters) don't work. At all. Which means no keyboard controls, no World of Trucks account login, no nothing! I'm 110% sure that I have en_US keyboard layout forced properly as I use "single layout for all windows" mode - and I'm able to type stuff just fine in in-game Steam overlay. I don't understand what the actual hell is wrong with this game.
Would not let me go to other windows
Does work Native (I didn't have issues with my dual monitor setup), but for me the bottom panel would always show even in Fullscreen. Forcing Proton Experimental fixed that.
Cursor rendered in game was stuck in the game
Performed slower than expected
Works well with Thrustmaster T80 in controller mode
It's a bit of a pain to play at the moment, controller configuration is not good enough out of the box
Resolution was too high on launch. Had to edit config.cfg file to run properly
Works natively OOTB.
If you have a non-English keyboard with special characters, the game controls don't recognize those special characters, only English ones. You need to assign keys that are present in the English keyboard layout.
If they're into truck simulators, sure. In all seriousness, it runs on par with Windows, if not a little better.
Set your resolution in the config.cfg file located under this directory: ~/.steam/steam/steamapps/compatdata/20880/pfx/drive_c/users/steamuser/My Documents/American Truck Simulator/ My example: uset r_mode_refresh "165" uset r_mode_height "1080" uset r_mode_width "1920" And set these to 1-2k each uset t_averaging_window_duration "2000" uset t_averaging_window_length "2000"
OpenGL is just terrible, I would average 40-60FPS. I tried out Proton.9.0-1, and it had some FPS and stuttering issues. GE-Proton.9-6 vastly improved stability, and increased my FPS to 70 in large cities, and up to 120FPS in rural areas. My framerate stays above 60FPS and never drops below. Overall, this was better than what I was expecting.
FPS fluctuation slightly higher threshold than windows, but overall average was higher by a good margain.
In /home//.local/share/American Truck Simulator/config.cfg change the following lines to match your monitor's specs:
uset r_mode_refresh "165"
uset r_mode_height "1440"
uset r_mode_width "2560"
NOTE: You have to run the game once in order for it to create this file.
Game tried to stretch over both monitors. Ran SteamTinker Launcher. Changed the resolution to my main monitor's resolution, opened ATS and changed the in game resolution in the settings. Was able to then disable STL's own setting, and remove it from steam's launchers. No further tweaks necessary after running it on Native post-STL
Read game-config notes.
On a dual monitor setup, you will need to change the game's resolution through SteamTinkerLauncher. Other than that, 0 issues so far
With a dual monitor setup, the native version will try to strech across both screens. With Proton, it works fine.
My wheel (G920) worked fine out of the box but my SKRS kept moving the mouse cursor when I'd flip one of the switches on it despite me telling the game to ignore it as a mouse. It only moves the mouse in the game and not on my desktop. I had to switch to Steam Input to get to stop.
The more complex your setup is, the more problems you'll run into.
Native mode doesn't work with a dual-monitor setup. It'll strech across both screens.
My G920 wheel works great but the SKRS I use was causing problems and I had to tinker with it.
Once I got everything working, the game runs great. I was able to get an extra 10 FPS out of the game compared to the same settings on Windows.
PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 PROTON_ENABLE_NVAPI=1 gamemoderun %command%
after switching to experimental and using the mentioned launch commands this ran perfectly
resolution was a bit silly with two monitors, initially was trying to go across both windows but ended up being stuck on the right monitor while still being ultrawide. Had to set resolution manually in the game's config files to start playing but worked flawlessly afterwards.
Works but resolution is a bit silly
Force Proton If You Have Multiple Monitors
As others have stated, you will want to force Proton if you have multiple monitors, otherwise the game attempts to stretch across both screens. What actually happens is I see half the game on one monitor, and my desktop wallpaper on the other.
The game asks if you want to run DX11 or OpenGL. I chose OpenGL. I haven't tried DX11 yet.
My PS5 DualSense controller worked using the in-game controller settings and selecting Steam Input as an option. From there, an official controller layout was available. My vertical look motion is not inverted when I want it to be even though Steam Input settings says it's inverted, so I might have to tinker with that.
I had to increase brightness within the game menu because it was too dark to see the truck's dashboard.
Other than that, smooth sailing.
PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 PROTON_ENABLE_NVAPI=1 %command%
The game runs well with the native GL version, but using proton experimental and a few options (plus some other native options more) I'm getting on average 100fps and it drops up to 70 on cities or crowded places. My other settings are: "-nointro -64bit -rdevice dx11 -mm_max_resource_size 100 -mm_max_tmp_buffers_size 1000"
It has a problem with dual monitors on the native version, had to switch to experimental.
I was unable to test without my dual monitor setup, but it should work out of box in the native version if you dont have dual monitors.
