The games crashes shortly after launch on Nvidia 565.77, tested with and without gamescope:
steam-2677660-nvidia.log

Issue link for performance issues, with card using way below maximum TDP: https://forums.developer.nvidia.com/t/565-77-indiana-jones-and-the-great-circle-only-runs-at-40-of-max-tdp-on-rtx-4090/315916

System Information

GPU: NVIDIA GeForce RTX 4090
Video driver version: nvidia-open 565.77
Kernel version: 6.12.2
Link to full system information report as Gist: https://gist.github.com/matte-schwartz/f50eaa2e63000db30269b49e771bd930
Proton version: experimental-bleeding-edge-9.0-140942-20241205-p8c3e86-w995693-db1ad43-v73e59c

Also getting a crash issue on Nvidia 565.57.01; a few seconds of the intro video's audio will play before suddenly closing. I did test the game with PROTON_HIDE_NVIDIA_GPU=1 and that did actually reach the main menu and there seemingly aren't any graphical issues there, however the framerate is extremely low hovering around the low 10-20 range so it's not playable.
steam-267766-hide-nvidia-gpu0.log

System Information

GPU: NVIDIA GeForce RTX 4070 Super
Video driver version: nvidia 565.57.01
Kernel version: 6.12.1-arch1-1
Link to full system information report as Gist: https://gist.github.com/CptCookies12/e978ad5cb133f0dad84c4f083664080a
Proton version: experimental-9.0-20241121b

As a workaround for now on NVIDIA, you can fake as an Ampere GPU with DXVK_NVAPI_GPU_ARCH=GA100 without disabling DLSS and NVAPI

upstream now with https://github.com/jp7677/dxvk-nvapi/commit/c29f6f0bef8f0d6122ce9346ccc95ec2fb3da701

runs fine with amdvlk btw, but no hdr since its amdvlk

Workaround applied to upstream mesa/RADV: https://gitlab.freedesktop.org/mesa/mesa/-/commit/c2f8f20ef75a00917a652e32d4caa48029c68681

I believe you host a Mesa PPA for Ubuntu, which my system uses. So may I ask if you know when it will be added to the next Mesa release in your PPA?

Isnt it possible to enable these as launch parameters? e.g radv_legacy_sparse_binding=true RADV_DEBUG=nodcc,zerovram %command%

Having a problem with this game as an NVIDIA user. On my RTX 3070 the fps does not get any higher than 15-17, even in the main menu, even with the lowest settings, even in 720p.

Some other users pointed this issue out as well, with them having more powerful GPUs (4080 Super and 4090). Tried launch arguments, none of them worked. The issue may be because of the limited power usage (it does not get higher than 70 watts for some reason).

I still don't know if the issue is in the game's engine, compatibility layer or in GPU drivers. Thought that mentioning this problem here should help in solving it.

System Information
GPU: NVIDIA GeForce RTX 3070
Video driver version: 565.57.01
Kernel version: 6.11.9

I have RTX 4070 and i've got 10-15 FPS no matter if i pick 720 low or 4K max, TDP usage is 40W.

GPU: NVIDIA GeForce RTX 4070
Video driver version: 565.77
Kernel version: 6.12.3 & 6.13-rc

Tested both closed and open nvidia drivers, many proton version.

Adding some details:

When using mangohud, one can see that even 16GB cards and above (Nvidia in my case) don't use more than around 4GB of VRAM. The PCIe bus is heavily utilised, albeit not at 100%. This looks like how a card with actually low VRAM would behave: Starting to "swap" and losing a ton of performance.

GPU load is reported at 100% all the while only consuming some 70W, so the card is busy with... something. Checking clock rates, it did enter it's highest P0 power state (=no problem with a stuck power save mode or something), so I would assume that the "barrier" around the 4GB mark for the actual VRAM usage plays a leading role regarding this issue.

Not sure if this is some driver, transition layer or game issue. The ingame stats don't show this problem as they properly report the correct amount of VRAM. They game therefore "sees" the proper VRAM amount and also allows high settings without complaining.

Also adding onto the Nvidia framerate issue, I can also confirm there's a major issue with memory/VRAM utilization. On my 4070 Super, GPU load is 100% but VRAM stays locked at 3.3GB with RAM usage going way higher than Windows does when using the Ultra preset (same as what I'm running on Windows 11). Everything renders correctly but the VRAM usage being bugged means even at the lowest preset the game doesn't run well enough to be playable.

Arch Linux (nvidia 565.57.01)

Windows 11 (Nvidia driver version 566.36; framerate locked to 60)

The 4GB issue makes me think of resizable bar and 4G decoding, it could be worth toggling it on/off and seeing whether that makes a difference.

The 4GB issue makes me think of resizable bar and 4G decoding, it could be worth toggling it on/off and seeing whether that makes a difference.

Worth testing it out. How to I disable any of this per-game? Don't know 'cause I never encountered problems related to this.

Though it's not particularly 4GB, but anything would be great if it helps.

Afaik you can only enable it in the bios, but you can disable it at runtime with VKD3D_CONFIG=no_upload_hvv

Afaik you can only enable it in the bios, but you can disable it at runtime with VKD3D_CONFIG=no_upload_hvv

Indiana uses Vulkan explicitly. Will this variable apply to it? VKD3D is for DirectX games as I know

If you want to be sure then probably find out how to toggle it in the bios, I guess.

I disabled resizeable bar in the BIOS for my 4090 and the performance tanked to 5fps, I think the only fix for this will have to come from Nvidia

The 4GB issue makes me think of resizable bar and 4G decoding, it could be worth toggling it on/off and seeing whether that makes a difference.

Good thinking but the game engine itself "sees" the correct amount of VRAM (when enabling the performance stats), only using other tools like mangohud or nvtop then shows how much is in actual use, for whatever reason.

So while one should certainly check and test for the RBar setting in the BIOS, it seems like other factors are at play when it comes to the artificial VRAM limit, in turn causing a severe performance downgrade for otherwise very capable cards.

There is not many "tricks" Nvidia users can try since it's a Vulkan game. I also think Nvidia needs to fix this and that may take a while. It we try to push hard enough a fix may be in the next 570 driver. Though I hope for a hotfixed 565 driver.

Same here with a RTX 3080 10G, game crashes immediately after launch.

Please NVIDIA, fix your shit, we want to get those Linux CCU numbers up :open_hands:

Please NVIDIA, fix your shit, we want to get those Linux CCU numbers up 👐

A bit of a tangent, but still: a year ago, it took them over two months to fix the most glaring performance issues with Starfield, which prompted me to switch to AMD. They really don't care about gaming on Linux, so personally, I wouldn't count on them.

I gave them proper feedback in the NVIDIA forums :stuck_out_tongue_winking_eye:
https://forums.developer.nvidia.com/t/bug-indiana-jones-and-the-great-circle-only-runs-at-40-of-max-tdp-on-rtx-4090/315916/35?u=jomai92

Experiencing the same issues on NVIDIA 565.77 as outlined in this post. With everything set to the lowest possible setting it still only achieves about 10-15 FPS on my 4090 RTX.

It never clocks up to a higher P state, VRAM usage is stuck around 2-4 GiB despite having 24 GiB, and the PCIe traffic is off the charts at 100% utilization. It appears that the graphics is running completely off of system memory which explains everything.

Please NVIDIA, fix your shit, we want to get those Linux CCU numbers up 👐

A bit of a tangent, but still: a year ago, it took them over two months to fix the most glaring performance issues with Starfield, which prompted me to switch to AMD. They really don't care about gaming on Linux, so personally, I wouldn't count on them.

However, back in 2020 it took only a week to fix DOOM Eternal (which uses almost the same engine). So I hope we will wait for only a couple of days. I don't want to go back to windows for a single game lol

So as you can see in the nvidia forums thread this is likely the fault of the engine. NVidia provided a workaround for the predecessor so hopefully they can do that again soon.

Imho talking aggressive to someone also never helps to get help from them. Not constructive (looking at some other comments here and there). Btw AMD announced to step back from high end GPU marked so maybe switching is a bad threat.

Apparently, Nvidia does have some special code in the vulkan driver for this game, but it could just be leftover code from Windows. You can even spot the new DOOM game exe in there.

for i in /usr/lib/libnvidia*.so; do echo $i; strings $i |grep -i TheGreatCircle.exe; done

Theoretically, through some reverse engineering, one could copy the settings for DOOMEternal to this game, if Nvidia takes their time to fix it.

@chaitan3 Those exes are probably "windows leftovers", not sure if they have any real effect in Linux. I haven't found any specific fix that's visible in the Linux driver for doom eternal that actually works for TGC, it might be masked by some hash or simply isn't findable by text search.
There's an application workaround for doom eternal tho', that makes the game use PCores.... but that's it.

I had a go at trying to make the doom eternal settings apply to The Great Circle but it either did not work or had no effect.

FWIW, I also deleted the NV application profile for Indiana Jones - The great circle in Windows and tried without it, game still ran fine...
So it seems the issue is purely Linux specific.

Use official workaround - https://forums.developer.nvidia.com/t/bug-indiana-jones-and-the-great-circle-only-runs-at-40-of-max-tdp-on-rtx-4090/315916/55

@ga2mer nicely hacked, works here too. I tried doing similar stuff but I focused on the DOOMEternal stirng

@ga2mer nicely hacked, works here too. I tried doing similar stuff but I focused on the DOOMEternal stirng

@shelterx can you post this fix to Nvidia developer forum post? Just for people to have a workaround for now

@shelterx @ga2mer could you share this file with me? when i replace text indiana won't run, i also swapped file directly in usr/lib - the same result. maybe i'm doing something wrong...

EDIT: Hmm weird, i've got segfault at 8 ip 00007147b5c3a6b7 sp 00007ffc5d167f00 error 4 in ld-linux-x86-64.so.2[e6b7,7147b5c2d000+2a000] likely on CPU 6 (core 0, socket 0) after this modification

EDIT2: Hmm i'm doing something wrong, can't even put default libnvidia-glcore in envs

So here i only have libnvidia-gtk2.so.510.47.03 and libnvidia-gtk3.so.510.47.03 . No libnvidia-glcore.so present. Can i still do the hack and yes in which?

System is Mint 21.3 with 550.120

Update 1: Found it. It's in /usr/lib/i386-linux-gnu/
Update 2: 69 64 54 65 63 68 bytes or idTech text is not present in libnvidia-glcore.so.550.120
Update 3: It's also not present in 560.35

@ga2mer
tried all this but game doesn't run with LD_PRELOAD=libnvidia-glcore.so.565.77 LD_LIBRARY_PATH=. %command%
not sure what i'm doing wrong

It's in /usr/lib/i386-linux-gnu/

I'm not sure it's correct dir, the game is x64, so the libraries you need are probably somewhere mentioning x64 or not mentioning x86, but better upgrade drivers to 565.77

not sure what i'm doing wrong

Like I said it may not work and I don't know how to use it properly, I have a very weird setup so it worked 50/50

Try copying this lib to some dir in your user folder, like the hack folder and in the commandline only write a path like this
LD_LIBRARY_PATH="/home/your_username/hack:$LD_LIBRARY_PATH" %command%.

also the wrong ld could mess up the launch, so it's better to restart steam before doing that

Replying to https://github.com/ValveSoftware/Proton/issues/8292#issuecomment-2531731068

I confirm this is working, I also see slightly better memory management than on Windows. On windows the game drops to 5 fps if the game exceeds the memory budget available, on Linux performance drastically drops but it is a lot better.

@ga2mer that's basically what I did and it worked.

It's important to replace the text properly otherwise the library might get corrupted

It's in /usr/lib/i386-linux-gnu/

I'm not sure it's correct dir, the game is x64, so the libraries you need are probably somewhere mentioning x64 or not mentioning x86, but better upgrade drivers to 565.77

You are correct. Found another one in /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.550.120
Still there is no idTech to be found in there. Also not in the other nvidia libs. So it might be a version issue. An upgrade is not as easy as for Mint 550 is the latest available offically.

Can we discuss why this works?

So, already right now, the libnvidia-glcore has the same kind of workaround for Doom Eternal? And this workaround is still needed for Doom Eternal? Why is this workaround needed at all?

Is the engine doing something weird/wrong there? Couldn't this be fixed maybe in the engine? Wouldn't that be more reasonable?

Why is this only happening in Proton, and not in Windows? Or does the Windows Nvidia driver has the same workaround for idTech (Doom Eternal), and also already for Motor (Indiana Jones), just the Linux Nvidia driver does not have it yet?

@ga2mer
LD_LIBRARY_PATH="/home/your_username/hack:$LD_LIBRARY_PATH" %command%
thanks, this did the trick, game launches with a lot better fps.
Another issue I have now is that the desktop cursor stays on top of the game in gnome and massively lags the game when moving the mouse around. It's smooth when playing with controller, but the cursor stays on top in the middle of the screen.

• 69 64 54 65 63 68

Doesn't work here.

There is a launch options fix: https://forums.developer.nvidia.com/t/bug-indiana-jones-and-the-great-circle-only-runs-at-40-of-max-tdp-on-rtx-4090/315916/54
__GL_13ebad=0x1 %command%

Can confirm that this works for 550.

On 3070

Yes! Works on 565.77 too! (Arch Linux)

I am missing dlss frame generation option on nvidia using proton experimental, is anyone else?

In reply to: https://github.com/ValveSoftware/Proton/issues/8292#issuecomment-2532537311

This is almost certainly because of the workaround that was needed to get this game not to crash immediately upon launch: https://github.com/jp7677/dxvk-nvapi/commit/c29f6f0bef8f0d6122ce9346ccc95ec2fb3da701 since WINE_DISABLE_HARDWARE_SCHEDULING=1 did not fix it. I'll have to double check what the settings menu looks like on Windows

Do the open and propreretary drivers make any difference?

They do not.

Can confirm that running with __GL_13ebad=0x1 and DXVK_NVAPI_GPU_ARCH=GA100 works. The latter is needed so DLSS works if you're on an Ada GPU. If you're running from Steam just set the launch options to:

DXVK_NVAPI_GPU_ARCH=GA100 __GL_13ebad=0x1 %command%

You can also skip the obnoxious minute long worth of splash screens with +com_skipIntroVideo 1 in here as well

DXVK_NVAPI_GPU_ARCH=GA100 __GL_13ebad=0x1 %command% +com_skipIntroVideo 1

The original issue on steam deck is not fixed yet, right?

The original issue on steam deck is not fixed yet, right?

No, theres two things still open:

• artifacts around the eyes (issue in RADV)
• Photo camera takes black pictures (unclear root cause, could be wine as it also happens on other drivers)

source: https://gitlab.freedesktop.org/mesa/mesa/-/issues/12257

The game needs a fix for the mouse pointer, if you alt-tab then go back into the game, the desktop mouse pointer is shown in the game. (at least when using KDE)

The game needs a fix for the mouse pointer, if you alt-tab then go back into the game, the desktop mouse pointer is shown in the game. (at least when using KDE)

Just enable borderless fullscreen, and you should be good to go.

Just enable borderless fullscreen, and you should be good to go.

Yeah, that works, thank you!

Replying to https://github.com/ValveSoftware/Proton/issues/8292#issuecomment-2532629267

Game crashes at startup if I enable Frame Gen and restart the game. Does this happen with me only?

@shishimaru90 FG isn't working as of right now, probably because it's a pure vulkan game. I think Nvidia needs to step in and help.

@shishimaru90 FG isn't working as of right now, probably because it's a pure vulkan game. I think Nvidia needs to step in and help.

It works on Windows, so, yes, they should try to help improve things on Linux systems as well.

In Linux, proton runs the install script every time the game starts, it probably fails that's why it keeps running it.
This does not seem to occur in Windows, it runs the script once.

One workaround is to rename the GamingRepair/GDK_InstallScript.vdf file in the game folder.

But some official proton fix/workaround is needed for this.

In Linux, proton runs the install script every time the game starts, it probably fails that's why it keeps running it. This does not seem to occur in Windows, it runs the script once.

One workaround is to rename the GamingRepair/GDK_InstallScript.vdf file in the game folder.

But some official proton fix/workaround is needed for this.

Well since the game bundles GamingRepair tools, which require the Microsoft Store (see Forza Motorsport's issue), I wonder if it is not working because of the hard dependency on the MS Store.

Since I don't have the game, could someone see if using cloud saves from Xbox works since I believe that's what the Gaming Repair stuff is for.

EDIT: I looked up the game on SteamDB and it does indeed have the Gaming Services repair tool bundled.

On Arc B580 I am able to load the menu and sometimes see the environment when starting the game, but am not able to play. Ubuntu, kernel 6.12.3, Device: Mesa Intel(R) Graphics (BMG G21) (0xe20b)), Mesa 25.0~git2501210600.e80279~oibaf~o. Vulkan shader compliation takes minutes but skipping it seems to be okay.

An update for Steam Deck users, supposedly, the green outlines on character’s eyes were supposedly fixed in one of the Beta updates for Steam Deck, but this does not appear to have been pushed to the Stable channel yet despite the recent January updates. https://store.steampowered.com/news/app/1675200/view/707725115500003615

I’m using the following commands on Steam Deck:
radv_legacy_sparse_binding=true radv_zero_vram=true RADV_DEBUG=nodcc %command%

Regarding blank pictures, that issue might have been fixed? I haven’t encountered that bug at all during my playthrough, and I’ve had the game since January 8th.

Wont launch anymore after todays Update 3: vkcreatedevice failed with error (unknown)

https://steamcommunity.com/app/2677660/discussions/0/604148672905655915/

Yeah, same for me after the update yesterday game cannot be launched anymore.
Full Error Message:
English: Could not create the Vulkan device: vkCreateDevice failed with error (Unknown)

Tried both Experimental and 9.0-4

System Information

OS: CachyOS x86_64
Kernel: Linux 6.13.3-2-cachyos
DE: KDE Plasma 6.3.1
WM: KWin (Wayland)
CPU: AMD Ryzen 5 5600X (12) @ 4.65 GHz
GPU: AMD Radeon RX 7900 XTX [Discrete]
Memory: 32 GiB

@mvelten1710 @chkuendig
It's an AMD issue then because it works with Nvidia (RTX 4070).

it's a radv issue that should be reported, amdvlk seems to work fine with the latest update

edit: https://gitlab.freedesktop.org/mesa/mesa/-/issues/12652 reported here

Game started crashing in the last few hours only when DLSS is enabled immediately upon alt tab to desktop or back to game. Enabling/disabling framegen and gamescope makes no difference.

Trigger: Alt-tab to desktop or from desktop to game
Causes: Game crashes
Conditions:

• Proton Experimental Bleeding Edge, DLSS any preset.
• OR Proton Experimental 'Stable', DLSS any preset, DXVK_NVAPI_GPU_ARCH=AD100 + framegen on or off. Appears to be stable with DLSS, no framegen and not setting DXVK_NVAPI_GPU_ARCH=AD100.
• OR GE-Proton9-25, DLSS any preset, DXVK_NVAPI_GPU_ARCH=AD100 + framegen. Appears to be stable with DLSS, no framegen and not setting DXVK_NVAPI_GPU_ARCH=AD100.

Cannot replicate with FSR, native TAA or XESS. Issue is exclusive to DLSS.

Interesting looking logs:

5841.132:0124:0160:warn:seh:dispatch_exception backtrace: --- Exception 0xc0000005.
5841.132:0124:0160:trace:seh:dispatch_exception code=c0000005 flags=0 addr=00000001404988E8 ip=1404988e8
5841.132:0124:0184:warn:debugstr:OutputDebugStringA "[30] FATAL ERROR: vkQueuePresentKHR failed with error (VK_TIMEOUT)\n[30] \n===========================[30] \n  FORCED CRASH[30] \n===========================[30] \n [30] FATAL ERROR: vkQueuePresentKHR failed with error (VK_TIMEOUT)\n\n"
5841.132:0124:0160:trace:seh:dispatch_exception  info[0]=0000000000000001
5841.132:0124:0184:trace:seh:dispatch_exception code=40010006 flags=0 addr=00006FFFFFC1CF57 ip=6fffffc1cf57
5841.132:0124:0160:trace:seh:dispatch_exception  info[1]=0000000000000000
5841.132:0124:0184:trace:seh:dispatch_exception  info[0]=00000000000000e5
5841.132:0124:0160:warn:seh:dispatch_exception EXCEPTION_ACCESS_VIOLATION exception (code=c0000005) raised
5841.132:0124:0184:trace:seh:dispatch_exception  info[1]=000000000fa1fe10
5841.132:0124:0160:trace:seh:dispatch_exception  rax=0000000000000000 rbx=0000000000000000 rcx=00006fffffa6e2f8 rdx=00006fffffa6dd80
5841.132:0124:0184:warn:seh:dispatch_exception "[30] FATAL ERROR: vkQueuePresentKHR failed with error (VK_TIMEOUT)\n[30] \n===========================[30] \n  FORCED CRASH[30] \n===========================[30] \n [30] FATAL ERROR: vkQueuePresentKHR failed with error (VK_TIMEOUT)\n\n"

Full log (Proton Experimental Bleeding Edge): https://gist.github.com/chonty/e30ad55af02a66385048ef0840cb9785
Full log (Proton Experimental stable + DXVK_NVAPI_GPU_ARCH=AD100): https://gist.github.com/chonty/8115edf9babe612e3e2ce67827c53157

System Information

Proton: 1740092814 experimental-bleeding-edge-9.0-165777-20250220-pbc285f-wc80927-d0691a7-v56fb00
OS: Arch Linux
Kernel: Linux 6.13.3-arch1-1
DE: KDE Plasma 6.3.1
WM: KWin (Wayland)
CPU: AMD 7800X3D
GPU: Nvidia RTX 4090
Memory: 32 GiB

Theres a workaround in wine bleeding edge for the RADV issue (game not starting after update 3) which will probably land pretty soon in proton experimental: https://github.com/ValveSoftware/wine/commit/7ea2208c568bee2c79db3194edc272722e3efa4e

its working on proton exp already, has the same issue as amdvlk tho, fails some type of detection and only xess or native options are available, no fsr3 or fsr3 frame generation, can't toggle them using game's console as well

EDIT: game takes ages to load now, it was fine before with amdvlk, also HDR is not working since launch

Found an interesting problem with Indiana Jones on PopOS 24.04 and Cosmic. The game has been working with RT and DLSS (but no frame gen option?). However since the update IF you enable ray reconstruction (which is necessary for ray traced shadows from light sources) then the games rendering 'stops' and you get a black screen. Turning Ray Reconstruction off brings the image back. This on NVidia on the 570.86 driver and an RTX5090. Interestingly gamescope which had been working with the game now also appears not to work if ray reconstruction is on. I assume this is some sort of issue with Proton Experimental and the NVAPI dlls?

@eaglemmoomin I had the same issue and what seemed to have resolved it was deleting the proton experimental folder, verify proton experimental files, and deleting the game wineprefix steamlibrary/steamapps/compatdata/2677660.

Curious to see if you encounter my new problem: with DLSS enabled, see if you can alt-tab to and from the game a few times without it crashing.

For the problem with the ray reconstruction setting causing a black screen on Nvidia (570.86.16 driver), using the just release Proton Hotfix or the much riskier Proton Experimental Bleeding Edge runner fixes the issue.

Both runners should also offer the enforcement of the transformer model for SR and RR via the dxvk-nvapi parameters explained in their wiki: https://github.com/jp7677/dxvk-nvapi/wiki/Passing-driver-settings#drs-settings

For me, the game either:

• Immediately crashes on the first startup logo
• Once in game, is stuck at 2 or 3 FPS. (Menu runs at 60).

Nvidia 4090, 565. I've tried Experimental and Proton Hotfix.

steam-2677660.log

Once in game, is stuck at 2 or 3 FPS. (Menu runs at 60).
...
Nvidia 4090, 565. I've tried Experimental and Proton Hotfix.

This might not be a problem with Proton from what I can tell:
Did you already apply the Nvidia-specific environment variable mentioned here? https://forums.developer.nvidia.com/t/bug-indiana-jones-and-the-great-circle-only-runs-at-40-of-max-tdp-on-rtx-4090/315916/55

Or pick the current 570.86.16 beta driver, which does not need the mentioned variable any more and works fine out of the box with recent runners like Proton Hotfix for this game.

This might not be a problem with Proton from what I can tell: Did you already apply the Nvidia-specific environment variable mentioned here? https://forums.developer.nvidia.com/t/bug-indiana-jones-and-the-great-circle-only-runs-at-40-of-max-tdp-on-rtx-4090/315916/55

Or pick the current 570.86.16 beta driver, which does not need the mentioned variable any more and works fine out of the box with recent runners like Proton Hotfix for this game.

I was able to get into the game for about 2 seconds before it crashed, but it seemed like the FPS was normal with the 570 drivers. However:

• When launching the game, it asks to run in safe mode. If I choose no, it still crashes at the first startup logo.
• If I choose yes, I can get into the menu but it immediately crashes once I get into the game.

Again, I don't think that's an issue with Proton as it would otherwise show up for more Nvidia users. The game crashing almost instantly is not a regular occurrence these days. If frame generation is enabled, things are wonky for sure but since you've also tried the safe mode, the culprit isn't this setting.

I'd suggest taking it to the Nvidia Linux forums while providing some more details re: your system and perhaps some logs from the runner in use. Also feel free to try other runners (which would also confirm that Proton might not be to blame) via things like Lutris.

Reddit might also offer some already tried tips and tricks. If not, feel free to open a thread over there, perhaps in r/linux_gaming.

The black screen here doesn't seem endless; after 2m45s, the game starts and main menu appears.

I don't use any launch options and on Proton Experimental with Steam Deck on Stable branch.

I feel like the issue is an excessively long loading time right after the logos disappear.

Hi. I noticed that FSR is not appearing as a selectable option, although it was added on Update 3.
Only Native TAA or XeSS.

I'm using Proton Hotfix, on a 6800 xt.

Let me know if you need any additional information.

@eaglemmoomin I had the same issue and what seemed to have resolved it was deleting the proton experimental folder, verify proton experimental files, and deleting the game wineprefix steamlibrary/steamapps/compatdata/2677660.

Curious to see if you encounter my new problem: with DLSS enabled, see if you can alt-tab to and from the game a few times without it crashing.

I ended up using the Proton Hotfix as I wanted to be able to try DLSS 4 FG and Proton Experimental doesn't seem to offer that. Was able to turn that and ray reconstruction on with that. After a couple of false starts. I did end up using gamescope as well (I'm running PopOS! 24.04 Alpha). As I had a few times that the game started and just went back to the desktop.

Hi. I noticed that FSR is not appearing as a selectable option, although it was added on Update 3. Only Native TAA or XeSS.

I'm using Proton Hotfix, on a 6800 xt.

Let me know if you need any additional information.

Do we know something about this? I'm on a 6900XT, whilst I can see FSR, it works so bad, turning down the wattage consumption of the GPU to half of it, meaning low FPS and I don't get Frame Gen option as I do on Windows.

The Rx 9070 xt has image corruption

@slimsha3 What kind of image corruption? Can you attach a screenshot?

Hello @slimsha3, please copy the contents of Steam Runtime Diagnostics from Steam (Steam -> Help -> Steam Runtime Diagnostics) and put it in a gist, then include a link to the gist in this issue report. Also, please share a screenshot of the misrendering.

Steam Runtime Diagnostics.txt

somehow the screenshot looks way better than on my monitor. plus when starting indiana jones it crashes and restarts gaming mode and then i can get into the main menu by clicking on safe mode. I tried playing with the game settings but it persists. Using the proton experimental bleeding edge. Used to work perfectly on my 6800 xt

@slimsha3 which Mesa are you running?

im running MESA 25.0.1-3

@slimsha3 Can you try running mesa-git? Either by building yourself or with PPA/AUR maybe?

sadly i cant do that cuz im on bazzite, it can only update via the rpm-ostree

Your issue might have already been fixed yesterday, but it requires mesa-git or you need to wait for 25.0.2 which is expected in 1.5 weeks.

I have an AMD Sapphire Pulse RX 9070XT. I am using mesa-git.

I can boot into Indianna Jones and the Great Circle with mesa-git, and FSR 3.1 upscaling works fine.

But as soon as I enable FSR 3.1 Frame Generation, the game black-screens. I believe the game hasn't crashed because I still have audio -- the rendering just seems to halt.

I am using Proton Experimental.

vulkaninfo output:

tfinnegan@fedora:~$ vulkaninfo --summary
WARNING: radv is not a conformant Vulkan implementation, testing use only.
==========
VULKANINFO
==========

Vulkan Instance Version: 1.4.304


Instance Extensions: count = 24
-------------------------------
VK_EXT_acquire_drm_display             : extension revision 1
VK_EXT_acquire_xlib_display            : extension revision 1
VK_EXT_debug_report                    : extension revision 10
VK_EXT_debug_utils                     : extension revision 2
VK_EXT_direct_mode_display             : extension revision 1
VK_EXT_display_surface_counter         : extension revision 1
VK_EXT_headless_surface                : extension revision 1
VK_EXT_surface_maintenance1            : extension revision 1
VK_EXT_swapchain_colorspace            : extension revision 5
VK_KHR_device_group_creation           : extension revision 1
VK_KHR_display                         : extension revision 23
VK_KHR_external_fence_capabilities     : extension revision 1
VK_KHR_external_memory_capabilities    : extension revision 1
VK_KHR_external_semaphore_capabilities : extension revision 1
VK_KHR_get_display_properties2         : extension revision 1
VK_KHR_get_physical_device_properties2 : extension revision 2
VK_KHR_get_surface_capabilities2       : extension revision 1
VK_KHR_portability_enumeration         : extension revision 1
VK_KHR_surface                         : extension revision 25
VK_KHR_surface_protected_capabilities  : extension revision 1
VK_KHR_wayland_surface                 : extension revision 6
VK_KHR_xcb_surface                     : extension revision 6
VK_KHR_xlib_surface                    : extension revision 6
VK_LUNARG_direct_driver_loading        : extension revision 1

Instance Layers: count = 11
---------------------------
VK_LAYER_FROG_gamescope_wsi_x86_64 Gamescope WSI (XWayland Bypass) Layer (x86_64) 1.3.221  version 1
VK_LAYER_KHRONOS_validation        Khronos Validation Layer                       1.4.304  version 1
VK_LAYER_MANGOHUD_overlay_x86      Vulkan Hud Overlay                             1.3.0    version 1
VK_LAYER_MANGOHUD_overlay_x86_64   Vulkan Hud Overlay                             1.3.0    version 1
VK_LAYER_MESA_device_select        Linux device selection layer                   1.4.303  version 1
VK_LAYER_MESA_overlay              Mesa Overlay layer                             1.4.303  version 1
VK_LAYER_VALVE_steam_fossilize_32  Steam Pipeline Caching Layer                   1.3.207  version 1
VK_LAYER_VALVE_steam_fossilize_64  Steam Pipeline Caching Layer                   1.3.207  version 1
VK_LAYER_VALVE_steam_overlay_32    Steam Overlay Layer                            1.3.207  version 1
VK_LAYER_VALVE_steam_overlay_64    Steam Overlay Layer                            1.3.207  version 1
VK_LAYER_VKBASALT_post_processing  a post processing layer                        1.3.223  version 1

Devices:
========
GPU0:
        apiVersion         = 1.4.309
        driverVersion      = 25.0.99
        vendorID           = 0x1002
        deviceID           = 0x7550
        deviceType         = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU
        deviceName         = AMD Radeon Graphics (RADV GFX1201)
        driverID           = DRIVER_ID_MESA_RADV
        driverName         = radv
        driverInfo         = Mesa 25.1.0-devel
        conformanceVersion = 1.4.0.0
        deviceUUID         = 00000000-0300-0000-0000-000000000000
        driverUUID         = 414d442d-4d45-5341-2d44-525600000000
GPU1:
        apiVersion         = 1.4.309
        driverVersion      = 25.0.99
        vendorID           = 0x10005
        deviceID           = 0x0000
        deviceType         = PHYSICAL_DEVICE_TYPE_CPU
        deviceName         = llvmpipe (LLVM 19.1.7, 256 bits)
        driverID           = DRIVER_ID_MESA_LLVMPIPE
        driverName         = llvmpipe
        driverInfo         = Mesa 25.1.0-devel (LLVM 19.1.7)
        conformanceVersion = 1.3.1.1
        deviceUUID         = 6d657361-3235-2e31-2e30-2d6465766500
        driverUUID         = 6c6c766d-7069-7065-5555-494400000000
tfinnegan@fedora:~$ 

I'm also trying to run this on a 9070XT and having problems. In fullscreen or borderless windowed, there's "fuzz" everywhere. Sorry for the photo of my monitor, but I can't actually capture it in a screenshot. Screenshots all look normal.

Steam runtime diagnostics

It's exclusive to this monitor. On my second monitor it's fine. Even the intro movies, performance overlays, it's all borked like that. Tried changing all the graphics settings. I don't think it's a problem with the monitor, as it's fine everywhere else. I'll report back if I work something out.

edit: I was running it under sway. I tried installing KDE Plasma. Same issue, and then I enabled HDR in the display settings and that fixes it, whether HDR is enabled in the game or not. So possibly not a Proton issue but something about driving this monitor the 9070XT doesn't like. It's an LG 27GL850-B on the off chance someone has the same hardware combo.

edit: amdvlk works, I should've tried that sooner as most reports stated issues with radv. Sorry if I've added noise here.

Yeah, the game does not render properly on RX 9070 XT (kernel 6.14, mesa git 3d76f307). I get similar graphical corruption. :(

@brenmous @shelterx Hi there. If you are able then make a issue on the mesa tracker.

@Blisto91 Done.
https://gitlab.freedesktop.org/mesa/mesa/-/issues/12924

Since Update 4, I have horrible traversal stutter in this game, and have confirmed it on two systems, one with a 7800 XT, and another with a 9070 XT. Getting well over 100 FPS, but the traversal stutter drops to well below 20 for a few seconds, and is 100% reproducible simply by walking across the world.

The new Update 4 Hotfix 2 patch released today on Steam did not fix the issue.

My Steam System Information

And a short YouTube video showcasing the issue clearly.

@chaosmaou what happens if you try amdvlk?

@chaosmaou what happens if you try amdvlk?

Interesting, that fixed the traversal stutter completely, but breaks WiVRn compilation (a separate issue)

I got a black screen for a surprisingly long time (AMD 7900XTX Mesa drivers).

The game in (the default of) full screen (on my 4k monitor) running under Proton experimental showed up as taking up 1/4th of the screen rather than actually being full screen.

Once the game sat for a bit, I was able to go into the settings and change the game to borderless full screen and then everything more or less worked as you would expect.

Replying to https://github.com/ValveSoftware/Proton/issues/8292#issuecomment-2726864976

Mám ten istý problém. Našlo sa riešenie ?