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
- Script resets to use the previous Skybox color when saving the Scene changes
- [2D] Sprite Library Editor window throws NullReferenceException error when entering Play Mode with Game View maximised
- Game View Tab Scale changes erratically when a Unity Tab is on a different screen with a differing Display Scale
- Six way lighting receiving wrong lighting from APV when set to World Space
- Crash on SortByExecutionOrder when interrupting the .androidpack import process
Add comment