cgltf VS LZ4

If you want to go all the way, https://learnopengl.com/ is a favorite around here. You could build a glTF viewer from scratch starting from that tutorial and https://github.com/jkuhlmann/cgltf and eventually building towards https://google.github.io/filament/Filament.html or whatever wacky artsy direction you like.

Use https://github.com/jkuhlmann/cgltf to parse the files. https://github.com/ocornut/imgui for your UI. Maybe https://www.libsdl.org/ just to set up a window, handle mouse clicks and initialize the GL context in that window.

Use glTF and https://github.com/jkuhlmann/cgltf Or, looks like you are using C#, so https://github.com/vpenades/SharpGLTF

Do you really have to use fbx? An open format like gltf is better supported, and there are bazillions loaders(I use cgltf without any issues, which is also used by raylib, Unigine and bgfx). It's also a perfect fit for OpenGL.

I recently discovered this pattern in cgltf (https://github.com/jkuhlmann/cgltf), and I agree, it makes deployment so much nicer.

Use https://github.com/jkuhlmann/cgltf It’s the most popular loader.

It's easy to generate a BVH for a generated triangle set (like a fractal pyramid or a dense cube). But, quickly generating a high quality BVH for a loaded model requires some research. Use https://github.com/jkuhlmann/cgltf to load models.

Write a simple glTF viewer in OpenGL. This is a throw-away warm-up. So, don't fret over the code. Don't do anything complicated. Shoot for a simple, forward renderer for a simple, animated character with trivial Phong lighting, diffuse map, normal map and a basic directional shadow map. Use OpenGL ES 3.0/GL 4.3 API with no crazy features. Don't worry about performance. Use https://github.com/jkuhlmann/cgltf to load the files. KTX is a great container for textures.

LZ4 is a bit more complicated, but seems faster: https://github.com/lz4/lz4/blob/dev/doc/lz4_Block_format.md

According to these https://github.com/lz4/lz4 values you need around ten (10) quite modern cores in parallel to accomplish around 8GB/s.

The popular NoSQL database Cassandra utilizes a compression algorithm called LZ4 to reduce the footprint of data at rest. LZ4 is characterized by very fast compression speed at the cost of a higher compression ratio. This is a design choice that allows Cassandra to maintain high write throughput while also benefiting from compression in some capacity.

Yeah, sure, when you have monster core counts. on regular systems, not so much, here's from their own github page. it achieves, eh, 5GB/s on memory to memory transfers, i.e. best case scenario. so, uh, no? i'm not even sure it's any better than the CPU decompressor one Nvidia used.

> The downside of lz4 is that it can’t be configured to run at higher & slower compression ratios.

lz4 has some level of configurability? https://github.com/lz4/lz4/blob/v1.9.4/lib/lz4frame.h#L194

There's also LZ4_HC.

Since nobody mentioned it, I'll add lz4 (https://github.com/lz4/lz4).