Functions to return objects that in contacts/collisions

Hi there,

I would like to use this simulator to test collision detection algorithms. I am wondering if there are functions I can use to return any objects that are in contacts/collisions? Thansk!


There is a PhysX demo about Contact report (at least in Isaac Sim 2020.2.2 as far I know): Demo showing contact report listening

You can execute it from menu Physics > Demo > PhysX under Snippets section.

Also, you can find the code at /isaac-sim/_build/target-deps/kit_sdk_release/_build/linux-x86_64/release/extsPhysics/omni.physx/omni/physx/scripts/scenes/

The demo script prints the next information for the contact:

Contact found:
Actor0: /World/sphere
Actor1: /World/groundPlane/collisionPlane
Collider0: /World/sphere
Collider1: /World/groundPlane/collisionPlane
Num contacts: 1
Normal: 1.3435885648505064e-07 0.0 1.0000001192092896
Position: 0.1749073565006256 0.0 -0.8332841396331787
Impulse: 0.049639005213975906 0.0 369450.96875

Contact lost:
Actor0: /World/sphere
Actor1: /World/groundPlane/collisionPlane
Collider0: /World/sphere
Collider1: /World/groundPlane/collisionPlane
Num contacts: 0
1 Like

Thanks a lot for replying. The demo works but there is a problem. I find that if I change the sphere size to be smaller (radius = 5 for example). Contact found will not work even tho the contact lost works. If I increase the density, the contact found will work again, so it is something related to the mass of the part it seems like. Do you have any idea why is that?

Another question is is there any specific extension I have to enable If I want to run a python script to use this function? I try to use this function in a python script rather than in that demo but the program freezes in kit.update() as soon as there is a contact.


The problem seems to be the contact report threshold parameter (physxContactReport:threshold) of the contact report API (ContactReportAPI). Actualy, this parameter has a value of 200000.000. I changed this value to 1.0 for the sphere (with radius = 5), for example, and the contact reports works again. So,in order to have your system working, you need to play with this parameter :)

1 Like

Thanks again Toni. Things work great in the demo. However, when I use python script to reproduce this demo, the simulator just freezes when there is contact between ball and the floor. Do you have any insights on this? Here is the script I run.

import os
from omni.isaac.synthetic_utils import OmniKitHelper
from omni.physx.scripts.scenes.ContactReportDemo import ContactReportDemo
from omni.physx.scripts.scenes.Base import Demo
from omni.physx import _physx
import omni
SCALE = 50.0

    "width": 2048,
    "height": 1024,
    "renderer": "RayTracedLighting",
    "samples_per_pixel_per_frame": 64,
    "max_bounces": 10,
    "max_specular_transmission_bounces": 6,
    "max_volume_bounces": 4,
    "subdiv_refinement_level": 2,
    "headless": False,
    "experience": f'{os.environ["EXP_PATH"]}/isaac-sim-python.json',

def main():
    kit = OmniKitHelper(CUSTOM_CONFIG)

    # Get the current stage
        translation=(0, 200, 0),
        attributes={"radius": 100, "intensity": 100000.0, "color": (1, 1, 1)},
    collision_report = ContactReportDemo()
    stage = kit.get_stage()
    frame = 0
    print("simulating physics...")
    while frame < 120 or kit.is_loading():
        kit.update(1 / 120.0)
        frame = frame + 1

    while 1:
        kit.update(1.0 / 60.0, 1.0 / 60.0, 4)
    # Return to user specified render mode
    # everything is captured, stop simulating

if __name__ == "__main__":


How are you running that script? Could you detail about launch command, environment configuration, current working directory, etc…?

I am running that command using python 3.6 in terminal and I set up the environment following this The working dir is python_samples. Please let me know if you need other information.


Sorry for my late reply, last week was very busy.

You can also reproduce the demo as a custom extension and enable it Window > Extension Manager

For example:

    |-- config
    |   `-- extension.toml
    `-- scripts
        `-- test


display_name = "Test"

"omni.kit.editor" = {}
"omni.physx" = {}

name = "scripts.test"

import omni.kit.editor
import omni.ext
import omni.appwindow
import omni.kit.ui
import gc
import asyncio

# ------------
from omni.physx.scripts.scenes.ContactReportDemo import ContactReportDemo
# ------------


class Extension(omni.ext.IExt):
    def on_startup(self):
        self._editor = omni.kit.editor.get_editor_interface()
        self._usd_context = omni.usd.get_context()
        self._stage = self._usd_context.get_stage()
        self._window = omni.kit.ui.Window(
        self._load_btn = self._window.layout.add_child(omni.kit.ui.Button("Load"))

        # ------------
        self.collision_report = ContactReportDemo()
        # ------------

    async def _create(self, task):
        done, pending = await asyncio.wait({task})
        if task in done:

            # ------------
            self._stage = self._usd_context.get_stage()
            # ------------
            self._editor_event_subscription = self._editor.subscribe_to_update_events(self._on_editor_step)

    def _on_environment_setup(self, widget):
        task = asyncio.ensure_future(omni.kit.asyncapi.new_stage())

    def _on_editor_step(self, step):

    def on_shutdown(self):
        self._window = None

Thanks for your reply again. Yes I can reproduce the demo as a custom extension without any problem. The problem is just we want to run the program using OmniKitHelper as a python script so that the script is independent of the files under _build. However, when I tried that, the simulation just freezes when there is contact. It seems like the contact report is not supported when running simulation using OmniKitHelper?


I’m glad to hear about that. I hope this post helps you to solve your main question :)

Btw, I prefer to work with extensions due to the extensions discovery service: “extension manager constantly monitor folders for changes and automatically syncs all extensions found in specified folders”. Then, the code is reloaded after any changes without the need to restart the simulator…