Title

Message

Confirm

Want to earn a free DisplayFusion Pro license? We're looking for DisplayFusion translators!
<< DiscussionsReply

Window Destroyed Triggers Not Processing (worked previously)

Avatar from Gravatar.com
Dreamer3
16 discussion posts
I can't say for sure when this started because I haven't played too many games lately, but my triggers that I have used for years stopped working. The ones that trigger on window created still work fine, but not on the window being destroyed. I'm attaching L1 logs of me launching 3 games in a row without doing anything else. I am using Display Fusion 9.5 Beta 1.

These are for csgo.exe, tf2.exehl2.exe, and rainbowsix.exe
• Attachment [protected]: DisplayFusionDebugInfo.zip [75,500 bytes]
Jan 26, 2019 (modified Jan 26, 2019)  • #1
Keith Lammers (BFS)'s profile on WallpaperFusion.com
Could you attach a backup of your settings? (Settings > Options > Export)

Thanks!
Jan 29, 2019  • #2
Avatar from Gravatar.com
Dreamer3
16 discussion posts
Here you are. There shouldn't be any changes for the triggers since when they worked.

The process triggers seem to still work (the one I setup for Uplay closing does for example). My settings are a bit confusing because it's a bunch of rules I've setup over the years to accomplish different tasks and workaround problems different programs have had.
• Attachment [protected]: DisplayFusion Backup (2019-01-29 @ 16-54, 9.4.99.101, OPTIMUSPRIMEDES).reg [1,587,356 bytes]
Jan 30, 2019  • #3
Keith Lammers (BFS)'s profile on WallpaperFusion.com
Thanks! I noticed some of the Trigger rules have a Monitor Profile condition specified. If you take that condition out, does the Trigger work?
Jan 30, 2019  • #4
Avatar from Gravatar.com
Dreamer3
16 discussion posts
Removing the monitor profile condition seems to have worked, but not flawlessly. CSGO and R6 perform as I would expect, but TF2 (hl2.exe) doesn't. Sometimes the trigger happens when I close TF2 and sometimes it does not.

I launched the game 10 times (starting triggers processed properly each time, though they aren't looking for hl2.exe they are looking for the steam launch window). 5/10 times the game was not detected closing.

After that I ran the game 5 more times and L1 logged it (attached) where the same inconsistent behavior was observed.
• Attachment [protected]: DisplayFusionDebugInfo.zip [349,662 bytes]
• Attachment [protected]: DisplayFusionSettings_2019-01-30_16-41-39.png [33,131 bytes]
Jan 31, 2019 (modified Jan 31, 2019)  • #5
Keith Lammers (BFS)'s profile on WallpaperFusion.com
What if you use the "Process Ended" event instead of "Window Destroyed?"
Jan 31, 2019  • #6
Avatar from Gravatar.com
Dreamer3
16 discussion posts
Yeah, that works. I had feared it would have given me this (https://www.displayfusion.com/Discussions/View/nvidia-share-overlay-falsely-setting-off-triggers/?ID=ed43d65d-bf85-44fc-8857-347e044ed80e) problem again, but it appears to be good after 5 tests.

It wasn't working at first. I had to make sure to remove the window class because when you swap it to process ended, the window class section gets greyed out, but is it still looking for it?

Also, just to test I tried to do a window destroyed trigger to see if maybe Valve changed the window class for TF2, but doing it that way still didn't process properly, and it reintroduced that Share Overlay problem I dealt with 2 years ago.

Luckily, it appears by just shifting to a process ended trigger I have no problems.
Jan 31, 2019 (modified Feb 1, 2019)  • #7
Keith Lammers (BFS)'s profile on WallpaperFusion.com
Ok, glad to hear that works! I'll check out that issue with the Window Class in the Process Ended Trigger as well.

Thanks!
Feb 1, 2019  • #8
Keith Lammers (BFS)'s profile on WallpaperFusion.com
Just a quick follow-up to let you know that I was able to reproduce that issue with the Window Class in the Process Ended Trigger and have added it to our list to fix up.

Thanks!
Feb 6, 2019  • #9
Was this helpful?  Login to Vote  Login to Vote
<< DiscussionsReply