Search Issue Tracker
In Progress
In Progress in 2.0.X
Under Consideration for 1.0.X, 1.1.X
Votes
0
Found in [Package]
1.0.0-exp.4
1.1.5
2.0.0
Issue ID
NAVB-74
Regression
No
Poor Editor performance when there are a large number of NavMeshModifier GameObjects in the scene.
How to reproduce:
1. Open the “NavMeshModifierPerf.zip” project
2. Open the “NavMeshModifierPerf” scene
3. Enter Play mode with “SimpleSpheres” GameObject *enabled* and “NavObstacles” GameObject *disabled* and observe the time taken
4. Enter Play mode with “SimpleSpheres” *disabled* and “NavObstacles” *enabled* and observe the time taken again
Expected result: The time taken to enter Play mode is pretty much the same between steps 3 and 4
Actual result: The time taken to enter Play mode in step 4 is much longer than step 3
Reproducible with: 1.0.0-exp.4 (2021.3.34f1), 1.1.5 (2022.3.19f1), 2.0.0 (2023.2.8f1, 2023.3.0b5)
Reproducible on: Windows 10 (by reporter), Windows 11
Not reproducible on: no other environment tested
Note:
- The user has provided possible ways of fixing the described issues
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Custom ScriptableObject asset in the project setting are not well deserialized during the Reimport All process
- Fixing Message Loss in UMPE During Domain Reload
- The Editor freezes when ScheduleReadOnly of IJobParallelForTransform with dependency is used
- Text is truncated in the Inspector when the display scale is set to 150%
- CancellationTokenSource(<timeout>) has incorrect cancellation status when used in WebGL Player
Add comment