Scene Object Not Spawning on Scene Load

I am referencing this page of the docs.

Then, when the scene is fully loaded, NetworkServer.SpawnObjects() is called to activate these networked scene objects. This will be done automatically by the NetworkManager when the server scene finishes loading...

I am not seeing this behavior in 5.2.1f1.

I load a scene (on the host) that has an object with a network identity attached. That object is disabled when the scene finishes loading. It is not being activated, as I believe it should, based on the documentation. In the prior scene I have a Network Manager that is not unloaded with the scene (so it is still active on scene load).

Can anybody shed some light on my issue?

 

Bump. I'm stumped.

 

Here is a very very simple example. Start the host, then click the button to load the next level.

Per the documentation, when the scene is finished loading, the host should activate the cube (which has a Network Identity).

https://dl.dropboxusercontent.com/u/4231220/DemonstrateNotActivating.unitypackage

 

Same behavior in 5.2.2f1.

Can anybody besides me reproduce this? Is it a bug or is my project not doing things the way it should?

 

@seanr
Thanks for the reply. I tried moving the object to be a root object, and the issue remains. Modified demo project at...

https://dl.dropboxusercontent.com/u/4231220/IssueWithNetworkObject.unitypackage

 

I have the same issue. My scene objects do not automatically load either (On the LocalHost they are enabled, but on LocalClient they are disabled and never "spawned"). They have NetworkIdentity on the root of the object and the documentation says sceneObject spawning should be automatic... so I'm not exactly sure what is going wrong.

As a solution I have a persistent singleton object with this code that seems to fix it. Unsure why this bandaid is needed though, I feel like I'm not doing something right or there is some bug preventing things from spawning (I've had issues with NetworkTransform and SyncList's preventing scene objects from spawning. http://forum.unity3d.com/threads/bug-synclistfloat-crashes-networkanimator.361187/).

In any case create a persistent object and slap this code on it and see if this fixes your issue.

Code (csharp):

1.  
2. private void Awake()
3. {
4.    DontDestroyOnLoad(this);
5. }
6.  
7. private void OnLevelWasLoaded(int level)
8. {
9.    if(isServer)
10.    {
11.       NetworkServer.SpawnObjects();
12.    }
13. }
14.  

 

@Zullar Thank you very much for your workaround. I'll wait for @seanr to reply, but then I think I will report this as a bug.

 

@Zullar

I tried your workaround and I only have partial success. The object is activated on the LOCAL client. However, on remote clients it is still disabled and I get an error:

Spawn scene object not found for 1
UnityEngine.Networking.NetworkIdentity:UNetStaticUpdate()

 

OK. Few more questions.
-Are you using a custom NetworkManager?
-Are you using NetworkTransform?
-Are you using SyncLists?

Somehow for me it seemed these things affected the spawn messages that are sent (not 100% sure). I saw really strange things. Doing things like deleting my SyncList would cause sceneObjects to spawn properly, or re-arranging components in the object heirarchy could also turn the scene object spawning problem on/off. If we can pinpoint the exact scenario that is causing our sceneObjects to fail to spawn then hopefully SeanR can help fix the bug.

 

In my actual project I am. But in my example scene (linked to above) I am not.

No, I am not.

In my actual project I am. But in my example scene, I am not.

 

I'll grab the patch and try with my project linked above.

@seanr BTW, did you test w/ my project?

Thanks

 

First off, thank you @seanr for looking into this matter. I appreciate the support.

I have downloaded 5.2.2p1 and it is an improvement. Now, the object is enabled on the local client. However, it is still deactivated on any remote client.

You can see this in my example project by building and running as host, then pressing the button to load scene two. Then, in the IDE, run and choose to be a client. Then click the button on the client to load the same scene. You will see the cube is created, but it is disabled.

If I remember correctly, it wasn't even being enabled on the local client, so this is an improvement. I guess I should check the bug list and see what was included in p1. Maybe I can find the existing bug and add this info.

 

The only fix in the patch that may be related, that I can see is this one. Otherwise I don't know what changed the behavior with the local client.

 

@seanr If you make one change to LoadIt.cs...

Code (CSharp):

1.     public void OnClick()
2.     {
3.         //Application.LoadLevel(1);
4.         NetworkManager.singleton.ServerChangeScene("Scene Two");
5.     }

Then build and run as host. Scene Two is loaded and cube is active on local client. Then run in the IDE and choose client. Upon being connected this remote client automatically loads Scene Two, the cube is present but still disabled.

 

@seanr
Do you have a working example I can import? As of now, I haven't see it work properly and plan to file it as a bug.

Thanks

 

@seanr

With a little more tinkering, I think I determines why I see the bug and you don't. We were doing things in a different order.

But will NOT surface if you do things in this order:
1) Run EXE
2) Start Host on EXE
3) Start Client in IDE
4) Connect client
5) push button

But will surface if you do things in this order:
1)Run EXE
2) Start Host on EXE
3) Push button
4) Start Client in IDE
5) Connect client

So, if a client is NOT connected and the host loads a scene, when the client connects it will load the scene, but will not activate scene objects.

If I client is connected and a host loads a scene, the client will load the scene and activate the scene objects.

So, I will just make the necessary adjustments in my actual game.

@seanr Thanks for your assistance.

 

Tinjaw, does your NetworkManager call Awake()? If so this seems to override the parent Awake() method which initializes everything. This causes problems... it took me forever to figure out. Made a post here.
http://forum.unity3d.com/threads/unet-scene-objects-not-spawning-w-custom-networkmanager.369236/

 

I'm still totally lost on this... In a persistent world game the you always run into what Tinjaw points out above: the client connects after the level is loaded and none of the scene objects will enable "automatically" which is all the docs say.

putting a command to Network.SpawnObjects(); onto the player prefab being spawned with the newly connected player does not enable the objects.

In what situation is SpawnObjects() supposed to work?

To backup, I'm running 5.3.5f1. I have a single scene with the basic network manager in it. The scene has a tree that has a network identity (because it is interactable) and so is disabled for any clients that connect past the host player.

 

I think I am experiencing the same issue (Unity 5.5.1f1).
I have a project with a custom NetworkManager implementation, onlineScene is left unconfigured, and the host/server always changes the scene after it has started.
When a client connects, it switches to the new scene, but scene objects fail to spawn (remain deactivated) and I see errors similar to "Spawn scene object not found for 1".

Cause:
When a client is connected, OnClientConnect is called before processing scene change from the server.
With the standard NetworkManager, if onlineScene is not configured, this will result in ClientScene.Ready being called.
Because the client has reported ready, it will receive spawn messages while the new scene is still loading, and the spawn commands will fail.

Workaround:
Override OnClientConnect in the custom NetworkManager, do not call ClientScene.Ready and do not call the base implementation.
Rely on OnClientSceneChanged to call ClientScene.Ready and adding the player after scene has changed (in my project, the server always changes the scene).

 

For anyone else who comes across this problem make sure your networked scene GameObjects are set to active before you build the player!! Otherwise you will get these errors. I spent 3 hours trying to work that out.

 

I upgraded my Unity 5.4 project to 5.6 and started getting this issue.

helgewl's answer solved it for me Thanks

 

I have...
SceneTown (no networked objects)
SceneDungeon1 (many scene networked objects)
SceneDungeon2 (many scene networked objects)
SceneDungeon3 (many scene networked objects)

If clients connect while in Town then everything is OK. But if the players are in SceneDungeon2 and a new client connects I get all sorts of UNET errors. I'll have to try @helgewl workaround and post how it goes.

Should we bug report this?

 

btw if you've created a prefab with a network identity on it and forgot to add it to the NetworkManager spawnable prefab list before playing in the editor, as a host or client then you will need to delete the prefab, remove all the network components, make the prefab again, play the game, stop the game, put the network components back on and then add it to the spawnable prefab list. This will clear out the errors. And from my previous message also make sure it is set to active on build/play.

 

@Tinjaw

By the way ,I am not good in eglish.

Here is the solution:--

Check your lobby scene or "starting scene" or the scene where you click on "start host" / "join" that there is no such Gameobjects(in LobbyScene) contain "networkidentity", if you have any such Gameobjects(in Lobby Scene), then delete or remove "network identity" for this time and and run the game, this time you will get the Gameobject(in Play Scene) enabled in your "play scene" or "load scene" on client side.

 

Thank you very much for taking the time to message me with this information. I appreciate it.