Processing Ajax...

Title
Close Dialog

Message

Confirm
Close Dialog

Confirm
Close Dialog

Trigger - Can't get process ended to work

User Image
mrl72
3 discussion posts
I have a trigger set up as follows:

Process Ended.
Frequency: Always
Match conditions:
Process filename "K:\LaunchBox\BigBox.exe"
Monitor profile: Mame
Delay: 60000ms (1min)
Run function: Load monitor profile: Main

I run "K:\LaunchBox\BigBox.exe".
Switch to profile "Mame".
After exactly 30 seconds DF triggers and switches back to profile "Main".
K:\LaunchBox\BigBox.exe process is still running.

I have also tried using the windows destroyed feature and this doesn't work either.

Any help appreciated! (running v9.5)

From log:

2019/11/11 11:28:29.7148##_##INFO:L1##_##displayfusion.exe:8064##_##WindowProcess:WindowProcessTHISTHREAD:Static##_##-##_##Name: Load Monitor Profile: Mame##_##-

2019/11/11 11:29:05.6045##_##INFO:L1##_##displayfusion.exe:8064##_##DFTrigger:ExecuteActions##_##-##_##Trigger [GetTriggerMatchesAndRunTriggerActionsIfNeededWORKER]: Process Filename: 'K:\LaunchBox\BigBox.exe', Monitor Profile: 'Mame', Delay before checking match conditions (MS): 10000ms, Run Function: 'Load Monitor Profile: Main'##_##-
2019/11/11 11:29:05.6056##_##INFO:L1##_##displayfusion.exe:8064##_##DFTriggerAction:ExecuteAction##_##-##_##RunFunction##_##-
2019/11/11 11:29:05.6056##_##INFO:L1##_##displayfusion.exe:8064##_##WindowProcess:WindowProcessTHISTHREAD:Static##_##-##_##Name: Load Monitor Profile: Main##_##-
2019/11/11 11:29:05.6056##_##INFO:L1##_##displayfusion.exe:8064##_##WindowProcess:CTR##_##-##_##Source: Trigger, HotKey: 'Load Monitor Profile: Main', Window: Window is NULL##_##-
2019/11/11 11:29:05.6065##_##INFO:L1##_##displayfusion.exe:8064##_##MonitorProfiles:ActivateMonitorProfile##_##-##_##Main: ecef2b65-b9b7-48fd-8c3b-44449929e7c2, Reason: HotKey/TitleBarButton##_##-
• Attachment [protected]: Capture.JPG [58,953 bytes]
Nov 11, 2019 (modified Nov 11, 2019)  • #1
Keith Lammers (BFS)'s profile on WallpaperFusion.com
I wonder if that EXE is launching a second process and the first one terminates. Could you send over a debug log?

  • On the DisplayFusion Settings > Troubleshooting tab, change the Logging drop-down to "L1: Log Minimal" and click Apply
  • Reproduce the issue and note the time so we'll know where to check in the log file
  • Click the "Export Info to File" button on the Settings > Troubleshooting tab
  • Reply with the file attached
  • Disable debug logging after sending the log

Thanks!
Nov 13, 2019  • #2
User Image
xreaper
3 discussion posts
I'm facing the same issue, Bigbox does have a startup video that plays whilst the databases/cache are loading and that might be creating a new instance of bigbox.exe while terminating the previous one, meeting the trigger condition for process end when the program actually loads
Dec 6, 2019  • #3
Keith Lammers (BFS)'s profile on WallpaperFusion.com
Yeah, that would do it. What might work better is to use the Window Created/Window Destroyed Triggers. With those, you can try specifying the Window Text and/or Window Class to differentiate the splash screen from the main window.
Dec 9, 2019  • #4
User Image
xreaper
3 discussion posts
I know it has been a while but since then I created a work around for this issue and decided to post it just in case someone else comes across this problem.
So as I said a couple of years ago, Bigbox was creating several windows which triggered the "window destroyed" trigger.
Anyway, since I use autohotkey for a lot of stuff around here I created a script that launches bigbox, and renames the final window to what you want DF to look for as the "window destroyed" event.
;Press ctrl+alt+shift+p to change monitor profile then launch BigBox through Steam;
^!+p::
Send ^+2
Sleep 3000
Run steam://rungameid/11332905014558457856
WinWaitActive, LaunchBox Big Box
WinSetTitle, LBVideo ; Set Startup video Title
WinWaitActive, LaunchBox Big Box
WinSetTitle, LBFinal ; Set Final Window Title
return

This way, you set the "window destroyed" event's window name to "LBFinal".
You can change "Run steam://..." to "Run bigbox.exe" if you're not using steam
And you can also delete the "^!+p::" part and compile the script as an exe to have it as a standalone launcher.
Hopefully this will help anyone in the future that has come across this problem, and sorry for reviving such an old thread.
Feb 14, 2022 (modified Feb 14, 2022)  • #5
Was this helpful?  Login to Vote(-)  Login to Vote(-)