-nolauncher
Smooth experience "high" settings 1080p with solid 60 fps (75-60 fps)
Using GE Proton but run smooth with proton 9 by default
gamemoderun %command%
Crashes often due to Vulkan error in native version, Windows version with Proton works
En Steam Deck, Límite de FPS a 30, TDP a 9W y GPU a 1100 mhz. En el juego, preajustes gráficos en Bajo, sin reducir escalado de resolución, y a 1280x800. Con estos ajustes, aunque no lo veamos a 60 fps, es perfectamente jugable, no se ve nada mal y nos durará la batería.
Sin los cambios mencionados también es jugable, pero los FPS oscilan entre 45 y 60 dependiendo del preajuste gráficos, así como un aumento mayor del consumo de batería y de temperatura. Recomiendo limitarlo a 30 fps.
game-performance mangohud %command%
There have been no problems
Swapped seamlessly between Native and proton. Ended up using Proton to make modding easier
Funciona correctamente y con fluidez, tanto utilizando Proton como con su versión nativa.
En momentos aleatorios el juego puede llegar a emitir sonidos de estática, pero nada realmente molesto.
Un par de veces al llegar a zonas muy grandes el juego puede llegar a trabarse y crashear, sin embargo tras reiniciarlo vuelve a la normalidad.
Es recomendable utilizar la versión nativa del juego con equipos desactualizados ya que sus ajustes gráficos no llegan a las implementaciones aplicadas a la versión de Windows tras la actualización para DX12. En caso de utilizar la versión nativa de Linux es reecomendable utilizar los siguientes comandos:
- MESA_SHADER_CACHE_MAX_SIZE=2G - for AMD/Intel
- __GL_SHADER_DISK_CACHE_SIZE=2000000000 - NVIDIA's driver (470 or newer)
The game runs amazing. I experienced zero issues. With all settings at maximum I was able to pull around 200 FPS average.
mangohud gamemoderun PROTON_ENABLE_NVAPI=1 %command%
No hitches at all and DLSS worked perfectly with NVAPI enabled.
heavy stuttering when moving to new areas
Alright; for starters: the native version was completely unplayable for me. Only proton worked ok-ish.
However, using DX12 will result in heavy graphics artifacting, overflowing RAM, and sound glitches. I changed the version in the graphics menu. the game works ok-ish now with dx11 enabled at 30-40fps
no dx12 means you don't get XESS which could help with performance tho :/
Native Linux borked as usual
The launcher opens but the game never starts when I click play. I dunno why I keep being surprised by Native Linux not working.
Runs perfectly
I have an AMD graphics card, I didn't try the native version since I plan to use modding tools, I used proton experimental from steam, with DirectX 12 enabled (i did not need to do anything extra for this) later I set everything to ultra the only thing i'm switching off is motion blur since i don't like it, so far I reached the first campfire and everything runs smooth and without performance issuses or bugs, a small detail is that i don't use wayland
Works absolutely great (played for couple of hours)
Happened so far once: Saved my Game and loaded it again... Game crash... After rebooting the Game my savefile loaded without issues.
Randomly crashes with the Native version. Gives Vulkan errors "VKWaitForFences Failed"
Native version randomly crashes every 10-30 minutes with Vulkan errors. Ontop of that, the Native version does not have graphical features that the Windows game has, such as DX12 enhancements, Ray Tracing, among others.
So I ended up using the game via Proton, and that fixed the crashing error But I could not play with DX12 option set, it would crash instantly upon launch. I want the additional graphical features and Ray tracing, so I wanted to fix DX12
To fix the game crashing on DX12, I had to download ProtonTricks.
From ProtonTricks,
Protontricks > Shadow of tomb raider > Install default prefix option > Choose d3dcompiler_47 from list > OK
Now the game runs with DX12! Weird, why isnt that set by default?
So the game is playable after initial crashing and time wasting and tinkering, once its up and running and fixed it plays fine, but its not an amazing first impression.
gamemoderun mangohud %command%
Windows and Linux savefiles wont sync. Manually copied the Windows saves (Documents\Shadow of the Tomb Raider) to Linux (~/.local/share/feral-interactive/Shadow of the Tomb Raider/SaveData//save*.dat) in order to share save files between the two.
Other than having to manually sync the savefiles between Windows and Linux, this game is a perfect Linux showcase game.
Native version works better than the Windows Version for me atleast. Could achieve locked 60fps 99%of the game with some drops to 58-59.
Controller was mapped properly however skipping cutscenes only worked via a keyboard. Might be a personal distro issue but reporting still.
AMD's drivers on Linux are more optimised.
Native version worked perfecty, proton would not.
Native version worked for me without any problems, giving me Windows like experience. Using proton would cause instant crash on startup. Don't know why is this the case because most of the time it's native version borked and proton come to help. For me. It's the opposite now.
9 TDP
Small text
You set the graphics to normal and then make the following modifications: Motion blur: off. Spatial reflections on the screen: off. Dynamic hair: low. AMD FidelityFX CAS: 50%. VSync: off. Smoothing: TAA. TDP: 9. FPS limits: 40. With these modifications I get 3 hours of battery
My DS4 controller keep looking up the sky and spinning
With the Epic version, if you not enable EOS Overlay, game would stuck at menu with black screen and music playing in background.
Enable EOS Overlay via Heroic Launcher fix the problem.
Esnync and Fsync enabled the game would not launch, turned off and getting black screen where the main menu is meant to be.
I have the epic games version running trough heroic games and tried various version of proton without success.
I don't know if it was due to a Kernel, KDE6 or mesa update, but the game works perfectly fine with DX12 enabled now (my previous report stated the game would crash to desktop if DX12 was selected)!
NOTE: If you played for a while through Native app you can download saves from https://store.steampowered.com/account/remotestorageapp/?appid=750920 and copy/overwrite the save files located at; /home/username/.local/share/Steam/steamapps/compatdata/750920/pfx/drive_c/users/steamuser/Documents/Shadow of the Tomb Raider/76561198013787404/ (I USE MANJARO, THIS LOCATION MIGHT NOT APPLY TO YOU!) on your computer.
The startup launcher needs the usage of the touchscreen or a mouse
Windows version from Epic works flawlessly, including DLSS and Nvidia ray tracing; DualShock 4 glyphs appear properly
If you get a web browser popup asking you to connect SOTTR to Epic account (?? kinda weird, I got the game on EGS, but okay...), you HAVE TO accept it; otherwise you'll be stuck on a black screen when loading the game, benchmark will be completely broken, and with a new save you won't even reach the main menu. This popup wasn't a thing a couple months ago, perhaps a game update has introduced it.
official control layout maps the right analog stick as mouse, which does not work good for camera control and especially aiming. Configuring it as joystick is recommended.
Having finished all three "new" Tomb Raider games on Deck, I have to say they all work perfectly fine in general. As mentioned here, the default control layout has a big error - the right stick is treated as mouse instead of joystick. So you won't hit anything when aiming ;) Change it, or use one of the many community provided control layouts that already fixed this, and you're good to go. Besides that point, there is nothing to complain about. You can set really high graphical options, the Deck has enough power to make this game run really good.
VKD3D_CONFIG=dxr PROTON_ENABLE_NVAPI=1 PROTON_ENABLE_NGX_UPDATER=1 %command% -nolauncher
It can run with ray tracing selecting Proton compatibility and adding the launch options above. The game runs with smooth frametimes. The benchmark feature in the display options is not representative of the actual gameplay.
DX12 crashes before loading main menu, with DX11 the game can be played
Install the latest vc_redist
DX12 crashes before loading main menu
Native version works great, but I wanted to play DX12 version for better graphics and RT. Mesa devs are aware of this issue. Hopefully it will get fixed eventually
Played through, had one crash and in the Cities with a lot of people are frame rate drops. In conclusion very enjoyable
Provided you plan on cross-saving between a Steam Deck and Windows PC version of the game, I would not recommend playing it on Deck.
Limit to 45 fps.
Launching with the native Linux version (no version of proton selected in Steam) prevents saves made on the Windows version frrom being loaded or recognized.
If ran in Proton, it's required that you launch the game in desktop mode to change dx12 to dx11 in the launcher, otherwise the game won't launch. It will launch normally from game mode after this change.
The Proton version of the game, as compared to native Linux, performs worse. Anywhere from 5 to 10 fps lower.
While it worked, it worked well. Then it stopped working.
The last crash murdered my save game
During my first 3 hours playing, it crashed 6 times
I'm actually ready to handle occasional crashing, but blitzing my save is a bridge too far. Do not recommend.
"Level of Detail" & "Shadow Quality" are extra heavy on your CPU. Setting "Shadow Quality" to any setting except "Off" will result in massive FPS drops when many NPCs are loaded. Biggest impact is in town areas, where I would get 40FPS instead of ~120FPS. "Level of Detail" affects how many NPCs are loaded, so do not set this higher than "High", then set "Shadow Quality" to either "Off" for significantly more FPS or "Ultra" if you're like me & you don't like having no shadows.
DX12 only works if you set "Shadow Quality" to "Off". Only play on DX12 if you already plan to turn shadows off and you need XeSS/DLSS. According to this GitHub issue, this is apparently an RADV driver problem so hopefully a future Mesa update fixes this?
VKD3D_CONFIG=dxr %command% -nolauncher
Start and Select were flipped
