Possible 'Update Project' Problem (Vague)

[tsegordonParticipant]

Hi there, apologies for how vague this is, I’m trying to work out a pattern but not having much luck, and our project is pretty large so I can’t just send it all.

We upgraded to the latest NC from the Asset Store (how can I tell which version I had previously?). The Update Project button appeared on the FSM Owner so I hit that and it went away and touched all the scene files in our project and I’m able to Edit FSM on them all now if I load them in the editor, which is great.

However, on some scenes, if I load them in with SceneManager.LoadSceneAsync(levelName, LoadSceneMode.Additive); at runtime the FSMs seem to be empty. This all worked fine pre-upgrade.

If I load one of those problem scenes into the Editor and make a minor change to the FSM, and save, then I can LoadSceneAsync it happily.

Beyond that I’m not really sure what’s going on, or why…

I can pull a few versions of a problem scene file from our Perforce if that might help? Doing a text diff doesn’t show anything too crazy looking, although I’m suspicious that there’s a

_graph: {fileID: 1175852005}
that becomes _graph: {fileID: 0}
when I do the Update Projects, and then goes to _graph {fileID: 1493448698} when I manually update and re-save the FSM, but I have no idea if I’m barking up the wrong tree here.

Let me know if there’s anything I can do that might help you track down what’s happening.

[GavalakisKeymaster]

Hello,
Hmm. I think I know what is the problem here.
Can you please open up GraphOwner.cs and replace the code in Awake() with the following and let me know if everything works correctly for you?

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

protected void Awake(){ if ( !string.IsNullOrEmpty(boundGraphSerialization) ){ if (graph == null){ graph = (Graph)ScriptableObject.CreateInstance(graphType); graph.Deserialize(boundGraphSerialization, true, boundGraphObjectReferences); instances[graph] = graph; return; }   graph.SetSerializationObjectReferences(boundGraphObjectReferences); }   graph = GetInstance(graph); }

Thanks in advance.

[tsegordonParticipant]

That seems to have done the trick, thanks! We’ll keep a close eye on it for a few days and let you know if we spot any problems.

[GavalakisKeymaster]

Thanks!
Yes, please do let me know if you find any other issues!

[patientzerogamesParticipant]

I had the same problem (will try your new code to see if it fixes it).
Another thing I noticed is that if you create a new nested FSM the created .asset file does not get automatically assigned to the SubFSM anymore. It’s just a minor problem but still somewhat annoying.

[GavalakisKeymaster]

Hey,
Hmm. I cant reproduce this problem. When I hit “Create New” in the nested FMS node, The newly created FSM is automatically assigned as well.
Do you get any errors at all in the console?

Thanks.

[Author]

Posts