Behavior infinite compilation

When editing Behavior Graphs, when saving the graph or hopping back to unity editor the Behavior starts a compilation that leads into a loop and a debbugind message related to BehaviorGraph.OnAfterDesserialize();

Sometimes the issue persists even when closing and reopening unity, leading to the graph window being open on editor start, and the same compilation loops happen

Unity 6000.0.30f1

Compilation Loop - The same erros repeat after every compilation


do you have custom nodes?

1 Like

Yes i do!
Some nodes with events and acess to external c# classes, do you think this is leading to the problem?

I don’t know. can you show the code of these custom nodes.

Hi @LucasBemol,

Seems like you’ve got a case where a graph module in graph asset is null. Not sure how this could have happened.

Could you try to delete the runtime asset of your graph? (You will need to reassigned the graph to your agents). Let us know if that solves the issue please.

Sorry for the inconvenience

1 Like

Currently whenever reopening unity editor it gets stucks in the same loop

I’ll keep trying to open it and avoid the bug somehow, but is there any other way I can delete the runtime asset without using the Editor?

edit: After deleting by windows explorer one of the subgraphs that was used on this graph on project folder i could open the project again and delete the main graph runtime assets

I’ll let you know if it the bug happens again, thanks!

1 Like

Thank you for the details, in case this is happening again, could you share with us the culprit graph assets?

I believe this is the first time this issue is reported, if you have any more insight about what step you might have taken to get into that state, please feel free to share more here :slightly_smiling_face:

Thanks

1 Like

After deleting all old Muse.Behavior graphs all the console errors are gone, I already deleted all old muse custom actions and I am currently working on “porting” then to the new behavior version since they were incompatible, so I think maybe the issue was related to upgrading the project from Unity 2022.3.6 to unity 6 and keeping the old muse behavior graphs and leading behavior to manipulate this old .asset files.
Hope this is usefull! as said I will keep you informed!
Thanks again

Oh yeah that would explain a lot!

Behavior had a big backend overhaul for 1.0, especially around graph asset and blackboard, so we highly recommend recreating graphs that was made using Muse Behavior.
We didn’t had time to implement a proper upgrade path for the assets and some underlying data might still be corrupted.

Sorry for the inconvenience :grimacing:

1 Like