What is the right way to use Orbit in Extension Workflows?
\nI hope this is the right place to ask. Thanks!
","upvoteCount":1,"answerCount":1,"acceptedAnswer":{"@type":"Answer","text":"Yes, it is possible to use Orbit in extension workflows. You need to add it as a dependency to your extension as shown here.
\n[dependencies]\n\"omni.isaac.orbit\" = {}\nI am not 100% sure if Orbit is visible directly as an extension on Omniverse platform. But based on the information about kit-project-template, it should be. Let me know if it doesn't work.
","upvoteCount":1,"url":"https://github.com/isaac-sim/IsaacLab/discussions/132#discussioncomment-8034803"}}}
-
|
I've started working with Isaac Sim lately and was curious about trying out the functionalities Orbit provides. So far I've mostly been working with the Extension Workflow in Isaac, since I find it quite convenient for explorative development. Looking at the docs and the code I've failed so far to figure out how to use this kind of workflow together with Orbit. Naively I thought that if I start Isaac Sim via the Orbit python launch file (i.e., What is the right way to use Orbit in Extension Workflows? I hope this is the right place to ask. Thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Yes, it is possible to use Orbit in extension workflows. You need to add it as a dependency to your extension as shown here. I am not 100% sure if Orbit is visible directly as an extension on Omniverse platform. But based on the information about kit-project-template, it should be. Let me know if it doesn't work. |
Beta Was this translation helpful? Give feedback.
Yes, it is possible to use Orbit in extension workflows. You need to add it as a dependency to your extension as shown here.
I am not 100% sure if Orbit is visible directly as an extension on Omniverse platform. But based on the information about kit-project-template, it should be. Let me know if it doesn't work.