Search Issue Tracker
Active
Votes
0
Found in
2018.2.0f2
2022.2.0a13
Issue ID
1061119
Regression
No
[NavMeshComponents][Player] NavMesh.UpdateNavMeshData performing much worse in x86 Windows Player
Steps to reproduce:
1. Open attached project "Example navMesh bug.zip"
2. Build Scene "AndyBugExample" for Windows x86 (choose x86 from the Architecture drop down in Build Settings)
3. Profile the build and see that NavMesh.UpdateNavMeshData is taking a lot of time (around 35ms on the tester's machine and around 90ms on the user's)
Expected result: performance in Player and Editor is the same
Actual result: performance in Player is much worse when building for x86 architecture
Reproduced with: 2018.2.0f2, 2018.3.0a8
Note: not tested with earlier versions due to NavMeshComponent incompatibility
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment