Philip Rebohle

Why are the thread syncs in `ConsiderFlush` necessary? We should get consistent behaviour simpy by adjusting the heuristic. The specific implementation also massively inflates the actual submission count compared to...

`wsi::enumMonitors` calls `EnumDisplayMonitors` on win32 platforms. If that function returns monitors in a random order, it's not clear what we need to do to to sort them correctly. I guess...

Again, the main concern here is that we really need *very* strong guarantees that changing the default behaviour here isn't going to break a whole bunch of games that rely...

I'm not arguing that our behaviour is technically wrong, I just don't feel comfortable changing it because it's extremely difficult to test (I can't even replicate the actual issue on...

There's games that literally break when the graphics driver dll doesn't start with "ati" or "nv", i'm not trusting this blindly.

Games don't just use DXGI to do monitor stuff, games use 30 different APIs at the same time and expect them to match. Even if it's not documented. Even if...

> If Wine lists the monitors in the order of primary first by default - as stated in the first reply - Does it though? > Not to mention that...

We get LUIDs from `winevulkan` if supported by the wine build in question in order to avoid problems like these, we should never hit the code you linked in practice....

Gonna be honest, this type of software just isn't interesting for us to support especially as long as it doesn't work on Wine to begin with. Can take a look...

Based on the log, using native `d3dx11_43` might help (or some other d3dx library, would need the *full* wine log to be sure), but yeah, probably a wine problem.