DisplayFusion RSS: Nvidia share overlay falsely setting off triggers https://www.displayfusion.com/Discussions/RSS/?TopicID=ed43d65d-bf85-44fc-8857-347e044ed80e DisplayFusion RSS: Nvidia share overlay falsely setting off triggers Tue, 05 May 2026 16:07:57 GMT en hourly 1 https://www.displayfusion.com/Discussions/RSS/?TopicID=ed43d65d-bf85-44fc-8857-347e044ed80e RE: Nvidia share overlay falsely setting off triggers https://www.displayfusion.com/Discussions/View/nvidia-share-overlay-falsely-setting-off-triggers/?ID=ed43d65d-bf85-44fc-8857-347e044ed80e#10 Tue, 29 Nov 2016 19:23:47 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/nvidia-share-overlay-falsely-setting-off-triggers/?ID=ed43d65d-bf85-44fc-8857-347e044ed80e#10 DisplayFusion Excellent, glad to hear it! ]]> RE: Nvidia share overlay falsely setting off triggers https://www.displayfusion.com/Discussions/View/nvidia-share-overlay-falsely-setting-off-triggers/?ID=ed43d65d-bf85-44fc-8857-347e044ed80e#9 Fri, 25 Nov 2016 22:47:59 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/nvidia-share-overlay-falsely-setting-off-triggers/?ID=ed43d65d-bf85-44fc-8857-347e044ed80e#9 DisplayFusion
Quote:
Nuts, it seems like the NVIDIA overlay uses a bunch of different (sometimes random) window classes.

What about if you change the Window Class condition from:

Code
Copy
Select All

-"CEF-OSR-WIDGET"


to:

Code
Copy
Select All

"Valve001"


If I read the log correctly, that seems to be the window class for the actual CS:GO window, so that should make the rule only match that window.


This works as far as I can tell. Thank you. ]]> RE: Nvidia share overlay falsely setting off triggers https://www.displayfusion.com/Discussions/View/nvidia-share-overlay-falsely-setting-off-triggers/?ID=ed43d65d-bf85-44fc-8857-347e044ed80e#8 Fri, 25 Nov 2016 20:41:21 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/nvidia-share-overlay-falsely-setting-off-triggers/?ID=ed43d65d-bf85-44fc-8857-347e044ed80e#8 DisplayFusion Nuts, it seems like the NVIDIA overlay uses a bunch of different (sometimes random) window classes.

What about if you change the Window Class condition from:

Code
Copy
Select All

-"CEF-OSR-WIDGET"


to:

Code
Copy
Select All

"Valve001"


If I read the log correctly, that seems to be the window class for the actual CS:GO window, so that should make the rule only match that window. ]]> RE: Nvidia share overlay falsely setting off triggers https://www.displayfusion.com/Discussions/View/nvidia-share-overlay-falsely-setting-off-triggers/?ID=ed43d65d-bf85-44fc-8857-347e044ed80e#7 Fri, 25 Nov 2016 19:40:05 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/nvidia-share-overlay-falsely-setting-off-triggers/?ID=ed43d65d-bf85-44fc-8857-347e044ed80e#7 DisplayFusion 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. ]]> RE: Nvidia share overlay falsely setting off triggers https://www.displayfusion.com/Discussions/View/nvidia-share-overlay-falsely-setting-off-triggers/?ID=ed43d65d-bf85-44fc-8857-347e044ed80e#6 Fri, 25 Nov 2016 19:20:09 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/nvidia-share-overlay-falsely-setting-off-triggers/?ID=ed43d65d-bf85-44fc-8857-347e044ed80e#6 DisplayFusion The debug log might have the details I need. Could you try this?
  • On the DF Settings > Troubleshooting tab, change the Logging drop-down to "L2: Log Detailed" and click Apply
  • Reproduce the issue and note the time so we'll know where to check in the log file
  • Send us the DisplayFusion.log and DebugInfo.html files (can be found by clicking the Open Log button on the Troubleshooting tab)
  • Disable debug logging after sending the log

Thanks! ]]> RE: Nvidia share overlay falsely setting off triggers https://www.displayfusion.com/Discussions/View/nvidia-share-overlay-falsely-setting-off-triggers/?ID=ed43d65d-bf85-44fc-8857-347e044ed80e#5 Fri, 25 Nov 2016 04:12:32 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/nvidia-share-overlay-falsely-setting-off-triggers/?ID=ed43d65d-bf85-44fc-8857-347e044ed80e#5 DisplayFusion 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? ]]> RE: Nvidia share overlay falsely setting off triggers https://www.displayfusion.com/Discussions/View/nvidia-share-overlay-falsely-setting-off-triggers/?ID=ed43d65d-bf85-44fc-8857-347e044ed80e#4 Thu, 24 Nov 2016 21:38:05 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/nvidia-share-overlay-falsely-setting-off-triggers/?ID=ed43d65d-bf85-44fc-8857-347e044ed80e#4 DisplayFusion Thanks! I can't imagine why the trigger would be firing on that window, as it seems to be running under its own process.

If you add the following to the Window Class box in the Match Conditions of the Trigger, does that solve it?

-"CEF-OSR-WIDGET" ]]> RE: Nvidia share overlay falsely setting off triggers https://www.displayfusion.com/Discussions/View/nvidia-share-overlay-falsely-setting-off-triggers/?ID=ed43d65d-bf85-44fc-8857-347e044ed80e#3 Mon, 21 Nov 2016 23:37:42 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/nvidia-share-overlay-falsely-setting-off-triggers/?ID=ed43d65d-bf85-44fc-8857-347e044ed80e#3 DisplayFusion 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. ]]> RE: Nvidia share overlay falsely setting off triggers https://www.displayfusion.com/Discussions/View/nvidia-share-overlay-falsely-setting-off-triggers/?ID=ed43d65d-bf85-44fc-8857-347e044ed80e#2 Mon, 21 Nov 2016 21:44:16 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/nvidia-share-overlay-falsely-setting-off-triggers/?ID=ed43d65d-bf85-44fc-8857-347e044ed80e#2 DisplayFusion It sounds like the NVIDIA share overlay might be running under the game's process. Would you be able to install one of our other apps, Window Inspector, and send me the info for that NVIDIA share overlay? Here are the steps:
  • Launch Window Inspector and your game
  • Hover your mouse over the NVIDIA share overlay
  • Press Ctrl + Shift + F2 to save the info
  • Send me the HTML file that it creates
]]> Nvidia share overlay falsely setting off triggers https://www.displayfusion.com/Discussions/View/nvidia-share-overlay-falsely-setting-off-triggers/?ID=ed43d65d-bf85-44fc-8857-347e044ed80e Sun, 20 Nov 2016 08:08:23 GMT Binary Fortress Software https://www.displayfusion.com/Discussions/View/nvidia-share-overlay-falsely-setting-off-triggers/?ID=ed43d65d-bf85-44fc-8857-347e044ed80e DisplayFusion 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. ]]>