usHallgrim
Published
PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 %command% -nointro
I always try the game without tinkering, and the game seemed to be fine before I added the launch options but it felt -smoother- with the launch options I used.
Game would not run until I forced Proton and also it crashed once but did not crash after using the -maxMem=4096 launch option.
-maxMem=4096
When [Alt] + [Tab]bing out of game, I could not switch back into the game.
I ran the game for about 4 hours, before submitting this report.
Game works great except for it would crash during saves until I forced Proton 5.13-6. Now everything seems perfect!
I had to force Proton 5.13-6.
Using Proton 6.13-8 at the start of the game, I could save but just a few rooms in it would crash when saved. I read SteamDB posts and saw a fellow who tried forcing 5.13-6 to fix this issue. I did the same and it fixed the problem.
PROTON_ENABLE_NVAPI=1 DXVK_ASYNC=1
Alt Tab in and out of game to get it to the correct monitor and if the load up screen isn't working this will often get the game going.
See my launch options fixed a lot of the crashing for me.
Have to manually move game to primary monitor everytime I leave and return to game.
I recommend the game.
If you experience crashes, try the different tweeks on ProtonDB, the first one I tried and that helped me was c1-launcher on github.
C1 Launcher helped immensely with the crashes.
I would recommend c1-launcher just for it eliminating the initial load screens. Game loads much faster with c1-launcher. It also helped reduce crashing for me.
Ran flawlessly out of the box.
Seems to only run on your primary monitor if you have a multimonitor setup.
OOTB I didn't get past the EA launcher.
Instead of tinkering with this version, I went ahead and purchased the remastered edition and it was flawless and the remastered version doesn't have that annoying/borked EA launcher.
See significant bugs section. A typical Linux gamer would get necessary tweaks done, but I'm not sure a typical PC gamer would.
In Nvidia Configuration > OpenGL > uncheck Sync to VBlank In Dead Space > Visuals > Vsync > Off (unless in zero gravity or when moving the marker when planetside. In Steam > Dead Space > Properties > General > Launch Options > type “-nointro DXVK_FRAME_RATE=60” without the quotes. Definitely play with Xbox One controller (plugged in).
3 Crashes.
Sometimes I died when landing in zero gravity when Vsync was off. Also, when Vsync was off -- on the final level -- sometimes the marker and drawbridges would fly off the map. Play these parts with Vsync on seemed to fix the problem.
The game loaded up and started nicely but it was crashing every few minutes, so in my Nvidia X Server Settings > OpenGL Settings, I unchecked "Sync to VBlank" and "Allow Flipping". I also turned off Vsync in the Dead Space 2 settings. The game crashed twice on a single playthrough. If you [Alt] + [Tab] out of the game, sometimes the game screen will be corrupted when you tab back in. Just tab back out and back in and you're good to go.
See my customization.
Crashed twice.
The game not starting problems seem to be with the EA/Origin launcher. Try different version of Proton if you are having problems -- I got mine to work with Proton 5.13-6. If different Proton's don't work, try moving the game. It seems to work better if you install Dead Space 3 in your original library at the time you installed Steam. Also, when I [Alt] + [Tab]bed out of the game, when I tabbed back in the controls and sound didn't work, so I saw on ProtonDB a fellow that suggested that you have to tab out, then in, then out, then back in and then the sound and controls work. This worked for me.
See my customization comment above.
See my customization comment above.
See my customization comment above.
Crashed about 4 times.
By the end of my tinkering the game crashing seemed to be overcome, but this was pretty late in the gameplay.
PROTON_ENABLE_NVAPI PROTON_NO_ESYNC PROTON_NO_FSYNC %command%
Alt-Tab didn't always return you to the game. So Alt-Tab out, in, out, and back in again to solve.
I finally got the game to quit crashing, or an update stopped the crashing. Not sure which.
See https://thomasclark.us/articles:gaming:20220220-kingdom-come-deliverance-on-linux-mint for more info on the tinkering I have done. Some folks don't seem to need tinkering.
Over 40 hours and game runs great. No tinkering needed for me.
A great experience all around.
Pretty much a flawless experience on Linux Mint and my hardware.
On my dual monitor setup I was unable to move game between monitors it always displayed on primary monitor.
Flawless. Just picked Forced>Experimental Proton and I had no issues or crashes. Others (Windows users) did occassionally crash. Great co-op game.
Before switching to GE7-15 and using "PROTON_NO_FSYNC=1 taskset -c 0,1,2,3 nice gamemoderun DXVK_ASYNC=1 %command%" launch options I was getting frequent crashes. Afterwards, it almost never crashed, maybe twice in 40 hours?
Issues to deal with whether you are on Linux or Windows.
- A lighting bug associated with newer hardware, for which there is a fix.
- You can't select resolutions higher than 1600x1200 in the settings menu, for which there is also a fix. To fix the lighting issue launch the game with -shadowmode=projector. You can tell if the lighting bug is fixed during the intro screen. If Lambert doesn't cast a shadow on the wall, the bug IS NOT fixed. If he does cast a shadow on the wall, the bug IS fixed.
To get the game to run at the resolution of your display (i.e. 1080p or above) go to /system/SplinterCellUser.ini search for "Resolution" and change that line to read Resolution=1920x1080 (perhaps higher resolutions will work as well not sure) (do not try changing this in game apparently).
More info is available on my website: https://thomasclark.us/articles:gaming:20220118-splinter-cell-on-linux-mint#tinkering-to-get-it-to-run-on-linux
Tinker to solve for resolutions above 1600x1200.
Crashed twice in 10 hours of gameplay.
What a great game and it ran beautifully!
If you have issues, try different Proton versions. I started with 6.3-8 but had to switch to 5.13-6 after an update to my system.
