Search Issue Tracker
Fixed in 2018.1.X
Votes
0
Found in
2018.1.0a7
2018.1.0b1
Issue ID
978659
Regression
Yes
MAC OSX - Raycasting is incorrect. (seems to be casued by Camera.main.ScreenPointToRay)
The Navmesh agents in the attached project should move to where the user clicks. This functionality seems to be broken.
Steps to reproduce
- Download the attached project (AI TEST.rar)
- Open it as a new project in Unity 2018.1.0b1.
- Open the example scene 1_multiple_agent_sizes.
- Open Assets > Examples > Scenes > 1_multiple_agent_sizes.
- Play the scene.
- Click on the green gound plane. Objects should move to where you have clicked.
Notice issue >> Objects do not move, or if they do they do not move correctly.
VIDEO ATTACHED
Note: Attached an updated ClickToMove.cs script. If you replace the projects ClickToMove.cs with this one, it will add a sphere to the points, giving a little more clarity.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Add comment