I am using the latest Isaac docker container for SDG. Unfortunately the advertised extension “omni.anim.xform_constraints” is no longer available.
Is there any alternative ways of achieving transform constraints in the latest Isaac? I need to put mobile phones in people’s hands.
cc @hclever
Creating the constraint in Machinima doesn’t work when running SDG in Isaac container.
I’m tracking this issue internally with a colleague. Others have noted the same issues. I’ll post an update when I have something concrete.
@pcallender any way to work around and somehow copy the plugin from machinima to isaac? I can modify the container as we please.
@Turowicz i tried doing that a few months back when using Composer. the Machinima you can download uses kit version 104 (pretty much all the apps in 2022), so the extension would break/stop working when simply copying the extension over to 2023 apps (which use kit version 105). that said, there’re suggestions of using the omnigraph to do constraints but not sure how that works with yaml.
Can you point me to the omnigraph workaround in python or gui? I will see what I can do script wise, because I can use python scripts and yaml together.
i haven’t seen an actual example, but this was the suggestion from one of the mods:
I have added the constrain node - it does not work in the new versions, its simply unrecognised.
i see. i don’t have any other leads, so hopefully the devs/mods can offer some additional insight (or provide a more robust documentation on how to use those omnigraph nodes, feels there’s not enough info on the official doc)
@pcallender is anything happening with regards to this? This is a serious blocker for us. ANY kind of workaround will do.
Does not exist in 4.0.0
A solution is still being discussed. There’s a lengthy thread internally, but I can’t give much right now other than this is still ongoing.
@pcallender just so you know we are forced to hire 3d artists to place mobile phones in blender so we can have them attached to the person for randomization. Many other accessories coming right after that. With all the Omniverse greatness, that one lapse is costing us serious cash.
Worked around by using composer to insert sub-USDs into the bones (Hand Left / Hand Right)
Unfortunately this workaround has exposed another issue:
The workaround is bogus! Unfortunately it crashes the replicator.
PLEASE PLEASE ADD THE omni.anim.xform_constraint PLUGIN BACK AS DESCRIBED IN YOUR OWN DOCUMENTATION: Animation Constraints (beta) — Omniverse Extensions latest documentation
cc @jlafleche pls help
@Turowicz I’m asking a colleague to weight in with an alternative solution. I know you typically work with yaml, but maybe you could restate the need here to help get them up to speed. As I understand it, its attaching rigid objects to skel bones as hard attachments, correct? Whats your preferred way to implement the attachment? (python, yaml, content?)
We have now migrated to python. We want to attach mobile phones to hands (bones or joints).
We have tried implementing as content (putting an item inside the bone) - crash
We have tried using ActionGraph - crash
Crash details: Enabling omni.anim.skelJoint crashes the app
We’ll add an UsdSkel example to see if it works for you soon here