Instead of creating separate model files to accommodate designs that differ only in the textures of one or two meshes, I want to have one ShapeDiver model and define those specific textures via JS. One product (model) can potentially have 1000s of finishes (textures) and I’d prefer to define the relationships vs create 100s of models.
When the model is loaded, an initial texture would be set via updateAsync and the ShapeDiverImageInput. Custom user inputs would enable choice between variations of the texture (could be up to 30). Upon selection, the URL of the texture variation would be set in ShapeDiverImageInput.
I’m concerned about possible limitations? Affect on load times? Will the images be cached? Is there a better way of accomplishing this?