THREE.jsand its OBJExporter.js on the Scripting side.
- Devise a way to spatially-interact with “control point” vertices (like maybe how we edit Bézier curves in 2D?).
- Utilize an in-memory THREE.js geometry to represent the structure – which can easily be exported to OBJ format.
- Then upload the OBJ data via scripting to APT – emerging a virtual
- And then reference the resulting
atp://link as usual from a
The last three steps are reversible – it’s possible to read-back the
.obj data and import it into a THREE.js geometry again using OBJLoader.js.
I’ve not tried decoding OBJ files from scripting yet – but generating them and exporting to ATP seems to work fine (in fact, that’s how I implemented my dynamic 3D text experiment way-back-when – using THREE.js’s TextGeometry to extrude OBJ models on-the-fly and while in-world).
Might be a tad too slow CPU-wise to work on super-dense models, but if applied conservatively (like to manage a few tens of thousands vertices at a time) it seems plenty feasible.
Anyway, just tossing the idea out there as a potential stop-gap – while waiting on even-better ways to do in-world editing. If anybody has a strong interest in exploring this approach let me know and will attempt to share a few starting points.