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
0
Found in
2017.1.0p4
Issue ID
945970
Regression
No
Navmeshagent.Move results differs between Editor and Builds when lerped
Reproduction steps:
1. Open the attached project.
2. Play the 'Assets > Scenes > Racing' scene.
3. Click 'A' and 'D' keyboard buttons rapidly.
4. Notice how the object moves (GIFs attached).
5. Repeat steps 3 and 4 in a standalone build.
- Object swerves fast in Editor.
- Object swerves much slower in iOS build.
- Object Swerves very slowly in macOS and Windows standalone builds.
Reproduced with:
5.6.3p2, 2017.3.0a7, 2019.3.0a11
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:
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/