Area
Tags / Collections / Organization
Problem / use case
This relates to my thoughts in issue #528 about the Image Map files associated with 3D files. What if you expanded the idea of a 3D Saver to include the maps in an organized manner?
Proposed solution
An input for the 3D Model and below that, inputs for the various image maps such that they all had the same filename prefix as the model but each of the image maps had a suffix for their function. So you'd have like "My Model 001.glb", "My Model 001 Texture.png", "My Model 001 Metallic.png" and so on. Maybe a field next to each image input so you could set the suffix (some renderers might use the name Metallic while others use Metalness). This would be helpful for file management in general and also be a way for IMH to parse what goes with what so you could implement some sort of show/hide or nest associated image maps function in IMH.
Priority (your perspective)
Would use often
Alternatives considered
Or instead of relying on filename conventions, the saver injected some sort of metadata in each of the files that IMH could use to match things up.
Examples / references
No response
Image MetaHub version
No response
OS
None
Area
Tags / Collections / Organization
Problem / use case
This relates to my thoughts in issue #528 about the Image Map files associated with 3D files. What if you expanded the idea of a 3D Saver to include the maps in an organized manner?
Proposed solution
An input for the 3D Model and below that, inputs for the various image maps such that they all had the same filename prefix as the model but each of the image maps had a suffix for their function. So you'd have like "My Model 001.glb", "My Model 001 Texture.png", "My Model 001 Metallic.png" and so on. Maybe a field next to each image input so you could set the suffix (some renderers might use the name Metallic while others use Metalness). This would be helpful for file management in general and also be a way for IMH to parse what goes with what so you could implement some sort of show/hide or nest associated image maps function in IMH.
Priority (your perspective)
Would use often
Alternatives considered
Or instead of relying on filename conventions, the saver injected some sort of metadata in each of the files that IMH could use to match things up.
Examples / references
No response
Image MetaHub version
No response
OS
None