It also doesn't start here with default settings, but setting Texture Quality down to Medium lets me get to the main menu. Anything higher freezes after the intro video.

Proton version: GE-Proton8-9
Launch options: PROTON_SET_GAME_DRIVE=1 PROTON_ENABLE_NVAPI=1 VKD3D_CONFIG=dxr11 mangohud %command%

I tried setting everything to low but still hangs in the same spot and the same errors.

just added my Proton version and launch options to my last comment, try the exact same

used the "High" graphics preset, only dropped texture quality to prevent the freeze, I could get in-game now:

Same with your options

GTX 3080, using PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 VKD3D_CONFIG=dxr11 %command%, it gets past the intro where it shows the Wrench loading icon until I hear a beep, then it freezes.

Yeah, setting to Med gets me in, so the issue is NV cards on Higher or above textures.

Can confirm that setting it to MEDIUM got me in!
I didn't try MEDIUM because I had already put it on the lowest, but I guess there's something special with medium.

I've played for about an hour now, most settings (aside from textures which are medium) on high (including RT, with DLSS), runs pretty well up until it crashed during one of the "rifts".

I thought so too at first, but medium textures seems to be the only option that doesn't crash, so there has to be something else.

For sure anything related to DS or RTX IO does not work atm, rifts are painfully slow. Sadly the only way i see it working is if VKD3D adds RTX IO support and forwards DS calls to RTX IO. Then its just up to mesa to implement the extensions.

+1

Setting textures to medium allows getting past game freezing after intro logos, but setting it back to high/very high once in game locks it up again.

cpu: amd 5800x
gpu: nvidia 3090Ti
ram: 64GB
nvmeSSD: 1TB > slightly more than 200GB of free space available
Proton version: GE 8.9
Arch Linux, i3wm, picom, polybar
Driver: nvidia-open 535.86.05-4

Originally encountered two error dialogs, one after the other on launch. The first described not being able to detect the GPU. The second described that although my 3090Ti meets the minimum specs, my nvidia driver was outdated. The number listed for the driver version it thought I had was the 32bit max int. Clicking ok through both errors presented me with the launcher. Clicking play would move through the intro videos and then freeze on the first load screen with the wrench icon. The driver fields in the log file located at "/home/jaster/.local/share/Steam/steamapps/compatdata/1895880/pfx/drive_c/users/steamuser/Documents/Ratchet & Clank - Rift Apart/Ratchet & Clank - Rift Apart.log" appeared to be emtpy which may explain why the driver version was incorrect in the error dialog.
The next thing I tried was updating my GPU driver and rebooting. This led to exactly the same result. Then I added these launch options VKD3D_CONFIG=dxr VKD3D_FEATURE_LEVEL=12_1 PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 %command% and the game was finally able to launch. I did notice as I tested things that the game continued to crash when texture quality was set to anything above medium.
This configuration allowed me to play up until the cinematic "falling through rifts" sequence during the first boss fight. The game froze just as I was falling into the first rift and I found myself staring at a single frame. The purple background behind the portal was displayed and there appeared to be nothing on the other side. I believe this is the first instance in the main path of the game where direct storage is utilized so the issue is likely related to direct storage not working properly. The log file after this crash going into the rift appeared to contain no errors and just simply ends after normal behavior.

Edit: Set the game to low preset and disabled raytracing completely. Enabled dlss. This allowed me to move past the rift cinematic section.

Edit2: Setting texture quality specifically to low although everything else is on high allows me to move past the rift cinematic section.

Game brings up a error on launch and then crashes when using proton 8.0-3 but runs perfectly fine with proton Experimental

Log: https://gist.github.com/coreybruce/2fe4947b599ab93ed312df9ec6b8c547

@coreybruce That's an issue with an older version of vkd3d-proton, when you use Proton Experimental that error will go away.

That's an issue with an older version of vkd3d-proton, when you use Proton Experimental that error will go away.

Yeah I know that's why I said "but runs perfectly fine with proton Experimental" :P

Just as confirmation, the AMD gpu deck has no issues at all with high textures.

Slightly unrelated to the initial crash, but I get the same dmesg error when I get stuck in this rift
https://streamable.com/2zyd65

im having the same issue too. my specs are as follows
fedora linux
3090 TI
60gb ram
ryzen 5950x

i can max every setting except textures past medium

I've played for a bit now and got to the planet "Savali". It's completely unplayable on Nvidia and immediately crashes the game regardless of settings.
https://streamable.com/ygsbi5

I tried to get through the cutscene on my RX 570 and made a save once I got on the planet, but just 2 seconds after loading the save on the Nvidia card I got the same error as before in dmesg. The planet was loaded and I could run around for those 2 seconds, but it still crashes. I am now softlocked as this is a "forced" section and the backup file the game creates is on this planet, so I cannot go back and choose the other planet.

I can get game to run at medium preset (every other preset crashes). However, once I get to the nefarious juggernaut and go through the rift that opens in that boss fight the game immediately crashes. Unfortunately, you have to go through this rift. Ratchet & Clank Log File attached, error appears to be the following:

19:20:24:913 (00000608) > [D3D] device->GetD3D12Device()->CreateGraphicsPipelineState(&desc, __uuidof(**(&pso)), IID_PPV_ARGS_Helper(&pso)) failed with HRESULT 2147942487 (0x80070057)

@justbugs97 What does your log file say? I suspect a similar error. Log file can be found at:
~/.steam/steam/steamapps/compatdata/1895880/pfx/drive_c/users/steamuser/Documents/Ratchet & Clank - Rift Apart

Furthermore, Proton log file showed three important messages:
25917.355:013c:0264:warn:vkd3d-proton:d3d12_pipeline_state_init_graphics_create_info: Ignoring stencilTestEnable due to lack of stencil aspect.

25917.441:013c:0140:warn:vkd3d-proton:d3d12_command_list_IASetIndexBuffer: Invalid index format 0. This will map to R16_UINT to match observed driver behavior.

25920.577:013c:0274:err:vkd3d-proton:d3d12_pipeline_state_validate_blend_state: Enabling blending on RT 0 with format DXGI_FORMAT_R16G16B16A16_UINT, but using integer format is not supported.

Ratchet & Clank and Proton log files:
Ratchet & Clank - Rift Apart.log

steam-1895880.log

Relevant info:
Proton Experimental
Pop Os (22.04 LTS)
Kernel 6.2.6
GNOME 42.5
X11
RTX 4080
i9-12900kf
32gb ram

Yeah, same errors @cbacary.

I managed to play a bit more on the planet by reducing the graphics to very low, disabling DLSS and changing resolution to 1080p, however I then made the mistake of trying to up the graphics and accidentally put textures on High (which froze the game), since then I have not been able to load the save at all and I'm fearing it's corrupt.

I've played for a bit now and got to the planet "Savali". It's completely unplayable on Nvidia and immediately crashes the game regardless of settings. https://streamable.com/ygsbi5

I tried to get through the cutscene on my RX 570 and made a save once I got on the planet, but just 2 seconds after loading the save on the Nvidia card I got the same error as before in dmesg. The planet was loaded and I could run around for those 2 seconds, but it still crashes. I am now softlocked as this is a "forced" section and the backup file the game creates is on this planet, so I cannot go back and choose the other planet.

I got the same issue, I avoided the juggernaught portal issue by switching to my steam deck then loading a save after the fight. I can do the same for this plannet as it works fine on the deck but yeah ... This plannet is a pain, crashes every time it loads.

I also get the same message in my RCRA log file. I am running with:

Proton Experimental & GE 8.9
Archlinux (kver 6.4.7)
nvidia 535.86.05
X11 i3-gaps

game settings presets high with medium textures and launched with:

PROTON_SET_GAME_DRIVE=1 PROTON_ENABLE_NVAPI=1 VKD3D_CONFIG=dxr11 gamemoderun mangohud %command%

Plannet crashed the game just like juggernaught portal, and not much in the game logs other than:

15:07:15:131 (00001344) > [D3D] device->GetD3D12Device()->CreateGraphicsPipelineState(&desc, __uuidof(**(&pso)), IID_PPV_ARGS_Helper(&pso)) failed with HRESULT 2147942487 (0x80070057)
15:07:24:397 (00000328) > [Save] Request load save type 0, control 128, target -1
15:07:24:397 (00001516) > [Save] Request type 3 failed with code 0x00000002

That's odd that you have to turn your graphics to low, I'm playing at high preset with a 6700XT

As was concluded pretty early in the issue, this bug seems to be entirely contained to Nvidia cards.

Having the same issue as cbacary . At first I used Proton Experimental with all default. The game succeeded to start, but freezed trying to show start menu. I have changed game settings to medium and managed to get to Nefarius. But beating him is not possible because the game freezes trying to render rifts.

steam-1895880.log

The log ends with this:
15973.089:0114:0124:fixme:oleacc:find_class_data unhandled window class: L"#32769"
15973.089:0114:0124:fixme:uiautomation:uia_get_providers_for_hwnd Override provider callback currently unimplemented.
15973.089:0114:0124:fixme:uiautomation:msaa_provider_GetPropertyValue Unimplemented propertyId 30024
15973.091:0114:0124:fixme:uiautomation:uia_element_GetCurrentPropertyValueEx Default property values currently unimplemented
15973.091:0114:0124:fixme:uiautomation:uia_element_GetCurrentPropertyValueEx Default property values currently unimplemented
15973.091:0114:0124:fixme:uiautomation:msaa_provider_GetPatternProvider Unimplemented patternId 10002
15973.091:0114:0124:fixme:uiautomation:nc_provider_GetPatternProvider 00000000008F2CE0, 10002, 0000000001B2EC90: stub
15973.091:0114:0124:fixme:uiautomation:base_hwnd_provider_GetPatternProvider 00000000008F2C50, 10002, 0000000001B2EC90: stub

I am also experiencing these issues. The game needs to be run with Medium textures, everything else functions as expected when maxed out, even RayTracing. I was able to work around the first juggernaut by playing that section on SteamDeck. However, now I am getting stuck trying to get to Savali.

Logs: Game Log, Proton log

I have done some digging and have found the following:

From the game log, the failed CreateGraphicsPipelineState calls:
[D3D] device->GetD3D12Device()->CreateGraphicsPipelineState(&desc, __uuidof(**(&pso)), IID_PPV_ARGS_Helper(&pso)) failed with HRESULT 2147942487 (0x80070057)
Appear to be caused by:
err:vkd3d-proton:d3d12_pipeline_state_validate_blend_state: Enabling blending on RT 0 with format DXGI_FORMAT_R16G16B16A16_UINT, but using integer format is not supported.
The offending code in VKD3D is here. Disabling this return and just letting it disable blend prevents the E_INVALIDARG HRESULT. However, the game still hangs for me trying to enter Savali.

The other wine warnings about stubbed methods appear to happen when alt-tabbing and seem unrelated:

148236.250:0110:0124:fixme:oleacc:find_class_data unhandled window class: L"[#32769](/issue/ValveSoftware/Proton/32769)"
148236.250:0110:0124:fixme:uiautomation:uia_get_providers_for_hwnd Override provider callback currently unimplemented.
148236.250:0110:0124:fixme:uiautomation:msaa_provider_GetPropertyValue Unimplemented propertyId 30024
148236.251:0110:0124:fixme:uiautomation:uia_element_GetCurrentPropertyValueEx Default property values currently unimplemented
148236.251:0110:0124:fixme:uiautomation:uia_element_GetCurrentPropertyValueEx Default property values currently unimplemented
148236.251:0110:0124:fixme:uiautomation:msaa_provider_GetPatternProvider Unimplemented patternId 10002
148236.251:0110:0124:fixme:uiautomation:nc_provider_GetPatternProvider 00000000004B5DB0, 10002, 0000000001B2EC90: stub
148236.251:0110:0124:fixme:uiautomation:base_hwnd_provider_GetPatternProvider 00000000004B5D20, 10002, 0000000001B2EC90: stub

As was concluded pretty early in the issue, this bug seems to be entirely contained to Nvidia cards.

Ahh I see, that sucks

Latest Proton Experimental actually let me get to main menu and select a save file with texture settings set to "very high". After selecting save -> then it locked up lol. Some progress.

Same errors I assume? @hustin-paul

i can verfily the game runs great on my setup 3070ti and 7900xt only issue be rtx io is not working yet and proton-ge devs are very aware on the issue that they are waiting for linux dev start updating vulkan stack so nvidia can update their drivers for linux, they are depending on linux vulkan stack updates that have new 2 features codes for gdeflate to work on linux platform with VK_NV_memory_decompression= handles decompressing assets on GPU, and VK_NV_copy_memory_indirect handles copying decompressed data to Vulkan buffers/images....

right now for amd users ...there is no support as this time so they gonna get lot of lags between portals and loading constant than proton experiment dxvk_async would alleviated somewhat but it will freeze often during portals that requires Microsoft direct storage library on windows 11

Deleting the dstorage.dll and dstoragecore.dll fixed the high graphics crash! Game runs way better now! Directstorage not being implemented is whats screwing with the game. Since it only fires off on NV cards we can assume its related to RTX io.

for now deleting it would run best until vulkan gets updated for proton-ge devs to get implemented soon, it looking promising for the tech on my 3070ti, but sadly it run very poorly on 7900xt in full rt mode, with FSR2 is just don't help much, so i have to turn it off and cause it run like dog shit than ps5 RT performance mode, i wonder why amd not able use what sony use for their pc counterpart users ...it would run better than nothing even though ps5 rt detail kind it awkward with shadows is similar to nvidia RT on low

You mention GE a lot, is it not the VKD3D-proton devs adding it?

they are matching their version closely to experiment version that i don't normally use it directly on steam platform than running outside by desktop shortcuts with commands i put in place while make sure i don't use built in lsteamclient.dll on both i386 and x64 libraries for playing non-steam games and run better without steam interface loaded but i do keep separated copy for steam that normally ge folks added patches and fixes while steam own experiment might be updated day later or 2 before proton-GE implemented it on following days or weeks ..think of this when ubuntu gets latest stuff vs pop_os is behind in little bit for entire year of updates for their OS...stability is what GE folks focus on than bleeding edge folks

So after today's update I'm completely unable to get past the menu, once I've loaded a save (auto save, manual save, brand new save, etc.) I'm stuck on a black screen with the menu music playing in the background.
(00000324) > [Render] SL set d3d device failed. Error:Result::eErrorNotInitialized is the error I get in the Ratchet log

Deleting the dstorage.dll and dstoragecore.dll fixed the high graphics crash! Game runs way better now! Directstorage not being implemented is whats screwing with the game. Since it only fires off on NV cards we can assume its related to RTX io.

I can confirm that deleting dstorage.dll and dstoragecore.dll allows game startup with very high texture quality and progression past rift during boss fight on RTX 3090. Thanks for the tip.

rather than deleting dstorage.dll and dstoragecore.dll can you instead try launching the game with:

WINEDLLOVERRIDES="dstorage=d,dstoragecore=d" %command%

they are matching their version closely to experiment version that i don't normally use it directly on steam platform than running outside by desktop shortcuts with commands i put in place while make sure i don't use built in lsteamclient.dll on both i386 and x64 libraries for playing non-steam games and run better without steam interface loaded but i do keep separated copy for steam that normally ge folks added patches and fixes while steam own experiment might be updated day later or 2 before proton-GE implemented it on following days or weeks ..think of this when ubuntu gets latest stuff vs pop_os is behind in little bit for entire year of updates for their OS...stability is what GE folks focus on than bleeding edge folks

this reads as a giant run on sentence..

it's proton-experimental and vkd3d-proton devs that are doing all the work here. Just want to clarify that. Proton-GE builds on top of proton-experimental wine and vkd3d-proton changes that have already been upstreamed. Basically if it works in proton-experimental, then it should work in proton-ge, and usually it's bleeding edge that receives game fixes before any other forks such as my own.

rather than deleting dstorage.dll and dstoragecore.dll can you instead try launching the game with:

WINEDLLOVERRIDES="dstorage=d,dstoragecore=d" %command%

Same result, game starts correctly even with very high quality textures.

sure gloriouseggroll, and i watching how my little program been doing all those years as this late after calling quits way back then when creator just vanish from this planet , since i did started the idea of manipulating windows dlls from wine itself since its free from them, and i been getting tired of it for them not gonna anywhere with wine dlls by installing dx9 redist files over it. so i thought it would be neat hack the code from wine creators since i am not a coder in my experience just tweaking and tinker what is established and by then the team grew fast in that approach then i quit when someone took over it from github, the reason i quit is valve , i don't like valve business

Replying to https://github.com/ValveSoftware/Proton/issues/6968#issuecomment-1659263274

Thats why I was confused, didn't make any sense that you somehow we're getting DS to run when that's not your field. Though I wonder where he got his info from about the work being done on it. I had assumed those RTX IO extensions would be the key but Ive heard zero work on them being added to mesa or VKD3D-Proton.

rather than deleting dstorage.dll and dstoragecore.dll can you instead try launching the game with:
WINEDLLOVERRIDES="dstorage=d,dstoragecore=d" %command%

Same result, game starts correctly even with very high quality textures.

then this is very likely a much better workaround than deleting game files. I can add a proton-ge protonfix for it but valve will also likely want to do something similar

The newly released Proton Experimental includes some vkd3d-proton work which should help the Nvidia direct storage issues.
Do tell if any problems occur.

Looks like with the new game update, there's no way to enable raytracing on AMD cards on Linux. On Windows, you need a specific recent driver version that doesn't seem to even appear in Radeon Software's updates section in order for the game to let you enable raytracing.

Has anyone had any luck getting it working with RT on Linux with an AMD GPU?

Looks like with the new game update, there's no way to enable raytracing on AMD cards on Linux. On Windows, you need a specific recent driver version that doesn't seem to even appear in Radeon Software's updates section in order for the game to let you enable raytracing.

Has anyone had any luck getting it working with RT on Linux with an AMD GPU?

Confirming the same issue, was attempting to find a solution by faking the reported driver version, but I have no understanding of any ability of Proton to do this. My mesa driver is the latest pull from around 2~ hours ago, so I definitely have the "latest".

after update from 08/09 break the game here with nvidia driver.

after update from 08/09 break the game here with nvidia driver.

rollback to previous update game start again

after update from 08/09 break the game here with nvidia driver.

@tuxtergames Can you try on Proton Experimental again without being on the Ratchet & Clank beta? We just pushed out an update that should fix it.

@AJuujarvi I can load into game now on Nvidia 3090 on Very High settings with latest Proton Experimental, with no custom command args.

after update from 08/09 break the game here with nvidia driver.

@tuxtergames Can you try on Proton Experimental again without being on the Ratchet & Clank beta? We just pushed out an update that should fix it.

Testing here, its working again with experimental bleeding edge, but without RT and DLSS, if you leaving this options on launcher game won't launch, I using here just gamemode and mangohud with a 3060ti on a desktop in high settings, tks for this fix guys, you rock!!!!!

Recent series of game and proton patches have now rendered it unplayable. Game struggled to get past the menu without freezing, and then if it did, would crash moments after being ingame.

So I reinstalled, and now it wont get past the sony entertainment presents screen, it does get past it with PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 %command% only to crash after all the logos finish

GTX 3080, dunno whats going on here, yes the dstorage dlls are present.

@Bitwolfies Hello. Would you be able to post a Proton log?

@Blisto91 Have at er
steam-1895880.log

Gonna guess it has to do with
"2368.518:012c:028c:warn:vkd3d-proton:d3d12_command_list_IASetIndexBuffer: Invalid index format 0. This will map to R16_UINT to match observed driver behavior."

since its spammed 800 times.

Recent series of game and proton patches have now rendered it unplayable. Game struggled to get past the menu without freezing, and then if it did, would crash moments after being ingame.

So I reinstalled, and now it wont get past the sony entertainment presents screen, it does get past it with PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 %command% only to crash after all the logos finish

GTX 3080, dunno whats going on here, yes the dstorage dlls are present.

I'm playing right now and game works nice smoooth here, take out parameters of launch, doesn't work with RT or DLSS.

Works even less without them, so thats not the fix. Also worked fine with RT before this.

Just tried it seconds ago; proton experimental, no launch options, 3090 535.98, max details, debian trixie, kde plasma, wayland. Launches and plays fine.

oh, you wanted ray tracing. In that case:
PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 VKD3D_CONFIG=dxr11,dxr VKD3D_FEATURE_LEVEL=12_2 %command%

game launched fine, started playing, performance was ok with RTX features on very high, however game crashed during reload after dying, so there's still something going on here.

seems that crash was a one time occurrence. Wanted to catch a log of it, and no luck. Played for 15 mins with some deaths (new game+ on max difficulty ;p) and decided to quit before getting hooked again ;)

With last update ( v1.922.0.0) Ray tracing options are no longer available on AMD GPU. There is a startup message indicating that the driver is not up to date. Tested with Proton-Experimental

No problem when rolling back to v1.831.0.0, this is not a Mesa issue.

With last update ( v1.922.0.0) Ray tracing options are no longer available on AMD GPU. There is a startup message indicating that the driver is not up to date. Tested with Proton-Experimental

No problem when rolling back to v1.831.0.0, this is not a Mesa issue.

Can you try with Proton Exp Bleeding Edge?
https://github.com/ValveSoftware/wine/commit/740f66635052033d4543f71558b34f847e21fe16

This commit might have fixed that.

I think there's maybe been a regression. With Proton Experimental, it's specifically when you are aiming a weapon, the performance tanks down to about 20fps (from 100). It seems specific to this action and it happens every time you aim (mouse or controller).

I tried with Proton-GE 8.20 afterwards and the issue was completely gone, while also getting a 20fps boost.

Edit: Nvidia

@kisak-valve Here is the Proton log.

I'm not able to open the Help -> System Information or Help -> Steam Runtime Diagnostics prompts due to the dropdown disappearing bug. Is there a command to open those individual windows, similar to steam steam://settings?

Unsure if this is proton, but on the OLED deck the game doesn't display any controller glyphs, just question marks. Unsure if the OLED represents itself differently?

Maybe a regression but with Proton Experimental the game does not fully stop running when closing. Exiting the game closes the window but the process stays as "Running" until forcing "Stop" from the steam client.

Proton log:
steam-1895880.tar.gz

There is a regression in Proton Experimental where I'm getting a crash at the first Ms. Zurkon shop. As soon as the shop menu opens the framerate drops to single digits and then quickly crashes after a few seconds.
Reverting back to Proton 9.0-4 it works as expected.

This is with a Radeon 7900XT with mesa 25.2.0

Compatibility Report

• Name of the game with compatibility issues: Ratchet & Clank: Rift Apart
• Steam AppID of the game: 1895880

System Information

• GPU: RX 9070 XT
• Video driver version: Mesa 25.3.3
• Kernel version: 6.17.7-ba25.fc43.x86_64
• Link to full system information report as Gist:
• Proton version: 10.0-3

I confirm:

• [X ] that I have checked whether there are updates for my system available.

Symptoms

If any of the RT options are enabled (RT Reflections, RT AO, RT Shadows), the game immediately crashes with an error that the game is attempting to use more video memory than your system can support. This occurs regardless of the input and output resolution, and testing on Windows reveals actual VRAM usage is nowhere near the 9070 XT's 16 GiB VRAM buffer. Lowering the output resolution to 1440p doesn't resolve the issue. I am seeing the identical issue in Spider-Man: Remastered when enabling RT Reflections, the only RT option available in that game. Both games were produced by Insomniac and ported to the PC by Nixxes.

I tested in Steam Game Mode (bazzite-deck) and from my KDE desktop, and included logs for both. I see the same behavior in both cases. I validated game files in Steam but no errors were detected.

steam-1895880-gamemode.log
steam-1895880.log

Reproduction

1. Enable RT reflections, RT shadows, or RT ambient occlusion. The game will immediately crash with the above error.
2. To establish this is the cause, edit home/USERNAME/.steam/steam/steamapps/compatdata/1895880/pfx/user.reg and change "RTReflections"=dword:00000001" to "RTReflections"=dword:00000000" for Reflections. Do the same for RTShadows and RTAmbientOcclusion if you enabled those features.
3. Restart game and the game will run without crashing.

EDIT:

WORKAROUND: It turns out that I can prevent the crashes by using SteamDeck=0. When doing so, RT works normally without the crash/error message and VRAM usage is well below 16 GiB. SteamDeck=1 is set automatically by the Bazzite-deck image (boots directly into Steam Gaming Mode), and apparently it still applies when booting the game from the KDE desktop. Unlike other games, all the graphical options are available, but internally, it must be setting a low VRAM cap based on the limitations of the Steam Deck hardware.

on the pirate planet at the shop on the big arena platform am I capable of consistently with FSR 4, ( RDNA auto upscaling ) to get the game to "smear" as seen in the above picture its triggered by going in and out of the shop and simply jumping around, I've managed to replicate it on 3 repeated instances of shutting the game down going back to the spot opening the shop a few times and running around.

Game isn't impacted, swapping to another upscaler returns the game to a clean image, there is zero performance impact to be felt, the smear is just very.... visually obvious.