https://bugs.winehq.org/show_bug.cgi?id=45278
--- Comment #7 from Henri Verbeet hverbeet@gmail.com --- (In reply to Zebediah Figura from comment #6)
Sorry about my quietness on this bug. Problem is, I've gone over the IVB patch with a fine toothed comb at least twice now, and while I've fixed problematic rebases, the problematic parts only ever affected the tests. I don't know why this is failing for you, and I don't immediately have the D3D knowledge to figure out. If one of the D3D devs could take a look at this, I'd be grateful, but I understand there's not a lot of incentive to do so.
I found some time to look a little bit into this, and while I didn't see anything obviously broken in the patchset at first sight (but github is just terrible for review—I may just have missed it), one thing to note is that we started defaulting to core contexts in Wine 3.9. You may just be hitting a different (broken) path in an otherwise unchanged patch. Does setting "MaxVersionGL" to 0x00010000 help? The GL_INVALID_OPERATION messages in the log would be consistent with this being related to core contexts somehow. It may be interesting to put a breakpoint on wined3d_debug_callback() and get a backtrace, to see which call is causing those.