AstarPath component freezes additional editor instance

Hi,

I’ve just started developing a multiplayer game, and I’m still in the prototype process. I’ve come to a bug that seems to be related with the AstarPath component combined with the Multiplayer Play Mode package.

Currently, I have set it up so when I play the game in the editor it launches an additional editor instance, which acts as a client, while the main instance of the editor acts as the server (and also a client). The additional editor instance freezes, and this only happens when the AstarPath component is enabled at the start. If I run the game with the component disabled, the editor instance doesn’t freeze.

I’m not sure what could be the cause. The scene I’m currently testing on uses a single Recast Graph.

Any help is appreciated, thanks :slight_smile:

Update: After some more testing, I realized this behavior happens when AstarPath.scanOnStartup is set to true by default in the inspector. I’ve implemented a solution with a custom NetworkBehavior script that ensures this variable is set to false, and manually scan on awake only on the server. This fixed the issue for me. I’m still confused about why this happens tho :sweat_smile: