Search Issue Tracker
Won't Fix
Votes
3
Found in
2017.1.0f3
Issue ID
939576
Regression
No
NetworkBehaviour.OnStartClient is not called for non-player objects when a player reconnects
Steps to reproduce:
1. Download and open the attached project
2. Build for standalone
3. Launch a build instance
4. Set it as Server
5. Enter Playmode in the editor
6. Join as Client
7. Disconnect
8. Reconnect
Expected result: "Start Client Test Machine!" is logged twice due to 2 time connecting to the server
Actual result: "Start Client Test Machine!" is only called the first time a player connects
Reproduced on 5.5.4p2, 5.6.3f1, 2017.1.0p2, 2017.2.0b6, 2017.3.0a2
-
goldbug
Jun 29, 2018 12:36
For anyone landing here. This bug has been fixed in HLAPI CE
https://forum.unity.com/threads/unet-hlapi-community-edition.425437/This is the specific patch that fixes it:
https://bitbucket.org/vis2k/hlapi-community-edition/commits/78d159d7da0c71838aec67f9efee9641570b6105 -
goldbug
Jun 28, 2018 12:59
I have sent a pull request for HLAPI CE for this, you can find the fix here:
-
hexagonius
Feb 26, 2018 15:30
Just ran into this issue too. The term OnStartClient is a little misleading, though it behaves correctly. It's like a regular start, only called once during the lifetime of a gameobject and only on a client. It kinda stupid really, but I think what UNET expectes is switching between offline and online scenes.
-
aquay
Aug 31, 2017 01:12
Same result with my own project.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Dragon Crashers] Build fails in U6
- [Dragon Crashers] 4 Shader error messages on import
- [Dragon Crashers] Readme text is white on light grey
- Cursor stays in front of the first character when entering text in the TextMeshPro field
- Searching in Hierarchy causes unwanted component calls
Resolution Note:
Mass closure of UNET Bugs.
As UNet is Deprecated we are moving to low maintenance mode, where critical issues can get fixes.
Closing this bug as part of cleaning-up the Bug List.
If you feel this bug is really a road-blocker, you can reopen the bug and we will work this one.