Search Issue Tracker
Fixed in 5.5.0
Votes
0
Found in
5.5.0a5
Issue ID
821385
Regression
No
[Networking] NeyworkDiscovery component has "useNetworkManager" flag set to true by default
NeyworkDiscovery component has "useNetworkManager" flag set to true - this cause warning when user don't use NetworkManager in this scene
The correct behavior would be:
- to check if there is NetworkManager component in the scene and only then set this flag to true
OR
- simply set this flag to false by default
How we can reproduce it using the example you attached
1 Open attached project
2 Open scene "sc1" and press Play
3 Notice warning in console:
"NetworkDiscovery broadcast data changed while using NetworkManager. This can prevent clients from finding the server. The format of the broadcast data must be 'NetworkManager:IPAddress:Port'."
Actual result: that warning is expected and caused by "useNetworkManager" flag set to true (but in the script we are trying to change "broadcast data")
Expected result: "useNetworkManager" flag SHOULD NOT be set to true by default
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment