dxvk.shrinkNvidiaHvvHeap has been removed as a option with dxvk 2.0 which proton experimental includes. So i'm guessing the changed behavior with that is on proton stable?
DXVK version: Unable to retrieve, MangoHud doesn't work, neither does DXVK_HUD
Log files unable to retrieve.
No logs are created or hud shown if you run the game with PROTON_LOG=1 DXVK_HUD=full %command% ?
FH5 is a DX12 game.
29 Nov 2022, 16:22 by @.***:
dxvk.shrinkNvidiaHvvHeap> has been removed as a option with dxvk 2.0 which proton experimental includes. So i'm guessing the changed behavior with that is on proton stable?
DXVK version: Unable to retrieve, MangoHud doesn't work, neither does DXVK_HUD
No logs are created or hud shown if you run the game with > PROTON_LOG=1 DXVK_HUD=full %command%> ?
—
Reply to this email directly, > view it on GitHub https://github.com/doitsujin/dxvk/issues/3105#issuecomment-1330817623> , or > unsubscribe https://github.com/notifications/unsubscribe-auth/A3G6J6LGH3756I3LVOB7EULWKYNSHANCNFSM6AAAAAASOTEPU4> .
You are receiving this because you are subscribed to this thread.> Message ID: > <doitsujin/dxvk/issues/3105/1330817623> @> github> .> com>
Well FH5 being Dx12, would that mean DXVK has issues with it?
The game runs perfectly fine on other platforms such as AMD.
No logs are created or hud shown if you run the game with
Not explicitly logs, there is no clear location where those are stored. but huds do not appear at all - including mangohud.
Oh right xd.
You should make an issue at https://github.com/HansKristian-Work/vkd3d-proton then 🙂
Edit: dxvk doesn't handle d3d12 games. Tho it might use dxvk's dxgi.dll for some non graphics stuff. But i don't think that's relevant here.
DXVK doesn't handle DX12
29 Nov 2022, 16:26 by @.***:
Well FH5 being Dx12, would that mean DXVK has issues with it?
The game runs perfectly fine on other platforms such as AMD.
No logs are created or hud shown if you run the game with
Not explicitly logs, there is no clear location where those are stored. but huds do not appear at all - including mangohud.
—
Reply to this email directly, > view it on GitHub https://github.com/doitsujin/dxvk/issues/3105#issuecomment-1330824415> , or > unsubscribe https://github.com/notifications/unsubscribe-auth/A3G6J6LQ4IRQMSQJ6SR6U6TWKYOD7ANCNFSM6AAAAAASOTEPU4> .
You are receiving this because you commented.> Message ID: > <doitsujin/dxvk/issues/3105/1330824415> @> github> .> com>
that would explain why the hud doesn't show up.
NVIDIA reports it is using Vulkan via the API indicator.
well, honestly i'm not exactly sure because i remember it very clearly using DXVK.
If it was mangohud that reported it in the past then that is a known bug with mangohud that it would call vkd3d-proton for dxvk.
That's impossible, neither FH4 or 5 ever supported DX11 and DXVK doesn't deal with DX12.
29 Nov 2022, 16:35 by @.***:
well, honestly i'm not exactly sure because i remember it very clearly using DXVK.
—
Reply to this email directly, > view it on GitHub https://github.com/doitsujin/dxvk/issues/3105#issuecomment-1330836864> , or > unsubscribe https://github.com/notifications/unsubscribe-auth/A3G6J6LIYULG2F4RZJXXQC3WKYPDZANCNFSM6AAAAAASOTEPU4> .
You are receiving this because you commented.> Message ID: > <doitsujin/dxvk/issues/3105/1330836864> @> github> .> com>
As others have noted, it's a D3D12 games
okay.
proton experimentalx3 2022-11DXVK_HUDx3 2022-11DXVK_HUD=fullx2 2022-11PROTON_LOG=1x2 2022-11DXVK_CONFIG_PATH=/home/wael/dxvk.conf`x1 2022-11PROTON_LOG=1 DXVK_HUD=full %command%x2 2022-11dxgi.dllx1 2022-110x80000004x1 2022-11
Please describe your issue as accurately as possible.
If you use Windows, please check the following page: https://github.com/doitsujin/dxvk/wiki/Windows
Software information
System information
DXVK_HUDLog files unable to retrieve.
NVRM: Xid (PCI:0000:01:00): 31, pid=17601, name=ForzaHorizon5.e, Ch 00000025, intr 00000000. MMU Fault: ENGINE GRAPHICS GPCCLIENT_GCC faulted @ 0x5580_00008000. Fault is of type FAULT_PDE ACCESS_TYPE_VIRT_READWith
dxvk.shrinkNvidiaHvvHeap = TrueandDXVK_CONFIG_PATH=/home/wael/dxvk.confin the command launch parameters, the game will load and go to the festival and going out to drive, and then crash specifically with Xid 13. with 31 it crashes whilst its loading - before reaching the festival and into the actual game.what is more painful is that Nvidia has been solving Xid 31 errors with many games, and not this one.