Hello,
I have been having trouble getting the trigger "Process Created" and "Process Ended" working at all. This has been an issue for me for months now, and have now encountered the same thing on a new PC. For most situations, I have been able to get around it by using "Window Created" & "Window Destroyed".
Unfortunately for me, this does not seem to work for fullscreen applications, which I am now confronted with.
I have read through this thread on the subject, however I'm fairly sure that my case is different.
You should find the log files attached to this, I have reproduced the issue around 19h30.
Precisely, in order :
1-Cleared DisplayFusion logs
2-Opened [application].exe
3-Loaded [application] into fullscreen
4-Loaded [application] out of fullscreen
5-Closed [application] normally
6-Opened [application].exe
7-Closed [application].exe normally
8-Opened [application].exe
9-Force closed [application].exe using task manager.
None of these steps triggered any trigger results using "Process Created/Ended"
Doing the same with "Window Created" correctly triggers, but fullscreen unfortunately triggers the "Window Destroyed" trigger, even after setting a delay to check for the correct and new conditions of the fullscreen application (which has the exact same process name and window title contents).
What I would like to happen is quite simply use the triggers to load and unload a particular monitor profile while the process is running, regardless of whether or not it is in fullscreen.
Thanks in advance for your help !

Sure thing.

Neither the window text nor the Window Class seems to change when switching to or from fullscreen in the application I am using.
The window title does change when loading a file in this application, but it adds on more to the base text.
These two parameters are blocked out on "Process Created", though, so I had to use "Window Created" to find this.

Understood, thanks for looking into it.
Is the "Process Created" trigger not working only for me, then ?

I'm aware about the window created being a potencial workaround, but I'm still confused as to why the process created doesn't seem to work.
It's not important if there's truely nothing that can be done, I'm simply curious.

Oh, that makes sense !
I tried out a bunch of different processes, and some other programs behaved in a similar way to what I described above, but many did work completely as intended.
When I tried this a couple months ago with two other applications, neither of them worked with process created, only window created, so I assumed process didn't work correctly.
This makes things a lot clearer, thank you !