RESOLVED: Perform mode "pops" when opening other windows comps

Bugs
1

I’ve noticed this recently, last few stable versions its been a problem, and it persists in the latest 2023.11290

as seen in the linked video, when in full screen borderless perform mode, opening other window comps with hot keys or buttons causes a brief popping in the entire interface (including output). This doesn’t happen when the UI is even one pixel smaller than the screens resolution (i.e. 3840 x 2159), but if the window comp is set to fill, or the comp is the exact size of the output screen, this happens.

Wondering if that’s a Windows thing or a TD thing, figured I’d bring it up

2

actually, it looks like obs doesn’t accurately capture the floating windows on this screen, which is weird since im capturing a display, but what should be shown whiile its dark in the video is floating windowCOMPS i use often popping up over the UI like in the second half of the video where it does it with no problem if I have borders enabled

3

I think this has to do with exclusive mode when your project is full screen. Tagging a developer to get back to you.

Best,
Michel

4

This is expected behavior between the OS and the GPU driver. This occurs when we gain/lose exclusive access to the desktop display. When we have exclusive access it means all of the frames we are rendering will always get shown to the display. When you aren’t in exclusive mode then Windows Compositor can (and often will) decide not to update our window with a new frame we’ve provided it. If you arn’t seeing this flash when going into perform mode, then you output can have visual framedrops that arn’t accounted for anywhere.

5

What would be the best practice for a full screen borderless UI that also needs to have pop up dialogs?

How do I dynamically set the size of my window to be full screen, observing dpi scaling, without getting these pops? The pops are absolute deal breakers, I have a hard time believing there’s no supported workaround

6

The only way is to have the pop-ups be part of your UI, rather than another window. We have a long standing RFE to add an Overlay COMP that would aid with this, but it’s not done yet sadly

7

maybe there’s an argument that can be added to the default ways of opening windowCOMPs to behave as children of the perform window interface when in perform mode?

8

Yeah when the Overlay COMP comes, then a way to make that automatically used for things previously setup with Window COMPs when in perform could make using the best configuration easier

1 Like