When using the c-api, the getAgentPosition and getAgentVelocity methods take parameters for vectors in R^3, but the y-component is always zero. This is fine for simulations on the plane, but doesn't work for 3D heightfields or navigation meshes. The function needs to take the elevation into account.
When using the c-api, the
getAgentPositionandgetAgentVelocitymethods take parameters for vectors in R^3, but the y-component is always zero. This is fine for simulations on the plane, but doesn't work for 3D heightfields or navigation meshes. The function needs to take the elevation into account.