Isaac Sim Component Selection does not work properly

Omniverse Isaac Sim
, ,
1

The ‘component‘ selection mode does not work properly like the composer kit-app do. this bug exist in isaac sim 4.5 and 5.0. will there be any fix in the new release?
here i record a short demo of using ‘component‘ selection in composer and isaac sim

2

@richard2690905761 can you screenshot how the USD’s hierarchy looks like? i haven’t had issues selecting components prims on my end so wanted to make sure we are talking about the same thing. and have you set the model kind within your prims?

3

sure, here is the screenshot, And i did setup the kind to Component, otherwise it won’t work in Composer as well.

image
image1435×641 107 KB

image
image551×1044 78 KB

4

Thank you for sharing the screenshots and clarifying that you’ve set the kind to Component.

To help us investigate further and ensure we reproduce the exact issue, could you please:

  • Share the USD file— you used for your demo, so we can examine the hierarchy and metadata directly.
  • Upload a video— showing your workflow in Isaac Sim and Composer, including the stage window and component selection behavior. This will help us see precisely how the issue presents itself on your setup.

If possible, please note any specific steps or actions that reliably trigger the selection issue in Isaac Sim. This information will make it easier for the engineering team to trace and resolve the bug.

Thank you for your help!

6

no problem, here is the usd file

benchmark_electrical_appliance_000.zip (7.0 MB)

7

Hi @richard2690905761,

Thanks for providing the USD file — we were able to reproduce and root-cause this issue.

Root cause: In Isaac Sim 4.5 and 5.0, the Fabric Scene Delegate (FSD) — which Isaac Sim enables by default for simulation performance — did not correctly resolve USD Model Kind metadata during viewport picking. When you click a mesh in
“Component” selection mode, the picker is supposed to walk up the prim hierarchy to find the nearest ancestor with kind=component. Under FSD, this resolution was failing, so the component prim was never selected. USD Composer doesn’t use FSD,
which is why it worked there.

Your USD is correctly authored — /Aligned has kind=component with GeomModelAPI applied, exactly as it should be.

Good news: We’ve verified that this is fixed in Isaac Sim 6.0. Component selection correctly resolves to the kind=component ancestor prim, even with FSD enabled.

If you’re still on 5.x and need a workaround in the meantime, you can disable FSD by adding this to your app config or launch arguments:

  --/app/useFabricSceneDelegate=false

Note that this may reduce simulation performance.

Closing this one out. Thanks again for the detailed report and test assets — it made tracking this down much easier.