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
- Desktop Linux runtime does not respect -popupwindow command line argument
- Shader Graph more options dropdown button does not open the dropdown when clicked all the way to the right of the button
- “Attempting to draw with missing bindings“ warning lacks root cause indication and is thrown each frame when StructuredBuffer is accessed on DirectX12
- Shader Graph Import Settings documentation leads to "Sorry... that page seems to be missing!" page when opened through the documentation button in the Inspector window
- Unexpected Material change/transparency when switching between ShaderGraph and material at runtime in HDRP
Add comment