Search Issue Tracker
Duplicate
Votes
0
Found in
5.1.0f1
Issue ID
698291
Regression
Yes
[UNET] Multiple components sending commands prints InvokeCommand error
Reproduction steps:
1. Open attached project "UNET Bug"
2. Build the game with scene.unity included in the build
3. Launch the built executable
4. Hit play within the Unity editor
5. Select LAN Host within the Unity editor. At this point you'll see two log messages (CmdFirstCommand and CmdSecondCommand) and everything is working correctly
6. Select LAN Client on the executable. You'll start to get the InvokeCommand errors in the Unity editor log.
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
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
This is a duplicate of issue #696680