Just to clarify this for anyone else if you run into it,

even though the tag is different it will still trigger, but having them on a different layout does the trick,

Thank you.

Thanks Jean,

It seems you are correct.

I am using Adventure Creator and it is the hotspot detector causing this havoc.

I'll work around it,

Appreciated your swift response.

I think what you're describing is just the way Unity works:
http://answers.unity3d.com/questions/410711/trigger-in-child-object-calls-ontriggerenter-in-pa.html

It's the Unity solution for setting up compound colliders.

So the workaround might be the real solution, at least until Unity redesigns that system someday...

Makes sense, thanks for clarifying this and proving the links.

Awesome support.

I just want to confirm that adding a Rigidbody to the child solves this issue.

Scene: "parent" object, with a rigidbody and a capsule collider tagged as "Player".
Child object with a trigger on it as well (For other purposes) and not tagged as Player. (trigger covers more area than its parent, therefore its bigger)

Why does the trigger event on the Parent actually use the child as a trigger detection? The FSM is on the Parent itself, if this is a bug can you fix it please? or how can I?
If this is done purposely, how can I ensure that it only uses the parent for this specific FSM / trigger event...?

Thank you.

Try resetting preferences (bottom right corner of the editor -> Restore Default Settings). Or add a new state to try to reset the graph bounds.

Did both, but the states still stay all the way high up to the left corner.

What happens when you try to move the states? Do they keep their position?
Do you have a backup from before the states moved to the origin?

They do move around, just too much to move... no backup

If nothing works, you can export the template in a unitypackage and email it to me, and I'll take a look...



So I took it up on myself to literally copy paste peach state and re-connect them according to what it was before, which took quite sometime, but after I completed delete the ones that were way up there, re-opened playmaker window and now its nice and zoomed in as it once was. Just gonna have to go over it to see if any other weird things now are happening,

but honestly this should not be happening in the 1st place, please notify Jean or however to at least make an option where you can select a state and move it to the default start state, this is truly a pain hopefully I never ever have to experience this again.

Thanks for the help.



For example when I re-opened the PM Window it debugged this:

PlayMaker: Fixed Graph View bounds!
UnityEngine.Debug:LogWarning(Object)
HutongGames.PlayMakerEditor.FsmGraphView:SanityCheckGraphBounds()
HutongGames.PlayMakerEditor.FsmEditor:SelectFsm(Fsm)
FsmComponentInspector:OpenInEditor(PlayMakerFSM) (at Assets/PlayMaker/Editor/FsmComponentInspector.cs:300)
FsmComponentInspector:OnInspectorGUI() (at Assets/PlayMaker/Editor/FsmComponentInspector.cs:69)
UnityEditor.DockArea:OnGUI()



Why can't i do that manually?

Okay I just used my "secure" link to download the update, so how do I fix my FSM template with the states in the corner

C'mon there's gotta be some button or some shortcut you can press to move them back at least near the default start state... this is absurd.

 

PM version still says 1.7.7.f6

then I tried updating from the asset store, and the same version shows up,


I still have the issue though... 

I wish this wasn't significant but its a major template that I've been working on for quite some time now... its literally the brains of it all, almost all.

Jean help