zixaphir commented 1 year ago

Compatibility Report

Name of the game with compatibility issues: Forspoken
Steam AppID of the game: 1680880

System Information

GPU: NVIDIA GeForce GTX 1080 Ti
Driver/LLVM version: nvidia 525.53
Kernel version: 6.1
Link to full system information report as Gist: Info
Proton version: 7.0-5

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.

Symptoms

Game launches to an error dialog titled Luminous.RenderInterface that reads D3D12Core.dll(DirectX.AgilitySDK) didn't be installed on your Windows. Please update Windows.

Reproduction

Attempt to launch game.

steam-1680880.log

Katherine1 commented 1 year ago

Switching from Nvidia's open-source kernel modules to the fully proprietary ones resulted in a 2-3FPS uplift. Not surprising since the open kernel modules are considered to be in an alpha state, but worth noting as performance is currently a challenge on Nvidia cards.

Bitwolfies commented 1 year ago

So to clarify, the steamdeck=1 flag now only restricts some settings at this point? If so Valves gotta remove the forced option from the steamplay manifest.

Katherine1 commented 1 year ago

Yeah. Patch 1.02 fixed both the dx12 error and the denuvo error so the game starts up fine in normal mode now. You can turn it off manually, but Valve needs to get on removing the option so that it's no longer on by default.

At the moment the only issue I'm aware of is poor performance on Nvidia cards.

Katherine1 commented 1 year ago

NVIDIA performance is unchanged on patch 1.03

Katherine1 commented 1 year ago

NVIDIA performance is unchanged on patch 1.04

Katherine1 commented 1 year ago

NVIDIA performance is basically unchanged on patch 1.10

It looks like there is maybe a 10FPS bump in some places, but stuttering is unchanged.

For reference, on the Windows side, people are reporting their FPS almost doubling.

SzymonRysztof commented 1 year ago

I don't know if that's normal, but for me on Radeon RX6900XT, i'm having huge fps drops, from like 90FPS (4k) to 40-50 each 10-15 secs. It kinda looks like Vulkan shaders thing, but they are set to compile before game starts, and also, lag spikes doesn't seem to dissapear after playing for a while.

edt-xx commented 1 year ago

One interesting observation with patch 1.10. It does NOT like RADV_PERFTEST=gpl. With this enabled it starts and after displaying one or two of the 'working' circles goes to a blackscreen. This is with: mesa 23.1 (built from git), kernel 6.2.2, proton experimental or 7.06 kde wayland 5.27-2 on an up to date Arch install using either steam or steam-native.

ChaosBlades commented 1 year ago

Just played the opening chase scene and ran the benchmark. Not a single frame time spike and FPS is between 60-90 with an average of 78 fps in the benchmark. The previous patch gave me slightly lower FPS (Needed to use FSR Quality with DRS to keep above 60 fps) and I had some moderate frame time spikes. Would not say it was unplayable by any means. Graphics manually maxed (including motion blur), no FSR, and no DRS.

You still need to use SteamDeck=0 in order to enable all graphics settings. I ran with gamemoderun SteamDeck=0 %command%

3440x1440 5950X 6900XT (Overclocked) 32GB RAM NVMe SSD

Pop!_OS 22.04 LTS x86_64 6.2.0-76060200-generic Mesa 23.1.0-devel (git-2b00eaa 2023-03-12 jammy-oibaf-ppa) Proton Experimental Bleeding Edge GameMode Enabled although I see no difference between on/off in testing

If you are having issues might want to try the latest development version of Mesa, Newer version of Proton, or a newer kernel.

Nvidia issues, well best go with AMD GPUs if you plan on gaming with linux due to the driver being a black box. Nobody knows how the driver works due to closed source and it is difficult to resolve issues because of this. Maybe one day Nvidia will fix whatever problem is happening or someone smart enough can reserve engineer the issue. Nvidia is just an overall bad experience on linux and I would not necessarily blame the game for issues.

Katherine1 commented 1 year ago

Yeah, I suspect that whatever issue Nvidia cards are having with Forspoken is something on the driver side, which leaves us kinda stuck.

ipr commented 1 year ago

Might be related to #2927 that this is crashing ("SGDT instruction cannot be used by applications").

ipr commented 1 year ago

Time for crash log.. Having updated to Mesa 23.1.4 and with Proton 8.0-3 this is what I get currently.

Before the crash there is log entry: 85349.122:0134:0194:info:vkd3d-proton:vkd3d_pipeline_library_disk_thread_main: Flushing disk cache (wakeup counter since last flush = 31). It seems like application has stopped creating new PSOs for the time being.

This is then followed by the crash dump. steam-1680880.log.gz

mozo78 commented 1 year ago

There's something generally broken on NVIDIA (1080Ti in my case). The game doesn't utilize nor GPU nor CPU and they sit around 15-19% at 13-20 FPS (720p). The game is running REALLY bad. I hate Windows but I installed it to see how the game will run. It's running fantastic with 200 FPS on standard and with 70-80 FPS on Ultra settings and 1440p. Is there a bug on NVIDIA bugtracker? Are they aware about this problem?

mbriar commented 1 year ago

@mozo78 nvidia pascal and older performing badly in pretty much all d3d12 games on linux is known and is unlikely to ever change.

mozo78 commented 1 year ago

Hmm, I have many D3D12 games which are at least playable and some of them are running great. This one isn't even barely playable :( I'm waiting 4080Ti though :)

Katherine1 commented 1 year ago

@mozo78 nvidia pascal and older performing badly in pretty much all d3d12 games on linux is known and is unlikely to ever change.

I don't think that's relevant here as this game performs poorly on a 3080ti as well. It's known to perform poorly on all NVIDIA cards on Linux.

ChaosBlades commented 1 year ago

The Nvidia driver is a closed Source black box that nobody can even properly debug for let alone fix bugs and it's not like fixing Linux specific bugs is any kind of top priority for NVIDIA. If you plan on seriously gaming on Linux I would highly advise you just stick to an AMD GPU. I have a 6900xt and this game runs perfectly fine at 4K 60fps.

mozo78 commented 1 year ago

And what about GTA V? Every vendor has it's pros and cons.

mozo78 commented 1 year ago

I filed a bug, feel free to report the issue.

frozen-sea commented 1 year ago

It seems like the demo is being kept up-to-date as well, currently reporting version 1.21. It's definitely not just an older card issue. I'm getting bad performance due to one CPU core being pegged, it's always #5 that sits at basically 100% load all the time. Log doesn't look all that different compared to what the AMD users have posted. FORSPOKENDemo.exe is reported as using 20% when in game, while total CPU usage is 30% and I'm unable to determine where the additional 10% is coming from. Is all the Proton overhead factored into the .exe? Because then there would be some serious CPU usage from the driver.

Launch options: PROTON_LOG=1 PROTON_ENABLE_NVAPI=1 VKD3D_FEATURE_LEVEL=12_2 VKD3D_CONFIG=dxr11 %command%
Proton: 1692133061 experimental-bleeding-edge-8.0-52694-20230815-p314065-w247739-d4ae542-vaeb499
Nobara 38, kernel 6.4.8
RTX 4070 Ti, driver 535.98
Ryzen 5800X3D

steam-2228080.zip

ChaosBlades commented 1 year ago

And what about GTA V? Every vendor has it's pros and cons.

Not to bring this thread off topic but I just tested GTA V. Graphics Settings / Advanced Graphics Settings Maxed, Frame Scaling Mode and MSAA both Off (pointless at 4K). 6900XT. At 4k I get 90-140 FPS averaging around 100 FPS in the Benchmark. GPU is not overclocked and power limit has not been increased.

Take it from someone that has not used an AMD GPU since the AGP slot was a thing. ATI Radion X1300 (Oct 2005) was my last AMD GPU since the 6900XT I have now. Been an Intel/Nvidia user all that time. I switched from my GTX 1080 real quick when I switched to Linux full time. Experience has been so much better I bought another one for a living room PC using HoloISO. Windows is an Nvidia pro for sure but Linux it is a definite con. I frequent games on here quite often. I see Nvidia users with problems all the time that take a very long time to fix (if they ever get fixed) that I just don't have on AMD. If there is an AMD specific issue it is fixed in a reasonable amount of time from my experience.

I wish you the best of luck on the bug report. It is for an unpopular game on an unpopular OS. I don't see them making it a priority. Meanwhile on AMD the driver is open source so anyone with the knowledge can submit a PR and Linux is a much higher priority for AMD in general.

mozo78 commented 1 year ago

Replying to https://github.com/ValveSoftware/Proton/issues/6474#issuecomment-1679746436

Please use my link to confirm the problem on the NVIDIA bug tracker.

ipr commented 1 year ago

I found that turning on vsync and setting vram usage to low (lower than necessary) increased time between crashes from 1-2 minutes to ~20 minutes. It is at least enough to get through the apartment-scene in first chapter upto another save point that you can continue from.

Hadrianneue commented 1 year ago

constant screen flickering with the latest update, FSR3 FG needs VKD3D_FEATURE_LEVEL=12_2 environment variable ~~dxvk nvidia device id spoof~~ to show up but it crashes as soon as i try to turn it on, log from the demo bellow:

steam-2228080.log

edt-xx commented 1 year ago

I can confirm that the latest update with FSR3 makes forespoken a flickering mess here (it needs serious epilepsy warnings - It is that bad). I am on an up to date Arch install and have tried Proton 8.0-3 and experimental. Mesa is the newly released 23.2.1 (when using steam-native) though the same problem occurs with steam-runtime. There is no selection to disable/enable framegen and the two ray tracing selections are forced on and cannot be disabled.

On Fri, Sep 29, 2023 at 3:49 AM Adriano Martins @.***> wrote:

constant screen flickering with the latest update, FSR3 FG needs dxvk nvidia device id spoof to show up but it crashes as soon as i try to turn it on, log from the demo bellow:

steam-2228080.log https://github.com/ValveSoftware/Proton/files/12762149/steam-2228080.log

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

wendersonp commented 12 months ago

I can confirm the issue is happening, there should be a bleeding edge patch to address this.

ffrasisti commented 12 months ago

The game is a flickering mess on Steam Deck after the update regardless of settings. Its a health risk even. Even the menus are constantly flickering now.

CrashTD commented 12 months ago

still massive flickering even with the vkd3d fix in bleeding edge.

https://github.com/ValveSoftware/Proton/assets/45145914/819769d6-79bc-4eaf-9da8-80f4b35760db

akdean commented 12 months ago

https://github.com/HansKristian-Work/vkd3d-proton/issues/1717

lorenzo0932 commented 12 months ago

constant screen flickering with the latest update, FSR3 FG needs dxvk nvidia device id spoof to show up but it crashes as soon as i try to turn it on, log from the demo bellow:

steam-2228080.log

for me FSR Frame Generation option not appear even with this dxvk.conf:

dxgi.customDeviceId = 24c9
dxgi.customVendorId = 10de

Am I doing something wrong?


System information

    GPU: RX 6700 non XT
    Driver: mesa RADV
    Wine version: Proton Experimental with vkd3d-proton recompiled
    VKD3D-Proton version: 2.10.0/1.3.261

Hadrianneue commented 12 months ago

Replying to https://github.com/ValveSoftware/Proton/issues/6474#issuecomment-1741787730

i tested incorrectly, should've edited my comment, you just need VKD3D_FEATURE_LEVEL=12_2 %command% launch option, no dxvk spoof needed

lorenzo0932 commented 12 months ago

Replying to #6474 (comment)

i tested incorrectly, should've edited my comment, you just need VKD3D_FEATURE_LEVEL=12_2 %command% launch option, no dxvk spoof needed

thanks, i can confirm in my case flickering is solved when frame generation is active with the last vkd3d-proton patch