-
Notifications
You must be signed in to change notification settings - Fork 916
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
[Question] How to add a RigidContactView into the scene? #110
Comments
I had the same problem. I was able to solve it so I hope this would help: The initialization flow should be:
If you are working with SimulationContext (like in orbit examples) without a World object, you have to call view.initialize() directly, but you have to do it only after sim.reset() is called. |
Thanks a lot!!! That works. |
# Description This MR introduces wrappers around different [USD Physics](https://openusd.org/dev/api/usd_physics_page_front.html) and [PhysX solver](https://docs.omniverse.nvidia.com/kit/docs/omni_usd_schema_physics/104.2/index.html) schemas. The functions allow modifying the properties on an asset prim using configuration objects. The schemas supersede the current `omni.isaac.orbit.utils.kit.py` which did the same job but had duplication in the implementations. ## Type of change - New feature (non-breaking change which adds functionality) - This change requires a documentation update ## Checklist - [x] I have run the [`pre-commit` checks](https://pre-commit.com/) with `./orbit.sh --format` - [x] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [x] I have added tests that prove my fix is effective or that my feature works - [x] I have updated the changelog and the corresponding version in the extension's `config/extension.toml` file --------- Signed-off-by: Mayank Mittal <[email protected]>
# Description This is a follow-up to PR #110. It adds additional methods that allow defining i.e. creating the schemas at the specified prim path. This is useful when creating your own meshes or prims procedurally. The methods also check if there are any conflicting schemas on the prim to which we want to apply a new schema. This makes sure that schemas are defined on a prim gracefully. ## Type of change - New feature (non-breaking change which adds functionality) - This change requires a documentation update ## Checklist - [x] I have run the [`pre-commit` checks](https://pre-commit.com/) with `./orbit.sh --format` - [x] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [x] I have added tests that prove my fix is effective or that my feature works - [x] I have updated the changelog and the corresponding version in the extension's `config/extension.toml` file
# Description This MR introduces wrappers around different [USD Physics](https://openusd.org/dev/api/usd_physics_page_front.html) and [PhysX solver](https://docs.omniverse.nvidia.com/kit/docs/omni_usd_schema_physics/104.2/index.html) schemas. The functions allow modifying the properties on an asset prim using configuration objects. The schemas supersede the current `omni.isaac.orbit.utils.kit.py` which did the same job but had duplication in the implementations. ## Type of change - New feature (non-breaking change which adds functionality) - This change requires a documentation update ## Checklist - [x] I have run the [`pre-commit` checks](https://pre-commit.com/) with `./orbit.sh --format` - [x] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [x] I have added tests that prove my fix is effective or that my feature works - [x] I have updated the changelog and the corresponding version in the extension's `config/extension.toml` file --------- Signed-off-by: Mayank Mittal <[email protected]>
# Description This is a follow-up to PR #110. It adds additional methods that allow defining i.e. creating the schemas at the specified prim path. This is useful when creating your own meshes or prims procedurally. The methods also check if there are any conflicting schemas on the prim to which we want to apply a new schema. This makes sure that schemas are defined on a prim gracefully. ## Type of change - New feature (non-breaking change which adds functionality) - This change requires a documentation update ## Checklist - [x] I have run the [`pre-commit` checks](https://pre-commit.com/) with `./orbit.sh --format` - [x] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [x] I have added tests that prove my fix is effective or that my feature works - [x] I have updated the changelog and the corresponding version in the extension's `config/extension.toml` file
# Description This change switches to the newly added replicator API for tiled rendering. All tiled rendering behaviors are the same as before. The API provides a cleaner interface to initialize tiled rendering. ## Type of change - New feature (non-breaking change which adds functionality) ## Checklist - [x] I have run the [`pre-commit` checks](https://pre-commit.com/) with `./isaaclab.sh --format` - [x] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [x] I have updated the changelog and the corresponding version in the extension's `config/extension.toml` file - [ ] I have added my name to the `CONTRIBUTORS.md` or my name already exists there <!-- As you go through the checklist above, you can mark something as done by putting an x character in it For example, - [x] I have done this task - [ ] I have not done this task -->
Question
I find that the RigidContactView.initialize could not add the RigidContactView to the scene, which caused the simulation breakdown. What should I do to implement the
scene.add(RigidContactView)
function. It seems that there is no scene created directlyThe text was updated successfully, but these errors were encountered: