Quantcast
Viewing all articles
Browse latest Browse all 42

Are those orphaned states in my animation controller file?

There appears to be orphanned States in our animation controller file that are not displayed anywere in mecanim.

I found them when adding a debug.log output in the AWAKE section of a state machine behavior script to identify all the states were running the script in question.

When comparing the output of the console with all the states in the controller, there were more states initializing the script than suposed too.

Those extra states cannot be accounted for in any layers of the state machine. The only way to find them is to change unity's settings to serialize using text and to edit the controller file in notepad.

Some references appear to be broken in there. Makes me wonder what else could be wrong and how it affects our game. I suspect this may have something to do with collaborate being a b.... I mean itself.

**TLDR starts here**

**Here is a list of the orphaned entries I found in the animator controller file:**
scriptID name stateID state_name StateMachineID 114255904428394936 null 102833571480362396 6_Rifle ? 114307809870742404 null ? ? ? 114317491474646124 null 1102982001319280668 ClimdOnTop 1107996217619549848 114375502922679620 null 1102803319237603968 3_Katana ?
**Except for the 3rd state in the list all those states have empty references for:** - AnimatorStateMachine_Name - TransitionID - Transition_name

**The third states extra info is as follow:**
- AnimatorStateMachine_Name : ClimbOnTop 0 - TransitionID: 1101855164678388034 - Transition_name: null

**The Question:**
What's going on in there and what should/can I do about it?

**Please help, thank you.**

Viewing all articles
Browse latest Browse all 42

Trending Articles