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
- Crash on CheckDeviceStatus when converting materials from built-in to URP and using DX12
- Higher CPU frame time on Android devices with Cortex-A510 efficiency cores (vs Cortex-A55)
- Alt+click on List header does not recursively toggle child foldouts when items use a UI Toolkit CustomPropertyDrawer
- Artifacts are rendered in UITK when using Font Assets and using negative outlines
- Editor hangs when opening Asset picker window for AssetReference and a lot of addresable assets are present in the project
This is a duplicate of issue #696680