DavidL344
Published
DXVK_ASYNC=1 VKD3D_CONFIG=dxr,dxr11 mangohud %command% PROTON_HIDE_NVIDIA_GPU=1 PROTON_DISABLE_NVAPI=1 PROTON_ENABLE_NVAPI=0
On Hyprland, the first big window that appears is frozen in fullscreen (switching to windowed mode for that segment fixes the issue). After the initial intros play, a new window is spawned, which can be put to fullscreen, but with black bars around the bottom and right of the screen. During the entirety of the intros playing and the game window being open, there's another window in the background, which is fully black at all times (seems to be responsible for controller handling).
My DualSense controller (through Steam Input) would sometimes disconnect, and the game would remember the last pushed buttons and moved joysticks, leading the car to continue responding to the last input before the controller froze and disconnected after a few seconds. This happens very rarely, and re-connecting the controller fixes it most of the time. In rare cases, the haptive feeedback strength forces itself to 100% (any slight rumble would be at maxed-out), making it very uncomfortable to play for basically any period of time. Restarting the computer fully resolves any of those issues, be it the random disconnects or the excessive rumble.
Loading a save after setting a home on either of the expansion maps is much slower, and sometimes gets stuck in an infinite loop. Uninstalling the expansions forces the game to spawn the player on the regular map. To prevent this, I always return out of the expansions and save afterwards.
From time to time, the game stutters for up to 1-2 seconds when loading new areas. It seems to be mostly fixed now, so it might soon not be an issue anymore.
Loading into either expansion might take longer than usual, sometimes even a few minutes. While that is happening, the frame rate is artificially limited to 30 FPS, the same as when loading a save directly from an expansion. Joining an online game also temporarily limits the frame rate while loading, but from what I've seen, its loading speed seems unaffected.
Switching to Proton Experimental is absolutely necessary for the login window to pop up. After the initial login, both Proton Hotfix and ProtonGE work just fine.
In order to remove the black bars in fullscreen on Hyprland, the following solution works:
- Switch to a second workspace right after pressing "Play"
- After the small splash screen with a car and the game's name appears, switch to a third workspace
- Once the third workspace opens a black window, move back to the second workspace - the window that spawned there will contain the game
- Bind compositor-wide fullscreen key binding in your Hyprland configuration (~/.config/hypr/hyprland.conf):
bind = SUPER, F11, fullscreen - Focus the game's window and use the key binding that you've just added to your configuration (Super+F11 in this case)
The reason the custom key bind is necessary, is because toggling fullscreen with Alt+Enter will cause the game to flicker a few seconds before exiting back to windowed mode).
Moving the camera around might result in temporary stuttering (audio not affected). It seems to only happen on a high frame rate output (240+ FPS), however - limiting the frame rate to 120 FPS fixes the issue.
Sometimes, the game doesn't start in fullscreen mode, which can be fixed by either pressing the Alt+Enter key combination twice or switching to another workspace and back.
On certain Proton versions, the mouse sensitivity is significantly higher.
Without toggling the Proton override in the game's settings, the game freezes within seconds after landing in the main menu.
When toggling the Proton version override in the game's settings, Steam starts re-downloading the game - this can be reverted by pausing the update, toggling the switch back, and resuming the update.
Setting custom version of Proton fixes an inevitable freeze in the main menu seconds after loading into it. Playing on most common refresh rate monitors will lead to next to no issues - on high frame rates, the game might stutter, but capping it on a lower value resolves it. On certain setups, the game might not launch in fullscreen mode (in my case, it was Waybar on Hyprland blocking a part of the view) - switching workspaces usually lets the game take up the whole screen. Alternatively, switching to windowed mode and back should also work.
MANGOHUD=1 LD_PRELOAD=$HOME/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so:$HOME/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so" /home/david/.config/r2modmanPlus-local/LethalCompany/linux_wrapper.sh" %command%
Landing the ship freezes the game for 5-10 seconds, and the overall frame rate seems to be on a weaker side despite not looking like a graphically demanding game at first glance.
Works flawlessly, including the promixity chat.
Played exclusively online with mods loaded using r2modman --no-sandbox with no issues whatsoever.
Works flawlessly
Played on a DualSense controller using SteamInput and everything just works, including nice-to-have features, such as haptic feedback and adaptive triggers. The game is showing Xbox controller glyphs instead, but given the game has PlayStation controller support disabled by default, this isn't an issue related to Steam/Proton.
MANGOHUD=1 __GL_SHADER_DISK_CACHE=1 __GL_SHADER_DISK_CACHE_SIZE=100000000000 __GL_SHADER_DISK_CACHE_SKIP_CLEANUP=1 __GL_SHADER_DISK_CACHE_PATH=/home/david/.cache/games/ow2 __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia DXVK_HUD=compiler %command%
The cursor doesn't align with the UI when the in-game resolution doesn't match the monitor's.
After certain conditions, the camera might move to point upwards. This happens seemingly randomly (a one-time thing after switching a character), and also during tasks such as re-plugging a mouse (moves the camera upwards periodically until the game is restarted).
Shaders re-compile on each game boot without downloading pre-cached shaders or explicitly setting shader cache environment variables.
Works with no major issues most of the time. Always make sure you're playing at your monitor's native resolution, minimise any external factors that might trigger a bug which points your in-game camera upwards, and download pre-cached shaders or set shader cache environment variables if necessary.
Works perfectly with no tinkering required
Running the game with Proton should be the preferred way moving forward. Starting with Windows 11, a compatibility mode with elevated privileges seems to be required to launch the game, which is objectively less user-friendly compared to simply launching the game with no prior tinkering.
