#"Object was initialized twice without being reset" for scene network objects on client

8 messages · Page 1 of 1 (latest)

summer lance
#

Since upgrading to FishNet pro version 4.6.19, I've been experiencing the following issue: Network Objects which reside in a scene result in the error "Object was initialized twice without being reset" on clients upon connecting. Some notes:

  • Prior to this I was on an old version of FishNet (version 3 or so) and didn't experience this
  • This happens on clients only, the server or host doesn't experience these errors
  • This issue happens even if the Observer Manager is disabled, and if the NetworkObserver components are disabled on their respective scene Network Objects
  • I'm calling sceneManager.LoadGlobalScenes(<game scene>) on the server, and there are no other scene load calls on the server or clients
  • None of these Network Objects are parented to other network objects
  • Interestingly, OnEnable seems to be called twice for these network objects in the scene, though I am not certain if this in itself is necessarily a problem.

Since this only started happening since I upgraded my project, I suspect that this may be a bug.

Thanks for reading

#

Looks like there's another similar comment, adding it here for bookkeeping if it's relevant: #🧽help message

rancid trench
summer lance
#

Ah ok yes this looks similar, though when I try experimenting with my project and even disable the Network Observer manager outright, I still get this issue. Either way I'll just wait for the fix.

#

Is there an easy workaround right now? Or should we just avoid having network objects in the scene for the time being?

rancid trench
#

Well, first see if it happens on the latest version of FishNet

#

It can probably be ignored for the time being until it is patched though

jovial mist
#

@summer lanceThe potential good news is, this might not be causing you issues. The error is there because we missed something during a reset, not necessarily that something is breaking.