https://bugs.winehq.org/show_bug.cgi?id=49077
--- Comment #17 from RC rich.coe2@gmail.com --- Sorry about that, the 'new' context in the comment above was a different testcase than the +d3d trace. ------- I suspect that recent changes in Mesa 20.0.[45] may be causing this issue. Previous version was mesa-20.0.3. - a bug in mesa-20.0.5 nouveau - a fix in mesa-20.0.5 where some previous behaviour worked is now broken
I'm updating to mesa-20.0.6 that just showed up in the repo. There's a couple of bug fixes in there.
If 20.0.6 fixes the issue, then this was a regression in 20.0.5, that's now fixed. If it's still broken, I will see if mesa-20.0.3 fixes the issue, and bisect if need be.
If not, I'll have find the gl commands and ordering that's causing the issue (hope not ...).