

LD_PRELOAD="" DXVK_HDR=1 ENABLE_HDR_WSI=1 gamescope -H 2160 -f -r 144 --force-grab-cursor --adaptive-sync --hdr-enabled --hdr-debug-force-output -- env MANGOHUD=1 gamemoderun %command% +com_skipIntroVideo 1
Sometimes Indiana's torso is transparent.
Xone controller not working in game whilst working in OS.
Huge frametime spike every so often.
No idea why it has the gold badge here, it's anything but gold.

Not enough VRAM (4GB)
For what I read, after patch 2 the game refused to load with a VRAM smaller than 8GB. For sure it does not run with my 4GB VRam. Couldn't find a way to overcome it. I am not sure but I would say this is a game error. The memory gets filled even before the first screen is shown. Why would they need so much memory so early on in the game? I would like to test if I can use very small resolution to overcome the supposed vram limitation, but I cannot start the game. Have not find anybody showing a solution yet.

Not enough VRAM (4GB)
The game says that it has no VRAM enough with 4GB to even start. I read that was a problem that appeared with the first patch. I let it here just to see if someone can bypass this problem. I play with Steam Deck OLED without problems. I feel I should be able to play with a 22 × Intel® Core™ Ultra 7 155H and NVIDIA GeForce RTX 3050 4GB Laptop GPU. The game fills the memory BEFORE it even starts. Do not make much sense to me.
I'm not super far in, but the game just works out of the box, no tinkering required. No stability, grapical or audio issues, no crashes.

__GL_13ebad=0x1 DXVK_NVAPI_GPU_ARCH=GA100 scb -W 3440 -H 1440 -r 144 -f --hdr-enabled -- %command% +com_skipIntroVideo 1
70-90 fps stable on medium settings with ray tracing off and hdr
ran first time with gamescope, launched in 1920x1080, but set 21:9 and 3440x1440 in game options and hasn't been a problem since
scb in launch options gave working steam overlay and recording

mangohud %command% +com_skipIntroVideo 1
Game runs really well on 7900XT, with 1440p UW I get over 100fps with everything at Supreme Settings and XeSS Balanced. With Path Tracing 30-60fps depending on how high.
However there's an issue since update 4 where the fps will drop to 10 as you walk around the map, and some people reported solving it by using amdvlk instead of Mesa. However I don't think that the stutters are gamebreaking, it's still very playable.
I also use ClearlyClaire-Proton-Experimental with Steam Input disabled to get Dualsense haptics working
You can use +com_skipIntroVideo 1 in Steam launch options to skip intro videos

RADV_DEBUG=nodcc gamescope -f -W 3840 -H 2160 --hdr-enabled --adaptive-sync -r 120 -- %command% +com_skipIntroVideo 1
I have the same problem like many others with update 4. With Mesa 25.1.1 i can start the game with working hdr, but get significant slowdowns on traversal and autosaves. Some times it's worse than that and the game will launch and won't go over 20-30 fps no matter the settings. Only restarting the game multiple times fixes this with Mesa 25.1.1. The only workaround is starting the game with AMDVLK v-2025.Q2.1. Than the performance is good and no traversal-slowdowns but unfortunatly hdr wont work anymore.

gamemoderun vk_amdvlk %command%
Using mesa drivers causes the game to stutter shortly, whenever entering a new area. I'm using amd-vulkan-prefixes from AUR to switch Vulkan drivers.

Ce jeu ne fonctionnait toujours pas 4 mois après sa sortie avec une Nvidia RTX 3080 10 Gb sous Windows 11. Après un contact avec le service technique de Betasda ils m'ont affirmé que ce GPU n'est pas pris en charge !? Il fonctionne pourtant parfaitement sous Linux...
The game is unplayable with update 4. Significant slowdown on traversal, every time it loads a new area frames drop to 20fps for a couple of seconds before resetting.
VK_DRIVER_FILES=/opt/amdvlk/etc/vulkan/icd.d/amd_icd64.json:/opt/amdvlk/etc/vulkan/icd.d/amd_icd32.json %command% +com_skipIntroVideo 1
Mesa causes extreme slowdown and stuttering during transitions / autosaves, required manually launching with AMDVLK (used amdvlk-opt)

Since game update 4, game runs great with amdvlk driver. Horrible traversal stutter when using mesa.
LD_PRELOAD="" mangohud game-performance vk_amdvlk %command%
Using mesa, the game will has horrible traversal stutter that was introduced in Update 4. Using the amdvlk driver fixes these issues and also gives a 10-15 fps boost in the game.
On Arch, I am using the "amd-vulkan-prefixes" package so I can keep mesa as my primary and enabled GPU driver. Prefix your launch commands with "vk_amdvlk" to use the driver with this game only. Fixes the stutter and gives better performance than mesa.

LD_PRELOAD="" mangohud DXVK_NVAPI_GPU_ARCH=GB200 PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 %command% +com_skipIntroVideo 1
LD_PRELOAD="" fix for stuttering with Steam Overlay DXVK_NVAPI_GPU_ARCH=GB200 Use this to fool the game into thinking you have 50xx series Nvidia GPU PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 typical Nvidia commands for DLSS and such

It does work on Steam Deck, but expect a long initial loading time of 4-5 minutes during which you get a black screen. It has not crashed. Don't exit the game, it will eventually go to the main menu.
Performance is OK, 30fps cap recommended. I think it's fine for a slower-paced title such as this to run at 30-ish. It's honestly better than I expected.

Game just shows black screen on play.

LD_PRELOAD="" gamescope -W 2560 -H 1440 -w 2560 -h 1440 --fullscreen --force-grab-cursor --mangoapp -- game-performance %command%
Without gamescope, system mouse cursor will appear on screen and stay on top if you alt-tab out of the game. Using gamescope with "--force-grab-cursor" fixes the issue.
Horrible traversal stutter introduced in update 4. Ruins the entire gameplay experience. Video showing issue here: https://youtu.be/9547pnayWoY
Played 18.2 hours, and since Update 4 I cannot continue the game to finish it. Quite disappointing. The Update 4 Hotfix 2 patch doesn't fix the traversal stutter.

none
After resuming from sleep, slight crackle
Limiting the framerate to about 30fps helps a lot with performance fluctuations

__GL_13ebad=0x1 %command%
The "__GL_13ebad=0x1" environment variable is due to a bug in the Nvidia drivers running id Tech engine games, and apparently goes back to Doom Eternal in 2020. Without adding it, my FPS maxed out at around 27 in the first jungle level, even on low settings. Adding the variable bumped the FPS up to 60 on medium settings.

mangohud gamemoderun %command%
ultra wide you can users can have a look here: https://github.com/Lyall/GreatCircleFix

Ran excellent at virtually the same FPS as in Windows, no fiddling necessary
Started the game in Windows because of all the fiddly reports here, but tried it on Linux and it ran at the same FPS as Windows. The engine uses Vulkan so no VKD3D or DXVK needed. Had maybe 1 crash my whole 35 hours playing. I did not enable full ray tracing so I can't speak to that, but everything else was either maxed or close to max

FSR Frame generation is the only thing I didn't get to work. Enabling it gives a black screen.

VK_ICD_FILENAMES= "insert you path to amd_icd64.json" %command%
Crashes when full ray tracing is enabled
Was not easy to get runing but after 3 hours I got it to work. The menu worked fine but crashed when I stated a game. Turns out I needed AMDVLK not RADV. This is what I did:
-Download the latest version of AMDVLK from github, it can be ***.deb or ***.rpm...
-Then just extract it into a folder that you have right to write and read, you're gonna need the amd_icd64.json and amdvlk64.so files.
-Indicate the path of the amd_icd64.json file in steam option with the command 'VK_ICD_FILENAMES=/etc/vulkan/icd.d/amd_icd64.json %command%'
-Finaly...edit the amd_icd64.json file, replace the values of the 2 places with 'library path' , set the path you put the 'amdvlk64.so' file.
This is for AMD GPU's of course, I'm using a RX 9070. It still Crashes when I enable full raytracing but otherwise seems to run fine.

Fun to be able to enjoy this without a beefy PC or geforce Now, it looks good on built in screen, On larger monitor, i kept default settings
45 FPS Limit (I use OLED version), no TDP Limit (Usually i have 10 TDP Limit)
Background noise (white) when using built in speakers; Use headphones. Note this audio issue does not occur with all my games.
GAme settings: Default :1280x800 native resolution. Except some Changes: blur medium; FPS limit 45; vegetation medium; upscaling FSR, super resolution balanced. Steam deck setting: no TDP Limit, no FPS Limit (limited by game), [upscaling FSR sharpness 2 though uneeded.]
Game launch is long (2-3 min). rest ok
Headphones required due to white noise issue. (i use BT headphones)
Clearly the deck is working harder than most titles i play, but perfectly enjoyable. For playing this game on a PC too, i would say for a long session i would use the PC or the deck docked with an external display, the graphics quality will be lower on the deck but the experience is comfortable. Steam OS 3.6.22. OLED.

HDR works. Got it on full path tracing, DLSS quality, Ultra and still getting 70 FPS. Looks awesome and game runs smoothly.
__GL_13ebad=0x1 DXVK_NVAPI_GPU_ARCH=AD100 PROTON_USE_WAYLAND=1 DXGI_ENABLEUE4WORKAROUNDS=TRUE PROTON_USE_FASTSYNC=1 ENABLE_HDR_WSI=1 DXVK_HDR=1 PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 DXVK_ALLOWFSE=TRUE %command%
So far, no crashes. The game does not like mangohud. I had to take it out of the launch options.

DXVK_NVAPI_GPU_ARCH=AD100 __GL_13ebad=0x1 mangohud %command%
My GPU (3090) was at 100% usage after the opening intro, even in the menu and was getting 10-13 FPS. Adding the __GL_13ebad=0x1 fixed this and made the game playable, 155 FPS ultra settings

During launch, the game gives a black screen but after some time, it loads the game without issues.

mangohud %command%
This game runs perfectly!

DXVK_NVAPI_GPU_ARCH=AD100 mangohud gamemoderun %command% +com_skipIntroVideo 1
After the current update, start in “Safe mode” once to reset all settings! Set up the start option “DXVK_NVAPI_GPU_ARCH=AD100” to get the correct DLSS support with RTX 4000! Without this, you will probably get a black screen, if "Ray Reconstruction" is enabled.
- 3440x1440 fullscreen.
- Highest settings, with the exception of reducing the "texture pool size" one level to avoid the "vram overflow crash".
- Full RT/PT and Ray Reconstruction enabled.
- DLSS quality + FG2.
- ~55 FPS in jungle area w/o FG.

While most settings were on low, Played on Steamdeck with external monitor, mouse & keyboard. Without command line, game starts unplayable.
radv_legacy_sparse_binding=true radv_zero_vram=true RADV_DEBUG=nodcc %command% +com_skipIntroVideo 1
Game is lots of fun and it was worth searching and finding the command line to get it to work on Deck!

I tried bleeding-edge proton experimental, experimental and hotfix. None worked. Driver error. I upgraded my Nvidia driver from 535 to 570. This with proton hotfix resolved all issues. Runs great.

I can't get the game to run after Update 3
lots of them
I tried every combination of Proton and commands proposed on NVidia forums. The game ran great before Update 3, now I always get the black screen.

env LD_PRELOAD="" PULSE_LATENCY_MSEC=120 gamescope -H 2160 -h 1080 -F fsr -f --adaptive-sync -r 55 --framerate-limit 55 --force-grab-cursor --hdr-enabled -- gamemoderun %command% +com_skipIntroVideo 1
After the latest update 3 you will need to enable Proton Experimental bleeding-edge, as mentioned by someone on the Steam discussions.

AMD_VULKAN_ICD=AMDVLK VK_DRIVER_FILES=/etc/vulkan/icd.d/amd_icd64.json mangohud %command% +com_skipIntroVideo 1
Out of the box experience lead to following error : “Could not create the Vulkan device: vkCreateDevice failed with error (Unknown)”. With Proton Hotfix I was able to start the game, but after initial animation I eded up with black screen. Had to install AMDVLK (https://github.com/GPUOpen-Drivers/AMDVLK/releases) and set launch options.

wouldn't launch with latest GE-Proton, had to use experimental. great performance, 100+fps, 1440p, max settings (minus path tracing)

If you have AMD GPU (like me) or are on Steam Deck, update 3 broke the game. It launches only to crash with a Vulkan error message. Use Proton Hotfix for now, but I expect this fix will land in Experimental and eventually stable

Update 3 has a bug that prevents the game to launch with RADV

radv_legacy_sparse_binding=true radv_zero_vram=true RADV_DEBUG=nodcc %command%
After the recent update #3, the game does not start anymore. Instead, it shows a dialog titled
Renderer setup error
saying
English: Could not create the Vulkan device: vkCreateDevice failed with error (Unknown)
and then terminates.

WINEDLLOVERRIDES="dinput8=n,b" DXVK_NVAPI_GPU_ARCH=AD100 gamescope -f --force-grab-cursor -W 5120 -H 1440 --hdr-enabled --adaptive-sync -r 120 -- %command% +com_skipIntroVideo 1
Update 3 and latest Proton Experimental increased performance (now getting 80ish fps on DLSS quality without FG) and resolved the Nvidia frame generation stability issue so enjoying at 120+fps now.
Setting DXVK_NVAPI_GPU_ARCH=AD100 still seems to be required for frame generation and you'll get a black screen if you enable ray reconstruction without it.