Same here with an RTX 3080.

The RTX issues are known. It's a driver bug and it has been reported to NV with bug number 5059946.

I've spent a lot of time trying to figure out a reasonable workaround, but to no avail.

The RTX issues are known. It's a driver bug and it has been reported to NV with bug number 5059946.

I've spent a lot of time trying to figure out a reasonable workaround, but to no avail.

@HansKristian-Work Thanks. Didn't Final Fantasy 16 have the same issue at launch? Curious if that was fixed via a driver release.

The RTX issues are known. It's a driver bug and it has been reported to NV with bug number 5059946.

I've spent a lot of time trying to figure out a reasonable workaround, but to no avail.

Thank you for this information. I'm sorry to be a bother, but would you be aware of any timeframe for when the next Nvidia driver may be released? Whether it includes the fix for this specific game or not, there's a lot of problems it's supposed to address that I and many others are anxious for.

I'm getting this whenever I launch:

DX12 is not supported on your system. Try running without the -dx12 or -d3d12 command line argument.

Running a 1080 Ti on 565.77.

Edit:

Setting this as launch options allowed it to launch, now compiling shaders:

VKD3D_CONFIG=dxr VKD3D_FEATURE_LEVEL=12_2 VKD3D_SHADER_MODEL=6_6 %command%

Edit 2: Tried some different combinations. This error always appears after the end of shader compilation:

Edit 3: See @shigutso's comment, thank you for the detailed information.

Note: Gamescope (HDR)

When running the game with gamescope for HDR, it initialy detects and is stuck at 720p for some reason no matter what one sets as Gamescope option for resolution.

Literally juggling haphazardly between Fullscreen/Windowed allowed me to gain actual targeted resolution. This should be immediately clear as all blurriness is gone from the menu itself.

A quick look from the AMD side (5700X, 6700XT):

• The game seems to have a native shader compilation step on first boot, though for some reason it crashed on completion. When you boot the game again it skips this step so you can play just fine.
• The game can't find save data from Remake, likely because they are in different prefixes. As with Metaphor: ReFantazio and its demo, the solution is probably to copy the Remake save data into Rebirth's prefix.
• The game uses full screen by default, though resolution is reported as 1920x1080 (on a 4K screen). The game is still outputting 4K though (also confirmed by frame rate). This can be fixed by selecting Windowed, changing the resolution to 4K, then selecting Full Screen again.
• Sometimes, there are noticeable LOD pop-ins at the start of cutscenes or when moving the camera quickly.
• Perhaps related to the previous point, frame rate is quite unstable when moving the camera (~55-60 dropping to ~47 FPS). Admittedly I'm running quite ambitious settings for the hardware (max settings except Low Shadows, and 66-100% resolution scaling), and I think it might be related to the dynamic resolution, because pinning it to 50-50% gets rid of the stutters (but it might also be due to the lower resolution)
• When I was fiddling with the graphics settings without any manual saves yet, I noticed that the game would always start with Japanese voices, even though I was making sure that it was set to English in the menu. Other settings would apply just fine. Restarting the game fixed this, I wonder if it is also an issue on Windows.

A quick look from the AMD side (5700X, 6700XT):
The game can't find save data from Remake, likely because they are in different prefixes. As with Metaphor: ReFantazio and its demo, the solution is probably to copy the Remake save data into Rebirth's prefix.

You're correct on the save profile, that worked for me earlier today

The RTX issues are known. It's a driver bug and it has been reported to NV with bug number 5059946.
I've spent a lot of time trying to figure out a reasonable workaround, but to no avail.

Is there a link to the bug report so we can track the progress? Also I'm experiencing the exact same issue, RTX 3060Ti + 565.77.

The RTX issues are known. It's a driver bug and it has been reported to NV with bug number 5059946.
I've spent a lot of time trying to figure out a reasonable workaround, but to no avail.

Thank you for this information. I'm sorry to be a bother, but would you be aware of any timeframe for when the next Nvidia driver may be released? Whether it includes the fix for this specific game or not, there's a lot of problems it's supposed to address that I and many others are anxious for.

According to phoronix the next driver is out on the 30th.

https://www.phoronix.com/news/GeForce-RTX-5090-Linux-Driver

The RTX issues are known. It's a driver bug and it has been reported to NV with bug number 5059946.
I've spent a lot of time trying to figure out a reasonable workaround, but to no avail.

Is there a link to the bug report so we can track the progress? Also I'm experiencing the exact same issue, RTX 3060Ti + 565.77.

Same deal with 3090. Game's pretty much unplayable. Hopefully some workaround surfaces, or it'll probably be a while before we get drivers with a fix. There's a phoronix article stating it'll be in a week, but will it fix this problem?

As to the bug tracker, according to nvidia dev portal:

1. URL should be https://developer.nvidia.com/bugs/5059946
2. however it can be only viewed by submitter.

Another AMD report (7700X, 7800XT) on Bazzite

Currently unable to watch the first cutscene or get through the first area without KWin crashing. Taking a while to understand why, because it's right at the end so every change takes 2-3m even with fast-forward.

Seems to be playtime dependent, after 5 minutes of usage like this (note the clock speed too...) it just bombs.

Confirm the copy save trick works for getting the bonuses so that's a quick win.

I am not sure how to distinguish whether this is an issue with the game, proton, the amdgpu driver or something else but I am sharing just in case.

Running a Ryzen 5800X with a 6800XT on an up-to-date Fedora 41 with Kernel 6.12.9-200.fc41.x86_64.
(Edit: glxinfo Device: AMD Radeon RX 6800 XT (radeonsi, navi21, LLVM 19.1.5, DRM 3.59, 6.12.9-200.fc41.x86_64) (0x73bf))

The game launches fine and I managed to play until Nibelheim where I get repeated crashes.
The gnome desktop session crashes and it sends me back to login.

On another note, the indoor lighting seems WAY too bright.

I tried proton experimental as well as the latest GE proton (9-23) to no avail.

In dmesg I see the following:

[Thu Jan 23 13:36:21 2025] amdgpu 0000:09:00.0: amdgpu: Dumping IP State
[Thu Jan 23 13:36:21 2025] amdgpu 0000:09:00.0: amdgpu: Dumping IP State Completed
[Thu Jan 23 13:36:21 2025] amdgpu 0000:09:00.0: amdgpu: ring gfx_0.0.0 timeout, signaled seq=145837, emitted seq=145839
[Thu Jan 23 13:36:21 2025] amdgpu 0000:09:00.0: amdgpu: Process information: process ff7rebirth_.exe pid 9031 thread vkd3d_queue pid 9174
[Thu Jan 23 13:36:21 2025] amdgpu 0000:09:00.0: amdgpu: GPU reset begin!
[Thu Jan 23 13:36:22 2025] amdgpu 0000:09:00.0: amdgpu: MODE1 reset
[Thu Jan 23 13:36:22 2025] amdgpu 0000:09:00.0: amdgpu: GPU mode1 reset
[Thu Jan 23 13:36:22 2025] amdgpu 0000:09:00.0: amdgpu: GPU smu mode1 reset
[Thu Jan 23 13:36:22 2025] amdgpu 0000:09:00.0: amdgpu: GPU reset succeeded, trying to resume
[Thu Jan 23 13:36:22 2025] [drm] PCIE GART of 512M enabled (table at 0x0000008000F00000).
[Thu Jan 23 13:36:22 2025] [drm] VRAM is lost due to GPU reset!
[Thu Jan 23 13:36:22 2025] amdgpu 0000:09:00.0: amdgpu: PSP is resuming...
[Thu Jan 23 13:36:22 2025] amdgpu 0000:09:00.0: amdgpu: reserve 0xa00000 from 0x83fd000000 for PSP TMR
[Thu Jan 23 13:36:22 2025] amdgpu 0000:09:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
[Thu Jan 23 13:36:22 2025] amdgpu 0000:09:00.0: amdgpu: SMU is resuming...
[Thu Jan 23 13:36:22 2025] amdgpu 0000:09:00.0: amdgpu: smu driver if version = 0x00000040, smu fw if version = 0x00000041, smu fw program = 0, version = 0x003a5a00 (58.90.0)
[Thu Jan 23 13:36:22 2025] amdgpu 0000:09:00.0: amdgpu: SMU driver if version not matched
[Thu Jan 23 13:36:22 2025] amdgpu 0000:09:00.0: amdgpu: use vbios provided pptable
[Thu Jan 23 13:36:22 2025] amdgpu 0000:09:00.0: amdgpu: SMU is resumed successfully!
[Thu Jan 23 13:36:22 2025] [drm] kiq ring mec 2 pipe 1 q 0
[Thu Jan 23 13:36:22 2025] [drm] DMUB hardware initialized: version=0x02020020
[Thu Jan 23 13:36:23 2025] amdgpu 0000:09:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
[Thu Jan 23 13:36:23 2025] amdgpu 0000:09:00.0: amdgpu: ring gfx_0.1.0 uses VM inv eng 1 on hub 0
[Thu Jan 23 13:36:23 2025] amdgpu 0000:09:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 4 on hub 0
[Thu Jan 23 13:36:23 2025] amdgpu 0000:09:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 5 on hub 0
[Thu Jan 23 13:36:23 2025] amdgpu 0000:09:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
[Thu Jan 23 13:36:23 2025] amdgpu 0000:09:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
[Thu Jan 23 13:36:23 2025] amdgpu 0000:09:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
[Thu Jan 23 13:36:23 2025] amdgpu 0000:09:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
[Thu Jan 23 13:36:23 2025] amdgpu 0000:09:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
[Thu Jan 23 13:36:23 2025] amdgpu 0000:09:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
[Thu Jan 23 13:36:23 2025] amdgpu 0000:09:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng 12 on hub 0
[Thu Jan 23 13:36:23 2025] amdgpu 0000:09:00.0: amdgpu: ring sdma0 uses VM inv eng 13 on hub 0
[Thu Jan 23 13:36:23 2025] amdgpu 0000:09:00.0: amdgpu: ring sdma1 uses VM inv eng 14 on hub 0
[Thu Jan 23 13:36:23 2025] amdgpu 0000:09:00.0: amdgpu: ring sdma2 uses VM inv eng 15 on hub 0
[Thu Jan 23 13:36:23 2025] amdgpu 0000:09:00.0: amdgpu: ring sdma3 uses VM inv eng 16 on hub 0
[Thu Jan 23 13:36:23 2025] amdgpu 0000:09:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 8
[Thu Jan 23 13:36:23 2025] amdgpu 0000:09:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 8
[Thu Jan 23 13:36:23 2025] amdgpu 0000:09:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 8
[Thu Jan 23 13:36:23 2025] amdgpu 0000:09:00.0: amdgpu: ring vcn_dec_1 uses VM inv eng 5 on hub 8
[Thu Jan 23 13:36:23 2025] amdgpu 0000:09:00.0: amdgpu: ring vcn_enc_1.0 uses VM inv eng 6 on hub 8
[Thu Jan 23 13:36:23 2025] amdgpu 0000:09:00.0: amdgpu: ring vcn_enc_1.1 uses VM inv eng 7 on hub 8
[Thu Jan 23 13:36:23 2025] amdgpu 0000:09:00.0: amdgpu: ring jpeg_dec uses VM inv eng 8 on hub 8
[Thu Jan 23 13:36:23 2025] amdgpu 0000:09:00.0: amdgpu: GPU reset(2) succeeded!
[Thu Jan 23 13:36:23 2025] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
[Thu Jan 23 13:36:23 2025] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!

Running a Ryzen 5800X with a 6800XT on an up-to-date Fedora 41 with Kernel 6.12.9-200.fc41.x86_64. (Edit: glxinfo Device: AMD Radeon RX 6800 XT (radeonsi, navi21, LLVM 19.1.5, DRM 3.59, 6.12.9-200.fc41.x86_64) (0x73bf))

The game launches fine and I managed to play until Nibelheim where I get repeated crashes. The gnome desktop session crashes and it sends me back to login.

Can confirm, the errors you pasted from your logs also show up on AMD 6900XT, Ubuntu 24.04, Kernel 6.8.0-51-generic.

[  301.193915] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=141858, emitted seq=141860
[  301.194494] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process ff7rebirth_.exe pid 26475 thread vkd3d_queue pid 26580
[  301.195042] amdgpu 0000:09:00.0: amdgpu: GPU reset begin!
[  301.600324] amdgpu 0000:09:00.0: amdgpu: MODE1 reset
[  301.600331] amdgpu 0000:09:00.0: amdgpu: GPU mode1 reset
[  301.600401] amdgpu 0000:09:00.0: amdgpu: GPU smu mode1 reset
[  302.104043] amdgpu 0000:09:00.0: amdgpu: GPU reset succeeded, trying to resume
[  302.107303] [drm] PCIE GART of 512M enabled (table at 0x0000008002000000).
[  302.107403] [drm] VRAM is lost due to GPU reset!
[  302.107406] [drm] PSP is resuming...
[  302.186651] [drm] reserve 0xa00000 from 0x83fd000000 for PSP TMR
[  302.328245] amdgpu 0000:09:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
[  302.328257] amdgpu 0000:09:00.0: amdgpu: SMU is resuming...
[  302.328263] amdgpu 0000:09:00.0: amdgpu: smu driver if version = 0x00000040, smu fw if version = 0x00000041, smu fw program = 0, version = 0x003a5900 (58.89.0)
[  302.328270] amdgpu 0000:09:00.0: amdgpu: SMU driver if version not matched
[  302.328305] amdgpu 0000:09:00.0: amdgpu: use vbios provided pptable
[  302.407854] amdgpu 0000:09:00.0: amdgpu: SMU is resumed successfully!
[  302.409133] [drm] DMUB hardware initialized: version=0x02020020
[  302.657197] [drm] kiq ring mec 2 pipe 1 q 0
[  302.663034] [drm] VCN decode and encode initialized successfully(under DPG Mode).
[  302.663288] [drm] JPEG decode initialized successfully.
[  302.663304] amdgpu 0000:09:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
[  302.663307] amdgpu 0000:09:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
[  302.663309] amdgpu 0000:09:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
[  302.663311] amdgpu 0000:09:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
[  302.663313] amdgpu 0000:09:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
[  302.663315] amdgpu 0000:09:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
[  302.663317] amdgpu 0000:09:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
[  302.663318] amdgpu 0000:09:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
[  302.663320] amdgpu 0000:09:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
[  302.663322] amdgpu 0000:09:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng 11 on hub 0
[  302.663324] amdgpu 0000:09:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
[  302.663326] amdgpu 0000:09:00.0: amdgpu: ring sdma1 uses VM inv eng 13 on hub 0
[  302.663329] amdgpu 0000:09:00.0: amdgpu: ring sdma2 uses VM inv eng 14 on hub 0
[  302.663330] amdgpu 0000:09:00.0: amdgpu: ring sdma3 uses VM inv eng 15 on hub 0
[  302.663332] amdgpu 0000:09:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 8
[  302.663334] amdgpu 0000:09:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 8
[  302.663336] amdgpu 0000:09:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 8
[  302.663338] amdgpu 0000:09:00.0: amdgpu: ring vcn_dec_1 uses VM inv eng 5 on hub 8
[  302.663340] amdgpu 0000:09:00.0: amdgpu: ring vcn_enc_1.0 uses VM inv eng 6 on hub 8
[  302.663342] amdgpu 0000:09:00.0: amdgpu: ring vcn_enc_1.1 uses VM inv eng 7 on hub 8
[  302.663344] amdgpu 0000:09:00.0: amdgpu: ring jpeg_dec uses VM inv eng 8 on hub 8
[  302.672107] amdgpu 0000:09:00.0: amdgpu: recover vram bo from shadow start
[  302.781922] amdgpu 0000:09:00.0: amdgpu: recover vram bo from shadow failed, r is -110, tmo is 0
[  302.781962] amdgpu 0000:09:00.0: amdgpu: GPU reset(2) failed
[  302.796148] amdgpu 0000:09:00.0: amdgpu: GPU reset end with ret = -5
[  302.796154] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* GPU Recovery Failed: -5

VKD3D_CONFIG=dxr VKD3D_FEATURE_LEVEL=12_2 VKD3D_SHADER_MODEL=6_6 %command%

This one works on my GTX 1660S and gets into the game. Now I get the same issue as @hjpaul7 reported (textures missing)

@dmsimard @AshtenThePlatypus perhaps you should file a Mesa bug, I've had similar occurrences in Indiana Jones The Great Circle, apparently it's due to the game trying to compile an invalid shader or something.
But searches online also led me to think it was a voltage issue of sorts, after all it was a very demanding title (especially on the VRAM side). Are your cards factory overclocked? Personally I haven't had issues in Nibelheim (I stopped at the end of the reactor section, so maybe it's after that), but I also wasn't running it at max resolution (66% scaling)

Same issue as @hjpaul7 with an RTX4060. Like others, I am unfortunately unable to find a workaround. At the very least, we're not experiencing this issue alone.

Interestingly enough, I was able to move Zach around. I was interested in seeing if the issue persisted past this scene (I see no reason why it wouldn't), but unfortunately the invisible geometry proved too tricky to navigate.

4080 Super having the same missing terrain. I'm unfamiliar with how issue threads work here, should AMD and Nvidia issues be mixed on the same conversation? It's clearly different issues.
I'll advance to a different area with the Steam Deck and report whether it works then, maybe it's just the first area's texture.

should AMD and Nvidia issues be mixed on the same conversation?

They shouldn't, but welcome to the internet ;)

im having the same problem with my nvidia 4080

dose anyone now what the eta on fixing the problem mite be thank u

I'll advance to a different area with the Steam Deck and report whether it works then, maybe it's just the first area's texture.

No use, Nibelheim has the same issue. I'll have to install a Windows ssd for now 😿

• 9700x, 7900XTX, Mesa 24.3.3-2
• Plasma 6.2.3-1
• Arch Linux 6.12.7-zen1-1-zen

I did crash once at the beginning, playing at 4k@60 mostly, TSRU 100-66%. High. At chapter 2 currently.

Hardware: AMD 6700XT, 5600X
Distro: Bazzite

In game lighting seems to be a bit off, scenes will go from unnaturally dark to unnaturally bright, etc.

Also, I had hard crashes happening as soon as I would load a save file, but the crashing stopped after enabling V-sync both in-game and setting an fps via gamescope in gamescope-session. Testing more to see if this will crash at all.

In game lighting seems to be a bit off, scenes will go from unnaturally dark to unnaturally bright, etc.

Does the change in brightness occur consistently as you enter or leave a dark or bright area (ex: entering/exiting a building)? The game does do some weird brightness adjustments to mimic your eyes adjusting to a brighter or darker environment, but it's that way on PS5 as well, and seems like expected behavior.

Does the change in brightness occur consistently as you enter or leave a dark or bright area (ex: entering/exiting a building)? The game does do some weird brightness adjustments to mimic your eyes adjusting to a brighter or darker environment, but it's that way on PS5 as well, and seems like expected behavior.

Ah okay, so then it is expected behavior, good to know.

endeavouros 5700x3d 7900xt

been getting some pretty hardcore crashes (whole system). seems slightly better under gamescope, but still happening. hope my gpu isn't dying...

Like Ratchet and Clank FF7 Rebirth uses Direct Storage according to pcgamingwiki. I remember with Ratchet removing the direct storage dlls improved performance significantly when I first used it in Proton eons ago. Not sure if this is the case still or not.

Because of the use of DirectStorage 1.2 API, a M.2 NVMe SSD is generally recommended over a SATA SSD.
https://www.pcgamingwiki.com/wiki/Final_Fantasy_VII_Rebirth

I hope this issue fixed asap :')

I'm getting this whenever I launch:

DX12 is not supported on your system. Try running without the -dx12 or -d3d12 command line argument.

Running a 1080 Ti on 565.77.
Edit:
Setting this as launch options allowed it to launch, now compiling shaders:

VKD3D_CONFIG=dxr VKD3D_FEATURE_LEVEL=12_2 VKD3D_SHADER_MODEL=6_6 %command%

According to PCGamingWiki, the game requires DX12.2, not DX12 to work. It doesn't support Vulkan nor DX11.
My GPU, a RX 5500 XT, has support for up to DX12.1, not DX12.2, so I get the same error above when trying to launch the game.

The game's store page says DX12 "Ultimate", and now I realized that's actually DX12.2

For NVIDIA, GTX 20 series support DX12 Ultimate.
For AMD, 6000 series support it.

Hopefully there's a workaround to allow older GPUs to run the game. If the Steam Deck can run it, my RX 5500 XT can run it too. Requiring DX12.2 seems unnecessary...

It does not look like the 570 driver fixes the problem.

In game lighting seems to be a bit off, scenes will go from unnaturally dark to unnaturally bright, etc.

Does the change in brightness occur consistently as you enter or leave a dark or bright area (ex: entering/exiting a building)? The game does do some weird brightness adjustments to mimic your eyes adjusting to a brighter or darker environment, but it's that way on PS5 as well, and seems like expected behavior.

Highly doubt this is the intentional look of the effect (7900 GRE)

Highly doubt this is the intentional look of the effect (7900 GRE)

Ryzen 5800X with a 6800XT on an up-to-date Fedora 41 with Kernel 6.12.9-200.fc41.x86_64.

Like you I am seeing the same thing indoors in Nibelheim and then shortly after that:

It does not look like the 570 driver fixes the problem.

570 wasn't released officially, yet. That "leaked" release might be incomplete. Especially considering, that there are works on FF7R-2 currently going on. Wait for the official release, then test again.

You can also see that brightness issue happening on the Nvidia cards if you try play "guess where the ground is"

Make sure you're using Proton Experimental, or those whiteout glitches are expected.

I use proton experimental bleeding edge and i still see white flashbangs full screen on mesa RADV drivers doesnt seem to happen on AMD pro drivers. (RX 6700 XT)

I've spent a lot of time trying to figure out a reasonable workaround, but to no avail.

Could you spare a little more detail? We can't read the bug report. There are numerous "mods" that replace/inject various DLLs, which apparently make the game workable on GTX 16XX series GPUs, and replace DLSS shipped with the game.

One of random URLs:
https://www.reddit.com/r/FFVIIRemake/comments/1i8mf4n/amdintel_gpus_you_can_mod_fsr_and_xess_into/

Do you believe such a "mod" could help work around the core issue we are suffering from, @HansKristian-Work ?

(to be precise: I'm not asking if replacing DLSS will fix this, but if we can hope to "mod out" the issue in some way)

game workable on GTX 16XX series GPUs

The game hard requires mesh shaders, and will error if FL 12.2 is not supported. I guess a mod that pretends 12.2 is supported on a non-RTX Turing will in theory work.

The bug in question related to mesh shaders being bugged on NV.

Do you believe such a "mod" ...

No. This needs driver fixes.

I use proton experimental bleeding edge and i still see white flashbangs full screen on mesa RADV drivers doesnt seem to happen on AMD pro drivers. (RX 6700 XT)

Do you have a proton log proving that? It's possible it ends up not using experimental somehow.

I use proton experimental bleeding edge and i still see white flashbangs full screen on mesa RADV drivers doesnt seem to happen on AMD pro drivers. (RX 6700 XT)

Do you have a proton log proving that? It's possible it ends up not using experimental somehow.

it doesn't let me upload anything so im sending what the proton log spammed over and over:
8507.193:0138:02f0:warn:vkd3d-proton:d3d12_pipeline_library_load_pipeline: Pipeline "EAA5EF7558AC200F" does not exist.
8507.194:0138:02f8:warn:vkd3d-proton:d3d12_pipeline_library_load_pipeline: Pipeline "9B9CC9D2CBBF38F3" does not exist.
8507.195:0138:02f4:warn:vkd3d-proton:d3d12_pipeline_library_load_pipeline: Pipeline "854ABC93A01E9DD8" does not exist.
8507.196:0138:0310:warn:vkd3d-proton:d3d12_pipeline_library_load_pipeline: Pipeline "32CFE69502D8960A" does not exist.
8507.196:0138:0300:warn:vkd3d-proton:d3d12_pipeline_library_load_pipeline: Pipeline "C608EA2E06D49C31" does not exist.
8507.196:0138:0304:warn:vkd3d-proton:d3d12_pipeline_library_load_pipeline: Pipeline "C2B94A59E98B38BF" does not exist.
10827.688:0138:0774:warn:vkd3d-proton:d3d12_command_queue_QueryInterface: {db6f6ddb-ac77-4e88-8253-819df9bbf140} not implemented, returning E_NOINTERFACE.
10827.693:0138:0224:warn:vkd3d-proton:vkd3d_native_sync_handle_release: Failed to release semaphore (#12a).
10827.693:0138:0224:warn:vkd3d-proton:dxgi_vk_swap_chain_wait_worker: Failed to increment swapchain semaphore. Did application forget to acquire?

Sadly i cant attach images cause my internet might be acting up right now upload fails.

Edit: could upload an image of it on an external site if its okay https://imgur.com/a/1ofiaKY

gpu 7900xtx
cpu 7800x3d
os archlinux
4k@144hz
mesa-git
proton-ge 9-23

it seems that when you move camera view there is an abnormal drop in fps even if the gpu is not having a high workload, to almost completely solve the problem i did the following things:

i started the game with
VKD3D_CONFIG=small_vram_rebar,no_staggered_submit gamemoderun gamescope --adaptive-sync -h 2160 -r 144 -f -- %command%

reason:

• it seems that the binary name does not end with -shipping.exe, this prevents vkd3d from applying the workarounds that are there by default for all unreal engine games, so I applied them with vkd3d_config.
• It seems in addition that starting the game with gamescope and gamemoderun seems to improve a bit more.

I changed the following settings in the game:
graphics quality: high
minimum/maximum upscale: 66%
maximum framerate: 90fps

i put maximum 90fps because it seems that my gpu most of the time can hold this framerate maximum and going beyond it starts to vary the number of fps too often.

in addition I used https://www.nexusmods.com/site/mods/757 to be able to use intel xess as an upscaler

now the game is quite smooth even moving the camera view

i started the game with VKD3D_CONFIG=small_vram_rebar,no_staggered_submit gamemoderun gamescope --adaptive-sync -h 2160 -r 144 -f -- %command%

The 'shipping' executable you're used to seeing is located in the End/Binaries/ directory. I'm not going to try to look into the root directory executable for fear of the SE gods bringing the hammer down. However, even if you attempt to launch from the baked executable you won't be able to launch it from the path directly - if you do you'll get the FF7 splash screen with a message saying to start the game from the Steam client

to almost completely solve the problem i did the following things:

By problems are you referring to the textures failing to load in when the scene initially loads e.g. the title of this issue? Or is this just a general performance tweak for better FPS on your AMD card?

This issue I thought was exclusive to Nvidia GPUs.

inxi -b
System:
Host: Kernel: 6.13.0-2-cachyos arch: x86_64 bits: 64
CPU:
Info: 6-core Intel Core i7-8700K [MT MCP] speed (MHz): avg: 4401
min/max: 800/4700
Graphics:
Device-1: NVIDIA GA106 [GeForce RTX 3060 Lite Hash Rate] driver: nvidia
v: 565.77
Display: wayland server: X.org v: 1.21.1.15 with: Xwayland v: 24.1.4
compositor: kwin_wayland driver: X: loaded: nvidia unloaded: modesetting
gpu: nvidia,nvidia-nvswitch resolution: 1920x1080~240Hz
API: OpenGL v: 4.6.0 vendor: nvidia v: 565.77 renderer: NVIDIA GeForce
RTX 3060/PCIe/SSE2
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: nvidia-settings,nvidia-smi
wl: wayland-info x11: xdpyinfo, xprop, xrandr
Info:
Memory: total: 32 GiB available: 31.28 GiB used: 4.04 GiB (12.9%)

This issue I thought was exclusive to Nvidia GPUs.

it is, but some AMD guys decided to squat here and didn't get the subtle messaging to go away, and build their own issue ;)
that being said, original issue seems to be resolved with 'wait for new drivers and hope for the best'.

it is, but some AMD guys decided to squat here and didn't get the subtle messaging to go away, and build their own issue ;) that being said, original issue seems to be resolved with 'wait for new drivers and hope for the best'.

Issues are filed per game, not per some specific one issue. Keep this edgy gatekeeping for somewhere else please.

Issues are filed per game, not per some specific one issue

If so, then issue template requiring specifying the GPU, describing the symptoms, logs etc. seems misleading, not to mention the added "NVIDIA Drivers" label.
And nobody's gatekeeping anything. I merely suggested, basing on the above, that creating a second issue regarding the AMD problems might just be "cleaner" for everyone. If that's only me, so be it - I won't be mentioning this again.

[andrew@arch FINAL FANTASY VII REBIRTH]$ pwd
/home/andrew/.local/share/Steam/steamapps/common/FINAL FANTASY VII REBIRTH
[andrew@arch FINAL FANTASY VII REBIRTH]$ find . -name "*.exe"
./End/Binaries/Win64/ff7rebirth_.exe
./End/Binaries/Win64/unins000.exe
./End/Binaries/Win64/dlss-finder.exe
./ff7rebirth.exe

@slbillups I don't have any binary that has -shipping

cyberpunk issue 1700 comments, gta v issue 1600 comments, i dont see how for a couple of comments we have to isolate this issue to nvidia problems

Because this is a nvidia specific issue that is related to the dxgi swapchain/VkPipeline failing to stream in and render the world textures. I don't frequent this repository, and since the title of the post wasn't titled with anything mentioning that this is a nvidia-specific issue, the nvidia developer forums or the VKD3D repo may be a better place for discussion.

However when it comes to games, I see many users who either create a new github account for the sole purpose of adding information that is likely just an issue with the end-user hardware configuration. I think these issues are more suited for the Steam discussion platform, protondb, etc rather than the Proton github repository...

@andrew-ld I tried your vkd3d flags and they didn't seem to make that much of a difference, the first one in particular is supposed to only work with cards with <= 8GB VRAM.

Though as I mentioned in my first post, I think what really helps there is disabling the dynamic resolution scaler, which you did by setting the range to 66-66%. I also think that the LOD pop-in issue I was experiencing is due to me running the game at 4K (I had a range of 66-100% res scale, and setting it to 100-100% made it more consistent), I might be hitting some VRAM limits there, so it makes sense. At 66-66% the pop-in issue goes away.

Confirming I am also experiencing the missing textures issue on a 3060 Ti, Fedora 41, driver 565.77, kernel 6.12.10-200.fc41.x86_64

i started the game with
VKD3D_CONFIG=small_vram_rebar,no_staggered_submit gamemoderun gamescope --adaptive-sync -h 2160 -r 144 -f -- %command%

not sure if it was the game update that was released today or these flags but it is working great for me now. Thanks @andrew-ld

5800x3d
7900xtx
6.12.10-203.nobara.fc40.x86_64

@jeffhirsch I tried again today and it looks like the VKD3D_CONFIG workaround is still needed

I get this error using my DS4 Official Sony Wireless Adaptor. Tried Disabling/Enabling Steam Input.

Works fine using Wired.

Bus 001 Device 008: ID 054c:0ba0 Sony Corp. Dualshock4 Wireless Adaptor

LowLevelFatalError [File:Unknown] [Line: 103] 
SECURE CRT: Invalid parameter detected.
Expression: Unknown Function: Unknown. File: Unknown Line: 0



0x00006fffffc1cf57 kernelbase.dll!UnknownFunction []
0x000000014463533f ff7rebirth_.exe!UnknownFunction []
0x0000000144636c94 ff7rebirth_.exe!UnknownFunction []
0x000000014246ff03 ff7rebirth_.exe!UnknownFunction []
0x00006fffffa6508b ucrtbase.dll!UnknownFunction []
0x0000000141b6cee6 ff7rebirth_.exe!UnknownFunction []
0x00006fffffa0111c ucrtbase.dll!UnknownFunction []
0x00006fffffed482d kernel32.dll!UnknownFunction []

Proton Log if it helps.

steam-2909400.log

This game is steam deck verified. Why is this labeled as "unofficial"?

Hi,

Other issue is on AMD 7900 XTX with RADV (24.3.4) & Kernel 6.12.10 :

So I guess I have no choice but to boot up Windows for now, hope this gets resolved soon.

Issue:
Various textures not rendering. Some Nvidia driver problem as far as my understanding goes.

OS: Arch Linux
Compositor: Hyprland
GPU: RTX 3070 Ti
GPU DRIVER: nvidia-dkms
CPU: Ryzen 5 5600X

@liberodark As mentioned here https://github.com/ValveSoftware/Proton/issues/8408#issuecomment-2612790354 that's fixed by using Proton Experimental

Happens to my boyfriend using a 4080 SUPER, both NVIDIA Open 565.77 and NVIDIA Open 570.86, Arch Linux. Using Proton Experimental Bleeding Edge. Tried both SteamDeck=0 and SteamDeck=1.

Let us know what we can do to help fixing this problem.

Let us know what we can do to help fixing this problem.

See here:
https://github.com/ValveSoftware/Proton/issues/8408#issuecomment-2613018177

TL;DR: Wait for next nvidia drivers and hope for the best.

in case anyone's wondering: no, 570.86.15 that went public today do not resolve this issue. :(

edit:
TIL: frown/meh emoji hides comment as off-topic ;)

Also having the same issue.

Latest Arch Linux
EVGA 3080 Ti

Let us know what we can do to help fixing this problem.

See here: [#8408 (comment)](https://github.com/ValveSoftware/Proton/issues/8408#issuecomment-2613018177)

TL;DR: Wait for next nvidia drivers and hope for the best.

In Windows, we have tried hardcapping feature level for the game to both 12_1 and 12_0 while also disabling Feature Level Upgrade altogether and the game still looks fine despite running at lower framerate. I do not think this is driver-related, but feel free to change my mind.

Replying to https://github.com/ValveSoftware/Proton/issues/8408#issuecomment-2618892110

The quoted post below is by Hans-Kristian Arntzen, the creator of vkd3d-proton. I assume the workaround he was trying to create would be within vkd3d.

The RTX issues are known. It's a driver bug and it has been reported to NV with bug number 5059946.

I've spent a lot of time trying to figure out a reasonable workaround, but to no avail.

Replying to https://github.com/ValveSoftware/Proton/issues/8408#issuecomment-2619048268

What does this bug do exactly? I thought the problem was mesh shaders, right?

What does this bug do exactly? I thought the problem was mesh shaders, right?

I'm not a technical enough person to understand the actual issue at play

Doc - Fix Resolution issue within Gamescope

gamescope --force-windows-fullscreen -b -w $(kscreen-doctor -j | jq '.screen.currentSize.width') -h $(kscreen-doctor -j | jq '.screen.currentSize.height') -H $(kscreen-doctor -j | jq '.screen.currentSize.height') --hdr-enabled --mangoapp -- %command%

The --force-windows-fullscreen is key.

Those having the issues with full system crashes on AMD cards like me should look at https://gitlab.freedesktop.org/drm/amd/-/issues/3131

I used to have to play on low settings in a tiny window to prevent the high usage but now I can play maxed out for as long as 10 minutes.

Will have to play test longer but this might help some. Short version is the clock speeds for the GPU are higher than what should be set by the manufacturer so either set them manually or try setting the profile daemon to manual then back to auto

@elken i am the author of the issue on free desktop, i think that in this case the GPU crash is because of a bug in the game, vkd3d Is trying to workaround the issue

maybe is even crashing for that issue but anyway there is another crash caused by the game

Since there's people thumbing me down all the time in this issue, I'd like to elaborate on my troubleshooting process.

• I was told the problem with this issue was linked to mesh shaders
• -> so I tried making them unavailable in Windows, which still didn't cause the issue to happen, or any issue whatsoever, hence why I'm personally not convinced it's a driver issue

If straight reducing the available shader model version is not enough to make this issue appear, so how does this bug work exactly?

Edit: On a side note, reducing FL to 12_1 or even to 12_0 also causes even more features to be unavailable. It's weird that the game is still able to work properly with Direct3D 12 FL 12_0 assuming that missing mesh shaders would completely break terrain and most of the scenery.

I'd prefer receiving a constructive answer on this matter rather than thumbs down if that's possible, thank you.

@elken i am the author of the issue on free desktop, i think that in this case the GPU crash is because of a bug in the game, vkd3d Is trying to workaround the issue

maybe is even crashing for that issue but anyway there is another crash caused by the game

The issue in question fixed all my issues, and I've seen others having the exact same kind of crash as me 😄

vkd3d-proton-pso-retain-references.zip which contains this workaround and hopefully helps with the AMD driver crash (I suppose).

* I was told the problem with this issue was linked to **mesh shaders**

* -> so I tried **making them unavailable in Windows**, which **still didn't cause the issue to happen**, or any issue whatsoever, hence why I'm personally not convinced it's a driver issue

My guess would be:

1. the problem occurs when mesh shaders are available, but broken. (as is on currently available NV drivers up to and including 570.86.15)
2. game checks for available features once during startup, pops an error message and quits if hard requirements are not met, and doesn't bother with this further down the line, therefore blindly using "unavailable" features anyway, as long as initial checks were satisfied.

Replying to https://github.com/ValveSoftware/Proton/issues/8408#issuecomment-2621728724

A quick workaround would be disabling mesh shaders altogether, since feature level 12_0 theoretically don't expose mesh shaders even if available, right? FF seems to run when forcing it to FL 12_0 on Windows, without mesh shaders, it looks fine but it runs at a lower framerate.

FF seems to run when forcing it to FL 12_0 on Windows, without mesh shaders, it looks fine but it runs at a lower framerate.

Could you explain how you did that? Because the game refuses to start if it cannot create a FL 12.2 device when I tested.

FF seems to run when forcing it to FL 12_0 on Windows, without mesh shaders, it looks fine but it runs at a lower framerate.

Could you explain how you did that? Because the game refuses to start if it cannot create a FL 12.2 device when I tested.

• Download and install Graphics Tools from Optional Features
• Open dxcpl from a Run box
• Add FF's executable
• Cap feature level and make sure to disable Feature Level Upgrade
• Apply

* Cap feature level and make sure to disable Feature Level Upgrade

Assuming this works properly, and attempts to use mesh shaders are indeed blocked , then perhaps it's the other way around: game checks for FL 12.2, is being lied to that it's supported, and then Unreal Engine manages to work around missing features? That would explain how people made FF work on GTX 1650, even though it obviously doesn't support 12.2

Can the same be attempted with vkd3d? i.e. reporting 12.2 available, but then failing attempts to use 12.2 features, or at least mesh shaders?

It's not impossible. I haven't tried that myself at least.

Replying to https://github.com/ValveSoftware/Proton/issues/8408#issuecomment-2621817808

Assuming the game attempts to create FL 12_2 and cannot fallback, then yes, it is being lied to and then Unreal Engine works missing features around. That's plausible.

I tried this, but the game fails to boot with an error about missing assets:

diff --git a/libs/vkd3d/device.c b/libs/vkd3d/device.c
index 494bb067..201f0af6 100644
--- a/libs/vkd3d/device.c
+++ b/libs/vkd3d/device.c
@@ -4303,6 +4303,8 @@ static HRESULT STDMETHODCALLTYPE d3d12_device_CheckFeatureSupport(d3d12_device_i
                     data->MaxSupportedFeatureLevel = fl;
             }
 
+            data->MaxSupportedFeatureLevel = D3D_FEATURE_LEVEL_12_0;
+
             TRACE("Max supported feature level %#x.\n", data->MaxSupportedFeatureLevel);
             return S_OK;
         }
@@ -4702,6 +4704,7 @@ static HRESULT STDMETHODCALLTYPE d3d12_device_CheckFeatureSupport(d3d12_device_i
             }
 
             *data = device->d3d12_caps.options7;
+            data->MeshShaderTier = 0;
 
             TRACE("Mesh shading tier %#x.\n", data->MeshShaderTier);
             TRACE("Sampler feedback tier %#x.\n", data->SamplerFeedbackTier);

I have no idea how dxcpl manages to boot the game up with tier 0 mesh shaders (FL 12_0). Is it plausible to assume that Windows would be emulating them through WARP (not to be confused with "force warp" which forces software rendering for everything)? Maybe it's not UE compensating, it could be Direct3D itself.

Edit: This would also explain why the game runs 15-20 fps slower when forcing 12_0.

Edit: This would also explain why the game runs 15-20 fps slower when forcing 12_0.

I think we need some way to incontrovertibly prove that the game is actually demoting mesh shaders to plain-old vertex shaders here somehow. The lowered FPS is curious, but it's unclear what the dxcpl tool ends up doing.

Edit: This would also explain why the game runs 15-20 fps slower when forcing 12_0.

Can you reproduce these results with other games like Alan Wake 2 as well?
I still do not understand why mesh shaders are the issue here with nvidia users. Alan Wake 2 used them extensively, and I had no issues with it -- the game did not even warn me about missing features whatsoever.

Edit: This would also explain why the game runs 15-20 fps slower when forcing 12_0.

I think we need some way to incontrovertibly prove that the game is actually demoting mesh shaders to plain-old vertex shaders here somehow. The lowered FPS is curious, but it's unclear what the dxcpl tool ends up doing.

Yeah, I agree, but I don't know where to start to begin with. Unlucky.

Edit: This would also explain why the game runs 15-20 fps slower when forcing 12_0.

Can you reproduce these results with other games like Alan Wake 2 as well? I still do not understand why mesh shaders are the issue here with nvidia users. Alan Wake 2 used them extensively, and I had no issues with it -- the game did not even warn me about missing features whatsoever.

I unfortunately don't own Alan Wake 2. But yes, you're right, Alan Wake 2 actually has mesh shaders as a strict requirement.

maybe benchmarking the nvidia asteroids demo might work as well? link

I have tried to get it running in bottles, but it closes on my machine with a "mesh shaders not supported, demo will close"-like error message -- despite the lines below:

11068.130:0020:0024:info:vkd3d-proton:d3d12_device_determine_ray_tracing_tier: DXR support enabled.
11068.130:0020:0024:info:vkd3d-proton:d3d12_device_determine_ray_tracing_tier: DXR 1.1 support enabled.
11068.130:0020:0024:info:vkd3d-proton:d3d12_device_caps_init_feature_level: DX Ultimate supported!

Replying to https://github.com/ValveSoftware/Proton/issues/8408#issuecomment-2622223633

If you can, try capping FL to 12_0 under Windows for the executable and see if it still runs without complaining. I can't test right now.

No need to try that. I verified that the dxcpl tool thingy does not do anything for d3d12, and also confirmed that with someone who knows the details. That override is for d3d11 only. I also verified through capturing the game on Windows that it is still using mesh shaders.

No need to try that. I verified that the dxcpl tool thingy does not do anything for d3d12, and also confirmed that with someone who knows the details. That override is for d3d11 only. I also verified through capturing the game on Windows that it is still using mesh shaders.

Uhm, this is what I get by capping Feature level limit + disable feature level upgrade on Cyberpunk 2077:

It says there has been an error initializing Ray Tracing and that my drivers could be obsolete or damaged. It's telling me to reinstall my drivers.

Are you sure you're not using the dxcpl from the old DirectX SDK? Make sure it says Direct3D 10/11/12:

You can get the updated dxcpl from PC settings -> Optional Features

(regardless, a quick google search confirms that dxcpl works for d3d12, other than this I have no idea how to help)

Edit: sometimes dxcpl doesn't work, see my new answer below

I filed a bugreport at mesa for amdgpu crashes: https://gitlab.freedesktop.org/mesa/mesa/-/issues/12545

Small correction: It seems like you were right about the game still using mesh shaders, dxcpl doesn't prevent the game from using them. Welp, no idea what's going on honestly then, Direct3D works in weird ways.

People still use dxcpl in combination with D3D12 to change the feature level. It seems like some games can forcibly decide what to do, somehow. This is not always the case for all games. CP2077 really really didn't like me changing the FL limit.

Edit: Ratchet & Clank: Rift Apart also reacts in a bad way, but only after going through the launcher and launching the game.

I've managed to replicate Hans' error; also tried numerous more forced "downgrades", and each attempt resulted either in DX12 being unsupported error, "Game files required to initialize the global shadre library are missing" error, or just generic "Fatal error!" while "checking saved data..."

That aside, has anyone tried 550.40.83 drivers?

Vulkan Developer Beta Driver Release Updates
January 24th, 2025 - Windows 553.64, Linux 550.40.83

    New:
        [VK_KHR_depth_clamp_zero_one](https://registry.khronos.org/vulkan/specs/latest/man/html/VK_KHR_depth_clamp_zero_one.html)
        [VK_KHR_video_maintenance2](https://registry.khronos.org/vulkan/specs/latest/man/html/VK_KHR_video_maintenance2.html)
    Fixes:
        Allow linear images with VK_IMAGE_CREATE_DESCRIPTOR_BUFFER_CAPTURE_REPLAY_BIT_EXT
        > **Fix gl_NumWorkGroups behavior for mesh shaders** <
        Fix alignment requirement for buffers created with VK_BUFFER_USAGE_2_PREPROCESS_BUFFER_BIT_EXT
        Don't attempt to clear fragment shading rate attachments used with dynamic rendering

EDIT: Just tested them; unfortunately nothing has changed. Still no ground post intro sequence.

At least they're looking into it internally at nvidia https://github.com/NVIDIA/open-gpu-kernel-modules/issues/708#issuecomment-2623167940

Pity their bug reports can't really be viewed so no visibility on the progress.

For AMD hangs, we have two game workarounds merged now which have successfully worked around some hangs on our end at least:

• https://github.com/HansKristian-Work/vkd3d-proton/pull/2319
• https://github.com/HansKristian-Work/vkd3d-proton/pull/2320 (from 1 hour ago)

Nvidia released 570.86.16 today: https://www.nvidia.com/en-us/geforce/drivers/results/240524/

Sadly, it doesn't resolve the problem. Oh well.

For AMD hangs, we have two game workarounds merged now which have successfully worked around some hangs on our end at least:

* [Add PSO retain workaround for FFVII Rebirth. HansKristian-Work/vkd3d-proton#2319](https://github.com/HansKristian-Work/vkd3d-proton/pull/2319)

* [Workaround missing CS barrier in Rebirth. HansKristian-Work/vkd3d-proton#2320](https://github.com/HansKristian-Work/vkd3d-proton/pull/2320) (from 1 hour ago)

Thanks, those really solve gpu hangs for me!

Replying to https://github.com/ValveSoftware/Proton/issues/8408#issuecomment-2625433490

I'm sorry but, how did you test it? Do I have to compile vkd3d-proton or something like that? Or maybe using proton experimental is enough to have the latest version?
I don't know much about this…

@HansKristian-Work works for me! THANK YOU!

@mmequignon

vkd3d-proton-pso-retain-references.zip

which contains the mentioned workarounds. Replace the dlls inside proton and make sure to use a clean prefix.
mangohud will show 99.0.0 vkd3d version

@HansKristian-Work works for me! THANK YOU!

@mmequignon

vkd3d-proton-pso-retain-references.zip

which contains the mentioned workarounds. Replace the dlls inside proton and make sure to use a clean prefix. mangohud will show 99.0.0 vkd3d version

I'm sorry, I don't quite understand what you mean. Could you please give me a hand? I'm quite the beginner here.
If you're ok, you can reach me by email, it is on my gh account.
Thanks!

Just use Experimental bleeding-edge. There is no need to download dlls like this. We're in the process of pinning a Hotfix build that should automate this stuff.

Just use Experimental bleeding-edge. There is no need to download dlls like this. We're in the process of pinning a Hotfix build that should automate this stuff.

Ah great, I didn't know about that, thank you. 🙇
I'll try this tomorrow and give feedback!

Any news for Nvidia users on the issue we're having? Is it even a Nvidia issue considering a new driver came out yesterday and the issue persisted.

Any news for Nvidia users on the issue we're having? Is it even a Nvidia issue considering a new driver came out yesterday and the issue persisted.

NVIDIA just don't care about us Linux users, NVK is our only hope in the long term.

Any news for Nvidia users on the issue we're having? Is it even a Nvidia issue considering a new driver came out yesterday and the issue persisted.

On the Nvidia website it is listed as a beta driver. They have mentioned they are looking into the issue, so hopefully by time, or before, it comes out of beta it will be fixed.

Please stop arguing about Nvidia. I'm following this issue for an update on when I can play this game, not to have my inbox spammed with arguments about how good or bad they are as a company. Please, if you wanna argue about Nvidia on Linux, go to Reddit or something.

I'm experiencing massive stutters just by moving the camera around.
I tried doing the same on Windows, and it doesn't happen.

I also tried this launch command and disabled dynamic res

Additionally, I set the graphics to low and capped the framerate at 30 FPS, but the issue still persists.

gpu 6700xt
cpu 5700x3d
os archlinux
linux zen kernel
mesa-git
proton-ge 9-23 and proton experimental bleeding edge

Any news for Nvidia users on the issue we're having? Is it even a Nvidia issue considering a new driver came out yesterday and the issue persisted.

On the Nvidia website it is listed as a beta driver. They have mentioned they are looking into the issue, so hopefully by time, or before, it comes out of beta it will be fixed.

Sweet, thanks for the info, suppose i'll replay the first remake in the meantime

For AMD hangs, we have two game workarounds merged now which have successfully worked around some hangs on our end at least:

• Add PSO retain workaround for FFVII Rebirth. HansKristian-Work/vkd3d-proton#2319
• Workaround missing CS barrier in Rebirth. HansKristian-Work/vkd3d-proton#2320 (from 1 hour ago)

I can confirm these patches fixed the lighting issue. I use proton GE 9-23 and override the vkd3d dll with the latest master commit on de2987b

The lighting was too bright but it is fixed with the patch.

The vending machine was flickering and transparent previously. After the patch, the object is rendered correctly.

I am running Debian unstable, Ryzen 5 5600x, AMD Radeon 7800XT. No crash anymore so far with my limited testing.

Additionally, I set the graphics to low and capped the framerate at 30 FPS, but the issue still persists.

gpu 6700xt
cpu 5700x3d

@arnxxau make sure you're on proton experimental bleeding edge as referenced here. That fixed all my issues on amd.

The RTX issues are known. It's a driver bug and it has been reported to NV with bug number 5059946.
I've spent a lot of time trying to figure out a reasonable workaround, but to no avail.

Is there a link to the bug report so we can track the progress? Also I'm experiencing the exact same issue, RTX 3060Ti + 565.77.

I am afraid no. I have reported bugs to NV in the past and their bugs are kept private to NV and the bug reporter and this is enforced by only using email for comms

Additionally, I set the graphics to low and capped the framerate at 30 FPS, but the issue still persists.

gpu 6700xt
cpu 5700x3d

@arnxxau make sure you're on proton experimental bleeding edge as referenced here. That fixed all my issues on amd.

Hi @jeffhirsch, I'm sure I was on Proton Experimental Bleeding Edge. The lighting issues and transparent objects were fixed, but I'm still experiencing a stuttering behavior when moving the camera around, which does not happen on Windows.

I tested it on Windows to see how bad the stutters really were since reviews mentioned that stuttering does occur. However, when I tried it on Windows, I realized that the stuttering wasn't as bad as I expected, and the way it currently runs on Linux doesn't seem to be the correct behavior.

I also tried:

• Limiting the FPS with external limiters
• Changing to various proton versions (proton9, protonge, proton experimental.....)
• Changing my kernel to amd-drm-next and CachyOS
• Running the game through Gamescope
• Running the entire Steam session through Gamescope (like on the Steam Deck)
• Disabling VRR in-game, within GNOME, and in Gamescope
• Disabling VKD3D cache
• Disabling DirectStorage with FF7Hook
• Updating to the latest mesa git

None of these fixed the stuttering.

Just use Experimental bleeding-edge. There is no need to download dlls like this. We're in the process of pinning a Hotfix build that should automate this stuff.

Just tried to run the game with experimental bleeding edge, and I'm still experiencing random crashes.

CPU: AMD Ryzen 7 3700X
GPU: AMD RX 7900 XT
Kernel is 6.12.10

Square Enix has made a post on the Steam forums that they are investigating issues with the game when using AMD. https://steamcommunity.com/app/2909400/discussions/0/597391264850139769/

Replying to https://github.com/ValveSoftware/Proton/issues/8408#issuecomment-2628946388

i exhibit the same stuttering on my system
With an RX 6700 XT and 5600X on 6.13 Cachyos kernel
it only happens when i turn the camera otherwise experimental bleeding edge fixed all pain points for me, but the stutter is really jarring and can't be fixed even with fps cap. One thing to note is when i updated the game's direct storage version, it seemed to improve quite a bit, but when the camera moves my cpu gets extremely hammered. Possibly IO read speed issues or something can't keep up?

Todays Rebirth patch appears to do nothing to help with the Nvidia issue.

Just got the Nvidia 570 drivers on Arch today and ground textures still don't load. And can confirm that the patch today also did nothing to fix it.

OS: Arch Linux
KERNEL: 6.13.1-arch1-1
CPU: 13th Gen Intel Core i9-13900K
GPU: NVIDIA GeForce RTX 4080
GPU DRIVER: NVIDIA 570.86.16

I'm experiencing massive stutters just by moving the camera around. I tried doing the same on Windows, and it doesn't happen.

I also tried this launch command and disabled dynamic res

Additionally, I set the graphics to low and capped the framerate at 30 FPS, but the issue still persists.

gpu 6700xt cpu 5700x3d os archlinux linux zen kernel mesa-git proton-ge 9-23 and proton experimental bleeding edge

Try updating to Linux kernel 6.13.1 if you have an AMD GPU. In Linux kernel 6.12.10 and older, the power saving was too aggressive on my AMD graphics cards (RX 7900 XTX and RX 7800 XT). The VRAM P-state clock speed were stuck between 96 MHz, 456 MHz, and 772 MHz instead of the max of 1249 MHz. Linux kernel 6.13.1 on Arch Linux has the VRAM clock speed go up to 1249 MHz as expected in this game.

You can see the VRAM clock speed in MangoHud or if you run cat /sys/class/drm/card1/device/pp_dpm_mclk.

Replying to https://github.com/ValveSoftware/Proton/issues/8408#issuecomment-2632930197

Mate. This is a specific bug report for NVIDIA missing textures problem.

If you're so enthusiastic about responding on how it performs on AMD cards and how to fix or optimize that, I recommend you open a proper forum thread on the subject or a bug report with AMD.

Stop hijacking NVIDIA specific bug reports on Github for unrelated discussions.

Your behavior is exactly why NVIDIA keeps those restricted internally.

Replying to https://github.com/ValveSoftware/Proton/issues/8408#issuecomment-2632958122

No you are incorrect. This is a per game tracker. I understand the OP is discussing the mesh shader problem affecting Nvidia GPUs with the buggy drivers. However, AMD users need a place to discuss the game issues affecting this game as well. AMD drivers can be buggy as well.

As OP, I hope @kisak-valve can kind of chime in or lock this thread temporarily:

This thread should be for all to report constructive information to help Proton developers.

Nvidia: It's a driver issue, stop spamming this thread.

AMD: Users have legit issues, let them post Proton logs or launch args.

Threads should be info gathering for developers, not a debate. If you have nothing to contribute, don't comment.

Replying to https://github.com/ValveSoftware/Proton/issues/8408#issuecomment-2632930197

I ran your command while the game was running, and it was operating at maximum speed (1000MHz with the 6700XT).

I've recorded two short videos comparing the frametime graphs using MangoHud on Linux and MSI Afterburner on Windows.

The Linux recording was made using GNOME Recorder.
The Windows recording looked extremely poor with the built-in recorder, so I had to use OBS instead.

On Linux, some overlay parameters are missing. I suspect this is due to the CachyOS kernel I installed for testing purposes. However, the stuttering occurs on all the kernels I’ve tested.

All Linux tests were run from the internal NVMe drive.
Previous Windows tests were done on an external SSD to check performance. The only issue with the external SSD was extreme texture pop-in, but the game ran smoothly without severe stutters.

For this Windows recording, the game is running from a small partition of my internal NVMe drive, where Linux is also installed, but formatted in NTFS so Windows can read it.

Both recordings were made with high settings, VSync enabled, and a 60 FPS cap with dynamic resolution.

The stutters persist regardless of the game’s configuration. This is just the way I’m currently playing it on Windows.

Windows:

https://github.com/user-attachments/assets/86e4ee18-33c8-4c73-a15d-08bc73d156be

Linux:

https://github.com/user-attachments/assets/5c8fa535-6716-4739-9f83-ea7b7fd5792a

Sorry for making this so long, and thanks to everyone contributing

OS: Arch Linux
KERNEL: 6.13.1-cachyos
CPU: Ryzen 5600X
GPU: NVIDIA GeForce RTX 2060
GPU DRIVER: NVIDIA 570.86.16
Proton: Proton-Experimental [Bleeding Edge]

Just because I was curious, and my installation somehow lets me move around without issue, I decided to follow a playthrough to get through the first area a little ways (incredibly awkward with so much missing geometry), and can confirm that the bloom/lighting issue is ALSO present here as on AMD. Once you are indoors and get to a certain point, the background gets bright enough to make it difficult to see, similar to this prior post.

Replying to https://github.com/ValveSoftware/Proton/issues/8408#issuecomment-2633019715

Take a look at description, you are confusing people then mid way taking it back. Update your issue description to a more generic form.

As kisak just said, this is a per-game issue tracker. Both NVIDIA and AMD users have the right to type in here.

"I just said that if you want to post on AMD, then you should open a bug report for it"
-> No, because kisak said that this is a per-game report. and you have no right to change the way Valve works.
I personally think Valve is doing a great job by keeping the reports per-game, imagine what a mess it would be to have a report for every problem X in the game Y. I can't even imagine it.
People are posting feedback about how the game is running on Proton for them and are being responded to. I don't see a problem with that.

for red team stuttering there is a fix
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/33370

for red team stuttering there is a fix https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/33370

I just updated to the latest Mesa Git build currently available, which includes this fix (25.1.0_devel.201497.e550a3cab04.d41d8cd-1).

However, the stuttering persists for me and feels the same as before.

Can anyone confirm if this fix has resolved the stuttering for them?

@arnxxau
Using 7800xt with mesa-git, the mr do fix stuttering on my system.
Moving camera around no longer cause stuttering when setting background model to ultra or enable DRS.

With the updated caching system, there should be a new directory name radv_builtin_shaders in the games shader cache directory <steam library>/shadercache/2909400/radv_builtin_shaders

I can confirm the stuttering fix makes no noticeable difference on my system.
The radv_builtin_shaders directory is created in the shader cache directory.

mesa-tkg-git-25.1.0_devel.201501.08cd331cc0b
CachyOS
7900 XTX
13900k

@AshtenThePlatypus @arnxxau are using custom proton like proton-ge or dlss injectors like dlss enabler, optiscale ecc?

The Mesa shader stutter fix is an improvement, especially in detailed areas like Kalm. Much smoother than before. However, the frame time graph is still jagged like a sawtooth.

RX 7800 XT
Arch Linux kernel 6.13.1-zen3-1-zen
Mesa 25.1.0_devel.201535.48edb9cec24
Proton Experimental 9.0 20250203
High preset
Background model detail: Ultra
In-game Framerate and Display Sync Tech: 60 fps and VRR

https://github.com/user-attachments/assets/87ff871f-2261-48df-9a5d-0d0e93e52dd9

Screenshot outside Junon while camera is turning to show frame time graph:

@spiffeeroo the first video looks like the opening scene of the game, that part is known to lag a lot, i don't know why but even on windows and on other brands gpu's it happens, you stay there just 30 minutes.

the frame time graph is still jagged like a sawtooth

The frame time graph in Mangohud isn't necessarily indicative of the actual frame pace, since that frame time graph is latched on CPU based on the present thread's progress calling vkQueuePresentKHR, not game thread. The game does struggle with frame pacing in general based on my testing (seems to be caused by IO not being as async as it could be), and when running with 144Hz VRR, the jitter is really bad, but when running with vsync on a display that is 60 Hz, the behavior improved dramatically, and it looks very smooth to me even on an aging 3950x. Using a frame limiter in-game seems to make the problem worse since there is no FIFO queue that can absorb the jitter.

I have a hunch that for the people reporting it stutters a lot and the people that say it works just fine, it might be a difference in VRR usage.

I don't have an AMD card to see how it's running on Linux but since I'm on Nvidia I have been putting some time in on Windows.

I can say the frame times on windows are jagged as well. I also experience frequent-ish stuttering especially when I am progressing further into a zone which I think might be the game loading in new assets.

Hopefully this is helpful in determining what may be Linux performance issues versus optimization problems on FF7's end because it has been a messy release for Windows users as well.

Fwiw, I had the dx12.2 issue and the game didn't launch on any proton version I tried. Tried changing the Wine config to Windows 11/10, but it didn't help. With the Steam launch arg -dx11 like I have in FFVIIR it gives me some other error and the game won't launch.

This was on launch. I refunded the game and haven't seen any mentions of success for gamers with similar hardware. Has anyone else?

Overall pretty disappointed Square has released yet another poor PC port (It's broken and lacking basic features on Windows too). It's inexcusable.

@arch ~ → neofetch
                   -`                    @arch
                  .o+`                   -----------
                 `ooo/                   OS: Arch Linux x86_64
                `+oooo:                  Host: Z790 AORUS ELITE AX
               `+oooooo:                 Kernel: 6.12.10-arch1-1
               -+oooooo+:                Uptime: 11 days, 4 hours, 34 mins
             `/:-:++oooo+:               Packages: 1271 (pacman)
            `/++++/+++++++:              Shell: bash 5.2.37
           `/++++++++++++++:             Resolution: 3440x1440
          `/+++ooooooooooooo/`           DE: Plasma 6.2.5
         ./ooosssso++osssssso+`          WM: kwin
        .oossssso-````/ossssss+`         Theme: Breeze-Dark [GTK2], Breeze [GTK3]
       -osssssso.      :ssssssso.        Icons: breeze-dark [GTK2/3]
      :osssssss/        osssso+++.       Terminal: ghostty
     /ossssssss/        +ssssooo/-       CPU: Intel i7-14700K (28) @ 5.500GHz
   `/ossssso+/:-        -:/+osssso+-     GPU: AMD ATI Radeon RX 7900 XT/7900 XTX/7900 GRE/7900M
  `+sso+:-`                 `.-/+oso:    GPU: Intel Raptor Lake-S GT1 [UHD Graphics 770]
 `++:.                           `-/+/   Memory: 9089MiB / 64057MiB
 .`                                 `/

@marcusziade you almost certainly got the dx12.2 not supported error because you're using amdvlk as vulkan driver instead of radv, extremely common issue on Arch that will negatively affect other games as well. Install vulkan-radeon lib32-vulkan-radeon, uninstall amdvlk lib32-amdvlk (even if you refunded the game, it will help other games as well). The game can't run with -dx11 due to it using mesh shaders.

Is there anything new about the Nvidia drivers on Linux? I can't play the game at all after the intro because of the missing textures. I know there's a bug report with Nvidia but none of us can see anything about it.

/////////////                
         /////////////////////            ----------------------
      ///////*767////////////////         OS: Pop!_OS 22.04 LTS x86_64
    //////7676767676*//////////////       Kernel: 6.9.3-76060903-generic
   /////76767//7676767//////////////      Uptime: 6 days, 16 hours, 29 mins
  /////767676///*76767///////////////     Packages: 2729 (dpkg), 47 (flatpak),
 ///////767676///76767.///7676*///////    Shell: bash 5.1.16
/////////767676//76767///767676////////   Resolution: 1024x768
//////////76767676767////76767/////////   Terminal: /dev/pts/2
///////////76767676//////7676//////////   CPU: AMD Ryzen 9 5900X (24) @ 3.700GH
////////////,7676,///////767///////////   GPU: NVIDIA GeForce RTX 3060 Ti Lite
/////////////*7676///////76////////////   Memory: 56671MiB / 64224MiB
///////////////7676////////////////////
 ///////////////7676///767////////////
  //////////////////////'////////////
   //////.7676767676767676767,//////
    /////767676767676767676767/////
      ///////////////////////////
         /////////////////////
             /////////////

Replying to https://github.com/ValveSoftware/Proton/issues/8408#issuecomment-2654998078

Sadly nothing yet. All we can really do is wait until an Nvidia driver update to hit and hope it fixes it. I am under the impression that it can't be fixed via Proton. You could maybe make a post about it on the Nvidia Linux forums and see if anyone can provide updates. https://forums.developer.nvidia.com/c/gpu-graphics/linux/148

Replying to https://github.com/ValveSoftware/Proton/issues/8408#issuecomment-2654998078

I appreciate your reply and the info! I'll continue to watch this thread and also add my troubles to the Nvidia Linux forum. I see someone posted it there on 2/2.

I might have found a temporary workaround for NV, but it requires some modding.

If you're brave enough, you can try building https://github.com/HansKristian-Work/pyroveil as instructed and use the config file in https://github.com/HansKristian-Work/pyroveil/tree/master/hacks/ffvii-rebirth-nvidia and it should magically work.

EDIT: Seems like dropping the file doesn't work for whatever reason, so PYROVEIL_CONFIG=/path/to/pyroveil/hacks/ffvii-rebirth-nvidia/pyroveil.json seems to be needed.
EDIT: You may need to delete vkd3d-proton.cache and vkd3d-proton.cache.write as well.

Can confirm it works on my end (at least on the opening scene). Well done you absolute genius. <3

EDIT: Seems like dropping the file doesn't work for whatever reason, so PYROVEIL_CONFIG=/path/to/pyroveil/hacks/ffvii-rebirth-nvidia/pyroveil.json seems to be needed.

I didn't have to explicitly set the path to the json on my end. I put it next to the exe file as documented on the readme (~/.steam/steam/steamapps/common/FINAL\ FANTASY\ VII\ REBIRTH/pyroveil.json) and used PYROVEIL=1 %command% in the game's properties in steam.
If that's relevant: GPU RTX 3070, driver 570.86.16, kernel 6.13.2-zen1

I can also report success with pyroveil by just dropping the .json directly next to ff7rebirth.exe and adding PYROVEIL=1 to the start of my launch command. I am using 570.86.15 from the cuda repository on kernel 6.13.1 on an RTX 3090.

EDIT: I am running in gamescope for HDR -- would that be why dropping the config next to the .exe works? This is my full command:

PYROVEIL=1 DXVK_HDR=1 gamemoderun gamescope -H 1440 -W 2560 -f --hdr-enabled --hdr-debug-force-output -- %command%

Replying to [#8408 (comment)](https://github.com/ValveSoftware/Proton/issues/8408#issuecomment-2657340142)

Unfortunately, I can not report success. Here's my proton log and system info

I'm a bit of a dumbo so I probably did something wrong, but my log does report that pyroveil is loading the config.

I'm a bit of a dumbo so I probably did something wrong, but my log does report that pyroveil is loading the config.

Try deleting vkd3d-proton.cache and .cache.write. It's under End/Binaries in the game install folder.

That worked. Thanks!

Also reporting success here with the Pyroveil workaround on Bazzite 41.

570.86.16 drivers on a 4070 Super with kernel 6.12.12-203.bazzite.fc41.x86_64

Sadly, my attempt still failed. I deleted the cache and cache.write files but I still fail to see textures. I'm guessing that I need to have the PYROVEIL_CONFIG value stored somewhere, but where am I supposed to place it, exactly? I'm guessing the launch options?

PYROVEIL=1 PYROVEIL_CONFIG=/path/to/pyroveil/hacks/ffvii-rebirth-nvidia/pyroveil.json %command% should work. Replace the exact path as needed. Remember to delete vkd3d-proton.cache between every failed attempt.

Oh, pfft. I didn't actually replace the path appropriately. Derp.

That said, I did change the path accordingly, still no dice. Something I did notice is that I got no shader rebuild prompt by Steam OR in-game (which I did the first time I tried), so I'm guessing there's something still residual holding onto it?

Feeling a bit dumb at the moment, but I'm getting a kickback of no such file or directory when I attempt such. Clearly I'm doing something wrong there.

Many thanks @HansKristian-Work, I can confirm it is working on my side, just followed the README instructions.

OS: Arch Linux
GPU: Nvidia RTX 3080
Video driver version: 570.86.16-2
Kernel version: 6.13.2-zen1-1-zen

Ah, yeah, I was missing that.

Log grep yields:

pyroveil: Found config in /home/xxxxxxx/.steam/steam/steamapps/common/FINAL FANTASY VII REBIRTH/pyroveil.json!
pyroveil: JSON parse failed: 3
pyroveil: Found config in /home/xxxxxxx/.steam/steam/steamapps/common/FINAL FANTASY VII REBIRTH/pyroveil.json!
pyroveil: JSON parse failed: 3
pyroveil: Found config in /home/xxxxxxx/.steam/steam/steamapps/common/FINAL FANTASY VII REBIRTH/pyroveil.json!
pyroveil: JSON parse failed: 3
pyroveil: Found config in /home/xxxxxxx/.steam/steam/steamapps/common/FINAL FANTASY VII REBIRTH/pyroveil.json!
pyroveil: JSON parse failed: 3
pyroveil: Found config in /home/xxxxxxx/.steam/steam/steamapps/common/FINAL FANTASY VII REBIRTH/pyroveil.json!
pyroveil: JSON parse failed: 3
pyroveil: Found config in /home/xxxxxxx/.steam/steam/steamapps/common/FINAL FANTASY VII REBIRTH/pyroveil.json!
pyroveil: JSON parse failed: 3
pyroveil: Found config in /home/xxxxxxx/.steam/steam/steamapps/common/FINAL FANTASY VII REBIRTH/pyroveil.json!
pyroveil: JSON parse failed: 3
pyroveil: Found config in /home/xxxxxxx/.steam/steam/steamapps/common/FINAL FANTASY VII REBIRTH/pyroveil.json!
pyroveil: JSON parse failed: 3
pyroveil: Found config in /home/xxxxxxx/.steam/steam/steamapps/common/FINAL FANTASY VII REBIRTH/pyroveil.json!
pyroveil: JSON parse failed: 3
pyroveil: Found config in /home/xxxxxxx/.steam/steam/steamapps/common/FINAL FANTASY VII REBIRTH/pyroveil.json!
pyroveil: JSON parse failed: 3
pyroveil: Found config in /home/xxxxxxx/.steam/steam/steamapps/common/FINAL FANTASY VII REBIRTH/pyroveil.json!
pyroveil: JSON parse failed: 3

It works! RTX 4070 Super 550.144.03 6.8.0-52-generic ubuntu 24.04. This is what you will do if you are using flatpak steam, you have to install it in steam directory:

cmake . -Bbuild -G Ninja -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=$HOME/.var/app/com.valvesoftware.Steam/.local

Took me some time to make it work cause i was dumb and installed Pyroveil to a different folder but it worked for me too.

OS: Arch Linux
GPU: Nvidia RTX 3070
Video driver version: 570.86.16-2
Kernel version: 6.13.2-2-cachyos

Can confirm this fix works for loading textures, however I'm softlocked after the first cutscene and can't move Zack around, which is completely unrelated. Dunno what's up with that but if anyone knows a fix please let me know. Great work @HansKristian-Work !

Edit: Switching to Proton Experimental did the trick. Cheers!

Sorry all! I am also having some issues as well and went through all the comments and am a bit confused. Are we cloning and making pyroveil inside of our rebirth directory where the .exe is located? I cloned and made it in a separate folder and copied the pyroveil.json over and it's not working. Thank you for any help on this!

PYROVEIL=1 PYROVEIL_CONFIG=/path/to/pyroveil/hacks/ffvii-rebirth-nvidia/pyroveil.json %command% should work. Replace the exact path as needed. Remember to delete vkd3d-proton.cache between every failed attempt.

Really appreciate your work, thank you! Can confirm the game is playable on my RTX 3060Ti.

Now to set about getting it to run well....

It works! Thank you so much. :)

My specs:

Fedora 41
Kernel 6.12.11-200
CPU: Ryzen 9 7950X
GPU: Nvidia GeForce GTX 3060 Ti
Driver version: 570.86.16
Proton Experimental [bleeding-edge]

@HansKristian-Work Amazing, it works exactly as advertised! Thank you for continuing to put your time into this one, I for one really appreciate it.

OS: Bazzite F41
GPU: RTX 3080 Ti
Kernel: 6.12.12-203
Driver Version: 570.86.16
Proton Experimental

steam-2909400.log

OS: Ubuntu 24.04
GPU: RTX 4070 Super
Driver: 550
Proton: Experimental

Encountering graphical glitch after skipping scenes:

I can confirm that the workaround works.
I've fired them somewhere orderly, created a Build Folder for it under ./home . Then copied the .json from the hacks folder to beside the .exe of the game. Also added the Launch Options PYROVEIL=1 %command%

Tried it on these two systems and it worked, I'm using GE-Proton 9-25 on both.

First System:

• Zbook Fury 16 G10
• Fedora 41
• RTX2000 Ada Laptop GPU
• Driver: 570.86.16-5

Second System:

• Custom PC
• Fedora 41
• RTX4060ti 16GB
• Driver: 570.86.16-5

Edit: If you run into stutter while moving the camera: switching from VRR to Vsync fixed it for me. The Framerate is very stable.

I think I discovered my problem. The json I grabbed was not the same file as the one I had locally. Copying the local json seemed to do the trick.

Awesome work, @HansKristian-Work !

So now I can move around in the game but it runs very poorly even on lowest settings, maybe 15-20 FPS even for the cinematics. I really appreciate @HansKristian-Work for stepping in and helping out but I don't really want to play if it's going to be like moving through sludge.

I set everything to Low, running at 1920x1080 on this hardware:

CPU: AMD Ryzen 9 5900X (24) @ 3.700GH
GPU: NVIDIA GeForce RTX 3060 Ti Lite
RAM: 64GB

Given that the low spec for the game is an RTX 2060 I'd hoped it would be playable on Low via Proton but I'm getting nowhere near the FPS that Windows users are reporting. Not sure what to do though, maybe set up GPU passthrough to a Windows VM? Or wait for a driver update?

For comparison, Returnal runs great on this system on High settings. I really don't think it's that my hardware is lacking.

Intel Arc B580

Game does not launch. Error message comes up, "DX12 is not supported on your system. Try running without the -dx12 or -d212 command line argument."

System Information

GPU: Intel Arc B580 
Video driver version: Mesa 25.1.0-devel (git-6652eb0ec3)
Kernel version: 6.13.2-zen1-1-zen 
Link to full system information report: https://gist.github.com/GalacticDeep/0c8949dc48d0e224ec52e5535f1209c3
Proton version: Experimental

@HansKristian-Work Thank you so much!!! Working great so far!!!

OS: Mint 22 Cinnamon
CPU: Ryzen 7 7435HS
GPU: RTX 4070 mobile max-q
Kernel: 6.8.0-53-generic
Driver Version: 570.86.16
Proton Experimental

Forgot to say thanks for the pyroveil fix! been playing all day!! one thing i suggest if anyone is having crashes still with it, limit your monitor to 60hz!!

OS:Debian 12
CPU: AMD Ryzen 7 2700x
GPU:RTX 3060ti
Kernel: 6.1.0-30-amd64
NVIDIA Driver Version: 570.86.16
Proton Experimental

I just want to further document my stuttering experience with this game.

• OS: CachyOS
• CPU: Intel i9-13900k
• GPU: RX 7900 XTX
• Kernel: Linux 6.13.2-2-cachyos
• DE: KDE Plasma 6.3.0
• mesa: mesa-tkg-git 25.1.0_devel.201804.a9b6a54a8cc-1
• Proton versions tested:
  • Steam's default (for this game)
  • experimental
  • GE
  • proton-cachyos

As suggested by @HansKristian-Work It could be a VRR issue, the game and monitor's refresh rate don't seem that locked in.
Usually when games have VRR stutters the monitors refresh briefly goes to max (240 hz in this case) which does not happen here.

The monitors refresh rate is in the top right.

https://github.com/user-attachments/assets/0f03d9bb-1394-492a-82c7-04fd58553a0a

The issue is the same running without any launch options and with my usual launch options:
LD_PRELOAD="" game-performance gamescope -w 3840 -h 2160 -r 240 -f --hdr-enabled --adaptive-sync -- %command%

It's also present at all in game quality settings but does seem to get a little better on Low.

3080Ti. Thank you very much.

@arnxxau Using 7800xt with mesa-git, the mr do fix stuttering on my system. Moving camera around no longer cause stuttering when setting background model to ultra or enable DRS.

With the updated caching system, there should be a new directory name radv_builtin_shaders in the games shader cache directory <steam library>/shadercache/2909400/radv_builtin_shaders

I do have the new folder in shadercache. I also cleaned the prefix and the shadercache folder before testing.

@AshtenThePlatypus @arnxxau are using custom proton like proton-ge or dlss injectors like dlss enabler, optiscale ecc?

Yes. I'm using protonge and optiscaler, but I also tried proton experimental and completely disabling optiscaler, and that didn’t change anything.

Replying to [#8408](https://github.com/ValveSoftware/Proton/issues/8408#issuecomment-2660607517)

I tried disabling VRR everywhere, but I still get the same stutters.

If VRR was the issue, then why does turning it off in-game, in the desktop manager, and in the display settings not fix it?

Also reporting success here with the Pyroveil workaround on Bazzite 41.

570.86.16 drivers on a 4070 Super with kernel 6.12.12-203.bazzite.fc41.x86_64

I am still new to linux (using Bazzite), can I ask for your help to get this working?

I followed the instructions on the Pyroveil Git, but I get met with this:
bazzite@bazzite:~/pyroveil$ cmake . -Bbuild -G Ninja -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=$HOME/.local CMake Error: CMake was unable to find a build program corresponding to "Ninja". CMAKE_MAKE_PROGRAM is not set. You probably need to select a different build tool. CMake Error: CMAKE_CXX_COMPILER not set, after EnableLanguage CMake Error: CMAKE_C_COMPILER not set, after EnableLanguage -- Configuring incomplete, errors occurred!

I tried installing Ninja but I don't think I am doing it right... I really don't know what I am doing... I just wanna play FFVIIRebirth

Anyone got any advice? I can't get the game to start. I installed and setup pyroveil and it appears to find the config file (see logs) so I'm not sure what the issue is!

steam-2909400.log

Linux Mint 22 Cinnamon
6.11.0-17-generic
RTX 3050
570.86.16
Proton experimental

I'm definitely noticing a lot of stuttering in cutscenes while using pyroveil on Nvidia, although gameplay seems fairly smooth so far. This occurs even on Low settings. I'm running the game off an M.2 drive as well.

I also noticed some flickering behaviour with some of the lighting, along with light sources popping in and out. Has anyone else experienced this?

Just wondering if a anyone has advice or workarounds.

Fedora 41
Kernel 6.12.11-200
CPU: Ryzen 9 7950X
GPU: Nvidia GeForce GTX 3060 Ti
Driver version: 570.86.16
Proton Experimental [bleeding-edge]

I tried disabling VRR everywhere, but I still get the same stutters.

If VRR was the issue, then why does turning it off in-game, in the desktop manager, and in the display settings not fix it?

Set the monitor refresh rate to your frame rate cap and use V-sync. So set a 60 fps limit within the game's setting, set the monitor refresh rate to 60 Hz. Do not use an external frame limiter.

If your in-game fps drops below the frame rate cap, then the frame time becomes jittery again. Probably only set 120 Hz refresh rate on the monitor if you can guarantee 120 fps minimum.

I have a 240 Hz monitor, but only setting the monitor refresh rate to 60 Hz mostly fixes the frame time graph with a 60 fps in-game cap. Changing the monitor refresh rate to 120 Hz or 240 Hz refresh rate is still jittery, even though conventional Internet wisdom says multiples of 60 Hz refresh rates should be okay. This game has a quirky engine.

This screenshot is when I spin the camera around in Kalm.

CPU: AMD Ryzen 7 7840U
GPU: Nvidia GeForce GTX 3060 Ti
nvidia 570.86.16-5 (Arch)
Proton Experimental [bleeding-edge]

pyroveil lets me play the game, but it only runs at about 22fps @ 1080p. Not sure if that's an expected result of the workaround or if there's something else going on.

If I run with the same graphics settings on a Windows VM with GPU passthrough I can get 60fps fairly consistently.

Some installation instructions for anyone running on Bazzite (or similar). You will need to run this in a distrobox container, preferably a fedora one

1. Create a Fedora distrobox if you don't already have one: distrobox create fedora (You can also make one using BoxBuddy, which should already be installed on Bazzite. Make sure you select the registry.fedoraproject.org/fedora-toolbox image)
2. Enter the distrobox using distrobox enter fedora
3. Install the required dependencies: sudo dnf install make automake gcc gcc-c++ kernel-devel ninja-build
4. Clone the repository: git clone https://github.com/HansKristian-Work/pyroveil.git
5. Enter the folder using cd pyroveil
6. Run git submodule update --init to download the extra submodules
7. Run CMake cmake . -Bbuild -G Ninja -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=$HOME/.local
8. Run ninja to install the library: ninja -C build install
9. Copy the pyrofveil.json file from hacks/ffvii-rebirth-nvidia to the installation directory (Steam > Final Fantasy VII REBIRTH > Right click the game > Browse Local Files)
10. Delete all the the cache.write files from the End/Binaries/Win64/ where FF7Rebirth is installed
11. Edit the launch options of FF7Rebirth in Steam to the following: PYROVEIL=1 %command%
12. Launch the game

@RoboRev Hopefully this can help

I think most people who use NVIDIA cards and have problems with getting it fixed might miss the step of deleting the vkd3d proton cache.

Don't make a misatake with this command below.

rm -rf $HOME/steaminstallfolder/steamapps/common/FINAL FANTASY VII REBIRTH/End/Binaries/Win64/vkd3d-proton.cache

If you're unsure, change directory in the folder first before deleting the cache file.

Then start FFVII and you're good to go.

Replying to https://github.com/ValveSoftware/Proton/issues/8408#issuecomment-2661058683

Make sure you download and install using this: sudo rpm-ostree install ninja-build

I'd add that it works with ultrawide fix as well. So for those of you playing on like 7680x2160 resolution for example, this combination works well.

Fix for shaders + ultrawide fix.

CPU: AMD Ryzen 7 7840U GPU: Nvidia GeForce GTX 3060 Ti nvidia 570.86.16-5 (Arch) Proton Experimental [bleeding-edge]

pyroveil lets me play the game, but it only runs at about 22fps @ 1080p. Not sure if that's an expected result of the workaround or if there's something else going on.

If I run with the same graphics settings on a Windows VM with GPU passthrough I can get 60fps fairly consistently.

Same here with GTX 1650.

Well @HansKristian-Work's solution works for getting the textures in loading, frequently a lot of the characters or environment geometry will explode in a bunch of tris, haha. Anyone know a workaround?

OS: Linux Mint 21.3 Cinnamon
GPU: RTX 3080 Mobile

3. Install the required dependencies: sudo dnf install make automake gcc gcc-c++ kernel-devel ninja

@bleuthoot-sven First thank you so much for the help here.

I am getting an error at step 3 saying that it is unable to find a match : ninja

I think this is the same issue I was having before - Ninja not found

@bleuthoot-sven Okay so I THINK I was able to install ninja properly by having it install ninja-build instead of ninja in the command line. (from what I understand they are the same thing...)

But now I am having an issue where cloning the git doesn't clone everything properly. when I try to run cmake, I get a bunch of errors all saying the same thing:

"PATH TO FOLDER" does not contain a CMakeLists.txt file.

When I look in the Pyroveil directory, this is true. Looking in the Git repository, there seems to be an insane amount of files not being copied over, including said .txt files. Even when I manually download the zip file from github, those files are still missing. Really not sure what is going on here

Replying to https://github.com/ValveSoftware/Proton/issues/8408#issuecomment-2663863819

@RoboRev

Whoops, I forgot to add a few steps. Added them.

FYI: all of the steps, except the ones installing the required packages/setting up the distrobox container/deleting the cache, are from HansKristian-Work github page.

Replying to https://github.com/ValveSoftware/Proton/issues/8408#issuecomment-2663880244

AMAZING!! So before I read this update, I manually downloaded and extracted each subfolder into their respective proper folders lol. Followed everything else and BAM! WE ARE UP AND RUNNING!! THANK YOU SO MUCH FOR THE HELP, YOU ARE A HERO

Thanks for the fix but the game randomly crash during fights with the following error:

NVRM: Xid (PCI:0000:01:0 0): 31, pid=240017, name=ff7rebirth_.exe, Ch 00000036, intr 00000000. MMU Fault: ENGINE GRAP HICS GPC4 GPCCLIENT_GCC faulted @ 0xfffffdf0_0033f000. Fault is of type FAULT_PDE ACCESS_TYP E_VIRT_READ

Is it somehow related to the workaround mentioned above?

CPU: AMD Ryzen 7 7840U GPU: Nvidia GeForce GTX 3060 Ti nvidia 570.86.16-5 (Arch) Proton Experimental [bleeding-edge]

pyroveil lets me play the game, but it only runs at about 22fps @ 1080p. Not sure if that's an expected result of the workaround or if there's something else going on.

If I run with the same graphics settings on a Windows VM with GPU passthrough I can get 60fps fairly consistently.

I found the solution for this: for whatever reason, if I set my Wayland plasma desktop resolution to 1440p and play at that resolution then the game runs at ~60fps, but if the desktop resolution is 4k and I set the in-game resolution to 1080p or 1440p it runs 20-30fps. I don't really understand why that would be the case, maybe something to do with using an eGPU with limited bandwidth.

@Paddlefruit I'm experiencing the same thing after playing for a while. I have to quit to tittle screen and reload the game in order to solve all those black polygons.

RTX 3050 Mobile
ubuntu 24.04

Doesn't work for me. Seems I don´t get it. I tried everything but still no textures. Seems I build it wrong, but I really don´t know. I wish there was a video tutorial. Messing with it for 4 days now.

Games is Epic Games Version on Heroic Games Launcher.

System

Garuda Linux (Arch) on Kernel 6.12.1-1-cachyos-bore
AMD Ryzen 5 5600X
Nvdia RTX 4060 Ti
32 GB Ram

Doesn't work for me. Seems I don´t get it. I tried everything but still no textures. Seems I build it wrong, but I really don´t know. I wish there was a video tutorial. Messing with it for 4 days now.

System

Garuda Linux (Arch) on Kernel 6.12.1-1-cachyos-bore AMD Ryzen 5 5600X Nvdia RTX 4060 Ti 32 GB Ram

@CeeJay654 could you please check proton logs to see if PYROVEIL was loaded correctly?

Not much time right now. A bit busy.

Where is the log in

/.steam/steam/logs/

Replying to https://github.com/ValveSoftware/Proton/issues/8408#issuecomment-2610532289

Does it work with a GTX? Is this only for Linux or does it also work for Windows?

@abelbmx no it doesn't work, while the override maybe tricks the game into starting, it crashes later while compiling shaders. There is no workaround if it requires mesh shaders.

Thanks for the fix but the game randomly crash during fights with the following error:

NVRM: Xid (PCI:0000:01:0 0): 31, pid=240017, name=ff7rebirth_.exe, Ch 00000036, intr 00000000. MMU Fault: ENGINE GRAP HICS GPC4 GPCCLIENT_GCC faulted @ 0xfffffdf0_0033f000. Fault is of type FAULT_PDE ACCESS_TYP E_VIRT_READ

Is it somehow related to the workaround mentioned above?

I too am also experiencing this for the 1st time in Chapter 3. I have to save before each fight

Linux

nvidia-bug-report.log.gz

6.13.3-arch1-1 #1 SMP PREEMPT_DYNAMIC Mon, 17 Feb 2025 17:42:11 +0000 x86_64 GNU/Linux

Anyone know how to fix this? Insane stuttering ONLY when panning camera, using the workaround to make textures work with NV gpu. Fedora 41, proton bleeding edge(which ended up stuttering the least). Shaders are already compiled.
https://github.com/user-attachments/assets/98ebf43b-3d5c-46c5-b327-4592c82140d8

https://www.youtube.com/watch?v=U8xTyT5eY-0 just watched this video on a 4070Ti and it has nearly zero stutters. What is wrong with my config??

Anyone know how to fix this? Insane stuttering ONLY when panning camera, using the workaround to make textures work with NV gpu. Fedora 41, proton bleeding edge(which ended up stuttering the least). Shaders are already compiled. https://github.com/user-attachments/assets/98ebf43b-3d5c-46c5-b327-4592c82140d8

https://www.youtube.com/watch?v=U8xTyT5eY-0 just watched this video on a 4070Ti and it has nearly zero stutters. What is wrong with my config??

Same issue here, RTX 4060 on Fedora 41, 565.77 driver. Tried Proton Bleeding Edge and GE 9-25.

@Dragonslayer12302 , @alexiscirmi While it might not help everybody, what helped me against the camera panning stuttering on an 8 Gb VRAM GPU ( GeForce RTX 3060 Ti ) was to lower the Background Model Detail (or what is it called) as well as the Texture Resolution all the way down to Low (basically as low as it can go). This is, as far as I have noticed, likely because the game constantly tries to render the objects in and out of view as you rotate the camera, and the more detailed the objects are, the more gittery it becomes. This game is also an overwhelming VRAM hog: Even setting the Textures to Medium on such a seemingly capable GPU causes it to run out of memory and begin stuttering in a lot of locations in mere 10-20 minutes. I've measured VRAM usage in Mangohud, but the symptom is unmistakable, as soon as it goes over 7.9 Gb, stuttering ensues.

Pyroveil mostly works, but after Nibelheim I get a similar problem as @Paddlefruit. After a few minutes of playing the tris on the characters and terrain explode and flash rapidly, covering the screen. For me it doesn't go away until I delete the vkd3d proton cache again and restart the game. The issue always returns after playing for a few minutes. Any idea what might be happening here or if there is a workaround?

Specs
OS: Linux Mint 22
KERNEL: 6.8.0-53-generic
CPU: Intel Core i7-14700F
GPU: NVIDIA GeForce RTX 4070
GPU DRIVER: NVIDIA 550.120
RAM: 32 GB

Replying to https://github.com/ValveSoftware/Proton/issues/8408#issuecomment-2670915830

I guess this is driver related. I've seen an RX 6600 not having this issue on Linux. Yes, less fps but not this stuttering. Let's hope it'll be fixed on the next Nvidia driver version.

Replying to https://github.com/ValveSoftware/Proton/issues/8408#issuecomment-2670915830

I have already tried setting everything to the lowest settings even at 720P with 33% DLSS, it does not help.

Regardless, I know the 24GB VRAM on my card is not an issue.

For those who are seeing the exploding tris, I updated my graphics driver from 550 to 570 and the issue never returned. I am not sure if this is the fix or if the fix is a side effect from forcing a recompilation of all of the game's shaders.

For those who are seeing the exploding tris, I updated my graphics driver from 550 to 570 and the issue never returned. I am not sure if this is the fix or if the fix is a side effect from forcing a recompilation of all of the game's shaders.

The issue with 570 is that it causes alt-tab problems on majority of games. 550 is the most stable

@jobs-git afaik that is caused by VRR, you can just deactivate it for now then you wont get the alt-tab blackscreen

@jobs-git afaik that is caused by VRR, you can just deactivate it for now then you wont get the alt-tab blackscreen

That is weird because some games also need VRR to have stable frametimes (i.g. rebirth)

I just got the exploding triangles issue using pyroveil yesterday as well. For me it started in the Mythril Mines, weird how it seems to pop up at different spots for everybody. Deleting the vkd3d-proton.cache does not seem to help either.
The flickering seems to not happen in Proton 9.0-4, however this version freezes constantly for me for whatever reason.

CPU: Intel I7-7700K
GPU: Nvidia GeForce GTX 3080 Ti
Nvidia 570.86.16-8
Arch Linux
Proton Experimental

I would like to share my experience about pyroveil.

First of all, thanks a lot to @HansKristian-Work for this amazing work!!

Steam was installed on my laptop by a snap package and I suppose the mod isn't working in this case. I had to remove steam and reinstall the .deb package downloaded from steam website to see that software directories are different with this way to install it. After this, following the readme steps was making the job and the solution worked very well.

So for anyone who have issues with pyroveil, maybe this solution could help.

And now, let's play!! 😁

Ubuntu 24.04 - Wayland
Nvidia 550 drivers

@pavethem

weird how it seems to pop up at different spots for everybody

yes, it's weird indeed... it was very casual for me on chapter 2 and 3 but after mythril mine it comes now very often. exiting to title screen and reloading the game makes it go away for me but it's very annoying since it's happening every 2 minutes.

RTX 3050 Mobile
Nvidia 550 drivers
Ubuntu 24.04 - wayland

Reporting success with NVIDIA + pyroveil.

System

• CPU: AMD Ryzen 9 5900X (24) @ 4.951GHz
• GPU: NVIDIA GeForce RTX 3060 Lite Hash Rate
• Drivers: 560.35.03 | CUDA Version: 12.6
• Memory: 32G DDR4
• OS: Ubuntu 24.10 x86_64
• Kernel: 6.11.0-18-generic
• DE: GNOME 47.0 + Wayland
• WM: Mutter

Configuration of pyroveil

• clone & build
• Drop pyroveil.json somewhere locally
• Configure Steam to run the game with:
  -- PYROVEIL=1 PYROVEIL_CONFIG="/chosen/path/pyroveil.json" %command%
  -- Proton experimental

Success

Game works, no tris explosion, no crashes.
Performance: 45-60fps @ 4k with some annoying stutters

Replying to https://github.com/ValveSoftware/Proton/issues/8408#issuecomment-2676413599

I switched to the deb install from the snap package. This fixed it.
@HansKristian-Work Pyroveil likely needs a different install location with snap, similar to how flatpak's install dir is different. I tried dropping the library to several other lib folders within the snap directory to no avail, I'm not too well versed how steam differs when using different installs.

RX 7900 XT
5800X3D

It's a generally great experience based on latest VKD3D and RADV git. There is a crash on the exact same spot every time on chapter 12, in which driving the boat through the northern part of open sea crashes the game. More specifically, the game flashes white, freezes and crashes the video driver.
Not a VRAM leak, although it seems like a shader related memory violation.

It is also reproducible on stable Mesa, older Proton 9.0.5 and VKD3D-Proton with Rebirth's shader quirks (before this commit).

Attaching my whole FINAL FANTASY VII REBIRTH folder that goes in ../My Documents/My Games/. It includes my save file for testing. You need to drive the boat around the gray area just north of this save's shore.

Oddly enough, driving through the whole rest of the map it works just fine, just like playing the rest of the game overall (~110 hours in)

FINAL FANTASY VII REBIRTH.zip

Thank you @kisak-valve.

Proton log attached.
steam-2909400.log

gist: https://gist.github.com/hivehivemind/7fe29e9fadd0521ac3a27c36b6a732e2

Replying to https://github.com/ValveSoftware/Proton/issues/8408#issuecomment-2680446296

There is a crash on the exact same spot every time on chapter 12, in which driving the boat through the northern part of open sea crashes the game. More specifically, the game flashes white, freezes and crashes the video driver.

Do you have any information on exactly where that spot is? A screenshot showing where on the map it is should be enough to repro. The open sea isn't exactly small, and I didn't run into any issues when I played through that section.

You need to drive the boat around the gray area just north of this save's shore.

I guess this might be enough to repro.

Do you have any information on exactly where that spot is? A screenshot showing where on the map it is should be enough to repro. The open sea isn't exactly small, and I didn't run into any issues when I played through that section.

It is right around this area, more specifically:

Just an update on the freezing issue: when not using gamescope the problem seems to occur less frequently.

@hivehivemind We found another game sync bug. A workaround was pushed to vkd3d-proton master. https://github.com/HansKristian-Work/vkd3d-proton/pull/2362 Hopefully that fixes the hang.

The new Vulkan beta driver from NVIDIA 570.123.01 (https://developer.nvidia.com/vulkan-driver) was reported by them to resolve the bug that pyroveil hacked around. I ran around in Nibelheim to test and it seems to work as expected now.

The new Vulkan beta driver from NVIDIA 570.123.01 (https://developer.nvidia.com/vulkan-driver) was reported by them to resolve the bug that pyroveil hacked around. I ran around in Nibelheim to test and it seems to work as expected now.

tnx, now the game freezes and are stuck on Ubuntu 24.04

The new Vulkan beta driver from NVIDIA 570.123.01 (https://developer.nvidia.com/vulkan-driver) was reported by them to resolve the bug that pyroveil hacked around. I ran around in Nibelheim to test and it seems to work as expected now.

I just installed Nvidia driver version 570.124.04 on Arch with the 6.12.17 lqx kernel and without pyroveil, it still does not render textures. Am I misunderstanding that this should include the new vulkan-driver?

Can confirm arch nvidia driver 570.124.04 on 6.13.3-1-cachyos still does not render mesh textures, even after removing the vkd3d-proton.cache(and .cache.write) files and forcing shader rebuild.

Driver 570.123.01 is actually a newer (after 570.124.04) release that does not include anything in 570.124.04 but specific Vulkan fixes. see https://github.com/NVIDIA/open-gpu-kernel-modules/releases/tag/570.123.01

I've tested with both. The 570.123.01 Vulkan drivers do indeed fix the issue but they are not in the Arch repos for whatever reason. The regular 570.124.04 drivers (i.e. the ones in the Arch repos) do not fix the issue.

I can't get the game to launch on 570.123.01. As soon as I start it I get a wine C++ assertion failed error. The file is loader_thunks.c. There is no problem with other games. I also tried clearing the vkd3d cache files but still nothing. When I go back to 570.124.04 + pyroveil there is no problem.
Any idea how to fix this ?

I also tried 570.123.01 on Arch with the same results as tuxrinku. I tried a few different kernels and proton versions, but the error message was the same with every combination. I also tried "VKD3D_DISABLE_EXTENSIONS=VK_NV_low_latency2" as suggested for another game with the same error, but it did not help.

Driver 570.123.01 is actually a newer (after 570.124.04) release that does not include anything in 570.124.04 but specific Vulkan fixes. see https://github.com/NVIDIA/open-gpu-kernel-modules/releases/tag/570.123.01

I've uploaded packages of the nvidia 570.123.01 beta driver for ArchLinux, Manjaro, CachyOS on a secondary sub-domain of my website, if some are interested, it should save you some time. 👍

I also provided the modified pkgbuild used to create the packages which were originally on AUR for nvidia-beta, nvidia-beta-dkms, and nvidia-utils-beta

http://redirect.pepinature.net/nvidia-ff7rebirth/

Original .run from nvidia is downloadable here : https://developer.nvidia.com/downloads/vulkan-beta-57012301-linux

I've uploaded packages of the nvidia 570.123.01 beta driver for ArchLinux, Manjaro, CachyOS on a secondary sub-domain of my website, if some are interested, it should save you some time. 👍

Thank you for your work!
Could you please provide lib32-nvidia-utils package too?
For me, I'm receiving removing nvidia-utils breaks dependency 'nvidia-utils=570.124.04' required by lib32-nvidia-utils error, on Arch Linux.

I can't get the game to launch on 570.123.01. As soon as I start it I get a wine C++ assertion failed error. The file is loader_thunks.c. There is no problem with other games. I also tried clearing the vkd3d cache files but still nothing. When I go back to 570.124.04 + pyroveil there is no problem. Any idea how to fix this ?

Same with the 570.123.01 driver, tested now. :-/

On Archlinux, you can install the Vulkan driver using this PKGBUILD.
https://github.com/Frogging-Family/nvidia-all
It will conflict with the egl-x11 package. So you'll need to install the packages by running pacman with --overwrite *egl* and uninstall the egl-x11 package to deal with that.

@hivehivemind We found another game sync bug. A workaround was pushed to vkd3d-proton master. HansKristian-Work/vkd3d-proton#2362 Hopefully that fixes the hang.

@HansKristian-Work Updating back, the latest Rebirth patch (Version 1.003) summed with this commit fixed the hanging in that area. Several minutes tested.

Thank you for such a quick action on it!

The game work with the PYROVEIL method but there is a lot of stutter into cut scenes and after the cut scene the game does stutter and the framerate collapse I don't know why ...

I have to go back to main menu and to load a save to fix the stutter + framerate issue everytime.

( The game work properly into 1080p under Windows )

My config :
CPU : Ryzen 7700
GPU : RTX 3060ti ( driver : 570.86.16 )
RAM : 32 Go DDR5 6000Mhz
OS : Ubuntu 24.10
Desktop : Wayland

Replying to https://github.com/ValveSoftware/Proton/issues/8408#issuecomment-2708399676

I had a similar issue. I fixed it by:

• Disabling Variable Refresh Rate for all my monitors in my desktop settings
• Switching the sync mode from VRR to V-Sync in game
• Matching the monitor refresh rate to the locked FPS in game (59.95 Hz and 60 FPS for example)

Replying to https://github.com/ValveSoftware/Proton/issues/8408#issuecomment-2708424698

I do not have VRR available on my screens, refresh rate is set at 60 Hz on my both screens and in the game the V-Sync was already on.

edit : following your hint around refresh rate I turned off my second screen and the game run way better ! ( still doesn't match Windows performance but playable at least in medium )

I do have 2 screens with not exactly the same refresh rate 60hz and 59.95hz and with different resolution 1920x1080 and 1920x1200 ( 16:10 ) for the other.

I tried the solution of going to vulkan beta driver using frogging-family but I now get an Assertion failed! error from loader_thunks.c like [tuxrinku] earlier

Expression: "!status && vkQueuePresentKHR"

Not sure if there is a way to override this.

still unplayable linux i have geforce rtx 4060
FINAL FANTASY VII REBIRTH - 2025-03-08 3-48-56 PM.mp4
https://drive.google.com/file/d/1rwe_jRqGmOjasmm-M9JmCu0GDQPdADxk/view?usp=drive_web

On Sat, Mar 8, 2025 at 2:28 PM korodarn @.***> wrote:

I tried the solution of going to vulkan beta driver using frogging-family
but I now get an Assertion failed! error from loader_thunks.c like
[tuxrinku] earlier

Expression: "!status && vkQueuePresentKHR"

Not sure if there is a way to override this.

—
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/8408#issuecomment-2708457988,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BOZLYIWI7KAJTZ7COCGFF4D2TNAGDAVCNFSM6AAAAABVXRFUACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMBYGQ2TOOJYHA
.
You are receiving this because you commented.Message ID:
@.***>
[image: korodarn]korodarn left a comment (ValveSoftware/Proton#8408)
https://github.com/ValveSoftware/Proton/issues/8408#issuecomment-2708457988

I tried the solution of going to vulkan beta driver using frogging-family
but I now get an Assertion failed! error from loader_thunks.c like
[tuxrinku] earlier

Expression: "!status && vkQueuePresentKHR"

Not sure if there is a way to override this.

—
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/8408#issuecomment-2708457988,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BOZLYIWI7KAJTZ7COCGFF4D2TNAGDAVCNFSM6AAAAABVXRFUACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMBYGQ2TOOJYHA
.
You are receiving this because you commented.Message ID:
@.***>

I originally came across this issue a couple of days ago when I was running a 3060Ti and the game had no game textures which I eventually got working with the pyroveil fix. I've since swapped to the radeon 9070 thinking it would be better...

I had the flashbang issue yesterday before realizing I needed to swap the Proton Experimental to bleeding edge for the issues to be fixed. I went to bed thinking the game was all sorted... and then I got to Kalm; I've never seen a sky so white.

The game looks perfectly fine whenever the 'sun' isn't in play but the contrast is stark when it is. I've tried with and without HDR. In this case, the in-game brightness and HDR are set to 0 with my system brightness at 50~%.

OS: CachyOS (Fully up to date)
AMD Drivers: RADV(?) I've tried these and the AMDGPU ones
Proton: Experimental [bleeding-edge]
Launch options: gamescope -H 1440 -W 3440 -f -b --hdr-enabled -- %command%

Fairly new to Linux and especially the AMD GPU stack so this is a lot for me to get my head around but I thought I was in a good place. Can anyone confirm whether this is how the game is 'supposed' to look, whether I'm missing some config/setup, or whether there's something else that needs patching.

Edit:
Occurs to me that it might be useful to see my launch options

@WilsonMMM Does this occur outside of Kalm, such as on wide-open areas in the world map? Because I have noticed that my game is sometimes ridiculously bright in spots and ridiculously dark in others, if the camera angle is just wrong. It seems like it decides to base its exposure settings on random spots. There's a place in Under Junon that is pretty much 100% black all the time (behind the boats near the water).

@WilsonMMM Does this occur outside of Kalm, such as on wide-open areas in the world map? Because I have noticed that my game is sometimes ridiculously bright in spots and ridiculously dark in others, if the camera angle is just wrong. It seems like it decides to base its exposure settings on random spots. There's a place in Under Junon that is pretty much 100% black all the time (behind the boats near the water).

I'm still in Kalm. The graphics issues are extremely distracting so every time I try to play it I end up turning it off to search for fixes. Below are both from the entrance to the clocktower with the camera rotated slightly.

That doesn't look like a bug, that's just how the sun exposure effect looks in the game.

I'm pretty sure you're just describing the way the engine handles exposure. I'm pretty sure it's intentional (how the game is supposed to look) and you can see the effect done intentionally in some movies (e.g. windows being clipped while indoors and such). Final Fantasy VII Remake did this as well, here is a timestamped clip I just grabbed via youtube search https://youtu.be/NE0KGdUxzgg?t=489

I'm still in Kalm. The graphics issues are extremely distracting so every time I try to play it I end up turning it off to search for fixes.

Are we even sure that's Proton's issues and not Unreal Engine's?

I'm still in Kalm. The graphics issues are extremely distracting so every time I try to play it I end up turning it off to search for fixes.

Are we even sure that's Proton's issues and not Unreal Engine's?

Not at all, hahaha. It looks way over done but since I'd had a number of issues I honestly wasn't sure if it was another or simply how the game/engine was. @mbriar, @ekce, @PolisanTheEasyNick , Thanks for all confirming.

Hi,
I am affected by this bug. I have a GPU Nvidia 4090. After the opening scene, textures are missing, and I am unable to play. It looks like the screen shot.
This thread is huge, so I was not able to see if it exists a workaround.

Hi, I am affected by this bug. I have a GPU Nvidia 4090. After the opening scene, textures are missing, and I am unable to play. It looks like the screen shot. This thread is huge, so I was not able to see if it exists a workaround.

Nvidia is working a fix, but in the mean time you can use PYROVEIL to work around the bug.

The fix was on 570.123.01 driver. Workaround for black screen in games is switching to Wayland but it will cause mouse lag. Switching to VRR to Vsync repeatedly helps alleviate the issue. However, with this driver, I am now getting assertion failed.

This did not work:

VKD3D_CONFIG=dxr VKD3D_FEATURE_LEVEL=12_2 VKD3D_SHADER_MODEL=6_6 %command%

Nvidia Vulkan Dev 570.123.06 was releaed yesterday. No idea if it gets rid of the assertion failed message but give it a try.
* Fix crash on vkQueuePresent under some circumstances on Linux

In my case, with Pyroveil on a 4090, everything works mostly fine but I'm currently experiencing a missing skybox in the Junon region (Chapter 4). The sky was correctly rendering in Chapter 2. I've tried several proton versions but nothing seems to change.

Replying to https://github.com/ValveSoftware/Proton/issues/8408#issuecomment-2727040194

Did you try the last vulkan driver?

Replying to [#8408 (comment)](https://github.com/ValveSoftware/Proton/issues/8408#issuecomment-2727040194)

Did you try the last vulkan driver?

I just did, the issue persists. I've also tried manually deleting the VKD3D shader cache and verifying game files, to no avail.

Replying to [#8408 (comment)](https://github.com/ValveSoftware/Proton/issues/8408#issuecomment-2727040194)

Did you try the last vulkan driver?

I just did, the issue persists. I've also tried manually deleting the VKD3D shader cache and verifying game files, to no avail.

This I learned the hard way, I created a new game and those corruptions where gone.

Using save file that I initially uses old driver seems to cause the graphics corruption to stick even though I have changed to new driver already.

I managed to copy the game and my saves to my Windows machine and I have the same issue, it's a bug of the game. I think my previous messages should be marked as off topic!

I've encountered an unusual problem using Pyroveil that I haven't seen anyone else report. I haven an Nvidia 3060 and had the same missing environment bug as everyone else. I installed the Pyroveil workaround as explained above and the game worked great, up until the most recent update. Now I have lots of missing textures, showing up as a uniform gray or black, missing skyboxes, and weird lighting effects. I tried reinstalling Pyroveil and have cleared the caches numerous times. Has anyone else experienced this?

EndeavourOS, Nvidia 3060, driver versions 570.124.01 and 570.124.04

Replying to https://github.com/ValveSoftware/Proton/issues/8408#issuecomment-2713087034

I saw someone playing through Kalm on the PS5 and can confirm that the whiteout here is not intended. I'm now on the Junon side and have another incredible instance of it. In this case the sky is fine until you go up a wall into an event area.

System wise, fully updated CachyOS, AMD GPU, using the Proton Experimental (Bleeding Edge) as of 2025-03-11.

I tried the nvidia driver 570.86.15, but it is not solving the issue. I guess the one in Ubuntu repo still does not have the bug fix.
However, PYROVEIL solves the issue, at least to start the game!

PYROVEIL fixed FF7 Rebirth for me, at least so far! When first starting in Midgar, I was getting a transparent world except for the skybox, same as some others have shown.

I followed the build instructions for PYROVEIL, copied the FF7 Rebirth pyroveil.json to next to ff7rebirth.exe and added PYROVEIL=1 %command% to my launch options in steam.

I also had to switch my compatibility tool and force a specific one to get it to rebuild my shaders, i came back later on, after it rebuilt the shaders, and changed it back to the default and it still worked. so really it just needed to rebuild the shaders is all. There's probly a better way to do that, but it worked ¯\_(ツ)_/¯

Arch, RTX 3080, nvidia 570.124.04-1, linux 6.13.7.zen1-1, latest Proton Experimental

The Vulkan dev driver fixes the issue. It also fixes some other things so it's in fact better than the 570.124.06 driver.

@shelterx
Sorry for my ignorance, but how do I install the dev driver? From where is it sourced?

@Zarkorix Depends on your distribution.
I have packages for CachyOS here. Might work on Arch too, haven't tested.

UPDATE:
Arch/CachyOS users can use this AUR now, it's being maintained again.
https://aur.archlinux.org/pkgbase/nvidia-vulkan

@shelterx Ah - makes sense. Thank you. I'm on Fedora 41 at the moment. I assume at some point (relatively soon?) this will move out of beta and be released to everybody anyway.

@shelterx Sorry for my ignorance, but how do I install the dev driver? From where is it sourced?

Warning: If you cant do step 1 then please dont install the dev nvidia for your system's safety

1. Temporarily boot in run level 3. Just add 3 to the end of linux kernel command in grub.

2. Remove existing nvidia driver

sudo apt autoremove *nvidia*

1. Download the driver

Download this:

https://developer.nvidia.com/downloads/vulkan-beta-57012306-linux

1. Install the driver

sudo ./NVIDIA-Linux-x86_64-570.123.06.run

1. Reboot

I'll wait for the dev build to be production grade, meanwhile:

Install and Configure Pyroveil for FF7 Rebirth

#!/bin/bash

git clone https://github.com/HansKristian-Work/pyroveil.git
cd pyroveil
git submodule update --init
cmake . -Bbuild -G Ninja -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=$HOME/.local
ninja -C build install

config_url="https://raw.githubusercontent.com/HansKristian-Work/pyroveil/refs/heads/master/hacks/ffvii-rebirth-nvidia/pyroveil.json"
config_dest="$HOME/.steam/steam/steamapps/common/FINAL FANTASY VII REBIRTH/pyroveil.json"

curl -sLo "$config_dest" "$config_url"

if [ -f "$config_dest" ]; then
    echo "Pyroveil and configuration file installed successfully."
else
    echo "Failed to download configuration file."
fi

Don't forget to set steam launch argument, as pointed out before by @binaryberserker

PYROVEIL=1 %command%

Bonus Copy Saved data to get the bonus from Remake/Integrade

#!/bin/bash

src="$HOME/.steam/steam/steamapps/compatdata/1462040/pfx/drive_c/users/steamuser/Documents/My Games/FINAL FANTASY VII REMAKE"
dest="$HOME/.steam/steam/steamapps/compatdata/2909400/pfx/drive_c/users/steamuser/Documents/My Games/FINAL FANTASY VII REBIRTH"

if [ -d "$src" ]; then
  mkdir -p "$dest"
  cp -r "$src"/* "$dest"/
  echo "Save data copied successfully."
else
  echo "Source directory not found."
fi

My distribution (Fedora 41) just updated to 570.133.07 and FFVII Rebirth now plays without issue on Proton Experimental - no missing textures, and no need for Pyroveil.

Arch Linux; 570.123.06 from nvidia-vulkan AUR package. RTX 3060. Can confirm that beta nvidia-vulkan drivers works very good without need of Pyroveil. Also I'm using optiscaler with updated DLSS .dll and with enabled frame generation via optiscaler. Game at 80% of time works flawlessly, but sometimes there are major slutters, which got fixed by some time if you go to the menu (like pause, where you can choose items for characters and so on, not main menu of game) and sit there while slutters gone. I have a feeling that that issue is performing because of no free video memory available (I can decrease chance of getting that issue if I close all gpu-memory affecting applications like discord and so on).

Edit: updated driver to 570.133.07, all works as same. I can confirm that slutters was because of lack of GPU memory: while playing at medium texture setting, no slutters at all.
Noticed another issue: randomly game may freeze with end with need to kill process manually. Meanwhile at dmesg i can see message:

[ 6177.382226] NVRM: GPU at PCI:0000:26:00: GPU-165aaf64-98e5-4334-e0a2-f929f37136bf
[ 6177.382232] NVRM: Xid (PCI:0000:26:00): 31, pid=64338, name=ff7rebirth_.exe, Ch 000000d0, intr 00000000. MMU Fault: ENGINE GRAPHICS GPC1 GPCCLIENT_GCC faulted @ 0x26e0_00562000. Fault is of type FAULT_PDE ACCESS_TYPE_VIRT_READ

Still experiencing major stuttering and framerate drops on AMD when turning the camera, even w/ mesa-git. The radv_builtin_shaders directory does appear in my shadercache. Unsure of what to do, I'm still seeing drops of up to ~15fps when turning, even w/ VRR disabled and both my monitor and game capped at 60hz.

System Information:

• CPU: Ryzen 7 7700X
• GPU: Radeon RX 7700XT
• Kernel: Linux 6.12.19
• DE: KDE Plasma 6.3.3 (Wayland)
• Distro: NixOS 25.05 "Warbler"
• Using Proton Experimental [bleeding-edge]

Replying to https://github.com/ValveSoftware/Proton/issues/8408#issuecomment-2743712886

Same here!

Bazzite 41, game is rendering properly without Pyroveil now, but a new issue is happening: random freezes.

Driver 570.133.07 on a 4070 Super, on kernel 6.13.7-108.bazzite.fc41.x86_64

dmesg:

[ 1145.596300] NVRM: Xid (PCI:0000:01:00): 31, pid=10512, name=ff7rebirth_.exe, Ch 0000007c, intr 00000000. MMU Fault: ENGINE GRAPHICS GPC1 GPCCLIENT_GCC faulted @ 0xffffbbc0_0073b000. Fault is of type FAULT_PDE ACCESS_TYPE_VIRT_READ

Replying to https://github.com/ValveSoftware/Proton/issues/8408#issuecomment-2754226829

Wanted to back this up and express the same frustration. I'd hope something like a per game toggle for "steam deck optimized version" opt out selection. I also have a 7900xtx and was wondering why the game looks so rough now. Thanks for pointing this out

@xXJSONDeruloXx Are you also using Bazzite?
FF7Reirth is still 153.37GB on my machine.

@xXJSONDeruloXx Are you also using Bazzite? FF7Reirth is still 153.37GB on my machine.

Yes, Bazzite 41 but it is a -deck build, as I like the controller driven UI, is yours standard desktop?

@xXJSONDeruloXx Yes. (arch linux)

Seem like steam treat Bazzite as a steam deck and downloaded the steam deck version.
Or just because I downloaded the game before the update.

any idea what steam uses to determine this? maybe I could edit a line in a config file somewhere to work around

It seems bazzite deck images pass in launch arg -steamdeck with steam to accommodate BPM game mode flags.

I was able to directly launch Steam with /usr/bin/steam to bypass and got the current slightly different client, which then let me start the full sized download of 144 gb

Still, this is not ideal in practice and should be clearly available to opt out

@xXJSONDeruloXx Well this is opt-in (the -steamdeck arg, it's just opted-in by bazzite, not you).
May be you should open a issue to bazzite about setting steamdeck mode in the steam client?

I am using Ubuntu 22.04 and I get the full sized client (153gb according to my steam client). I believe this is a bazzite issue more than anything.

Replying to https://github.com/ValveSoftware/Proton/issues/8408#issuecomment-2771343073

This is offtopic to Proton.

In any case, this happens due to the "-steamdeck" launch argument, as some people stated, and it requires sudo to edit out of the gamescope session, which can be complicated with Bazzite's immutable image.

On CachyOS, which runs gamescope-session-plus, you can edit using sudo /usr/share/gamescope-session-plus/sessions.d/steam and around line 100 remove -steamdeck in the CLIENTCMD environment variable.
Everything normally works from there as far as I tested, still, and without the steam deck configuration bias for the games.

Replying to https://github.com/ValveSoftware/Proton/issues/8408#issuecomment-2772342165

Testing further, mangohud is not available without the "-steamdeck" argument in game mode as well as frame limit, VRR, and every other game-specific feature (including FSR/NIS image scaling), so it is not something Bazzite would like to take out but maybe workaround that eventually. VRR will be set automatically depending on your display, but HDR can be changed in the Steam "Display" menu.
I would recommend either sticking with the "-steamdeck" argument or taking it out only if these changes don't bother you.

Edit: the game is very stuttery here using the full texture package in a RX 7900 XT and 5800X3D. This is disappointing and wasn't an issue on previous versions using the same game full size.

Wow progress! I went ahead and was able to update to the full version of FFVII Rebirth by running steam without it using any arguments from desktop mode (/usr/bin/steam) as was mentioned above. I will be locking this version using some of the techniques to stop steam from updating a single game in the future.

I'm actually very surprised that we aren't hearing of people using something like ChimeraOS or Nobara reporting the same problem as I'm fairly certain they also use these flags to provide a console experience on general purpose hardware. It could also just be that there are more of us using Bazzite than either of these other systems.

I still feel that there should be an option within steam if there are 2 branches of a game released (Normal and Steamdeck) that allows the user to manually select a branch if their configuration is outside of Valves or the developers expectations.

The amount of people using linux is low, using a distro that automatically adds that flag on a desktop would be even lower (I use endevour and never had that), from those only a few would notice the texture size being wrong, and then being vocal enough to say something online. So yeah, it's to be expected not a lot of reports too fast.

As for the nvidia driver, nice to see 570.133.07 is installed already on Arch. Anyone checked the performance vs the pyroveil hack?

Anyone checked the performance vs the pyroveil hack?

Can't tell about performance in FPS, but when using Pyroveil + Optiscale's frame generation, I experienced full freezes. However, without Pyroveil and on 570.133.07 driver, there were no freezes with frame generation enabled.
Note that there are still freezes due to invalid memory accesses, especially in the Cosmo Canyon region for me, but I believe they are not related to frame generation but related to bugs in game on engine (why they occure muuuch much likely in specified region then?).
At this state I'm happy how playable this game is for me: >100 FPS in 3060 with framegen; sometimes full freezes, but it requires closing all GPU-related apps (Discord, Spotify, even Firefox) for freeing as much GPU memory as possible. If there is no much GPU memory available, then massive slutters occurs :c

I noted that if I then switched to game mode (where -steamdeck arg is passed in gamescope session config) it would automatically start trying to DL the 20 gigs from the SteamDeck Depot and overwrite the full version of the game.

Replying to https://github.com/ValveSoftware/Proton/issues/8408#issuecomment-2635377730

Same issue there

After Trial in Chapter 13, Cloud movement bugs out, like however to walk the game stucks you in that position permanently.

Using Steam Flatpak Proton Experimental Nvidia RTX 4070 570.123.06 Ubuntu 24.04

GUI freezing when capturin Red XIII photo using quest-camera during Writer's block odd-job in Gongga beach.

Ubuntu 24.04 + RTX 4070 S + 575.51.03 + Proton Experimental

Here is the SS when it happens, notice the GUI for the quest-camera did not load:

I was having terrible frametimes and fps drop on specific camera placements on AMD RX 9070XT with latest proton and mesa. It wasn't even running without specifying some flags mentioned above.

I'm glad to tell - issue is completely fixed by replacing amdvlk package with vulkan-radeon (in case of conflict install vulkan-radeon first, then you'll be able to remove amdvlk). It also improved my perfomance in different games by A LOT. Maybe this would help you too. Arch wiki does mention this, but i somehow overlooked it.

ff7 rebirth work now

On Sun, Jun 1, 2025 at 6:04 PM André @.***> wrote:

andreldmonteiro left a comment (ValveSoftware/Proton#8408)
https://github.com/ValveSoftware/Proton/issues/8408#issuecomment-2927975748

I'm having problems with audio. When playing the story so far video from
main menu using a 5.1 surround sound system, the audio supposed to be
coming from the centre speaker is played instead on the rear left speaker.

—
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/8408#issuecomment-2927975748,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BOZLYITDONK52LL7DIRRXVL3BN2FLAVCNFSM6AAAAABVXRFUACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSMRXHE3TKNZUHA
.
You are receiving this because you commented.Message ID:
@.***>

I am getting absurdly long loading times on CachyOS with Proton Experimental as well as Proton 9.0.4.

During these loading times my CPU usage ramps up to 100% and then down to normal usage 3 times per load. The loading screens usually last 3-5 minutes.

Ryzen 7 7800x3D
NVIDIA Geforce RTX 4090
32GB 6000 CL30
Lexar NM790 SSD (I am running on an SSD)

The proton log repeatedly prints the following sequence for around 1000 lines until the loading finishes:

10047.985:015c:0260:warn:vkd3d-proton:d3d12_command_queue_QueryInterface: {db6f6ddb-ac77-4e88-8253-819df9bbf140} not implemented, returning E_NOINTERFACE.

10047.989:015c:0278:warn:vkd3d-proton:vkd3d_native_sync_handle_release: Failed to release semaphore (#12a).

10047.989:015c:0278:warn:vkd3d-proton:dxgi_vk_swap_chain_wait_worker: Failed to increment swapchain semaphore. Did application forget to acquire?

Anybody having the same issues as me?

Will this ever fully work on non-Steam Deck hardware while running something like bazzite-nvidia-deck with SteamDeck=0? Or is it entirely up to the developer to just not force low resolution textures and other Steam Deck specific limitations?

Lot of Out of memory at Costa del Sol, can't do some side quests because of this...

Costa del Sol make the game crash so often and some side quests AND main quest after chapter 12 can't be continue because of this...

Anything else is perfect.

OS:ArchLinux
GPU:AMD Radeon RX 6900 XT
CPU:AMD Ryzen 9 7950X3D
RAM:32 GB @7200Mhz

I am seeing sporadic texture issues with a Radeon card. This seems different from the issue reported earlier on Nvidia.

The game works fine for most of the time, but after some time that varies between 1 and 2 hours textures start to become corrupt, first faintly and then more and more. This usually first affects the terrain, as in the screenshot, but then also affects other objects like buildings and vehicles after a while. Reloading the latest save fixes the issue.

Example:

Radeon 9060 XT
Debian Testing
kernel 6.15.6
amdgpu firmware 20250708
mesa 25.1.5
proton experimental

This is the output of "steam" at the BASH command line:

crowgirl@crowgirlscrowsnest:~$ steam
Testing for explicit PulseAudio choice...
...and PulseAudio has been explicitly chosen, so using it.
INFO: filtering /home/crowgirl/.local/share/flatpak/exports/share out of XDG_DATA_DIRS because it is unreachable
INFO: filtering /var/lib/flatpak/exports/share out of XDG_DATA_DIRS because it is unreachable
INFO: filtering /usr/share/kubuntu-default-settings/kf5-settings out of XDG_CONFIG_DIRS because it is unreachable

And the Steam client GUI (flatpack) does launch.

I cannot find a console_log.txt file, nor any logs for Steam in general except for the one steam-2909400.log file that was made for Final Fantasy VII Rebirth because of the special launching instructions given to Proton?

Thank you so much for your help. I'm not great at coding, but I do have a good general sense of Linux and computing in general as a cybersecurity professor. If you use any terminology that I don't understand, I will ask.

I feel fairly comfortable at the BASH command line, but I usually have to look up commands that I use less often.

@Capricornucopia ~/.local/share/Steam/logs is used by steam when installed from your package manager, flatpak doesn't usually let programs have direct access to your home folder, so the steam folder would be placed somewhere under ~/.var

This game still suffers from abnormal stuttering that isn't present when playing on the same hardware on Windows (at least on AMD).

It fails to maintain a stable framerate even when slowly panning the camera

Is anyone else experiencing this?

This game still suffers from abnormal stuttering that isn't present when playing on the same hardware on Windows (at least on AMD).

It fails to maintain a stable framerate even when slowly panning the camera

Is anyone else experiencing this?

Yes, I'm also on AMD (9070XT) and the game stutters on certain points no matter the framerate cap. I tried it on Windows recently and the stutter was not present at the same moments, but there was screen tearing when it stutters on Linux, even with VRR active.
Something isn't right with this game on PC.

This game still suffers from abnormal stuttering that isn't present when playing on the same hardware on Windows (at least on AMD).

It fails to maintain a stable framerate even when slowly panning the camera

Is anyone else experiencing this?

What distro are you using? if you're on any that simulates the SteamOS, like bazzite for HTPC, CachyOS Handheld, ChimeraOS, the game have a smaller download size due to thinking it's a Steam Deck, and I notived that version stutters like crazy when moving the camera, but on the full size game it doesn't

On this note, anyone found a fix for this steamdeck smaller size?

This game still suffers from abnormal stuttering that isn't present when playing on the same hardware on Windows (at least on AMD).

It fails to maintain a stable framerate even when slowly panning the camera

Is anyone else experiencing this?

Yup. Pop os 24.04 (gnome DE); rx 9070xt; ryzen 5 9600x; using optiscaler for FSR 4.0.2.

I had really bad camera pan stutter when my background model detail was set to ultra. Lowering that to high greatly mitigated the issue, and made it very playable. Stutter is still present, but quite rare now.

My CPU and GPU were nowhere near bottlenecking when i had the stutter issues... So i assumed it was poor game optimization.

Replying to https://github.com/ValveSoftware/Proton/issues/8408#issuecomment-4502365415

does this also occur notoriously in Nibelheim with Cloud + Seph?

Replying to [#8408 (comment)](https://github.com/ValveSoftware/Proton/issues/8408#issuecomment-4502365415)

does this also occur notoriously in Nibelheim with Cloud + Seph?

Nibelheim is one of the worse performance places in the game in my experience

This game still suffers from abnormal stuttering that isn't present when playing on the same hardware on Windows (at least on AMD).

It fails to maintain a stable framerate even when slowly panning the camera

Is anyone else experiencing this?

Yes, same issue here, 5800X3D, 7900XTX on SteamOS 3.8.22, and Proton Experimental, this game stutters so unbearably bad on camera rotations that playing it on PC is worthless. Capping the FPS does not "Fix" the problem because it has noticable stuttering even when a 30FPS cap is engaged in Game Mode QAM that presents as ~28 or so FPS when it happens.

Turning the camera:

Stationary:

A loss of almost 20FPS and egregious stuttering seems completely out of the ordinary and should probably be reviewed. On top of the stuttering assets in various locations can be seen popping in when they do not even on PS5 with a paltry Ryzen 3600 equiv CPU. The game is installed on a Gen 4 NVME.

I finally got it running! It appears a freshie start doesn't work in proton 9+. it might not have been caught due to getting past the initial menu into the starting cut scene but it freezes up just before game play. I have haven't had a chance to check the diagnostic yet,but I am curious if this is a whack-a-mole (as opposed to whack-a-box) situation where switching between proton versions gets one past certain parts but not subsequent others. Maybe this is call for a dynamic version switching mode for the compatibility layer based on aggregate UE?(???) EDIT: truth be told, Gemini said 8; hotfix, exp, 11,& 10 didn't work for me at this moment.

I sent this one to square because it is a little more in-depth but has anyone else notice thread timing issues where it works but is wonky in the change up from battle to exploration. I didn't notice it on the PS5 and Linux might be handled threads and locks a little differently than Windows or BSD,,,

EndeavourOS, Linux 7.1.5-arch1-2, mesa 26.1.6, Radeon RX7900XTX, Ryzen 7 7800X3D, Proton 11.0

White indicator appears mostly on wet surfaces but also appearing on some other surfaces (Nibelheim). Is it bug or feature?

Things i tried:
Changing Proton version to CachyOS_Latest
Disabling Russian localization (mod)
Changing graphical preset to "Low"
Changing upscaling method from FSR to TAAU

Video

Steam Deck, main Steam OS branch, latest Proton Experimental.

Game launches properly and on new game it crashes after the first video. If you watch the video, it crashes when the graphics engine engages. If you skip the video, then it crashes during the loading screen. I do not have access to any logs right now, but I can upload them later on. Anyone else has encountered this issue? It happens with the latest Proton-CachyOS and Proton-GE as well.

It happens only from gamescope. From the Plasma session the gameplay starts without issues. Here's the log from gamescope.
steam-2909400.log

@Txordi00 the game hasn't crashed on my end, can you share your display/graphics settings?

@Txordi00 the game hasn't crashed on my end, can you share your display/graphics settings?

I kept everything on default.

@Txordi00 the game hasn't crashed on my end, can you share your display/graphics settings?

Have you tried a new game & from gamescope?

@Txordi00 all my attempts were new games started from steamos game mode, the initial cinematic plays fine and after it ends I can control zack fair, I don't play much past this point as it sounds like this is where it crashes for you. Your logs show that the gpu is crashing. Have you rebooted your deck after first running into this? switching between game and desktop mode doesn't reboot the device, for example.

@Txordi00 all my attempts were new games started from steamos game mode, the initial cinematic plays fine and after it ends I can control zack fair, I don't play much past this point as it sounds like this is where it crashes for you. Your logs show that the gpu is crashing. Have you rebooted your deck after first running into this? switching between game and desktop mode doesn't reboot the device, for example.

Yes, I have tried to reboot but to no avail.

@Txordi00 what os build are you on? I updated to main specifically to check this, so there's a chance I'm on a newer build than you, and it happens to already be fixed. I'm on 20260807.1000

Also, what is your deck model? It shouldn't matter most of the time, but still would be good to specify in this case. I'm on deck oled.

Update:
A few other things. After you get another crash, go to steam > settings > system> create report (towards the end of the list) > save to desktop
This will create a text file on your desktop, upload it here as well

Replying to https://github.com/ValveSoftware/Proton/issues/8408#issuecomment-5269483559

Hi Simon! Sorry for taking long to answer. I do not have access now to the steam deck. I'm on the oled and on the same build than yours. I'll do that and upload the file tonight. I posted the issue in the gamescope repository as well. Thanks for your help!

Now it goes through the first part and it crashes later on... I'm starting to think that there's something wrong with my Steam Deck.
systemreport-20260813212313.txt

It looks like I'm not the only one with the problem:
https://www.reddit.com/r/SteamDeck/comments/1uftzkb/comment/otv9zor/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button
https://www.reddit.com/r/SteamDeck/comments/1uk8rpt/comment/outxvc3/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button
And it's been like two months since the first report on the issue...