Search Issue Tracker
Not Reproducible
Votes
1
Found in [Package]
1.1.0
Issue ID
N4EBUG-50
Regression
Yes
Prediction Smoothing Action "current" and "previous" values differences are too big when Network emulation is enabled
Reproduction steps:
1. Open the attached project “NetcodeSamples”
2. Open the “Assets/Scenes/Asteroids.unity”
3. Open the “PlayMode Tools” window (Multiplayer > Window: PlayMode Tools)
4. In the “PlayMode Tools” window enable “Network Emulation”
5. Set the “PC & Console Presets” field to “Broadband [WIFI] > Regional [50th Percentile]”
6. Enter the Play mode
7. Press the “Space” key
8. Inspect the Console window
Expected result: The “bp” Vector3 values are similar to the “cp” Vector3 values and the maximum differences between values are 0.05
Actual result: The “bp” Vector3 values are always close to zero or “NaNf”
Reproducible with: 1.1.0-exp.1 (2022.3.12f1, 2023.1.18f1, 2023.2.0b15, 2023.3.0a11)
Not reproducible with: 1.0.17 (2022.3.12f1)
Reproducible on: macOS 13.5.2
Not reproducible on: No other environment tested
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
- ScrollView speed is slower when entering Play mode
- UI Builder elements disappear and "Semantic - Unknown template name" error appears when changes to "Template" parameter are saved
- Renderers outside Light Probe hull use incorrect Ambient Probe values when "Renderer Light Probe Selection" is set to "Use Ambient Probe" and "Light Probes" on Mesh is set to "Blend Probes"
- ArgumentNullException error occurs when selecting a Camera in the Hierarchy with the Scene view open
- Clicking 'Open Editor Log' through the Console fails to open redirected Logs when relative Log files exist outside of the Project root
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. This bug seems to have been fixed at an earlier date. We are no longer able to reproduce it on the current main branch.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.