Skip to content

chore: updates for scene migration synchronization performance #3794

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: develop-2.0.0
Choose a base branch
from
Open

chore: updates for scene migration synchronization performance #3794

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f1a9ff4
update
NoelStephensUnity Nov 20, 2025
33d0f43
update
NoelStephensUnity Nov 20, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions com.unity.netcode.gameobjects/Documentation~/components/core/networkobject.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -112,9 +112,10 @@ Similar to [`NetworkObject.ActiveSceneSynchronization`](#active-scene-synchroniz

`NetworkObject.ActiveSceneSynchronization` can be used with `NetworkObject.SceneMigrationSynchronization` as long as you take into consideration that if you migrate a NetworkObject into a non-active scene via `SceneManager.MoveGameObjectToScene` and later change the active scene, then the NetworkObject instance will be automatically migrated to the newly set active scene.

:::warning
Scene migration synchronization is enabled by default. For NetworkObjects that don't require it, such as those that generate static environmental objects like trees, it's recommended to disable scene migration synchronization to avoid additional processing overheads.
:::
> [!NOTE]
> **Performance Check**<br />
> The `NetworkObject.SceneMigrationSynchronization` field is enabled by default! If your project can have many (600-1000+) spawned objects at any given time, this setting can cause performance issues. This setting only provides the ability to automatically synchronize the scene a NetworkObject is migrated to while it is spawned. If your `NetworkObject` does not change scenes and you have no need for automatic scene migration synchronization (_only applies when the integration scene management is enabled_), then it is recommended to disable this property to avoid additional processing overheads.


## Additional resources

Expand Down