Allen Lee

edward
You're running into some known bugs because "addNode()" is a special function that has an override that maps it to the regular python apex.graph API. See https://www.sidefx.com/docs/houdini/character/kinefx/apexscriptfunctions.html#graph-functions [www.sidefx.com] . So for now, please use function-based syntax instead when you need to connect more than one extra port like:

graph, aimN = apex.graph.AddNode(graph, "aim_object", "TransformObject", parms={'restlocal':aimN_rest}, properties={'shape':'blob'})

Thanks Edward, this really helped me!!~~
Write it this way, it doesn't bother me anymore. speed up and play! Thanks again~

I have made a simple rigging test,It runs fine.But when I am going to add nodes and assign properties, errors will be reported. May I ask if it is irregular for me to write this way

edward
Some of this is very much in progress as we indeed are building higher-level components for the next major release.
- I'm not sure about your node named "%tag()" issue. I suspect it might due to using %tag() in a place that only expects a name, not a pattern.
- When the graph becomes too complex, APEX Script is the way we envision things going. This allows one to scale up to production rigs.

There are starting to be some tutorials in the mean that you can check out if you haven't already. Go to https://www.sidefx.com/tutorials/ [www.sidefx.com] and type in "apex" as the search term. For example, someone made an APEX Script tutorial:
- https://www.sidefx.com/tutorials/effective-apex-scripting/ [www.sidefx.com]

Thank you for your reply. I'm looking forward to the next version. I've gone through many tutorials, and although it's still challenging, things are gradually improving. I encountered some issues while creating rigs with build-in components, so I had to dive into the nodes to check and understand the logic within. It's a painful yet joyful experience.~XD,THX~