As cage has pointed out, it might be simpler and certainly easier for many situations to simply switch the figure out for another figure - except where the person geneerating the different Uv map doesn't have the relevant rights.

This technique as it stands now, with my limited ability with PoserPython (and within what PoserPython can, itself, do) has these "features":

*Cannot currently select files - trivial I guess, but it would still take coding effort however trivial.

*Doesn't have nice library thumbs to run it. Should also be trivial

*UV file (currently with a .tvs extension) MUST match the currently selected figure/.OBJ file to work in terms of texture vertex counts and texture vertex seams.

*Minimal testing has been done - as I've said earlier, this is an early alpha, a "proof-of-concept" type test. More testing would be needed to make sure it's not screwing up somewhere. I'm a little bit suspicious of some of the code as PosePython is lacking some features I'd like - so at the end of the day my code makes more assumptions than I'd like which is limiting the functionality of the script.

*Design issues - at the moment, since I don't actually "feel" a marketplace for this script, I don't know whether it should prompt the user to locate the file to load or have a script per texture set so it's a one-click solution at the end point. Having the user select a file after running "Load UV" would be easier to maintain, I suspect.

*No animation - this isn't about animating from a Michael2 texture to a David3 texture to a Victoria 5 texture all on a single model - it's just about uv texture vertex switching. Bam - on or off, one way or another (or another or...)

*Slow (IMHO). It'd be better to have something written in native code in Poser itself, IMHO.

*Money. I've a kid to feed - if this would only sell to 5 people, or be used by 15 people as a freebie, then development will have to be minimal!

*All sorts of other stuff, I'm sure. but I forget for now. For example - were this to aim for "paid", what's the cheapest Renderosity allows? Because unless it's going to REALLY help merchants it's not worth a lot IMHO. Too simple. As with my Genesis tut, my Python coding skills just aren't all that impressive I'm afraid - I just throw rocks at it until the damn thing works LOL

At the moment it's basically slower than the same kind of feature in DAZ Studio, but also more limited. As the DS 4 feature has under-the-hood access it's able to swap to a completely different UV layout - different seams, different numbers of texture vertices. Otherwise it's the same kind of concept - switching or swapping UV data rather than animating from one set to another, with all the complciations that would arise from that.

Cheers,

 

Cliff