I’m experiencing a very strange problem in the latest version of the engine (4.12.3). My game is Blueprint-only.
It only occurs in this specific boss level, to my knowledge. For some reason, at random times during the level, all StateMachines in AnimBlueprints across the entire game will stop updating. They remain stuck on whatever State they were in, even if the variables controlling their Transition Rules have changed and should have triggered a state change.
What’s even stranger is that:
-The problem occurs completely randomly, but only in this level
-The variables controlling my States do appear to be updating correctly in the AnimBlueprint. The StateMachine just isn’t switching to the new state to reflect the new values.
-The problem becomes permanent unless I relaunch the whole game or editor. If I play the level with the options “Play->New Editor Window” or “Play->Standalone Game” in the UE4 editor, the effect becomes semi-permanent until I close the entire Unreal Editor and relaunch it. Once I’ve relaunched the entire editor, the problem is gone and my states work again.
-If I DON’T close the editor/game, then if I leave this boss level and enter another one, the problem persists even in other levels. Nothing changes animation states anymore, globally, until the game or editor is completely restarted.
Because the problem is happening to ALL AnimBlueprints in the game I am having a rough time debugging and figuring out where to even start looking for the cause. I have no idea what could possibly be causing ALL AnimBlueprints to screw up like this. It sounds like it could be a bug in the engine itself. Has anyone else encountered a problem like this? Any workarounds you can share? Is there’s a way to “reset” or trigger the StateMachines? I’ve tried setting the AnimMode to Asset and then back to Blueprint to see if that would reset the but it doesn’t. And even if there is a way to do this I don’t think it would be feasible for me to have reset the States for every little animated thing in the game.
I’m posting this here in addition to the AnswerHub just in case some other devs here might be able to offer a workaround. My game is inching closer to being finished but this problem is unfortunately putting a halt to everything.