Unity 2023.2.2f1 , Muse Behavior 0.5.5. Happened last night, I would have to recreate the behavior graph and try to get the error again to get screen shots.
I had a Behavior graph that ran parallel two switches on enum. I was fleshing out the graph for states of the character. Eventually I started getting this JSON max read depth error, and then the graph would be empty when entering play mode or reopening.
I could undo, get the graph to display again, and close/reopen. The graph would display correctly, but adding any more nodes or functionality would result in the error and erasing the graph.
I eventually got to a point where I couldn’t undo and get the graph back. I can try to recreate the situation later.
Can you please try this again with 0.5.6? I remember seeing it internally and I believe it was fixed but I could be mis-remembering 
I rebuilt the graph in 0.5.6. Still getting the Error and odd editor behavior. When entering play mode with the error present, the behavior graph is cleared away with all nodes removed. The character still performs the nodes that were previously present until it reaches the node connection that caused the problem. After leaving play mode and reloading the Graph; all nodes and variables have been deleted. Oddly, you can ctrl-z / undo a few times and get the graph back.
If I add a different node to either branch the error shows up. This is the 10th connection down the behavior graph. I’ve gone to different parts of the graph and branched down to the 10th connection, the error seems to always show up after the 10th connection is made. It either shows up immediately, or on reload of the Behavior Graph.
Behavior Graph when JSON error starts showing up
Removing this Connection to Talk Node, and error goes away
With Console, no connection, no error
With Console, node connected, error
Full Error text.
JSON MaxDepth error.pdf (237.5 KB)
Thank you very much for this! I’ll investigate this
I believe I have a fix. I’m going to try and get 0.5.7 out today.
Edit: FYI I asked release management to publish 0.5.7 but I think they’re out for the day. I’ll let you know once they did it, it might be Monday, sorry!
