Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.1.0b5
Issue ID
910041
Regression
No
2 warnings with the same info are thrown when user tries to set scene(not registered in Build settings) to NetworkManager
Online and Offline scenes should be registered in Build settings beforre you can set them to appropriate slots in NetworkManager, if scene is not registered and you try to set it to the slot - it should give warning - the problem is that right now it gives 2 almost the same warnings!
When user tries to set
How we can reproduce it using the example you attached
1 Create new project
2 Create new scene and save it
3 Create empty object and add NetworkManager component to it
4 Try to drag scene asset from Project view to Online or Offline scene slot in NetworkManager in Inspector
Actual result:
2 almost the same warnings appear:
- Scene [OfflineScene] cannot be used with networking. Add this scene to the 'Scenes in the Build' in build settings.
- The scene OfflineScene cannot be used. To use this scene add it to the build settings for the project
Expected result:
one warning is enough :)
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
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.