You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While I was working on the ManagerBasedRLEnvCfg, I found that if a new terrain cfg is added into EnvCfg, the terrain scanner RayCaster cannot measure the hit pos properly given the new terrain prim path.
Steps to reproduce
I want the new terrain be added on certain position and orientation, so the terrain is attached to a Xform. The new terrain is added as follow:
While running this env, the new terrain is added to the World and collision of new terrain works well.
However, the RayCaster result is weird. It seems that from the perspective of lower_terrain_scanner, the new added terrain is still at the initial pos and ori.
So, the problem is why RayCaster assumes the terrain remains the initial pos and ori, even if the terrain is already translated and rotated.
Hello, IsaacLab Team,
While I was working on the
ManagerBasedRLEnvCfg
, I found that if a new terrain cfg is added into EnvCfg, the terrain scannerRayCaster
cannot measure the hit pos properly given the new terrain prim path.Steps to reproduce
I want the new terrain be added on certain position and orientation, so the terrain is attached to a
Xform
. The new terrain is added as follow:While running this env, the new terrain is added to the World and collision of new terrain works well.
However, the
RayCaster
result is weird. It seems that from the perspective oflower_terrain_scanner
, the new added terrain is still at the initial pos and ori.So, the problem is why
RayCaster
assumes the terrain remains the initial pos and ori, even if the terrain is already translated and rotated.System Info
Describe the characteristic of your environment:
Additional context
Add any other context about the problem here.
Checklist
The text was updated successfully, but these errors were encountered: