Are there any disadvantages of asset compression?

There are many advantages and disadvantages to asset compression. You as a developer have to know where you are deploying your application and what that particular device(s) need(s) is/are. You have to know which assets will compress, which assets are already compressed, which are compressed by V3D compression methods and which are not. You have to determine your memory requirements, GPU capabilities, etc.

If you are delivering your application via the web…compressing is generally a good rule.
If you are delivering your application locally then you can test the which method produces the best result for your purposes.

Disadvantages – potential over compression, images/texture color space modification, … same things you run into when compressing an JPG.

But compression is both an active process you as the developer need to do and a process V3D an other applications do for you. As examples: A movie file…. you will need to compress this on your own to .mp4. A JPG you use as part of a texture. The JPG is already compressed and when you create the GLTF you may end up compressing it again…and get mixed results. Your 3D file is being converted to GLTF and a BIN. the .XZ compression provided through V3D makes for smaller files. Smaller file size to download for mobile devices…but may take a little longer to unpack once at the device but will be dependent on the device hardware your app is running on….for the most part the .XZ compression works pretty well.

The big issue is people often create applications that are just too large and then want compression to solve the problem. There are physical device memory limitations and bandwidth restrictions, etc. The best compression is the developer managing their assets and only loading the things they need and unloading them as required.

Hi,

Generally, Asset Compression is fine in every case, while Texture Compression should be enabled if rendering and GPU memory savings are more important than loading time.

kdv wrote:

It would be nice to have DRACO compression implemented into Verge3D exporter (instead of LZMA).

Sometimes DRACO performs worse compared to LZMA. Also, DRACO is lossy while LZMA keeps your geometry data intact.