undefined | Better HN

0 pointsrafram3y ago0 comments

> Even when requesting a full screen swapchain to avoid having to deal with the compositor, modern OSes will force you to go through that compositor and lie about it being fullscreen.

I’m honestly thankful for this bit of lying. Windows 8 and below had horrible, horrible issues with fullscreen programs, especially games - they’d change your screen resolution and thus move and resize all your other windows, they’d freeze for ten seconds when you tried to alt-tab out, and they’d frequently just crash when you switched back to them. Those problems are essentially nonexistent nowadays, and it’s worth the small performance cost that comes from going through the compositor.

0 comments

3 comments · 1 top-level

ohgodplsno3y ago· 2 in thread

I know that in Windows 10+ and on UWP apps, requesting a fullscreen swapchain straight up crashes and tells you "nope, you're going to go through the compositor".

But yes, alt-tabbing Source games was an exercise in patience.

raframOP3y ago

Is that disabled for programs targeting older OS versions? Or are you saying that the new behavior is only for UWP apps? Because that sounds like it would break a lot of old code.

ohgodplsno3y ago

Sorry, hadn't seen that response: yes, it's only when you opt in to UWP that it causes crashes. However, even if you didn't, Windows lies to you. If you ask for FSE (Full Screen Exclusive), it'll say alright buddy, and give you a Full screen that goes through DWM. I believe they have an article on that somewhere on the direct X blog called full screen optimizations, or something along those lines, that explains it.

j / k navigate · click thread line to collapse