Search Issue Tracker
Won't Fix
Won't Fix in 2020.3.X
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
There are no fixes planned for this Bug
Resolution Note (2020.3.X):
There are no fixes planned for this Bug