Hello!
I began noticing an issue where exposed FSM variables were not saving upon closing and opening my game project.
For example, I have a prefab instance with an FSM component. The FSM has several exposed variables I can change in the scene through the inspector. When I do so, save the scene, close and re-open Unity, the variables appear to have reverted to the prefab defaults. If I run the scene, the FSM behavior will reflect these default values. Furthermore, if I try to edit the variables, it will break the prefab connection.
After testing a few things, I found a workaround for the time being:
I can place a fresh prefab of that same game object into the scene and edit one of it's variables. Then when I re-load the scene (no saving necessary), I will find that the FSM variables in the problematic game object have returned to their modified values and the prefab connection is still intact. I am also free to change the variables with out fear of breaking the prefab connection.
While the problem returns every session, I don't necessarily have to perform these steps each time. If I skip a session and attempt the workaround in the following session, it will still repair the prefab instance. However, failing to do this workaround before building the project will result in the issue persisting into the build itself.
I've noticed this issue with one or two different prefabs with any type of variable but it does not seem to be effecting all game objects with FSM components.
Does this issue sound familiar to anyone? I'd really appreciate some insight on how to potentially fix this problem.
I'm using PlayMaker 1.9.0p20 and Unity 5.6.4f1
Thanks