Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug Report] ViewerCfg origin type = asset_root is broken #551

Open
2 of 3 tasks
KyleM73 opened this issue Jun 22, 2024 · 7 comments
Open
2 of 3 tasks

[Bug Report] ViewerCfg origin type = asset_root is broken #551

KyleM73 opened this issue Jun 22, 2024 · 7 comments
Labels
bug Something isn't working

Comments

@KyleM73
Copy link
Contributor

KyleM73 commented Jun 22, 2024

Describe the bug

When training with rsl_rl in the default locomotion/velocity environments, if you switch the viewer origin type to track the asset_root the terrain is not visualized when recording videos. see image below. visualization is not affected when the viewer is attached to the world, only when it tracks the robot. I have confirmed this occurs with multiple locomotion tasks.

Steps to reproduce

Reproduce by pasting this into the post_init() of any task cfg:

self.viewer.eye = (2.5, 0.5, 0.3)
self.viewer.origin_type = "asset_root"
self.viewer.asset_name = "robot"

Go1-Flat
image

Anymal-D-Flat
image

System Info

  • Commit: [9ab6b48] (main)
  • Isaac Sim Version: [4.0]
  • OS: [Ubuntu 20.04]
  • GPU: [RTX 3080 12Gb]
  • CUDA: [12.2]
  • GPU Driver: [535.183.01]

Checklist

  • I have checked that there is no similar issue in the repo (required)
  • I have checked that the issue is not in running Isaac Sim itself and is related to the repo

Acceptance Criteria

  • The terrain is visualized normally when the viewer tracks the asset_root
@Mayankm96
Copy link
Contributor

Mayankm96 commented Jun 23, 2024

Hi,

Thanks for reporting this issue.

  • Is the camera at an angle where the terrain is perpendicular to the camera plane?
  • Does it also happen for the rough terrain?

@Mayankm96 Mayankm96 added the bug Something isn't working label Jun 23, 2024
@KyleM73
Copy link
Contributor Author

KyleM73 commented Jun 24, 2024

  1. no, the camera eye is at (2.5, 0.5, 0.3). I tried other angles (eg 3.5, 3.5, 3.5) as well and it did not change anything (example in the image below)

image

  1. just tried it with the rough terrain envs- with the same angle as before (2.5, 0.5, 0.3) it looks like you can see the outline of the pyramid steps, but with the angle (3.5, 3.5, 3.5) you can clearly see the ground, but the color is incorrect

image

image

@Mayankm96
Copy link
Contributor

I am unable to reproduce this issue. I added the following to the post init call in the LocomotionVelocityRoughEnvCfg:

# adds tracking of the robot
self.viewer.eye = (2.5, 0.5, 0.3)
self.viewer.origin_type = "asset_root"
self.viewer.asset_name = "robot"

Here's what I see:

image

My configuration is as follows:

  • GPU: NV A6000
  • Driver: 535.183.01

@KyleM73
Copy link
Contributor Author

KyleM73 commented Jun 29, 2024

Are you able to visualize the terrain on flat ground as well? I am able to visualize the terrain as you were for rough terrains, but not for the default flat terrain (None generator, terrain set to ‘plane’, etc.)

@Mayankm96
Copy link
Contributor

When I ran the flat terrain example, that worked for me.

@KyleM73
Copy link
Contributor Author

KyleM73 commented Jun 29, 2024

Hmmm I'm not sure what's going on then. I tried pulling from main, rebuilding the container and retesting but I'm getting the same result- I can visualize the rough terrains fine but when tracking the asset_root the terrain is invisible for flat terrains... What else could be affecting this? same rsl_rl version? Same train.py options? I'm testing using the default env cfgs in isaac.lab_tasks/*

Note that I'm not doing any of this with the GUI, these are all coming from saved wandb videos, everything I do is in headless mode since I can't do x11 forwarding to my MacBook.

@Mayankm96
Copy link
Contributor

I haven't tested it within a container. Also I was running the random_agent.py script instead of a trained policy.

Will have to check with the above and see if I can reproduce the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants