Philip Rebohle
Philip Rebohle
> Tomorrow I'll check if replacing dxgi.dll in system32 fixes any issues Please don't do that, it'll break your Windows install.
Do we know what the issue is exactly? I really don't want to waste even more time on the horrendous shitshow that is ENB, it does some really weird shit...
The trace works, yes, and it shows one problem that can definitely cause crashes, gonna fix that and hope that it works.
Does https://github.com/doitsujin/dxvk/tree/range-checks fix the issue for you? (build [here](https://github.com/doitsujin/dxvk/actions/runs/770515241))
Yeah, no idea what to do then. The trace you attached replays perfectly fine on my end, not really sure how to debug this further, especially since the last API...
I mean, creating traces with different DXVK builds is probably not going to change anything since apitrace records D3D11 commands, which are *usually* unaffected by what DXVK is doing and...
you'd need to trace on Windows, or with wined3d if that works.
Same as on Linux I guess? You'll have the same problems with ENB though which makes the whole thing a real pain in the arse to work with.
> it still has dxvk v1.10.1... It ships DXVK master. Current DXVK development code is based on 1.10.1, the other point releases were created from a separate branch.
We haven't really supported this because there's no real use case for it. Yes, it can be fixed, but it is very, very **very** low on the priority list. >...