Behaviour Tree Disappears

[chrixParticipant]

While creating a behaviour tree (bound and as asset) all seems to work fine. After reloading the unity project (saved and closed before) the graph is empty and errors are displayed in the console like:

InvalidOperationException: Internal Deserialization Error – Object definition has not been encountered for object with id=11; have you reordered or modified the serialized data? If this is an issue with an unmodified Full Json implementation and unmodified serialization data, please report an issue with an included test case.
ParadoxNotion.Serialization.FullSerializer.Internal.fsCyclicReferenceManager.GetReferenceObject (System.Int32 id) (at Assets/ParadoxNotion/CanvasCore/Common/Runtime/Serialization/Full Serializer/Internal/fsCyclicReferenceManager.cs:61)
ParadoxNotion.Serialization.FullSerializer.fsSerializer.Internal_Deserialize (System.Type overrideConverterType, ParadoxNotion.Serialization.FullSerializer.fsData data, System.Type storageType, System.Object& result, System.Collections.Generic.List`1[ParadoxNotion.Serialization.FullSerializer.fsObjectProcessor]& processors) (at Assets/ParadoxNotion/CanvasCore/Common/Runtime/Serialization/Full Serializer/fsSerializer.cs:457)
ParadoxNotion.Serialization.FullSerializer.fsSerializer.TryDeserialize (ParadoxNotion.Serialization.FullSerializer.fsData data, System.Type storageType, System.Type overrideConverterType, System.Object& result) (at Assets/ParadoxNotion/CanvasCore/Common/Runtime/Serialization/Full Serializer/fsSerializer.cs:438)
UnityEngine.Logger:LogException(Exception)
ParadoxNotion.Services.Logger:ForwardToUnity(LogType, Object, String, Object) (at Assets/ParadoxNotion/CanvasCore/Common/Runtime/Services/Logger.cs:125)
ParadoxNotion.Services.<>c__DisplayClass15_0:<Internal_Log>b__0() (at Assets/ParadoxNotion/CanvasCore/Common/Runtime/Services/Logger.cs:113)
UnityEditor.EditorApplication:Internal_CallDelayFunctions()

I’m using Unity 2018.3.9f, NodeCanvas 2.9.1f.

Does anybody have similar issues or know where the problem comes from?

Thanks Chrix

 

[GavalakisKeymaster]

Hello,

I have been reported this critial problem more than once lately with Unity 2018.3.x, after about 2 years within which this problem neven existed. I begin to think that Unity changed something lately as far as when serialization callbacks are called. This is obviously a very critical problem and I am doing everything I can to reproduce this on my end as to determine what is the cause.

If you have any further information you can share, that would be fantastic. For example:

• Were there any prefabs involed?
• Were you using any Sub-Graphs?
• Are there any more cosole logs available that you can share?

Thank you.

[chrixParticipant]

Hi,

Unfortunately there were no prefabs or sub-graphs involved. It was a simple graph. Currently I’ve paused using NodeCanvas, but I’ve tried to reproduce the error.  Due to murphy`s law I couldn’t reproduce it until now. If there is more info I will let you know.

Thanks!

[GavalakisKeymaster]

Hello again,

Just want to let you know, that the bug was found and fixed. A new version is send to the asset store immediately after since it’s a very critical bug. If you want of course, I can send you the update to your registered email so that you don’t have to wait for the asset store to go live.

Thanks!

[chrixParticipant]

Great! I can wait for the asset store. Thanks a lot!

[Author]

Posts