Skip to content
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.

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

NRE from nested NetworkObjects #813

Open
f2069 opened this issue Nov 8, 2024 · 0 comments
Open

NRE from nested NetworkObjects #813

f2069 opened this issue Nov 8, 2024 · 0 comments
Labels
Acknowledged Your issue has been acknowledged and will be investigated. High Priority This task will be prioritized. Resolved Pending Release

Comments

@f2069
Copy link
Contributor

f2069 commented Nov 8, 2024

General
Unity version: 2021.3.18f1
Fish-Networking version: 4.5.4hf0 Pro
Discord link: https://discord.com/channels/424284635074134018/1293524096423825439 (comments)
Package: NRE.Condition.Report.081124.unitypackage.zip (from #812)

The object hierarchy and spawn logic is the same as here: #796

The SceneCondition condition is set in ObserverManager.
All NetworkObjects have a NetworkObserver component with the use Manager parameter.

Description
When switching from a scene on which nested NetworkObjects were created - an error occurs.

Replication
Steps to reproduce the behaviour:

  1. Open the "NestedSpawn.Menu" scene in both windows;
  2. Start the Server and Client in one window and Client in other;
  3. Press the "Load Scene" button on Server;
  4. Wait for the tower with rotating cubes to appear on the server and client;
  5. Click to the "Next scene" button - see the error.

Expected behavior
No NRE and a correct transition to the next scene.

Server error 1 (NRE NetworkObject.OnDestroy)

NullReferenceException: Object reference not set to an instance of an object
FishNet.Object.NetworkObject.OnDestroy () (at Assets/FishNet/Runtime/Object/NetworkObject.cs:519)
@FirstGearGames FirstGearGames added the Acknowledged - Maybe Bug Your issue has been acknowledged as a potential bug and will be investigated. label Nov 8, 2024
@FirstGearGames FirstGearGames added the Low Priority This task will be resolved when time permits. label Nov 16, 2024
@FirstGearGames FirstGearGames added Acknowledged Your issue has been acknowledged and will be investigated. High Priority This task will be prioritized. and removed Acknowledged - Maybe Bug Your issue has been acknowledged as a potential bug and will be investigated. Low Priority This task will be resolved when time permits. labels Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Acknowledged Your issue has been acknowledged and will be investigated. High Priority This task will be prioritized. Resolved Pending Release
Projects
None yet
Development

No branches or pull requests

2 participants