BUG "SetDestination" can only be called on an active agent that has been place
2018-03-30 09:52
911 查看
BUG "SetDestination" can only be called on an active agent that has been place
最近做一个作业的时候,导入了其他地形资源,重新对地形Bake之后 点击运行发现会出这样的错误。原因不是很清楚,有人说是角色的出生点位置离导航网格远了,我尝试了一下发现并不是这样的。
查了很多,在社区里找到了如下的解决办法
我们一开始要取消我们的角色上面的寻路组件,通过代码的方式进行组件的添加。
GameObject go = new GameObject("Target");
Vector3 sourcePostion = new Vector3( 100, 20, 100 );//The position you want to place your agent
NavMeshHit closestHit;
if( NavMesh.SamplePosition( sourcePostion, out closestHit, 500, 1 ) ){
go.transform.position = closestHit.position;
go.AddComponent<NavMeshAgent>();
//TODO
}
else{
Debug.Log("...");
}在指定范围内查找NavMesh上最近的点。该函数对NavMesh进行采样以找到NavMesh上最近的点。最近的点是根据到查询点的距离返回的。
如果不懂的话 这里有原文链接:
点击打开链接
相关文章推荐
- Unity中BUG:SetDestination can only be called on an active agent that has been placed on a navmesh 的处理
- 【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.
- Unity关于 "Move" can only be called on an active agent that has been placed on a NavMesh.问题的解决办法
- Unity 3D:"Get Remaining Distance" can only be called on an active agent that has been"错误
- 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的解决办法
- 导航报错SetDestination() can only be called on an active agent that has been placed on a NavMesh
- MSSQL: Invoke or BeginInvoke cannot be called on a control until the window handle has been created.
- 学习AJAX Toolskit之解决故障:RegisterDataItem can only be called during an async postback.
- Entity Framework 中 使用Include 解决ObjectContext instance has been disposed and can no longer be used for operations that require a connection错误 -原创
- android Cannot execute task: the task has already been executed (a task can be executed only once)
- Can't toast on a thread that has not called Looper.prepare()
- Silverlight + WCF + EF4 调用出错,Server 端的Exception:The ObjectContext instance has been disposed and can no longer be used for operations that require a connection.
- An explicit value for the identity column in table can only be specified when a column list is used and IDENTITY_INSERT is ON
- The ObjectContext instance has been disposed and can no longer be used for operations that require a connection.
- 解决bug:运行项目时报异常 “Can't create handler inside thread that has not called Looper.prepare()”
- Snapshotting a view that has not been rendered results in an empty snapshot. Ensure your view has be
- [org.springframework.context.annotation.ComponentScanBeanDefinitionParser] are only available on JDK 1.5 and higher 问题--MyEclipse设置JDK版本