PlayMaker Help & Tips > VR Help
States and Events?[SOLVED]
mic1991:
Hi guys,
I can't get the second state to move to the third state in this FSM, does anyone know what I'm missing?
Playmaker version 1.9.0.p4
Unity 2018.1.9f1
Broken Stylus:
The second state is looking for iTween to send a confirmation event at the end of the move.
So, is your pipette reacting to your inputs, then actually moving and reaching its destination? Could be a problem in coordinates, or who knows, even the scale of the game object? Perhaps there's an issue with the placement of the object within a parent's hierarchy?
Test the action with a simple object before applying to the prefab and see if it works properly that way.
mic1991:
Hi there,
Thank you for the reply.
Yeah the pipette is literally just supposed to 'move to' a vector, it does that fine to be fair. I can't say what happens next in Playmaker, This is made for an Oculus Go and so I haven't managed to get that working in the preview, as I think it needs to detect the device for things to work.
I'll have a crack at a repro in a different setting. What's odd is I used a different second state ages ago, and it happily transitioned into that one.
mic1991:
--- Quote from: Broken Stylus on March 30, 2019, 12:35:09 PM ---The second state is looking for iTween to send a confirmation event at the end of the move.
So, is your pipette reacting to your inputs, then actually moving and reaching its destination? Could be a problem in coordinates, or who knows, even the scale of the game object? Perhaps there's an issue with the placement of the object within a parent's hierarchy?
Test the action with a simple object before applying to the prefab and see if it works properly that way.
--- End quote ---
Hi again,
Quick question, if I need to send confirmation, does that mean I should add another event to the second state, which is sent to the next state, and then have the state 'ended' by the iTween event not be sent to any state? If so, should I use the same event as the third state?
Broken Stylus:
--- Quote from: mic1991 on April 03, 2019, 08:20:31 AM ---
--- Quote from: Broken Stylus on March 30, 2019, 12:35:09 PM ---The second state is looking for iTween to send a confirmation event at the end of the move.
So, is your pipette reacting to your inputs, then actually moving and reaching its destination? Could be a problem in coordinates, or who knows, even the scale of the game object? Perhaps there's an issue with the placement of the object within a parent's hierarchy?
Test the action with a simple object before applying to the prefab and see if it works properly that way.
--- End quote ---
Hi again,
Quick question, if I need to send confirmation, does that mean I should add another event to the second state, which is sent to the next state, and then have the state 'ended' by the iTween event not be sent to any state? If so, should I use the same event as the third state?
--- End quote ---
The problem is that you need to keep an eye on the iTween. What you could do, if you know how long the tween is always going to last, is cheat by having a Wait action for example, that sends a custom event, but that's dirty. You should really look into the iTween action and the behavior of the game object controlled by it and see if the entirety of the tweening is completed. Sometimes Unity fucks things up with miserable decimals and that is enough to make a behavior fail.
Try another iTween action too. There is simply no reason why this action shouldn't detected the completion of the tweening process.
Navigation
[0] Message Index
[#] Next page
Go to full version