Well, when I imported a Noesis-generated FBX and found it had ~70++ sub-rigs, each with its own material calling one of ~25+ texture sets (DSB+T), I was a tad disheartened...

--

As I understand it, GPU rendering must load all textures along with the models.

By analogy with meshes where, IIRC, 'Duplicate' command thriftily references original OBJ, PP2 or CR2, while a new library load or import piles up over-heads, how does eg Superfly handle texture calls ??

I've just thought, with a shudder, that auto-loading or dragging in a texture might add significant over-heads, while selecting from drop-down list --The one starting with 'None'-- may not...

A minor issue for 'simple' scenes but, when you're invoking a bunch of 2k, 4k, even 8k texture sets per material, with HDRI back-grounds...

Any chance of the Coder Gurus laying out the resource costs ??

Also, a plea for an 'engineering' dashboard' so we know what's stretching Poser, and so how close to failure we're flying...