So I use triggers a lot in order to get games to launch on specific monitors in fullscreen. It is incredibly useful for me because not all games allow me to specify which monitor they launch on, and always launch on the primary monitor. I have used this for months with no real issues until Nvidia updated Shadowplay to be this Share Overlay, which has some nice features of its own so I'd prefer to not revert back to the old one.

This is my basic setup for CS:GO in particular:
Launch: http://i.imgur.com/1CS3G27.png (no problem there)
Close: http://i.imgur.com/iwB0Psg.png

To be clear, closing the Share Overlay will only set-off the trigger while I am in CS:GO (in this case) so I assume the program sees it as me closing csgo.exe which is when the trigger is supposed to activate. If DisplayFusion is open the game flickers and changes monitor profiles, and if DisplayFusion is closed (or triggers are disabled) it functions normally without any flickers or noticeable changes. This behavior is also true for Team Fortress 2 where I use the same trigger setup.

As far as I can tell, it won't capture any information on the process because it's in exclusive fullscreen mode. I can capture information on the Share Overlay if I use [borderless] windowed mode, but it doesn't set off the trigger if it's using a windowed mode. That said, I much prefer to use exclusive fullscreen mode for competitive shooters due to the input lag windowed mode introduces.

Here are two Windows Inspector results using windowed modes, but I can't figure out a way to capture the Share Overlay in fullscreen mode.

I added -"CEF-OSR-WIDGET" to the Window Class and it did not work. What I figured out that if I run the game in a window then the Share Overlay does not set the triggers off, but it does while the game is in fullscreen. Is there a way I can capture the details of the Share Overlay while it is in fullscreen mode to better see what the difference is between the two modes? Having the Share Overlay up locks the mouse cursor to that monitor and prevents alt-tabbing. Also using Ctrl+Shift+F2 didn't work in fullscreen.

Or can I setup a script somewhere to make it so CSGO needs to be closed for something like >3 seconds in order to set off the trigger?

Ok so at the moment it is inconsistent. There should be a couple of times the trigger was falsely set off. The most recent was 13:36, but earlier times it sometime triggered and sometimes didn't so I tried a few times to get it to happen the first try I closed the Share Overlay.

EDIT: It seems like -"CEF-OSR-WIDGET" causes the inconsistency. With the trigger checking for it sometimes the trigger goes off and sometimes it doesn't. Without -"CEF-OSR-WIDGET" it always triggers.

This works as far as I can tell. Thank you.