Search Issue Tracker
Fixed in 5.0.X
Votes
0
Found in
4.3.0f1
Issue ID
573538
Regression
No
Behavior of Move and SetDestination is inconsistent with regards to the Stop function with stopUpdates set to true
To reproduce:
1. Open the Test Scene
2. There is a NavMeshAgentTest script on the 'Agent' object in the scene. The NavMeshAgentTest component will attempt a form of movement after calling Stop (true) on the NavMeshAgent.
3. Setting the 'Mode' variable to 'Move' and the 'Restart Position Updates' variable to false means the component will try NavMeshAgent.Move without setting updatePosition to true after the Stop (true) call. (Agent will not move here)
4. Setting the 'Restart Position Updates' variable to true with the same mode will cause the Move call to succeed. (Agent will move)
5. Setting the 'Mode' variable to 'SetDestination' will cause the agent to move to the given point without setting updatePosition to true. (The agent will move here anyway)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Add comment