> 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.)
I'm sorry, I don't mean to troll you, I'm just describing exactly what happened last time we added a performance workaround. We add a workaround, then someone immediately asks to fix it without the workaround. ¯\_(?)_/¯
[quote:33a7xihx]
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.
So, just to be clear, you don't have performance measurements to back this up?
[quote:33a7xihx]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.
I've never seen or heard any such cases of high-DPI causing performance issues in C2 games, unless it's due to GPU bandwidth limits. The option to disable high-dpi mode in the runtime is essentially a variant of "low quality" fullscreen mode. I don't think there's any kind of parallel to the editor there, editing software does not usually come close to GPU fillrate limits, it's entirely different to game rendering.