forbiddenlake
Published
gamemoderun %command%
Starting the game takes several tries due to a crash on the epilepsy warning. Very rarely crashed once in game.
Does not exit cleanly, have to click Stop in Steam
Does not work with Nvidia 565 drivers
Does not work with Nvidia 565.77 proprietary: vertex explosions in the benchmark and loading screens and game. No change with disabling GSP.
Does not work with Nvidia 565.77 open: now the main menu has vertex explosions too.
Does not work with: Proton experimental, Proton 9.0-4, Proton 8.0-5, GE-Proton9-20.
Supposedly[1], it/Mirage might work with GE-Proton8-3, but for me it does not: Now the error is "WGL_NV_DX_interop2 is required but not present."
Then I ran out of activations to try other Proton verisons.
Supposedly[1] it might work with 550, but with Arch/Nvidia EGL package changes, downgrading is no longer trivial.
DOES work with the "Vulkan Launcher" mod from Nexus Mods, but performance is very inconsistent.
Occasional lighting issues, mostly in cutscenes: Delayed lighting changes, or random bright spots.
Occasional freezes, requiring alt+tab and Stoping via Steam. Perhaps a dozen crashes in 90 hours.
I previously left a red thumbs down with Nvidia driver 565.77 due to unplayable graphics explosions. I downgraded to 550.90.07 - and kernel 6.6 - and the game runs smoothly (60 FPS at 2K), with occasional crashes.
I didn't see any difference with the overlay enabled or not. But the overlay is required to get free stuff from Ubisoft Connect including weekly challenges so I leave it enabled.
Native version runs perfectly. No compatability nor launch flags needed.
Like AV1, minor graphical glitches are actually part of the game, not real glitches
Native version runs very well with a couple quirks.
Significant terrain pop-in once I was able to move fast enough - on the mount I could hit a blue void because the ground took so long to load in. This is with textures set to full preload. But it helped (in game options) to use a higher fixed FPS, instead of setting to "Display" refresh rate.
Occasionally the D-pad would act like it was being held down when it was not. Was not a big deal because I only use the D-pad in menus. Disabling Steam Input did not help.
DXVK_CONFIG="dxgi.maxDeviceMemory = 15360;" %command%
I've been playing this game for a long time over a lot of different hardware. For the most part, it runs very well, with almost nothing that can be blamed on Linux.
- [Proton] I've used various flavors and versions of vanilla Proton (8-9), Proton GE (9+), and Proton-cachyos (202412+), and they all work fine.
- [Stuttering] The late 2024, early+ 2025 stuttering, especially at 5 minutes past the hour, is a game issue not a Linux issue.
- [Odyssey] On-foot FPS is not nearly as bad as it was 4 years ago, but it's still not as good as in space, and not as good as it is in the Legacy version. But it's fine.
- [Shadows, lighting] Flickering shadows and weird lighting sources are a game issue not a Linux issue.
- [9070 XT - current card] As of this writing, the 9070 XT requires 3 kernel patches in amdgpu not yet in a release (all titled "Protect FPU in ...") in order to not crash the kernel/display needing a hard poweroff. With them, and a recent linux-firmware and mesa 25.0.2+, the game works very very well. In space I can sustain 150-250 FPS with 1.5x supersampling and AA on at 1440p, so I plan to cap around 120 as my monitor is 120 Hz.
- [6700 XT] Runs fine, for this old card.
- [3070 ti] 8 GB VRAM is too low and causes constant stuttering. Limiting the VRAM using DXVK environment options (as noted here) helps significantly. This shouldn't be as much of an issue on AMD cards.
- [Crashes] Some, nothing unusual compared to playing on Windows.
Quitting the game doesn't work, have to force kill from Steam
gamemoderun %command%
Mods work too (manual installation via unzipping files in the right place)
Works well
Rare missing audio lines
Slight stutter after hours playing
I played 1 and 2 on Windows and 3 on Linux. The EA launcher is occasionally a problem. I consistently had to launch the game twice from Steam to make it in game.
Runs perfectly
Just need to manually click Stop after exiting, due to Ubisoft Connect
gamemoderun %command% -dx11 -force
The Proton version ran well. Using the native version, after 10-20 minutes 99% of the screen would go black, making the game unplayable.
The Proton version runs better than the native version.
Works great
Native XBox controller support didn't let me use the D-Pad. After switching to Steam Input (and changing the in-game button icons to XBox) it works great.
Controller did not work out of the box (used keyboard instead of trying to fix)
After 2-3 hours of playing, significant stuttering occurs. Fixed with a restart.
Native version immediately crashes. Most Proton versions including GE only show a white screen. Proton 4.11 works.
WINEDLLOVERRIDES="dinput8.dll=n,b" gamemoderun gamescope -W 2560 -H 1440 -f -r 120 -o 30 -- %command%
With gamescope, fullscreen still ate my mouse clicks and keypresses after alt+tabbing
Better framerates with gamescope, but would be acceptable without (probably at a lower resolution)
Also with gamescope, alt+f4 would not end all the Wine processes and the game would not relaunch without killing them manually or rebooting. Exiting normally via the slower return-to-title-then-exit worked fine though.
Can be modded, that's what my WINEDLLOVERRIDES launch option does (I just modded out the startup splash screens), but it's a bit complicated to get the mod going in the prefix, in a pure Linux setup.
