Search Issue Tracker
Won't Fix
Won't Fix in 6000.5.X
Votes
0
Found in
6000.0.65f1
6000.3.3f1
6000.4.0b3
6000.5.0a4
Issue ID
UUM-131324
Regression
No
NavMesh Components aren't named consistently
Reproduction steps:
1. Create a new project
2. Create or select a GameObject and press “Add Component” button in the Inspector
3. Observe Navigation section
Actual result: “Nav Mesh” is displayed in “Nav Mesh Agent” and “Nav Mesh Obstacle” Components while “NavMesh” is displayed in the rest of the Components
Expected result: “NavMesh” is displayed the same way in all of the components
Reproducible with: 6000.0.65f1, 6000.3.3f1, 6000.4.0b3, 6000.5.0a4
Reproduced on: macOS Tahoe 26.1 (M4)
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
- Build fails when building a project containing an 18+ dimension array with IL2CPP
- [Android][Sentis] Human poses are not detected when using the BlazePose model
- Sprite Editor Outline Tool Overlay is not displayed when no Sprite is selected
- “No method with RuntimeInitializeOnLoadMethod attribute” warning from ReadmeEditor.cs is thrown after installing Project Auditor Rules
- Projection matrix is altered when using RasterCommandBuffer.ClearRenderTarget on DX12 and Metal
Resolution Note:
Thank you for reporting this issue. At this time, there is no safe way to modify the names of these components without causing potential issues. For this reason, we will be closing this bug as Won’t Fix.
Resolution Note (6000.5.X):
Thank you for reporting this issue. At this time, there is no safe way to modify the names of these components without causing potential issues. For this reason, we will be closing this bug as Won’t Fix.