DisplayFusion RSS: Triggers: Process created/ended firing multiple times

RE: Triggers: Process created/ended firing multiple times

Binary Fortress Software — Mon, 20 Jun 2022 14:44:37 GMT

No worries, glad to hear that's mostly working. We will definitely post an update if/when we're able to add a cooldown timer to the triggers.

Thanks!

RE: Triggers: Process created/ended firing multiple times

Binary Fortress Software — Sat, 18 Jun 2022 16:47:39 GMT

I set it up to run when DF starts like you suggested. Aside from it occasionally not actually running when DF starts, it's been working perfectly for me. Until DF can be updated with some kind of trigger cooldown (as I had suggested before), this seems to be the best bandaid fix. Thanks for your help with this.

RE: Triggers: Process created/ended firing multiple times

Binary Fortress Software — Mon, 02 May 2022 15:05:35 GMT

The script is setup to run continuously in the background, so you can start it manually or have it run on a "DisplayFusion Starts" trigger.

You can add wait times to the script like this:

BFS.General.ThreadWait(3000);

So it would look something like this:

Code
Copy
Select All

BFS.DisplayFusion.RunFunctionAndWait("Function Name 1");
BFS.General.ThreadWait(3000);
BFS.DisplayFusion.RunFunctionAndWait("Function Name 2");

RE: Triggers: Process created/ended firing multiple times

Binary Fortress Software — Fri, 29 Apr 2022 23:03:25 GMT

Quote:

Ok, give this one a try. On line 36, set the function you want to run when the process has been detected (you can add more by copying that line).
On line 53, set the function(s) you want to run when the process is gone.
Hope this helps!

How do I set the function to constantly run in the background? And how do I add wait functions? (I've attached a screenshot of the trigger that has all the functions I need to run when Apex starts up.)

RE: Triggers: Process created/ended firing multiple times

Binary Fortress Software — Fri, 29 Apr 2022 18:18:18 GMT

Ok, give this one a try. On line 36, set the function you want to run when the process has been detected (you can add more by copying that line).

On line 53, set the function(s) you want to run when the process is gone.

Hope this helps!

RE: Triggers: Process created/ended firing multiple times

Binary Fortress Software — Fri, 29 Apr 2022 16:19:01 GMT

Quote:

I could write a scripted function that just runs in the background looking for the game process, when it finds the game process it runs your functions, then when the process goes away, it runs the other functions. If the script is set to loop every 10 or 15 seconds it shouldn't have much of an impact on CPU.

Do you want to try that?

Yes please, that would be great. Thank you.

RE: Triggers: Process created/ended firing multiple times

Binary Fortress Software — Mon, 18 Apr 2022 20:23:53 GMT

RE: Triggers: Process created/ended firing multiple times

Binary Fortress Software — Thu, 14 Apr 2022 17:30:20 GMT

Quote:

That's an interesting idea, I will check in with them on that.

Thank you. In the mean time, I need a reliable workaround. The Window Created trigger works flawlessly but Window Destroyed has never worked and I can't figure out why.

RE: Triggers: Process created/ended firing multiple times

Binary Fortress Software — Thu, 14 Apr 2022 17:16:13 GMT

That's an interesting idea, I will check in with them on that.

RE: Triggers: Process created/ended firing multiple times

Binary Fortress Software — Thu, 14 Apr 2022 16:36:25 GMT

I'm wondering if the devs have made any headway whatsoever in fixing this issue? It's gone from just being annoying to being a hinderance.
As of the last week, my triggers I use for Apex fire with an extremely long delay. I'm talking like a full 1 to 3 minutes (it feels like). Sometimes the trigger fires right when it should but one or two of the functions within the trigger don't fire till a few minutes later. It's now at the point of not being usable. This wouldn't be near as bad if these triggers didn't fire multiple times as Apex started up.
I have a suggestion for the devs that I believe would completely resolve my issue...
On my Android phone I use an app called Tasker. You use it to create Profiles that perform specified Tasks whenever specified Conditions are met. It's an extremely powerful and feature-rich automation tool. One of those features is the ability to enable a Cooldown Time on any profiles.
Here are a couple of screenshots:
TaskerCooldownTime1
TaskerCooldownTime2
As you can see in that second screenshot, the Cooldown Time's description says:
> The times after the profile has become active before it can again become active.
In other words, the profile can't fire again till the cooldown has ended.
Is there any way at all that the devs could implement a similar cooldown feature for triggers? I believe this would resolve my problem because with just a 1 or 2 minute cooldown, both the Process Started and Process Ended triggers wouldn't fire off a handful of times while Apex is launching.

RE: Triggers: Process created/ended firing multiple times

Binary Fortress Software — Thu, 20 Jan 2022 20:02:43 GMT

Finally had a chance to test out Halo: Infinite and I can't reproduce it with that either. I wonder what's different about our two systems but I can't think of what it could even be

RE: Triggers: Process created/ended firing multiple times

Binary Fortress Software — Tue, 07 Dec 2021 15:36:29 GMT

Ok thanks! I'll give that a try as well.

RE: Triggers: Process created/ended firing multiple times

Binary Fortress Software — Tue, 07 Dec 2021 14:53:06 GMT

Quote:

Ok, thanks for trying that out. Not sure why I can't reproduce it here any more, but if/when we're able to make the changes for checking process age, we'll be sure to let you know.

Thanks!

Ok. I have another game you could try to replicate this issue with... Halo: Infinite. The multiplayer is totally free and it basically behaves the same way as Apex.

RE: Triggers: Process created/ended firing multiple times

Binary Fortress Software — Fri, 03 Dec 2021 17:53:59 GMT

Ok, thanks for trying that out. Not sure why I can't reproduce it here any more, but if/when we're able to make the changes for checking process age, we'll be sure to let you know.

Thanks!

RE: Triggers: Process created/ended firing multiple times

Binary Fortress Software — Fri, 03 Dec 2021 16:38:28 GMT

Quote:

I had another thought on this, but for some reason I can't reproduce the multiple process start/end Triggers for Apex Legends any more.

If you change your "Process Created" Trigger to a "Window Created" Trigger, and set these two conditions:

Window Text: "Apex Legends"
Window Class: "Respawn001"

Does it still fire multiple times? Only looking to test to see if that fixes the trigger for starting Apex. If it does, I have an idea for fixing the trigger for ending Apex as well.

It does still fire multiple times but it's worse than the other one.

When using the Window Created as you instructed, it seems to run multiple times but does like half the job. The first time it triggers is when the Easy Anti-Cheat window is created, but it only runs the first action in the trigger (a custom function that toggles something on). Then when the actual Apex window is created, the trigger runs again, and runs every function. But then my first function gets toggled off since it ran prematurely when the Easy Anti-Cheat triggered the Window Created the first time around. At least when I use the Process Created trigger, it fires all my functions once (which runs some custom functions that toggle a few things on), then it runs the Process Ended (which runs a custom function that toggles those off), then it runs the Process Created again (which toggles them on as I want). The large majority of the time, all the functions I want to run end up do running the second time the Process Created is triggered.

RE: Triggers: Process created/ended firing multiple times

Binary Fortress Software — Thu, 02 Dec 2021 20:46:51 GMT

RE: Triggers: Process created/ended firing multiple times

Binary Fortress Software — Thu, 02 Dec 2021 19:25:53 GMT

Quick update on this. We have an idea on how we can make the process age condition work for this scenario and have added it to our list. We'll be sure to let you know if/when we're able to implement it.

Thanks!

RE: Triggers: Process created/ended firing multiple times

Binary Fortress Software — Thu, 28 Oct 2021 19:16:48 GMT

Ok, I was able to sort of reproduce this issue here. I'll do some more testing and see what I can find out.

RE: Triggers: Process created/ended firing multiple times

Binary Fortress Software — Thu, 28 Oct 2021 18:29:16 GMT

Quote:

Ok, so interestingly, I can't reproduce this issue. The Process Created and Process Ended triggers only fire once when I test it here, with or without the DF settings window open.
Do you have Apex Legends installed through Steam, or something else?

Steam

RE: Triggers: Process created/ended firing multiple times

Binary Fortress Software — Thu, 28 Oct 2021 18:25:00 GMT

Ok, so interestingly, I can't reproduce this issue. The Process Created and Process Ended triggers only fire once when I test it here, with or without the DF settings window open.

Do you have Apex Legends installed through Steam, or something else?

RE: Triggers: Process created/ended firing multiple times

Binary Fortress Software — Tue, 26 Oct 2021 15:51:55 GMT

Quote:

Not a clue, but I see that Apex Legends is free to play so I'm going to install it and do some testing here. I'll keep you posted on what I find out.

Ok, thank you.

RE: Triggers: Process created/ended firing multiple times

Binary Fortress Software — Tue, 26 Oct 2021 15:38:34 GMT

Not a clue, but I see that Apex Legends is free to play so I'm going to install it and do some testing here. I'll keep you posted on what I find out.

RE: Triggers: Process created/ended firing multiple times

Binary Fortress Software — Sat, 23 Oct 2021 16:36:27 GMT

Quote:

I can't think of a good way to achieve this with what's already in DisplayFusion. I'll add this to our improvements list and we'll see what we can come up with. If we're able to make some progress on it, we'll be sure to let you know.
Thanks!

Do you have any idea why the trigger works literally exactly as I want it to as long as one of the DF windows is open?

RE: Triggers: Process created/ended firing multiple times

Binary Fortress Software — Fri, 22 Oct 2021 18:00:40 GMT

RE: Triggers: Process created/ended firing multiple times

Binary Fortress Software — Wed, 20 Oct 2021 06:59:14 GMT

Quote:

Are you able to keep Task Manager open on another monitor while you launch the game? I'm wondering if the PID for r5apex.exe changes at all after you launch it? e.g. does it start as one number, then change again some time after it's opened?

Task Manager didn't work as I wanted it to but I did use ProcessExplorer. Your theory of multiple PIDs turned out to be correct.

As you can see in the two new screenshots I've attached, during just the initial Easy Anti-Cheat stage of launching Apex, an initial r5apex.exe PID starts only to be killed (PID 2088 in red) to make way for a new one that sticks around (PID 26548 in green).

What can be done about this? One idea that I could see working around this would be to make the Process Created trigger only match once the PID for a specified executable reaches a certain age. For example, have the Process Created only match once the PID reaches 20000ms in age (or whatever age I choose to input). Is this already a feature? If not, is there some other solution that we can come up with to solve my issue? (And why would this issue not be able to be reproduced whenever the DisplayFusion UI is open?)

DisplayFusion RSS: Triggers: Process created/ended firing multiple times

RE: Triggers: Process created/ended firing multiple times

RE: Triggers: Process created/ended firing multiple times

RE: Triggers: Process created/ended firing multiple times

CodeCopySelect All

RE: Triggers: Process created/ended firing multiple times

RE: Triggers: Process created/ended firing multiple times

RE: Triggers: Process created/ended firing multiple times

RE: Triggers: Process created/ended firing multiple times

RE: Triggers: Process created/ended firing multiple times

RE: Triggers: Process created/ended firing multiple times

RE: Triggers: Process created/ended firing multiple times

RE: Triggers: Process created/ended firing multiple times

RE: Triggers: Process created/ended firing multiple times

RE: Triggers: Process created/ended firing multiple times

RE: Triggers: Process created/ended firing multiple times

RE: Triggers: Process created/ended firing multiple times

RE: Triggers: Process created/ended firing multiple times

RE: Triggers: Process created/ended firing multiple times

RE: Triggers: Process created/ended firing multiple times

RE: Triggers: Process created/ended firing multiple times

RE: Triggers: Process created/ended firing multiple times

RE: Triggers: Process created/ended firing multiple times

RE: Triggers: Process created/ended firing multiple times

RE: Triggers: Process created/ended firing multiple times

RE: Triggers: Process created/ended firing multiple times

RE: Triggers: Process created/ended firing multiple times

Code
Copy
Select All