You could also try updating your drivers, Mesa 25.0.x is pretty old. There is https://launchpad.net/~kisak/+archive/ubuntu/kisak-mesa for latest stable Mesa on ubuntu.

Confirming this issue on my system. Resulting in the same GPU hang.

System Info -
Distro: Archlinux
Kernel: 6.16.8-1-cachyos
GPU: AMD Radeon RX 6700 XT
Driver: Mesa 25.2.3-arch1.2
Proton: Proton Experimental (latest as of 9/21/25) as well as GE-Proton10-15
vkd3d-proton: bundled with Proton Experimental and GE-Proton10-15
Tested on hyprland-0.51.1-1 swayfx-0.5.3-4 and xfce4-4.20.3-1

Crashing save in tar, as well as profile.

Saves.tar.gz

I couldn't get that save file to work. It either says save data is corrupt, or it doesn't register at all, so it might be that saves are tied to your steam profile.

Edit: Didn't refresh before I posted. But yeah, it's not going to be straightforward.

Since the save file didn't work, can any of you provide some more detailed instructions on how to get to the problematic area? Mission name, nearest fast travel point, or similar.

My log from the crash to just before shutdown. In this instance, the gpu recovered into tty, but it tends to fails to recover.

Sep 24 05:57:00 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32791)
Sep 24 05:57:00 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu:  in process GameThread pid 3576 thread vkd3d_queue pid 3721
Sep 24 05:57:00 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu:   in page starting at address 0x00000000003fc000 from client 0x1b (UTCL2)
Sep 24 05:57:00 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00301031
Sep 24 05:57:00 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu:          Faulty UTCL2 client ID: TCP (0x8)
Sep 24 05:57:00 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu:          MORE_FAULTS: 0x1
Sep 24 05:57:00 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu:          WALKER_ERROR: 0x0
Sep 24 05:57:00 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu:          PERMISSION_FAULTS: 0x3
Sep 24 05:57:00 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu:          MAPPING_ERROR: 0x0
Sep 24 05:57:00 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu:          RW: 0x0
Sep 24 05:57:00 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32791)
Sep 24 05:57:00 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu:  in process GameThread pid 3576 thread vkd3d_queue pid 3721
Sep 24 05:57:00 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu:   in page starting at address 0x0000000000000000 from client 0x1b (UTCL2)
Sep 24 05:57:00 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32791)
Sep 24 05:57:00 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu:  in process GameThread pid 3576 thread vkd3d_queue pid 3721
Sep 24 05:57:00 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu:   in page starting at address 0x0000000000008000 from client 0x1b (UTCL2)
Sep 24 05:57:00 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:3 pasid:32791)
Sep 24 05:57:00 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu:  in process GameThread pid 3576 thread vkd3d_queue pid 3721
Sep 24 05:57:00 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu:   in page starting at address 0x0000000000004000 from client 0x1b (UTCL2)
Sep 24 05:57:10 gil-archliunx kernel: sr 1:0:0:0: [sr0] tag#22 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
Sep 24 05:57:10 gil-archliunx kernel: sr 1:0:0:0: [sr0] tag#22 Sense Key : Not Ready [deferred] 
Sep 24 05:57:10 gil-archliunx kernel: sr 1:0:0:0: [sr0] tag#22 Add. Sense: Medium not present - tray closed
Sep 24 05:57:10 gil-archliunx kernel: sr 1:0:0:0: [sr0] tag#22 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
Sep 24 05:57:10 gil-archliunx kernel: I/O error, dev sr0, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
Sep 24 05:57:10 gil-archliunx kernel: sr 1:0:0:0: [sr0] tag#26 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
Sep 24 05:57:10 gil-archliunx kernel: sr 1:0:0:0: [sr0] tag#26 Sense Key : Not Ready [deferred] 
Sep 24 05:57:10 gil-archliunx kernel: sr 1:0:0:0: [sr0] tag#26 Add. Sense: Medium not present - tray closed
Sep 24 05:57:10 gil-archliunx kernel: sr 1:0:0:0: [sr0] tag#26 CDB: Read(10) 28 00 00 00 00 08 00 00 20 00
Sep 24 05:57:10 gil-archliunx kernel: I/O error, dev sr0, sector 32 op 0x0:(READ) flags 0x80700 phys_seg 3 prio class 2
Sep 24 05:57:10 gil-archliunx kernel: sr 1:0:0:0: [sr0] tag#8 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
Sep 24 05:57:10 gil-archliunx kernel: sr 1:0:0:0: [sr0] tag#8 Sense Key : Not Ready [deferred] 
Sep 24 05:57:10 gil-archliunx kernel: sr 1:0:0:0: [sr0] tag#8 Add. Sense: Medium not present - tray closed
Sep 24 05:57:10 gil-archliunx kernel: sr 1:0:0:0: [sr0] tag#8 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
Sep 24 05:57:10 gil-archliunx kernel: I/O error, dev sr0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 2
Sep 24 05:57:10 gil-archliunx kernel: buffer_io_error: 22 callbacks suppressed
Sep 24 05:57:10 gil-archliunx kernel: Buffer I/O error on dev sr0, logical block 0, async page read
Sep 24 05:57:10 gil-archliunx kernel: Buffer I/O error on dev sr0, logical block 1, async page read
Sep 24 05:57:10 gil-archliunx kernel: Buffer I/O error on dev sr0, logical block 2, async page read
Sep 24 05:57:10 gil-archliunx kernel: Buffer I/O error on dev sr0, logical block 3, async page read
Sep 24 05:57:10 gil-archliunx kernel: Buffer I/O error on dev sr0, logical block 4, async page read
Sep 24 05:57:10 gil-archliunx kernel: Buffer I/O error on dev sr0, logical block 5, async page read
Sep 24 05:57:10 gil-archliunx kernel: Buffer I/O error on dev sr0, logical block 6, async page read
Sep 24 05:57:10 gil-archliunx kernel: Buffer I/O error on dev sr0, logical block 7, async page read
Sep 24 05:57:10 gil-archliunx kernel: Buffer I/O error on dev sr0, logical block 8, async page read
Sep 24 05:57:10 gil-archliunx kernel: Buffer I/O error on dev sr0, logical block 9, async page read
Sep 24 05:57:10 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu: Dumping IP State
Sep 24 05:57:10 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu: Dumping IP State Completed
Sep 24 05:57:10 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu: [drm] AMDGPU device coredump file has been created
Sep 24 05:57:10 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu: [drm] Check your /sys/class/drm/card0/device/devcoredump/data
Sep 24 05:57:11 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu: ring gfx_0.0.0 timeout, signaled seq=200071, emitted seq=200073
Sep 24 05:57:11 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu: Process information: process GameThread pid 3576 thread vkd3d_queue pid 3721
Sep 24 05:57:11 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu: Starting gfx_0.0.0 ring reset
Sep 24 05:57:11 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu: Ring gfx_0.0.0 reset failed
Sep 24 05:57:11 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu: GPU reset begin!
Sep 24 05:57:11 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu: MODE1 reset
Sep 24 05:57:11 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu: GPU mode1 reset
Sep 24 05:57:11 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu: GPU smu mode1 reset
Sep 24 05:57:11 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu: GPU reset succeeded, trying to resume
Sep 24 05:57:11 gil-archliunx kernel: [drm] PCIE GART of 512M enabled (table at 0x0000008000300000).
Sep 24 05:57:11 gil-archliunx kernel: [drm] VRAM is lost due to GPU reset!
Sep 24 05:57:11 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu: PSP is resuming...
Sep 24 05:57:11 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu: reserve 0xa00000 from 0x82fd000000 for PSP TMR
Sep 24 05:57:12 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu: RAS: optional ras ta ucode is not available
Sep 24 05:57:12 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu: SECUREDISPLAY: optional securedisplay ta ucode is not available
Sep 24 05:57:12 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu: SMU is resuming...
Sep 24 05:57:12 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu: smu driver if version = 0x0000000e, smu fw if version = 0x00000012, smu fw program = 0, version = 0x00413e00 (65.62.0)
Sep 24 05:57:12 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu: SMU driver if version not matched
Sep 24 05:57:12 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu: use vbios provided pptable
Sep 24 05:57:12 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu: SMU is resumed successfully!
Sep 24 05:57:12 gil-archliunx kernel: [drm] kiq ring mec 2 pipe 1 q 0
Sep 24 05:57:12 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu: [drm] DMUB hardware initialized: version=0x02020021
Sep 24 05:57:12 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
Sep 24 05:57:12 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu: ring gfx_0.1.0 uses VM inv eng 1 on hub 0
Sep 24 05:57:12 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 4 on hub 0
Sep 24 05:57:12 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 5 on hub 0
Sep 24 05:57:12 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
Sep 24 05:57:12 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
Sep 24 05:57:12 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
Sep 24 05:57:12 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
Sep 24 05:57:12 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
Sep 24 05:57:12 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
Sep 24 05:57:12 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng 12 on hub 0
Sep 24 05:57:12 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu: ring sdma0 uses VM inv eng 13 on hub 0
Sep 24 05:57:12 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu: ring sdma1 uses VM inv eng 14 on hub 0
Sep 24 05:57:12 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 8
Sep 24 05:57:12 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 8
Sep 24 05:57:12 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 8
Sep 24 05:57:12 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu: ring jpeg_dec uses VM inv eng 5 on hub 8
Sep 24 05:57:12 gil-archliunx kernel: amdgpu 0000:0b:00.0: amdgpu: GPU reset(1) succeeded!
Sep 24 05:57:12 gil-archliunx kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!

Since the save file didn't work, can any of you provide some more detailed instructions on how to get to the problematic area? Mission name, nearest fast travel point, or similar.

Screenshot of exactly where this is occurring. After interacting with the portal, it plays the animation of going through it. In the middle of the animation, it says it's caching some shaders, and when the sound of it about to end is played, it crashes. The bounty is irrelevant (Had none first time it crashed), so the main mission of "Another Day, Another Universe" is the part of the story where this happens, with the shown objective. Takes place on the Elpis map, so there's only one fast travel at the beginning.

Same Problem at the Exact Same Mission when enterning Portal.
System Specs:
32GB RAM 3600MHZ
Radeon RX 6900 XT
Amd Ryzen 5600X

Using CachyOs
Ive Tried any Proton Version on Steam it crashes all the time.
steam-1285190.log Crash Log

UECC-Windows-114F693D4806548E8F354F867E473A99_0000.tar.gz Borderlands Crash

client.tar.gz Safe File where the crash Happens just enter the portal if this could help to reproduce.
You can get the Savegame to work on your steam account you need to decrypt it first with a Bl4 Safe Editor and my STEAMID64(76561198088954640) then encrypt again with your STEAMID64 Its locked to your steamid.
You can get Bl4 Safe Editor on nexusmods.com
I use this one:
https://www.nexusmods.com/borderlands4/mods/59

Can also confirm this on my system at the exact same point in the game.

Distro: Kubuntu 25.04
Kernel: 6.14.0-32-generic
GPU: AMD Radeon RX 6600 XT
Driver: Mesa 25.0.7-0ubuntu0.25.04.2
Proton: Proton Experimental

vkd3d_debug_cut.log

I hope this is useful - I've never debugged software like this before. I've attached the last couple thousand lines of the output of the VKD3D_LOG_FILE (the whole log was 1.7GB), before it starts spewing error messages. I tried using VKD3D_CONFIG=breadcrumbs, but I could never get past the loading screen (due to how slow the game ran with breadcrumbs enabled) to activate the portal (which causes the hang.) Hopefully this provides some more info.

I also didn't get this hang with AMDVLK, so that's one way to get through this part on RDNA2 while we try to figure this out. I made a report on the Mesa issue tracker here: https://gitlab.freedesktop.org/mesa/mesa/-/issues/13981

I also didn't get this hang with AMDVLK, so that's one way to get through this part on RDNA2 while we try to figure this out. I made a report on the Mesa issue tracker here: https://gitlab.freedesktop.org/mesa/mesa/-/issues/13981

Thanks so much for the workaround! Still would love to see this issue resolved, but at least I have a way to keep going through the story missions now!

I also didn't get this hang with AMDVLK, so that's one way to get through this part on RDNA2 while we try to figure this out. I made a report on the Mesa issue tracker here: https://gitlab.freedesktop.org/mesa/mesa/-/issues/13981

Ive Tried to do this with AMDVLK and still get the crash
Nvm I was just dumb. Ty

I also didn't get this hang with AMDVLK, so that's one way to get through this part on RDNA2 while we try to figure this out. I made a report on the Mesa issue tracker here: https://gitlab.freedesktop.org/mesa/mesa/-/issues/13981

Ive Tried to do this with AMDVLK and still get the crash Nvm I was just dumb. Ty

Hate to be the noob here, but how can I force AMDVLK on Bazzite? I have the same issue at the same spot :(

• Aorus B550 (current FGg Bios)
• XFX RX 6650XT
• Ryzen 7 5700X
• 32GB RAM
• GMONE48 / OS Stable (F42.20250916) / Wayland
• Linux 6.16.4-108.bazzite.fc42.x86_64

I also didn't get this hang with AMDVLK, so that's one way to get through this part on RDNA2 while we try to figure this out. I made a report on the Mesa issue tracker here: https://gitlab.freedesktop.org/mesa/mesa/-/issues/13981

Ive Tried to do this with AMDVLK and still get the crash Nvm I was just dumb. Ty

Hate to be the noob here, but how can I force AMDVLK on Bazzite? I have the same issue at the same spot :(

• Aorus B550 (current FGg Bios)
• XFX RX 6650XT
• Ryzen 7 5700X
• 32GB RAM
• GMONE48 / OS Stable (F42.20250916) / Wayland
• Linux 6.16.4-108.bazzite.fc42.x86_64

VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/amd_icd64.json %command%

Add this to Steam launch Options of Borderlands 4

VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/amd_icd64.json %command%

Add this to Steam launch Options of Borderlands 4

This will just cause the game to not launch unless AMDVLK is actually installed system-wide, which won't be the case for most people, and I don't think there even is a AMDVLK package for Fedora/Bazzite.

What you can do, however, on any distro, is to download the ubuntu package from here: https://github.com/GPUOpen-Drivers/AMDVLK/releases/tag/v-2025.Q2.1, extract the amdvlk64.so and the .json file from the package to somewhere, fixup the path in the .json to where you extracted the .so, and then launch games with VK_ICD_FILENAMES=/path/to/amdvlk.json %command%

VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/amd_icd64.json %command%

Add this to Steam launch Options of Borderlands 4

This will just cause the game to not launch unless AMDVLK is actually installed system-wide, which won't be the case for most people, and I don't think there even is a AMDVLK package for Fedora/Bazzite.

What you can do, however, on any distro, is to download the ubuntu package from here: https://github.com/GPUOpen-Drivers/AMDVLK/releases/tag/v-2025.Q2.1, extract the amdvlk64.so and the .json file from the package to somewhere, fixup the path in the .json to where you extracted the .so, and then launch games with VK_ICD_FILENAMES=/path/to/amdvlk.json %command%

Made some progress, but I probably missed something. Setup a distrobox, extracted the SO and JSON. Your instructions are pretty much the same as this post I found:

https://www.reddit.com/r/Bazzite/comments/1h389dm/how_to_get_amdvlk_on_bazzite/

My JSON is called amd_icd64.json, edited to point to the .SO:

{ "file_format_version": "1.0.0", "ICD": { "library_path": "/home/revan/Documents/BL4 AMDVLK/amdvlk64.so", "api_version": "1.4.313" }, "layer": { "name": "VK_LAYER_AMD_switchable_graphics_64", "type": "GLOBAL", "library_path": "/home/revanon3r/Documents/BL4 AMDVLK/amdvlk64.so", "api_version": "1.4.313", "implementation_version": "1", "description": "AMD switchable graphics layer", "functions": { "vkGetInstanceProcAddr": "vk_icdGetInstanceProcAddrSG", "vkGetDeviceProcAddr": "vk_icdGetDeviceProcAddrSG" }, "disable_environment": { "DISABLE_LAYER_AMD_SWITCHABLE_GRAPHICS_1": "1" } } }

In Steam, Borderlands 4 now has the following launch option:

VK_ICD_FILENAMES=/home/revan/Documents/BL4 AMDVLK/amd_icd64.json %command%

Launching the game Shaders Compile window popped up, finished, then nothing. Re-launching game will show as "Running" for a few seconds before it stops.

My JSON is called amd_icd64.json, edited to point to the .SO:

{ "file_format_version": "1.0.0", "ICD": { "library_path": "/home/revan/Documents/BL4 AMDVLK/amdvlk64.so", "api_version": "1.4.313" }, "layer": { "name": "VK_LAYER_AMD_switchable_graphics_64", "type": "GLOBAL", "library_path": "/home/revanon3r/Documents/BL4 AMDVLK/amdvlk64.so", "api_version": "1.4.313", "implementation_version": "1", "description": "AMD switchable graphics layer", "functions": { "vkGetInstanceProcAddr": "vk_icdGetInstanceProcAddrSG", "vkGetDeviceProcAddr": "vk_icdGetDeviceProcAddrSG" }, "disable_environment": { "DISABLE_LAYER_AMD_SWITCHABLE_GRAPHICS_1": "1" } } }

You extracted the wrong .json, you need the one in icd.d, and not implicit_layer.d

Also don't know what you used distro box for, the .deb can be extracted with standard archive tools on any distro.

They're both called the same json file, when I noticed that earlier I tried both :/ still learning the ropes with linux bazzite, clearly long way to go

They have the same name but different contents, one is not going to work. Also, you should put quotes ("") around the path in the steam launch option if the path has whitespaces. If it still doesn't work, post a proton log: https://github.com/ValveSoftware/Proton/wiki/Proton-FAQ#how-to-enable-proton-logs, with both launch options, so VK_ICD_FILENAMES="/home/revan/Documents/BL4 AMDVLK/amd_icd64.json" PROTON_LOG=1 %command%

It was the lack of quotation marks in Steam launch option. It worked, successfully recompiled shaders during the transition, I'm back on track in the game. Thank you so much!

Also confirming that the amdvlk workaround gets past the bugged gate

I'm running into this issue on my steam deck as well. I've been reading through the thread trying to figure out how to implement the workaround and failing.
My guess is RevanOn3r's longer comment is the gist of what I need to do but at a loss of how to do so. I'm sure it isn't helping I'm still getting familiar with how this part of owning a deck works.
Would anyone mind helping me get started with the work around?

Yeah, that's why I didn't want to do anything I was unclear about.
I was reading this thread and one of the other ones linked and from what was shared about it, it absolutely sounds weird!

Reminded me of the older issue that boiled down to the difference between AMD and Intel cores and why for the longest you didn't use one at all for any kind of rendering!

I'm sure you guys will figure it out!

I can confirm the ACO_DEBUG=nosched env var does the trick.

Can confirm it does for the steam deck as well, just put that in the launcher, awesome!
Thanks!

Radeon RX 6800
ACO_DEBUG=nosched fixed the issue for me as well.
Thank you.

ACO_DEBUG=nosched %command% I had to put that %command% at the end and wait for all the anti tamper messages to go which went after around 8 to 12ish hours because of changing the protons in compatibility so much I have a older 1st gen steam deck I used proton experimental and that code in the launcher got past that portal bit then took the code off once I had done that area and completed the mission completely the steam deck did slow down even more so than usual and there was alot of lag untill i got past that bit and went back to using lossless scaling. This was annoying me alot and kept looking up fixes for probably 2 weeks glad there was a fix this was very much appreciated guys for taking me down the path I needed to fix this issue.

Definitely noticed the change in performance, after completing the said mission and getting past the dimension I removed the line from my launcher settings and relaunched. Performance seemed to be mostly back to normal. Finished the story without noticing any similar issues.