Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
1
Found in
5.6.0f3
Issue ID
899771
Regression
No
Radius from "Navigation->Agents" is capped at 0.05, while Agent Radius from "Navigation->Bake" is capped at 0.001
To reproduce:
1. Open attached project "NavTest.zip".
2. Open "Test" scene.
3. Open "Navigation -> Bake" window.
4. Agent's Radius and Height can be set to 0.001. (if entered from the keyboard)
5. Open "Navigation -> Agents" window.
6. Agent's Height can be set to 0.001, but radius only to 0.05.
Expected result: "Navigation -> Agents" Radius should also be possible to set to the same amount (0.001), as in "Navigation -> Bake" window.
Actual result: "Navigation -> Agents" Radius is capped at 0.05. It's not consistent.
Reproducible: 5.6.0b1, 5.6.0p3, 2017.1.0b2
Note: "Agents" tab under the "Navigation" was added only in 5.6.0b1.
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note:
Will be fixed as part of substantial refactoring work planned for the NavMeshAgent.
More information will be communicated on the Navigation forum. https://forum.unity.com/forums/navigation.79/