Redacted

cridgit

​Redacted

Richard Haseltine

Sorry, no - I think the ections on the geometry pipeline went away while the strand based features were being worked on (to keep cats in bags) and they haven't yet come back. You could try using the discovery technique on DzShape to see if there was anything hopeful. Create a promitive and try tghis (no error checking at all):

// have a node with geometry selectedvar node = Scene.getPrimarySelection();// get it's geometryvar geom = node.getObject();// and its shapevar shape = geom.getCurrentShape();var member;// list the members of DzGeometryprint( "DzObject contains:" );for ( member in geom ) { 	print ( "\t" + member );}print( "\n======================================\n" );// list the members of DzShapeprint( "DzShape contains:" );for ( member in shape ) { 	print ( "\t" + member );}

I see some functions related to Leaf regions, which might be applicable (since regions are arranged in a hierarchy)

Richard Haseltine

Rob points us to setPropertyPath() in http://docs.daz3d.com/doku.php/public/software/dazstudio/4/referenceguide/scripting/api_reference/object_index/scenehelper_dz , using an existing property to see how the paths work:

The path to pass in should start with the hierarchical structure of the (labels of) regions, starting with the root region, down to the target leaf region, followed by the property group hierarchy within that region. Look at the path of an existing property for an example. Save yourself a lot of confusion that will result from trying to use the undocumented (unpublished) DzGeometryRegion directly.

cridgit

​Redacted

cridgit

​Redacted