If you mean "Override high DPI scaling" setting on Compatibility tab in C2 shortcut - I tried this and it didn't help.
In fact, I tried all compatibility settings and none of them made any difference.
If that's the case then high-dpi is probably not at fault for the slowdowns. I'd still like to get more feedback from more users before dropping this though.
Thanks for testing it out and providing feedback!
I'm a bit confused, are we not already able to turn off high-dpi scaling in the settings on our C2 projects ?
Yes but this is for Construct 2 itself and as far as I'm aware it makes use of this feature.
This seems to raise more questions than it answers...
Which setting, exactly?
I didn't know that - which setting has changed and how? ...
Windows 7 + Win10 (before update) / Win10 (after forced dpi update)
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.
The latest changes were done in r229, assuming that high-dpi is indeed the cause for slowdowns it would make sense for people which experience these issues without having a Win10 system with the latest updates.
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?"
Could you please stop being "trolly" and stop putting words in my mouth. I'm trying to have an honest and polite conversation which hopefully ends up in finding a solution to this problem. (I know you've had your fair share of bad experiences but I'm just trying to help by providing possible causes for this impactful issue.)
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.
This isn't really a request for a long-term settings option to degrade the quality of Construct 2, it would a temporally (beta) option in order to maybe find the cause for slowdowns and help you out to narrow it down and fix it. Unless of course you've found the cause already, in that case I'd really appreciate a heads up about it!
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.
That's the issue, as far as I know Win10 doesn't allow to disable high-dpi in the properties anymore (at least the community members I've asked couldn't find a way to disable it completly). Based on a more recent report about high-dpi and performance problems and the before mentioned updates in r229, which exactly fit the the affected parts of Construct 2, I thought this might be the fault of high-dpi. High-dpi is known for causing bad performance even in exported C2 games which lead to my assumption based conclusion that it might be at fault.