SPLINE-2-POLY v2.3 HAS BEEN RELEASED
Spline-2-Poly v2.x is a UI-driven MaxScript for Autodesk 3DS Max which can be used to create editable polygon meshes from closed loops of 3- or 4-splines.
The video previews show the basic functionality of Spline-2-Poly:
The first shows how meshes are created, modified, imported etc.
The second show additional right-click functionality which was added after the initial video was uploaded.
The third video is a Pre-release demo of S2P v2.2 which adds a user-requested feature currently named "Vertex Snap" (this has been renamed to "Vertex Mapped Patch" in the final release.
A fully-commented source code is included.
This is a Commercial Script
Known Bugs in v2.1
1. The UI does not activate the "Create the Mesh" button when importing a mesh that was created with a blank name. The workaround is to import the mesh, change the name in the Spline-2-Poly UI (not Max UI) to a non-blank value and then re-import the mesh.
Bug Fixes in v2.2
1. In Spline-2-Poly v2.1, it was not possible to create a mesh with a blank name field, but it was possible to create a mesh and then delete the mesh name in the UI. Once this blank name had been changed and saved as custom data on the mesh, it was possible to import the mesh but the UI would not activate the "Create the Mesh" button. A workaround was to import the mesh, change the name and then re-import the mesh.
This has been fixed in v2.2 which now allows Blank name fields (although not recommended)
2. When importing a named mesh which had been renamed in the Max UI, Spline-2-Poly would import the original name of the mesh as specified at creation time. In v2.2, the UI now imports the scene name of the mesh even if it is blank (see bugfix 1)
Bug Fixes in v2.3
Under certain circumstances, the new mesh creation routines in version 2.2 could cause “mesh pinching” and misalignment along some edges. This did not show up during testing (and still doesn’t) but has been proven to happen on a user-submitted file. Existing customers should have already received this update.
(Although no one has pointed it out yet - v2.3 was a "quick-fix" and I forgot to update the version/build numbers in this version - apologies for any confusion)