Unity中BUG：SetDestination can only be called on an active agent that has been placed on a navmesh 的处理
2017-03-11 20:44
573 查看
SetDestination can only be called on an active agent that has been placed on a navmesh
最近遇到这个BUG
意思就是他找不到navmesh上的目标，但是我发现有些新刷新的敌人是能够找到我来追我的，有些就不能
我将新敌人刷新在了离水平地面还有一定距离的高度，导致怪物本体没有位于mesh上
后来调整了下刷怪的高度
解决方法：
1.检查本体是否位于navmesh上
2.检查目标是否位于navmesh上
3.检查场景变更是否重新烘焙
最近遇到这个BUG
意思就是他找不到navmesh上的目标，但是我发现有些新刷新的敌人是能够找到我来追我的，有些就不能
我将新敌人刷新在了离水平地面还有一定距离的高度，导致怪物本体没有位于mesh上
后来调整了下刷怪的高度
解决方法：
1.检查本体是否位于navmesh上
2.检查目标是否位于navmesh上
3.检查场景变更是否重新烘焙
内容来自用户分享和网络整理，不保证内容的准确性，如有侵权内容，可联系管理员处理 
相关文章推荐
- 【BUG】 "SetDestination" can only be called on an active agent that has been placed on a NavMesh.
- "SetDestination" can only be called on an active agent that has been placed on a NavMesh.
- "SetDestination" can only be called on an active agent that has been placed on a NavMesh. 解决办法
- Unity关于 "Move" can only be called on an active agent that has been placed on a NavMesh.问题的解决办法
- Move can only be called on an active agent that has been placed a Navmesh的解决办法
- 导航报错SetDestination() can only be called on an active agent that has been placed on a NavMesh
- Move can only be called on an active agent that has been placed a Navmesh的解决办法
- BUG ＂SetDestination＂ can only be called on an active agent that has been place
- Unity 3D："Get Remaining Distance" can only be called on an active agent that has been"错误
- Unity 1.2 bug: InterfaceInterceptor can't wrap an interface that inherits from another interface
- An explicit value for the identity column in table can only be specified when a column list is used and IDENTITY_INSERT is ON
- Snapshotting a view that has not been rendered results in an empty snapshot. Ensure your view has be
- 学习AJAX Toolskit之解决故障：RegisterDataItem can only be called during an async postback.
- Silverlight + WCF + EF4 调用出错，Server 端的Exception：The ObjectContext instance has been disposed and can no longer be used for operations that require a connection.
- gridview导出exe处理时遇到RegisterForEventValidation can only be called during Render();错误
- 报错“Can't create handler inside thread that has not called Looper.prepare()” 的处理方法
- Can't toast on a thread that has not called Looper.prepare()
- android Cannot execute task: the task has already been executed (a task can be executed only once)
- The ObjectContext instance has been disposed and can no longer be used for operations that require a connection.
- MSSQL: Invoke or BeginInvoke cannot be called on a control until the window handle has been created.