Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.3.34f1
Issue ID
UUM-1130
Regression
No
MapLocation/CreateLocation are inconsistent when creating a second position from a previous MapLocation/CreateLocation output
How to reproduce:
1. Open the attached project "NavmeshIssueTest.zip"
2. Open the "BugReproductionScene" Scene
3. Enter the Play mode
4. Select the "Tester_PositionMissmatch" GameObject in the Hierarchy window
5. Trigger the "TestMapLocationInconsistency" function from the ContextMenu of "NavMeshNodeEdgesDrawer.cs"
Expected result: Both assertions are true, the position obtained from CreateLocation and MapLocation are the same
Actual result: Both assertions are false, the position obtained from CreateLocation and MapLocation are half a meter apart from each other
Reproducible with: 2019.4.38f1, 2020.3.34f1, 2022.1.0a12
Not reproducible with: 2022.1.0a13, 2022.1.0f1, 2022.2.0a13
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
- Channel remapping dropdown in the Terrain Layer does not open when clicked on the title
- The Editor freezes indefinitely when a large number of elements are entered in the Subgraphs or Categories lists
- Some Visual Effects package Assets links to documentation are not working
- Heatmap asset’s documentation button in the Inspector window leads to “Sorry... that page seems to be missing!” page when clicked
- Crash on MonoBehaviour::CallMethodIfAvailable when performing various actions
Resolution Note:
There are no fixes planned for this Bug