Based on my observations of IGS (Indigo Scene) files, there are opportunities for Reallusion to improve things, and other places where they'll be constrained by Indigo.

STATIC PROPS THAT DO NOT CHANGE could be written to a single, "common" mesh folder.  The IGS files could then point to those items in that folder.

ANYTHING THAT CHANGES SHAPE, such as avatars, cloth, and trees with wind, etc., need to be exported for each and every frame, because Indigo will render the mesh as-exported.

It looks like an IGS file can provide an XYZ translation/rotation/scale offset for a mesh.  That would be great because you could use a single mesh file even for props that move.  You'd put the translation information in the IGS file and still use a single, common mesh file.

They could also use a single mesh file with frame-specific texture files for items with dynamic materials.  But you'd still need unique mesh files if it changes shape.

It would take a little extra processing power during eh export to be smarter, but you'd save a ton of disk space, and it would probably be a faster export too, since you'd be writing fewer gigabytes to your hard drive.

---

iClone 7... Character Creator... Substance Designer/Painter... Blender... Audacity...
Desktop (homebuilt) - Windows 10, Ryzen 9 3900x CPU, GTX 1080 GPU (8GB), 32GB RAM, Asus X570 Pro motherboard, 2TB SSD, terabytes of disk space, dual  monitors.
Laptop - Windows 10, MSI GS63VR STEALTH-252, 16GB RAM, GTX 1060 (6GB), 256GB SSD and 1TB HDD