assimp VS opengametools

If you use something like libassimp https://github.com/assimp/assimp it will allow you to import these and access the data to generate your Vertex Array Objects then render to a frame buffer object.

If you just want to load other data in a relatively simple fashion, assimp https://www.assimp.org supports loading a bunch of different formats and is pretty easy to use.

The emscripten interface for the assimp library. It runs entirely in the browser, and allows you to import 40+ 3D file formats and access the result in JSON or glTF format. This is not a full port of assimp, but an easy to use interface to access it's functionality.

I ran into what sounds like a similar problem a few months ago. It turns out this was an assimp bug: https://github.com/assimp/assimp/issues/1974

You could give assimp a go (there is a python version) i've used it for 3DS before then you can export to something else. https://github.com/assimp/assimp/blob/master/port/PyAssimp/README.md

I have checked the source code for GLTF for this and it is not handled by Assimp. I created an issue as in their Github.

Assimp is your friend

Have you read the license? It's quite permissive. https://github.com/assimp/assimp/blob/master/LICENSE

There is probably some library more specific to your use case, but you can use assimp to load 3d models in C++.

Note for programmers: we use ogt_vox.h from opengametools by /u/jpaver so if you're using C/C++ you should be able to add .vox loading to your code which supports scenes exported by Avoyd relatively easily with this.

Check out ogt_vox.h by /u/jpaver which can read/write vox files.

Alternatively you could load the .vox data with the ogt_vox.h library and mesh it yourself.

The .vox cloud transparency issue was due to me not realising the transparency parameter wasn't set for these, so I had to set it on import to fully transparent. The import order issue was in part due to changes in the opengametools/ogt_vox.h import library I'm using and in part due to differences in the newer .vox file version order or how the import library handles these.

If you can program you might be able to do this yourself using a library like ogt_vox to write out the resulting vox file, along with code like Assimp to import the geometry. If the vertices are all on a unit grid it should be relatively trivial to go through the quads (2xtriangles), calculate the face normal, and modify the voxel just below the quad with the texture sampled from the texture coordinates.

You might find looking at the implementation in ogt_vox.h useful, along with this discussion about the materials.

I took the liberty of writing up a very basic demo of how to do this using the library: https://github.com/jpaver/opengametools/blob/master/apps/voxseparate.cpp - hope this helps.