So I had to type in integers, one at a time, until I found the ones that were associated with 'A_FILENAME' and 'A_RELOAD'. When you pass a string value as the name of an attribute it errors out. This is my first Lua script - the tough part was figuring out how to get the attribute values of the Octane nodes. Mike Pavlovich was asking for this, so I made it for him. I finally made the lua script to load polygroups from ZBrush as material inputs. Would Love an easier quicker way, but I think the main thing here is about how Rhino is poorly handling high poly mesh.Īnd the ZB with will be to be able to import rhino Curves converting them to ZB curves. STL, I’ll again open in Rhino to verify all dimensions remains as intended. The finished part decimated and exported as. Then these parts are exported to ZB for Live boolean, and the sculpting work. There for the ZB mesh in rhino is used locked while creating additional parts. Yet in Rhino 1 mil poly is already too much for it. I’d imagine a stronger computer will be more responsive…? My old machine can manage a 10 mill poly object in ZB easily. Lock it! and make no attempt to edit that mesh in Rhino.

the best way I found by now, is to send a decimated version. It comes in very cleanly as a fairly dense quads.

! -Export Pause GeometryOnly=Yes SaveTextures=Yes SaveNotes=No “/Users/akash/Zbrush Work/FromRhino.obj” VertexWelding=Welded YUp=Yes Enter DetailedOptions AdvancedOptions Angle=0 AspectRatio=6 Distance=0.0005 Density=1.0 Grid=0 Ma圎dgeLength=0 MinEdgeLength=0.0001 EnterEndĪnd if it was a subD object then it can usually be directly worked on in Zbrush. With the help of a number of people here, I ended up with this Macro:

Zbrush polygroups