info: d3d9.evictManagedOnUnlock = True
info: dxvk.enableAsync = true
Use an official build and remove those 2 options.
d3d9.evictManagedOnUnlock = True prevents the game from constantly crashing when using DXVK. Also removing those options doesn't fix the VATS delay.
Try with a recent master build of DXVK and without the option, it should improve the memory related crashes: https://github.com/doitsujin/dxvk/actions/runs/3259837904
Please make an apitrace of the issue and upload that.
What on earth is VTAS and how does it interact with DXVK?
V.A.T.S
It's the non realtime combat system in the fallout games https://fallout.fandom.com/wiki/VATS
Ah that thing, I thought this was a mod or something.
Please assume that we generally have no idea about the game in question even if it's as popular as Fallout.
I will try to see if i can reproduce this here later when i have time. (But apitrace would still be appreciated)
Try with a recent master build of DXVK and without the option, it should improve the memory related crashes: https://github.com/doitsujin/dxvk/actions/runs/3259837904
VATS delay still occurs with that build. Also doesn't seem to play well with msi afterburner (overlay doesn't show up when using that specific build).
Regarding apitrace, I tried it out, but while it did produce a file on my desktop, msi afterburner indicated that the game was running in d3d9 instead of vulkan. VATS issue wasn't occurring as a result. For reference, this is the link I used - https://github.com/apitrace/apitrace/releases/download/11.1/apitrace-11.1-win32.7z
Also doesn't seem to play well with msi afterburner (overlay doesn't show up when using that specific build).
The Vulkan integration of MSI Afterburner is broken and we don't support that.
Regarding apitrace, I tried it out, but while it did produce a file on my desktop, msi afterburner indicated that the game was running in d3d9 instead of vulkan. VATS issue wasn't occurring as a result.
That's fine. Please still upload the apitrace.
This seems to be a rather wide spread game bug. If you google "Fallout VATS delay" or "Fallout VATS lag", there are a lot of results.
Uploading the apitrace file now. Regarding afterburner, it works fine with 1.10.3 and prior versions. Just seems to have issues with the recent master build.
VATS lag has been a thing with the game from what I recall. But DXVK seems to exacerbate it. As I said, I tested DX9 & Vulkan, and the former had very little delay when initiating it.
Absolutely no idea what's going on. There's nothing in DXVK, that can delay things by seconds while still rendering frames.
This seems to be some super weird timing bug in the engine that's somehow triggered by DXVK.
I can't fix this.
The delay is actually a hardcoded 2 second wait, it was added as a workaround in one of the updates to address the hit percentages not always calculating correctly. I've tried to figure out what the bug they were trying to fix was but have been unsuccessful so far. You can lower the wait to 500ms in my Tweaks engine plugin if you add the line bFixVATSLag=1 under the [Tweaks] heading, but note that it causes the hit percentages to be slightly different.
https://www.reddit.com/r/fnv/comments/nxuor9/vats_hit_percentages_are_slow_to_load_when/
No clue, why this only happens with DXVK for you but I also don't see how D3D9 would be involved with that. There's nothing we can do here.
The same issue happens in Fallout 3 - there's a 1+ seconds delay when using DXVK, while on native d3d9 it's almost always instant.
Nothing extracted yet.
Using VATS often results in a delay until the shot percentages actually load in. With DX9, the percentages generally load instantly. With DXVK, they can either take a bit longer than DX9, or significantly longer (several seconds).
Log files
FalloutNV_d3d9.log