Can someone explain drago compression to me. This original file was 5mb. After dragon compression it got down to 700kb. How does this work. Even it have same number of vertices and triangles and on import i dont see a difference but I read some posts that it is lossy. Where exactly is it getting the loss?
Candle.glb (780.5 KB)
Hi there,
I haven’t heard of Drago compression, doing some research did you mean Draco compression? There seems to be lots of information about that online.
First: it’s Draco..
You wanna go down the rabbit hole of compression ? Well.. first it’s especially design for 3D (from github):
Draco was designed and built for compression efficiency and speed. The code supports compressing points, connectivity information, texture coordinates, color information, normals, and any other generic attributes associated with geometry. With Draco, applications using 3D graphics can be significantly smaller without compromising visual fidelity. For users, this means apps can now be downloaded faster, 3D graphics in the browser can load quicker, and VR and AR scenes can now be transmitted with a fraction of the bandwidth and rendered quickly.
and.. it’s all in the source… 
The loss in compressing geometry lies in the exactness. Acording to my info Draco truncates Floating Point values and is therfore “lossy”). Imagine a vertex/point with x value of “321.14647656524” truncated to “321.1464”. This reduces the required amount of data a lot.
Visually I newer had any issues. But I guess if you would zoom in extremly, it would be visible (e.g. like zooming in on a city model to a window of one of the houses).
Therefore I would use this format exclusively for exporting my data zu e.g. a 3D engine/Browser.