It only compiles once? I.E. does it act like colladra files? So we could remove the source files and it still has the cache version. Also, how will the format be controlled? As in what format will it be compiling it to and from, and do you want to limit these maps to that format alone? So in short, would it be taking tiffs as the input? Could it take a Photoshop, Krita, or Gimp document with layer folders named and auto separate those out into the correct channels? Would it only export out like a dxt5 dds? Some artists and company workflows use a master image file to work from. Each portion of the material texture is under its own folder in this image file. Having to export each folders as separate files if done more than a few times wastes time. Yep, we can create scripts/actions to help with this in the art programs. But its almost as much time as making a script to do option 1. Anycase if three wins out, could it be setup that all master images that are being combined can be chosen outside the materials folder (or even the engine directory)? As to keep it clean, and not having redundant information sent if using svn, the images that are linked to the combined compile version do not have to be in the same directory. Use local directory information using the material folder as the master path vs that computer as so it wont break the link as easily if one of the images is edited on another computer. Kinda redundant with 3.