Error with Network Prefab Hash not Found for Prefabs in Duplicated Scenes

[Moe-Baker]

Description

When loading a network scene, I get errors in the format:
[Netcode] NetworkPrefab hash was not found! In-Scene placed NetworkObject soft synchronization failure for Hash: ###########!.
This results in network objects not spawning.
This error occurs for prefabs instances placed in duplicated scenes.

Reproduce Steps

1. Create a prefab with a NetworkObject component attached.
2. Create a scene and place the prefab inside it.
3. Duplicate the scene from inside Unity.
4. Open the original scene & note the prefab instance's globalObjectHashWhatEver from the inspector
5. Play the scene directly, and note the hash not changing.
6. Open the duplicate scene & note the prefab instance's hash.
7. Play the scene and note the hash changing.

I suspect this is what causes my errors, which, by the way, occur when connecting a Windows editor client to a Linux player (executable) server, but not when connecting two Windows editors (Parallel Sync) client/server together.

Environment

• OS: [Windows Client & Linux Server]
• Unity Version: [6000.0.40f1]
• Netcode Version: [2.3.2]

[NoelStephensUnity]

Hi @Moe-Baker,

This should not happen as long as the scenes in build list is the same for the Linux server build as it is the Windows client builds.
If you want to duplicate a scene, then you should make sure to open it at least once to allow for serialization of the assets specific to that scene to occur.

Of course, if you are duplicating a scene to just have another version loaded without any changes to the duplicate scene then I would recommend just loading the scene being duplicated additively which allows you to load that scene (n) times all with unique in-scene placed NetworkObject instances.

I tried replicating your issue, but could not, using the below project:
InScenePlacedSceneLoading.zip

As a side note, I would recommend using MPPM as opposed to Parrel Sync as MPPM will assure that the AssetDatabase for all virtual client instances is kept synchronized.

If you can provide additional details about how you are building your linux server vs the windows server as it applies to your replication steps that might help me replicate the issue.