Hi,
yep, that's tricky. It's typically something you can only debug with the following:
- make a copy of your project, and work on debugging on that copy until you found out exactly what's wrong.
- turn features either all off and enable them one by one until it crashes then you know which feature it the problem or turn feature off one by one, either way.
- once you know what is the fsm that causes the trouble, then you need to check which action or sequence is the issue, with this you will need to pause and step forward until you can figure our, if it's a loop, you will see this as you constanly keep getting into the same cycle, else it will crash at one particular step as you enter a new state.
Let me know how this goes. Yes this is painfull
I have been there many time
also, it helps trying to soft debug by simply go over each fsm and logic and think hard about what it does and what could be wrong here, typically maybe you are trying to access a gameobject instance that is not there anymore, or something like that.
Bye,
Jean
