ObjToSchematic VS lume

I found a 3D model of a conch shell (OBJ format) and I uploaded it to objtoschematic.com where I decided the final size and which block to use. The site produced a structure file (nbt) of the shell composed of only pink wool blocks.

I personnally tried opening it in this .obj to schematic converter, but my friend also told me he tried in blender to the same result

ObjToSchematic was probably used to covert a 3D model to a schematic and probably Mineways to covert the schematic back to a 3D model to be re-rendered in Blender, explaining the pure pink background.

The project is Lume, working towards a 1.0 release. Lume provides a set of HTML elements for 3D rendering, built on three.js for rendering, with a system for defining new custom HTML elements with reactivity and templating powered by Solid.js.

This is awesome. We could totally turn this into a playable untap.in competitor using websockets and a framework like React/Solid or LUME

With that said, the situation looks different when looking at third-party tools. There are still some interesting libraries like Solid wrapper around Heroicons or Lume - a toolkit for interactive 2D and 3D experiences, but that’s about it. Still, with an already good first-party collection and numerous framework-independent tools, developing production-ready apps with Solid shouldn’t be a problem.

I'm actually working on a rather large Solid project right now and will post it in our community when it's live. There are a lot of really neat things built on Solid, checkout Lume (https://github.com/lume/lume) which uses Solid for it's elements and even an IDE https://www.glue.codes/.

lume / lume

While I write documentation for LUME, a 3D HTML toolkit, I will be posting demos that I create for the docs. I am posting one demo per day all 2021.

lume / lume