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

In extension workflow - some envs not updating in viewport #153

Open
VladimirFokow opened this issue Mar 20, 2024 · 1 comment
Open

In extension workflow - some envs not updating in viewport #153

VladimirFokow opened this issue Mar 20, 2024 · 1 comment

Comments

@VladimirFokow
Copy link

VladimirFokow commented Mar 20, 2024

In the extension workflow, in video example here (at 1:34),
after we click "START" we can see the cartpoles moving in the viewport.

When I try the same with Humanoid - it doesn't move (nor if "Test" is selected)
In the terminal I see that it is training -- but it just doesn't render in the viewport.

If I launch the training from the command line (not with the extension) (with headless=False by default), a window opens and there everything DOES move.

If I create my custom env, will I be able to check its training progress with the extension workflow? - how to ensure that it will be moving?

Envs:

In the extension workflow:
✅ = is moving
❌ = is not moving
(without emoji = not tested)


  • AllegroHand ✅❌ (hand yes, but the cube in the hand - no)
  • Ant❌
  • Anymal❌
  • AnymalTerrain❌ (and I only see one robot..)
  • BallBalance✅
  • Cartpole✅
  • Crazyfile✅
  • FactoryTaskNutBoltPick❌
  • FactoryTaskNutBoltPlace
  • FactoryTaskNutBoltScrew
  • FrankaCabinet❌
  • FrankaDeformable
  • Humanoid❌
  • Ingenuity
  • Quadcopter✅
  • ShadowHand
  • ShadowHandOpenAI_FF
  • ShadowHandOpenAI_LSTM


system info:

Ubuntu 22.04.3 LTS
Isaac Sim 2023.1.1.

@SuomiKP31
Copy link

This is caused by OmniHydra instancing not being enabled when we are using extension workflow. I believe all robots that don't move are using instanceable assets. I did see a warning in the command prompt, but currently I don't know how to enable it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants