![]() ![]() ![]() Where available, we are now using this function instead to work around this issue. This does not happen if the DPI_AWARENESS_CONTEXT value is set via the newer Set ProcessDpiAwarenessContext(), however that function was only recently introduced and is not available on all Windows 10 systems. This appears to affect various models - between my tests and user reports, I’ve seen it on a GTX 660, 1080 Ti and RTX 2070. This appears to happen consistently back on all driver versions (checked as far back as the 399.x drivers, oldest I could download from the NVIDIA site to test with). This does not happen on Intel, AMD, or software OpenGL drivers (in all of those cases, you get a nice, high-DPI app). When a thread opts into to handling per-monitor DPI awareness by calling Win10’s SetThreadDpiAwarenessContext() with any value other than “unaware”, and uses OpenGL, its window contents is scaled in correctly - specifically a corner of the viewport is being scaled up using nearest filtering, looking terrible, and, of course, discarding a portion of the rendered frame.Įxample, loading screen of Splody with 125% Scale: Įxpected (on non-NVIDIA or with workaround or no High-DPI scaling):
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |