Christopher Knappers

Hi there, yes we are unfortunately currently missing print and error callbacks in APEX. In the meantime, I find the best way to debug is to format debug log statements as strings using the string::Format callback and associated string formatting syntax in APEX Script, and then wire the debug strings to the output of the graph, or collect the list of all debug prints in a StringArray and wire that to the output of the graph. I also find the "Inspect Line" feature quite useful for finding where in a graph a particular line corresponds to, so that I can directly inspect the graph to find issues there.

Hello, if you expand a set you have created you are able to see a hierarchy of controls inside with the character name, rig name, and the control names under each rig. In this context "item" refers to a row in the tree corresponding to a character, rig, or control name. Doubling clicking on one of these items will let you rename it which can be used as a way to manually change the controls contained in a set. One option while renaming is to supply a pattern. For example, if you change the character name from "mychar.char" to "*.char" then that subtree underneath the character item will now apply to every character matching the pattern. The same can also be done with rig or control items in the tree, for example you could rename a control "wrist_*" to match both "wrist_l" and "wrist_r".