Trigger Event: every frame option

[doppelmonster]

Hello,

I need the "Trigger Event" Action to test only one time and then leave the action, even when there is no collision. In the moment you are stuck in the action until a collision happened. So a "every frame" option would be nice.

My scenario:
in a Pool Billard like game the user should be able to place a ball after a foul (ball in hand). So i switch the collider to trigger and let the  ser place the ball. if he is ready i want to do a one time check if the user placed the ball intersecting another one on the table.

[escpodgames]

Have you tried using On Collison Stay? its an option on the Collison event. This should check if the collider is inside a trigger.

[doppelmonster]

Detecting a collision is not the problem. I would need a "no collision" event or just check once for collisions and if no collision happened,it should just go on in the state (like most of the actions by default do). I need the "every frame" option to be able to turn it OFF. Right now "every frame" is always turned on for "Trigger Event"....

[jeanfabre]

Hi,

 on the state where you use that action, have a "next frame event" action after it firing "FINISH" and you'll be set.

bye,

 Jean

[doppelmonster]

Hi Jean,
sounds good, that would be exactly what i need.

But unfortunately it dont work for me. Now the Trigger is not catching the collision anymore.
I attached a screenshot with my setup. Now even when there is a collision the "Nofoul!" event is triggered. Turning the "Next Frame" action off will catch the collision.

What i am doing wrong?

[jeanfabre]

Hi,

 well, it's likely ( if your set up is correct) that indeed it doesn't collide on that frame...

mybe in your case you need to split your fsm into two, one that listen always to collisions and dispatch a custom global event when it does detect the collision you expect and another fsm only implement that custom event and perform a task.

 I never had any cases in my projects where I needed to check for a collision one frame only... I don't really see any use case, what happens generally is that I maintain a boolean variable that I raise to true and false manually based on the TRIGGER ENTER and TRIGGER EXIT, or with the trigger event custom action, that that feature is one fsm doing just that and nothing else, and other fsm simply check for that boolean flag when they need too. It's a lot cleaner I feel.

 does that make sense?

 bye,

 Jean

[doppelmonster]

Hi Jean,
my FSM are already split like you said (Trigger Test, Gameplay Manager). But i have to put a "wait" action in my Gameplay Manager because i will get no event on "No Collision". In some cases this makes it unrelyable (is there some explanation, how much can be done (actions, States) in a frame cycle?).

I find one shot Trigger action (or "no collision" events) very usefull for things that should happen when you are outside the triggerzone.

For customizing the action you would only have to add an execution end to it, or? I already tried it myself but with no luck. Either the action is not executed at all(passes on but dont detect anything) or the action dont pass to the next action in the state.


The other Thing with the Trigger Event action is, that it should have a multiple tag  option (one guy (Maddox?) provided a custom action for Collision Event which has this feature).

Playmaker is already very great and i can do 99 percent with what is already there (including your support and custom stuff i find in the forum).

[jeanfabre]

Hi,

 do you have a ref to that action maddox did, I'll see what can be done then, cause I am not sure I understand where is the issue now.

bye,

 Jean

[doppelmonster]

 reagrding the multiple tag option:


http://hutonggames.com/playmakerforum/index.php?topic=229.msg902#msg902

[MAX_POWER]

Repeat interval could be added to the trigger event for optimization reasons. Basically similar which raycast has so that you could set a every nth frame value.