Great out of the box.
ONLY degredation I can observe is worse generic/SDL gamepad support, the "DualShock 4 Default" binding preset does not line up with the DualSense controller, in the way that it does on Windows. Thankfully, Steam Input does not conflict with the game's input system at all, so all I needed to do was turn it on. Game looks and runs great overall!
Native performance continues to disappoint me! While technically you could run native, Proton has much better graphical fidelity.
One soft lock between levels in Adventure mode, but only while testing Proton compatibility.
Locked to 60fps/60hz to keep under the threshold, rather than letting demanding areas boost GPU wattage. You can play at 90fps no problem though, if you don't mind occasional power draw spikes.
Text is a tiny bit small in the menu, not an issue in gameplay though as there really isn't any (text that is).
Played with Proton instead of Native, not because the build is broken, but rather for cloud save support so I could go back and forth with desktop.
Quality of life improvements that make the game completely Deck Verified. That includes the controls. Not to mention the Graphical Effects and new Optimisations.
Worked out of the box, no tinkering needed
Just worked as expected. Had no problems with the game whatsoever.
Під час локальної гри текст на великому екрані може бути маленький.
Мультиплеер майже порожній.
Грається чудово на Стімдеці. Навіть не довелося щось окремо налаштовувати.
Had to change in-game settings
On first launch, set to wrong resolution
Native Linux build does not recognise Steam Deck's game pad and instead displays generic DirectInput button prompts
Juste un écran noir de temps en temps et problème de plein écran
S'affiche sur l'écran secondaire. Résolution pas adapté à l'écran principal
Native client does NOT recognize game controllers. Proton GE/Experimental client picks up controllers without issue.
Need proton for game controllers to work. Need game controllers for local split screen play. MEH!
WINE_CPU_TOPOLOGY=4:8,9,10,11 gamemoderun mangohud obs-gamecapture %command%
On native build, Dualshock 4 controller was laggy and unresponsive without launching the game with steam linux runtime compatibility tool.
When playing with proton, the framerate tanks if You have more than 4 cpu cores. You can avoid that by limiting amount of threads with WINE_CPU_TOPOLOGY. On native build, Opengl and zink perform worse than DXVK(via proton) in overall.
Max settings 800p@60fps
- Turn everything to max, except real-time reflections (turn them off);
- TDP: 9;
- GPU 900;
- Runs at 15W peak.
Power save config, 60fps
- Turn everything low or off, keep Anisotropic filtering on "Full" and Draw Distance on "Far";
- Switch Fullscreen off, set Resolution to 960x540, and enable Deck's FSR;
- TDP: 6;
- GPU: 600;
- Runs at 10W peak;
Tested on Campaign maps, custom maps may dip (not so) slightly, depending on complexity.
Max settings 800p@60fps
- Turn everything to max, except real-time reflections (turn them off);
- TDP: 9;
- GPU 900;
- Runs at 15W peak.
Power save config, 60fps
- Turn everything low or off, keep Anisotropic filtering on "Full" and Draw Distance on "Far";
- Switch Fullscreen off, set Resolution to 960x540, and enable Deck's FSR;
- TDP: 6;
- GPU: 600;
- Runs at 10W peak;
Tested on Campaign maps, custom maps may dip (not so) slightly, depending on complexity.
The HUD on car's back window and in-game "loading logs" during intros. Nothing terribly important.
WINE_CPU_TOPOLOGY=4:0,1,2,3 %command%
Running Distance with many cores available will cap performance.
Intial game bindings are very bad, with accelerate on the pause button. I suggest using the touch screen to fix the bindings before trying to play.
gamemoderun mangohud obs-gamecapture %command%
Dualshock 4 controller was laggy and unresponsive without launching the game with steam linux runtime compatibility tool.
Proton is bottlenecking performance, couldn't get more than 70fps(probably due to hyperthreading), Native version works buttery smooth.
Native port is running way better than proton version. Make sure to use Steam Linux Runtime as compatibility tool for bug-free experience.
Works as expected
The game works perfectly out of the box. There is no graphical degradation, performance is great, online multiplayer works, and there is no input lag. The content from Steam Workshop also works flawlessly.
By default it installs the Linux version which doesn't recognize the steam deck controller. I fixed it by forcing it to install the windows version and use proton. After that, there were no issues.
The game works well if run through proton, but Valve needs to have that be the default since the Linux version does not recognize the controller, as stated earlier.
In order to get gamepad emulation to work on Deck, you must manually specify the version of Proton to use. This will force Steam to download the Windows version and run the game through Proton, and it fixes gamepad input.
At the time of writing, Valve's decision to label this game Verified on Steam Deck is inaccurate. However, you can still enjoy this game with one minor configuration change.
- Open the Properties window of the game.
- In the Compatibility page, enable Force the use of a specific Steam Play compatibility tool.
- In the dropdown list that appears, select the latest version of Proton.
- Close the Properties dialog. Steam will redownload the Windows version of the game.
had to change resolution to read most text
no controller detected, must use k&m layout from community controller layouts which also make fine changes nearly impossible.
Default controls do not work at all
I had to use a community layout, the one i used didn't even have all the bindings and the most popular one didn't make a difference. You're going to have to set all the bindings yourself in order to play this game.
HUD is on your rear windshield, and with AA turned off for 60fps gameplay, the info on the on-car HUD can be difficult to read. Not much going on there though, outside of "INPUT CORRUPT" under certain circumstances.
1280x800, most graphics turned to low, rock-solid 60fps.
Level editor is a mouse and keyboard interface with lots of teeny UI elements, so I'd only try that in desktop mode when docked with real peripherals.
Time displayed on the car
Default controller settings are not mapped correctly. Just make sure to choose "Xbox 360 Default" as Selected Scheme in the game under the control settings and inputs are mapped correctly with the recommended gamepad layout from Steam. Game does not keep device independant graphics settings, so you might have to set your resolution and advanced graphics settings again every time. Having everything on maximum except real-time reflections to off results in perfectly consistent frametimes with 60fps at native resolution.
Controller mapping seems to be off
It seems that when using Intel integrated graphics, the native game runs at only 3-5fps with all the graphics settings at their absolute lowest (including 640x480 resolution).
Running the game through proton allows the game to run at ~50fps with low settings at native resolution (1366x768)
I have not run into any issues playing via Proton
Make sure to turn off hyperthreading on CPUs above 8 cores.
CPUs with more than 8 cores hyperthreaded (16 threads) will get a significant performance regression. My 12 core 24 thread 10920X (which would be the same as a 3900X or 5900X) had considerable lag with hyperthreading on. Turning off hyperthreading finally got the game to a playable framerate.
Owners of the 3900X, 3950X, 5900X, 5950X and Threadripper (AMD) or Skylake-X or 10900K (Intel) may run into a severe performance degradation above 8 cores hyperthreaded via Proton. To solve, turn off hyperthreading or turn off cores/CCDs to regain playable performance.
Using Proton is the only way to enable Custom Music and VR modes.
It doesn't need proton since it's a native linux game.
Using any Xiput compatible gamepad will have improperly mapped buttons, and it won't display the xbox layout.
Doesn't support Steam Cloud
Enabling Realtime reflections result in a massive frame drop. Disabling that option results with no problems.
Running natively the game will not start at all, however proton works flawlessly
i don't know why this game stopped working i liked playing it :(
Runs perfectly fine out of the box.
VR
VR on the Valve Index runs as expected (this feature is not supported by the native version of Distance).
Valve Index - Proton version works great for VR out of the box
Native version works great, too, but doesn't support VR.
Game runs perfectly fine.
Enabling "Realtime Reflections" in the game's settings will cause a massive frame rate drop. Everything else causes no issues.
Native version segfaults on Manjaro for me. A slightly more advanced (though not requiered) configuration can be found on the Steam forums here: https://steamcommunity.com/app/233610/discussions/3/2250055685730815710/#c2250055685739196649
Game works native on Linux (OpenGL). On Proton it works out of the box with DXVK (D3D11 to Vulkan translation). Tested with RADV and the new Mesa ACO compiler on Plasma.
Running this in Proton is the only way to get VR working. Everything works perfectly with my Vive.
Unknown(< 15 minutes with Proton)Forcing Proton is the only way to use the Custom Music feature on Linux. Works as expected. If you want to point to your home folder, it's Z:/home/(username) to find your music files. Distance accepts MP3, WAV and AIFF.
Unknown(< 15 minutes with Proton)
