hjpaul7 commented 2 weeks ago

Compatibility Report

Name of the game with compatibility issues: Final Fantasy VII Rebirth
Steam AppID of the game: 2909400

System Information

GPU: Nvidia 4090
Video driver version: 565.77
Kernel version: 6.12.10
Link to full system information report: Gist here
Proton version: Experimental

I confirm:

[x] that I haven't found an existing compatibility report for this game.
[x] that I have checked whether there are updates for my system available.

Proton Log: steam-2909400.log

Symptoms

Missing textures once you're able to play the game (after cutscene). I'm assuming there's supposed to be a UI tutorial prompt being displayed but cannot see it as you're unable to move the character.

Reproduction

Launch game
Get through opening cutscenes till you're able to play the game
Textures missing (screenshot below)

Uklosk commented 2 weeks ago

Same here with an RTX 3080.

HansKristian-Work commented 2 weeks ago

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.

hjpaul7 commented 2 weeks ago

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.

Dinjoralo commented 2 weeks ago

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.

seidtgeist commented 2 weeks ago

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.

DistantThunder commented 2 weeks ago

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.

roccodev commented 2 weeks ago

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.

EoinHealy0 commented 2 weeks ago

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

Zarkorix commented 2 weeks ago

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.

DuplicantWood commented 2 weeks ago

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

ofcaah commented 2 weeks ago

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.

elken commented 2 weeks ago

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.

dmsimard commented 2 weeks ago

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!

AshtenThePlatypus commented 2 weeks ago

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

Shin-Aska commented 2 weeks ago

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)

roccodev commented 2 weeks ago

@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)

NullCGT commented 2 weeks ago

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.

jorbuedo commented 2 weeks ago

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.

ofcaah commented 2 weeks ago

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

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

dabdude420 commented 2 weeks ago

im having the same problem with my nvidia 4080

dabdude420 commented 2 weeks ago

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

jorbuedo commented 2 weeks ago

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 😿

DistantThunder commented 2 weeks ago

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.

aarron-lee commented 2 weeks ago

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.

Rose-David commented 2 weeks ago

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.

aarron-lee commented 2 weeks ago

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.

remz92 commented 2 weeks ago

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...

grahfmusic commented 2 weeks ago

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

wildan-zog commented 2 weeks ago

I hope this issue fixed asap :')

shigutso commented 2 weeks ago

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...

steckums commented 2 weeks ago

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

zrooda commented 2 weeks ago

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)

dmsimard commented 2 weeks ago

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:

EoinHealy0 commented 2 weeks ago

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

HansKristian-Work commented 2 weeks ago

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

Cha1N1 commented 2 weeks ago

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)

ofcaah commented 2 weeks ago

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)

HansKristian-Work commented 2 weeks ago

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.

HansKristian-Work commented 2 weeks ago

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.

Cha1N1 commented 1 week ago

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

andrew-ld commented 1 week ago

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

slbillups commented 1 week ago

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%)

ofcaah commented 1 week ago

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'.

zrooda commented 1 week ago

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.

ofcaah commented 1 week ago

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-ld commented 1 week ago

[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

slbillups commented 1 week ago

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...

roccodev commented 1 week ago

@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.

Sloogs commented 1 week ago

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

jeffhirsch commented 1 week ago

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

ValveSoftware / Proton

Final Fantasy VII Rebirth (2909400) #8408

Compatibility Report

System Information

I confirm:

Symptoms

Reproduction

Note: Gamescope (HDR)