3dsmax-modeling

3ds Max Modeling Tools

Create primitive, Lathe, spline, curve-model, and loft geometry in the current 3ds Max scene. All tools touch the live scene through pymxs, so they declare affinity: main.

create_box retains depth as its public parameter and maps it to native Box length. Dimensions must be positive finite numbers in scene system units; the response reads them back from the node. A mismatch or unreadable dimension fails with the created node identity; the node remains available for inspection.

lathe_profile accepts two to 256 [radius, height] pairs. Radius must be non-negative; both values must be finite. It creates an XZ-plane spline and uses the native Lathe axis. The action reads back the spline knot count and modifier settings, and removes the new node if those postconditions differ.

Splines and curves

draw_spline builds a spline shape from an ordered list of world-space XYZ triples. It supports create, append, and replace modes over one spline index. Points are converted into the shape's object space, committed with updateShape, and read back in world space; a point that does not come back fails the call and removes the node the call created.

inspect_curve reads every spline of a shape as world-space knots with their in/out handle vectors, and returns a token that digests the geometry it read. edit_curve requires that token: if the spline changed since it was issued, the edit fails before anything is written. After an edit, every requested field is read back, and a field that did not take effect restores the captured knot state and fails the call.

curve_model adds a named, parametric layer on top: a rounded_rect, rectangle, circle, or polyline profile, optionally swept along a path spline with the native Sweep modifier. The parameters that produced the profile are stored on the node, so read and update work without repeating them, and list enumerates every stored curve model in the scene.

loft_mesh lofts two to sixty-four matching cross-section splines, optionally along a path spline, into a quad loft. The registered shape count is read back and must match; surface parameters are applied one by one and read back, so a parameter the host ignored fails the call and is returned in rejected_surface_params rather than being reported as applied. The rule is the same on create and on update: what differs is only what can be taken back. A create removes the node it just made, while an update keeps the caller's node - the accepted parameters stay on it - and takes only the cross-sections this call added back off.