http://bugs.winehq.org/show_bug.cgi?id=59147 --- Comment #4 from Rémi Bernon <rbernon@codeweavers.com> --- Yes, non-default DPI usage will cause every present to go through the offscreen rendering mechanism, as we need to upscale the surfaces. This is possibly going to hurt performance already but we also need to call glFinish in that case when the surface contents are meant to become visible on screen (for cases where buffer aren't swapped for instance). Now, the whole thing isn't very well defined yes, but that's not something we can change right during code freeze. Mostly the `flush` callback is meant to commit any change done to the surface properties and contents to the host, from the presentation thread (as opposed to the `update` callback which does the same -except for the surface contents- but from the window owner thread). Regarding wgl_context_flush, it needs to be called on glClear because of the memory DC surfaces, which show that they flush the surface contents too after these calls. Still, I think the iterative changes and fixes caused the offscreen presentation to be done more often than necessary, and I think we can safely do it explicitly when it is actually going to be necessary. https://gitlab.winehq.org/wine/wine/-/merge_requests/9817 should hopefully implement this. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.