Search Issue Tracker
Active
Under Consideration for 6000.5.X, 6000.6.X
Votes
0
Found in
6000.5.0a8
6000.6.0a1
Issue ID
UUM-131597
Regression
No
Netcode prediction errors when a non-replicated component is added to a predicted ghost
How to reproduce:
1. Open the “Netcode Bug Reproduction_2“ project
2. Open the “SampleScene”
3. Enter Play Mode
4. Press and hold SPACE key
5. Observe the Console
Expected result: No “…UnityEngine.Debug:LogError (object)” error is printed in the Console
Actual result: There is “…UnityEngine.Debug:LogError (object)” error in the Console
Reproducible with: 1.6.1, 1.9.0 (6000.0.59f1, 6000.2.7f1, 6000.3.0b4, 6000.4.0a1)
Reproduced on: Windows 11 Pro (24H2)
Not reproduced on: No other environment tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment