How to prevent scene NetworkObjects from auto Spawning ?

[Marc477]

I have a scene with thousands of NetworkObjects, but only a few of them needs to be active at a time.
If they are not spawned, everything would work smoothly, but scene objects are spawned automatically according to :
https://docs-multiplayer.unity3d.com/netcode/current/basics/object-spawning/index.html

How do I prevent this from happening? Is there a variable on the NetworkObject to prevent auto spawning?
Otherwise I don't see how it's possible to use Netcode with a large number of NetworkObjects.

I'd like to be able to call NetworkObject.Spawn() myself and manage which ones should be synced. Instead of spawning everything and lagging the game. Anyone knows how to do this?

EDIT
I tried to use CheckObjectVisibility, but the network code still loops on those objects every network tick, because those objects are still in the SpawnedObjects array, affecting performance. When an object isn't Spawned this does not happen. So I really need a way to not Spawn scene objects automatically.

[TheCaveOfWonders]

Disabled game objects won't spawn. So have them disabled, and then only enable the ones you want.

[Marc477]

So i tried disabling inside the Start() function and it doesn't work, it will spawn and sync right away.

Disabling in the Awake() function works, it prevents the Spawn, but then if I call Spawn() later (i tried from the component UI on the server by clicking on Spawn) it doesn't sync the object with the one already existing on the client scene.

So in other words, it's impossible to Spawn() an object that was already in the scene if it was disabled during awake.

[NoelStephensUnity]

@Marc477
I am converting this feature to a bug as you should be able to set the GameObject with the attached NetworkObject component as in-active. After looking at where the disconnect is, I realized that there is an issue with this.

[NoelStephensUnity]

This issue will be resolved in the next update.

[Marc477]

Cool, will it also be possible to Spawn() an object that was previously Despawn() ? So Spawn() and Despawn() at will without destroying the object ? So it keeps running on the server, but not on the client. And only sync with client under certain conditions. I think before there were issues with Spawn() an object that was previously Despawn()