Search Issue Tracker
Won't Fix
Votes
8
Found in
5.6.0b4
Issue ID
876092
Regression
No
NetworkDiscovery always produces an error when StopBroadcast() is called as side-effect of OnReceivedBroadcast
Reproduction Steps:
1. Open attached project.
2. Open "LocalDiscovery" scene.
3. Build & Run project in Standalone Player.
4. Wait until server is started in Standalone Player.
5. Enter Play mode back in Unity.
Result: Unity gives out error:
host id out of bound id {-1} max id should be greater 0 and less than {1}
UnityEngine.Networking.NetworkDiscovery:Update()
Reproducible with: 5.5.1f1, 5.6.0b6
Note: Not reproducible with previous versions.
Comments (1)
-
sebrk_hiq
Sep 04, 2017 14:45
Also StopBroadcast() doesn't actually stop broadcasting. It just continues. It was stated to be fixed in 5.5 here: https://issuetracker.unity3d.com/issues/broadcast-discovery-not-stopping-after-multiple-calls which is plain wrong. I'm adding 2017.1.0p5 to the list.
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
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
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.