Blender files can have meshes such as circles, cubes, cylinders, a dragon or any other 3D shape.
A mesh can be represented as a group of vertices and data about those vertices, such as their normals or UV coordinates.
Meshes can also have metadata, such as the name of it's parent armature (useful for vertex skinning).
blender-mesh-to-json seeks to be a well tested, well documented exporter for blender mesh metadata.
You can write data to stdout or to a file. At the onset it will be geared towards @chinedufn's needs - but if you have needs that aren't met feel very free to open an issue.
@see https://docs.blender.org/manual/en/dev/modeling/meshes/introduction.html - Mesh Introduction @see https://github.com/chinedufn/blender-actions-to-json - Exporting blender armatures / actions
All of the data about a Blender mesh
The bounding box that encompasses a mesh. This will usually come from Blender as a z_up coordinate system bounding box that you'll later convert to be y_up.
Configuration for combining multiple indices into a single index
Something went wrong in the Blender child process that was trying to parse your mesh data.
An individual channel within an image. Red, Green, or Blue.
An error when trying to flatten your exported data across multiple files into one HashMap of mesh name to mesh data.
An input to a material property.
Convert MesheshByFilename into a HashMap<MeshName, BlenderMesh> that flattens all of the meshes across all of the files into one HashMap.
Given a buffer of standard output from Blender we parse all of the mesh JSON that was
written to stdout by