Search Issue Tracker
Fixed
Fixed in 1.2.0
Votes
0
Found in [Package]
1.2.0
Issue ID
N4EBUG-15
Regression
No
Prespawned Ghosts fail to awake when designated as relevant
How to reproduce:
1. Open the “DotsSum-master” project
2. Open the “SampleScene”
3. Disable Multiplayer Simulation (Multiplayer > Window: PlayMode Tools > Simulator > “Disabled”)
4. Make sure to set PlayMode Type to “Client & Server” (Multiplayer > Window: PlayMode Tools)
5. Enter Play Mode
6. Move the player (red) Entity into sphere (green) Entities using WASD keys
Expected result: player collides with Entities without any rubberbanding
Actual result: when the player collides with Entities rubberbanding occurs and the sphere Entities fail to fully awake
Reproduced with: 0.17.0-preview.41 (2022.2.19f1, 2023.1.0b16, 2023.2.0a14), 1.0.0-pre.65 (2022.2.19f1, 2023.1.0b16, 2023.2.0a14)
Could not test with: 0.17.0-preview.41 (2020.3.48f1, 2021.3.25f1) (Could not resolve dependency issues)
Reproduced on: Windows 10 (by reporter), Windows 11
Notes:
1. In the “SortRelevance“ script uncommenting lines 29-33 fixes the issue
2. When downgrading the Entities Package to version 0.17.0-preview.41, downgrading the Netcode for Entities and Unity Physics packages caused script errors that were unresolvable, therefore Netcode for Entities and Unity Physics packages could not be properly 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
- 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
Resolution Note (fix version 1.2.0):
Fixed by adding default relevancy queries, making sure internal netcode prespawn tracking ghosts are always included