NoelStephensUnity
commented
1 year ago @FreshlyBrewedCode
Message Routing
Each NetworkObject instance has to have a unique NetworkObjectId. The reason is that any messages sent to each unique instance needs to know "which" unique instance.
- GlobalObjectIdHash--> Tells clients "what thing to spawn".
- NetworkObjectId ---> Is used in routing messages to the appropriate NetworkObject instance (which then is routed to a corrisponding NetworkBehaviour)
- NetworkBehaviourId --> Which NetworkBehaviour, associated with a NetworkObject instance (i.e. NetworkObjectId), that is sending/receiving a message.
Example: Two NetworkObjet instances of the same network prefab, with the same GlobalObjectIdHash value, would need unique NetworkObjectId values in order to be able to send/receive messages to their respective NetworkBehaviours. If you had two NetworkObjects with the same NetworkObjectId, then this process would break.
Alternate Approach
Have you tried just creating a "blank network prefab" where your dynamically instantiated GameObject for each mesh loaded is parented under the spawned instance of the "blank network prefab"?
The LoadMeshBehaviour script would handle letting the clients know what 3D mesh was associated with the instance and could be set on the server side.
The pseudo code example of that script:
using Unity.Netcode;
public class LoadMeshBehaviour : NetworkBehaviour
{
private void OnServerSerializeMeshInfo(FastBufferWriter writer)
{
// The server-host would write out the unique 3D mesh
// specific information pertaining to this instance here
// (i.e. path to asset or the like)
}
private void OnClientDeserializeMeshInfo(FastBufferReader reader)
{
// Clients would read the serialized 3D mesh specific information
// (i.e. path to asset or the like), and either load it at this point
// or store the information to be loaded when spawned locally
}
/// <summary>
/// Automatically invoked when:
/// Server-Side (Write): the associated NetworkObjet is being synchronized with
/// a joining client or spawned for the first time (and there are connected clients).
/// Client-Side (Read): the associated NetworkObject is spawned
/// </summary>
protected override void OnSynchronize<T>(ref BufferSerializer<T> serializer)
{
if (serializer.IsWriter)
{
OnServerSerializeMeshInfo(serializer.GetFastBufferWriter());
}
else
{
OnClientDeserializeMeshInfo(serializer.GetFastBufferReader());
}
base.OnSynchronize(ref serializer);
}
}Then when the client instance is spawned the 3D mesh can be loaded and parented under the spawned instance.
If you had specific NetworkBehaviour components associated with various 3D Meshes, then you would need to create a unique "blank network prefab" per unique combination of NetworkBehaviour components.
Example:
=========================================
-
BlankNetworkPrefabA
- LoadMeshBehaviour component
- UniqueNetworkBehaviour component A
- UniqueNetworkBehaviour component C
-
BlankNetworkPrefabB
- LoadMeshBehaviour component
- UniqueNetworkBehaviour component B
- UniqueNetworkBehaviour component A
-
BlankNetworkPrefabC
- LoadMeshBehaviour component
- UniqueNetworkBehaviour component A
- UniqueNetworkBehaviour component B
- UniqueNetworkBehaviour component C
========================================= For example, you could have 5 of your 3D Meshes that use BlankNetworkPrefabA, 10 that use BlankNetworkPrefabB, and 3 that use BlankNetworkPrefabC (in other words if you map out what NetworkBehaviour components are needed and then determine which 3D Mesh needs which NetworkBehaiour components you could then narrow down the number of "blank Network Prefab types" to a small set).
If this misses the mark by a long shot, then maybe you could describe what you are trying to accomplish a bit further?
i.e. What is the purpose of the 3D Meshes? Will you be sending messages via RPCs or will they have NetworkVariables associated with them?
Let me know if the alternative seems like it will work or if you have different needs (with more details on the 3D meshes being loaded and what kind of network synchronization they will need to provide).
FreshlyBrewedCode
Is your feature request related to a problem? Please describe. I am porting a single user app to a multi user experience and need to make sure interactable objects are synced. My existing app loads 3D meshes from disk at runtime and dynamically instantiates GameObjects for the mesh. I would like to keep the current loading/spawning logic and just add a
NetworkObjectcomponent and tell NGO to use the sameNetworkObjectIdfor the matching GameObjects (e.g. using the GameObject name/scene path as a unique identifier).Describe the solution you'd like I would like to add a
NetworkObjectcomponent manually on each client and tell NGO to treat it like aNetworkObjectthat was spawned by the server, ideally by manually assigning aNetworkObjectIdand registering the object with NGO.Describe alternatives you've considered Register the GameObjects using e.g.
AddNetworkPrefaband callingSpawnon the server, or wrapping the dynamic GameObject with a pre-defined prefab.Additional context Having to rely on NGO to instantiate networked GameObjects feels like an unneccessary step if there is existing spawning/instantiation logic in place. I understand that this is more of an advanced use case and ideally one would design their app/game with the NGO spawning approach in mind but this is not always the case. So far I have not found a good workaround.