Evan Robinson

I found the issue. I found the solution by downloading the character switching file and comparing how it was built:

https://www.sidefx.com/contentlibrary/character-switching/ [www.sidefx.com]

in the rigging with apex tutorial when he creates the guide properties, he gives the attribute the wrong name. He puts in "parms". In the character switching file the attribute name is "properties" and not "parms".

If I update the name to be "properties" it starts working.

edit: I found in the docs where it says to use "properties" too.

Hello,

I am trying to follow the KineFX rigging with APEX training. I am on video 6 where it talks about using attribute adjust dictionary to create the point attribute that tells apex graph to promote either translation, rotation, or scale (see photo). The video adds that the dictionary attribute created will override the values that are put directly on the apex auto rig node (see photo).

https://www.sidefx.com/tutorials/kinefx-rigging-with-apex-1/ [www.sidefx.com]

However, those dictionaries don't seem to have any effect at all. I was unable to get them working on my scene, so I downloaded the tutorial files and the promoted parms seem to have no effect in the file provided from SESI either. Take a look at my video. When I select the FKautorig node, there are no controls showing in the selection sets or viewport. If the dictionary is to control these t/r/s promote groups, I would expect to see controls in the viewport (since these values are supposed to come from the dictionary), right? Once I type in "*" you can see the apex graph actually update and add the t/r/s nodes in the graph. Furthermore, if I go to the scene animate and try moving a limb then disabling the attribute dictionaries, nothing changes. Note that in the video I made a mistake because it is loading the character from disk, so disabling nodes wouldn't affect it. However I also tried connecting the scene add character node to the nodes above (and not the file node) so that it is reading the nodes above and NOT the bgeo file and I still had the same issue. Am I just not understanding something? I would appreciate any help.

Thanks

Thanks again!