Post by travelion on Aug 31, 2020 20:28:11 GMT -5
I'm trying to simplify the import process for a recolor, and was looking at the following posts for inspiration:
I see that there's a `studio.importall` cheat, but my understanding is that it only works for png files, which isn't really viable for CAS objects.
In the first post, my understanding is that a properly formatted dds file would be importable via the warehouse batch import. I've tested this by doing an export of RLE2Images, modifying the dds in Photoshop, and then re-importing, and it seems to update the diffuse texture for the swatch. The downside is that the instance IDs at first glance seem very random. Digging through it, I wanted to verify that what I'm seeing is actually how things are working.
In my example object, the type and group of the RLE2Images seems to be fixed, and the instance ID seems to be the FNV64 hash of the CASPart "Name". This means that theoretically I could add a palette via Tools->Color Palette->Apply palette to package, go to the warehouse and batch export everything, recolor using a batch photoshop action that produces filenames based on swatch number, then sort the CASPart names by alphanumeric (since they seem to append a timestamp which ends up being sequential with swatch number due to the timing) and then hash those names to know what to rename my swatch dds files to. Then finally I could re-import the RL2Image files, and that would update the package.
I'm mostly trying to see if this is a really bad idea for some reason, or if there's an easier way to go about this. Any feedback or experience would be helpful.