Hello,
The way our workflow is, and not just ours, you need to version up/down caches quite a lot - in PRT Loader, for example. Right now I gotta remove the cache first, then browse again for the next one. I guess I can script it, but it would be nice to have it as a core feature.
If the version number is part of a sub-folder name but the actual PRT filename is the same, you can use the File Sequence Manager > Repath Selected Files to pick a different version. For example, if your sequence is
Z:\data\particles\partitions\someproject\somesequence\someshot\v001\someparticlename_part01of10_0000.prt
and you also have paths like
Z:\data\particles\partitions\someproject\somesequence\someshot\v002\someparticlename_part01of10_0000.prt
Z:\data\particles\partitions\someproject\somesequence\someshot\v003\someparticlename_part01of10_0000.prt
etc., you could just select the sequence(s) in the File Sequence Manager, pick the v002 subfolder in the Directory browser that pops up, and all paths that had v001 will switch to v002. If you had all 10 partitions, each partition will switch if it was selected and if the new sub-folder contained a file with the same name.
Because the PRT Loader supports arbitrary paths that can point anywhere, a built-in versioning mechanism like in Stoke would be tricky to implement. BUT, since everything is scripted and scriptable, you could write your own version manager script that knows your naming conventions and switches any number of PRT Loaders to various versions according to your rules.
You’re right, it’s very easy to script it. that’s what I’ll do.