Eschatos: Debug runtime popup about dxvk HOT 10 CLOSED

Testing on my windows laptop, tried with both regular DXVK and the build you provided, still results in the same pop up.

Update: Also providing a trace file incase that helps.
ESCHATOS.zip

from dxvk.

Can confirm it shows the popup when dxvk is used on Windows also. dgVoodoo2 is fine.
Game uses d3d9Ex if that matters

from dxvk.

Could you try with this build: dxvk-devel.zip, and see if that does anything?

from dxvk.

Thanks for trying it out. Is the trace captured with dxvk, WineD3D or native Windows?

from dxvk.

I'm guessing native windows, unsure cause I just downloaded the api trace files, slapped in the d3d9 one into the Eschatos game folder and ran it.

I can get the pop up to show up on both windows and Deck as long as i'm using DXVK

from dxvk.

I don't see anything out of the ordinary in the trace, except an early call to: IDirect3DDevice9Ex::CreateQuery(this = 0xa5f5dc0, Type = D3DQUERYTYPE_VERTEXSTATS, ppQuery = ?) = D3DERR_NOTAVAILABLE, which apparently fails on native, but should work fine with dxvk.

Here's a dxvk build that returns D3DERR_NOTAVAILABLE for that call to test with: dxvk-devel-2.zip

from dxvk.

Tried out that Devel-2 build and yep, that seems to fix it, Eschatos launched without that debug pop up box now.

from dxvk.

Yeah, thought so. According to official specs VERTEXSTATS is only available in debug runtimes: https://learn.microsoft.com/en-us/windows/win32/direct3d9/queries , so it sort of makes sense.

Still, a very silly check for a game to implement. I'll PR something to remove it, but I'm not sure if Josh or others need those queries for debugging/perf. testing or anything else, so we'll see how it goes.

from dxvk.

but I'm not sure if Josh or others need those queries for debugging/perf

Would be news to me and if Josh says so, we can still put it behind an environment variable.

from dxvk.

but I'm not sure if Josh or others need those queries for debugging/perf

Would be news to me and if Josh says so, we can still put it behind an environment variable.

I wouldn't bother if it's not explicitly needed then, since native doesn't support it.

from dxvk.