This seems to raise more questions than it answers...
Just a quick note before we go into more detail, Microsoft decided to drop the legacy option to disable application specific high-dpi scaling and pretty much force enable it now
Which setting, exactly?
[quote:31cwhx3u]As you might already know, Windows 10 more recently decided to only allow users to override the dpi setting and not disable it completely.
I didn't know that - which setting has changed and how? I still see DPI options in the Compatibility tab of an executable in the latest patched Windows 10.
[quote:31cwhx3u]However I found out that it's possible to set it to "Application Mode", which basically means that C2 has full control over the dpi mode.
C2 should already have full control over the DPI mode. It registers as a "system DPI aware" process, which means it handles the global system DPI setting. This does not cover the more recent support for multi-monitors with differing DPIs, but that seems a fairly niche case.
[quote:31cwhx3u]I assume that C2 has high-dpi support enabled by default, which could be the reason for why users started experiencing performance issues more recently and not before that mentioned update that started forcing high-dpi mode.
C2 has had basic support for high-DPI for as far back as I can remember. There's nothing we've changed on that front for a long time, and C2 should not have been using a compatibility mode, because it is natively system-DPI aware.
[quote:31cwhx3u]Simple, with an added option to disable high-dpi as a whole for C2 (despite it's downsides of overall quality)
This would make the whole UI look blurry. I'm sure the next question would be "how do I make sure the UI looks sharp?" We already worked around the event dialog performance issue by implementing a special setting, and then the next question was "how do I fix the performance issue without using the special setting?", so it seems these kinds of workarounds are not satisfying to users.
[quote:31cwhx3u]users that experience performance issues could test it out and provide feedback which could lead to the conclusion that high-dpi scaling is indeed at fault for the most recent performance issues with C2 on Win10.
What evidence is there that this does cause the performance issue? What measurements have been made with which combinations of settings and how do they compare? I don't see any evidence at all for this right now.