assimp VS tinyobjloader

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++.

Obj file parsing isn't really OpenGL... But you can take a look at this GitHub project: https://github.com/tinyobjloader/tinyobjloader

For the Blender export part, the simplest 3D model format is OBJ. It's a text format that can be read in only ~100 lines of code. You can use Assimp for this. Or you can use something like tinyobjloader: https://github.com/tinyobjloader/tinyobjloader

I've replaced tinyobjloader with fast_obj which speeds up model loading process significantly. Here is a good article comparing different obj loaders.

I don't think this is an issue with tinyobjloader but I'm unsure of how to troubleshoot from here. I've been following this tutorial to learn opengl.

Exampes I've seen are the stb single header libraries, as well as tinyobjloader. The necessity to do this is usually written in the comments at the top of the header file:

If you´re using tinyobjloader, the documentation here https://github.com/tinyobjloader/tinyobjloader explains how it works. There´s even a triangulate flag.

Try Tiny obj loader: https://github.com/tinyobjloader/tinyobjloader

Also, it's possible to store a color per vertex, tinyobjloader supports this extended format for OBJ. But, like you say, how many (if any) OBJ loading programs actually support these vertex colors I suspect you can count on one hand (and more likely, zero hands). Blender, for example, does a terrible job even interpreting cutout objects in OBJ files, a common case (see step 9). I doubt they'd ever add per vertex color import support for any file format they read in. But, I'm interested to hear if they do - Blender is (by far, I believe) the main DCC app used with Mineways exports.