How is this URGENT ?

http://www.catb.org/~esr/faqs/smart-questions.html#urgent

At any rate, Glide / Direct3D12 works here with the latest dgVoodoo version, so it's something else:

1) Driver / GPU issues: Have you tried WARP rendering?
2) Using a beta OS: don't report bugs based on this. Install a stable Windows version and test. Note that this might contribute to 1), your GPU drivers might just not work well with beta versions of Windows.

Direct3D12 has some limitations anyway, so you should get Direct3D11 working, that it has frequent lock-ups too makes me believe the above two things are likely culprits, rather than any issue with dgVoodoo.

xcomcmdr wrote on 2022-10-16, 18:10:

How is this URGENT ?

Because it's a huge glaring issue that makes certain games unplayable in Glide mode.

ZellSF wrote on 2022-10-16, 18:23:

http://www.catb.org/~esr/faqs/smart-questions.html#urgent […]
Show full quote

http://www.catb.org/~esr/faqs/smart-questions.html#urgent

At any rate, Glide / Direct3D12 works here with the latest dgVoodoo version, so it's something else:

1) Driver / GPU issues: Have you tried WARP rendering?
2) Using a beta OS: don't report bugs based on this. Install a stable Windows version and test. Note that this might contribute to 1), your GPU drivers might just not work well with beta versions of Windows.

Direct3D12 has some limitations anyway, so you should get Direct3D11 working, that it has frequent lock-ups too makes me believe the above two things are likely culprits, rather than any issue with dgVoodoo.

1. Yes, and it performs even worse.
2. I guess? It's just that I've been in the beta program for over a year and it's only now doing this.

Sorry for labelling it as urgent, I was just hoping I could find a solution faster if I got someone's attention. I was just kind of panicking because all of a sudden my Glide-rendered games using D3D 12 start acting up.

UPDATE: Okay apparently it was a GPU driver issue, I switched to Nvidia's Studio Drivers instead and now the issue is gone. Thanks for the suggestions.

UPDATE 2: This issue STILL hasn't been fixed over the course of several updates to Nvidia's drivers, and I have to keep rolling back to the one build that doesn't cause this issue. It's becoming a problem now because I now have to choose between downloading the new drivers to play certain games that require them and keeping the old drivers on my system.

I'm stuck on the Windows 11 Beta branch and I've tried getting back to the stable builds to see if the issue exists there too, but it's no use because I had to bypass 11's stupid Secure Boot requirement just to get the original upgrade INSTALLED all because my stupid motherboard won't recognize my drives if have Secure Boot enabled, meaning I can't do a proper reinstall without having to wipe all my apps. It's such a stupid situation that I can't get myself out of without fucking myself over. So if someone can PLEASE help me out here, I'd greatly appreciate it.

I'm late to the party, but yes, the symptoms are as if the GPU rasterization skipped (some) of the resource transitioning barriers in the command list.
Anyway, (as it already turned out), these types of rendering glitches are more than probably because of driver bugs. I used to come across with it (D3D11) when upgrading to newer driver version for my old (GF 1060) video card (probably the driver guys accidentally optimized out a necessary barrier somewhere in the code for the sake of better performance). That's why I rarely update my working drivers to the latest one and roll it back at once if I get a performance or rendering glitch not present before.
Btw, I still get similar glitches with the Adreno GPU.

Anyway, the presentation model defaults to 'automatic' which shouldn't change the behavior compared to older versions. And if an unsupported combination is set (like D3D12 + Discard) then dgVoodoo cannot even initialize.
I have no idea what to do with drivers and the OS in a beta program - maybe reserving a separate machine for that and have another for normal daily usage.