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
- HDRP 6-way VFX Shader is lit incorrectly when World coordinates are used
- 2D Sprite Renderer in front is affected by Sprites in the background when using Sorting Layers and a Shadow Caster 2D with Self Shadow
- Modifying UI Prefab child's Height only confirms the first 1 or 2 digits when the Scene is newly opened or the Prefab is newly created
- ProfilingSampler.Get() returns null and makes the Player only render black when building a Release Build
- Search text field visual controls for the Path binding in an Input Actions Asset is misaligned
This is a duplicate of issue #696680