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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
This is a duplicate of issue #696680