Quote - actually, ww has it's limits.   i've had a lot of trouble converting some items, but none with others.  it's a tremendously great tool, but not a magic bullet.

Agreed, but can you mention something better?  I've heard horror stories about Tailor and that's about all I know is in real competition with WW.  It can do quite a lot, and it is specifically mentioned that ymmv and you may need to tweak - this goes without saying.  Matching clothes from disparate figure to disparate figure is not a science - it is guesswork and some 'magic'.  Not knowing the limitations of the Python SDK for Poser, it may be that doing all of the work is 'not possible' (I've heard those two words enough for SDK programming!).

I don't want to deal with Poser dynamic cloth - it's slower than molasses buried in Antarctic glaciers (and I'm on a dual Xeon!).  For the cost of Poser, it is a great asset.  For practical use, it is mostly impractical.  In the time that you do a 'dynamic calculation' of cloth, I've done several hundred in C4D with Clothilde (for instance).

My point is, people keep moaning "but wherefore art my V3 clothes to goeth, kind gentle sir".  What?  You can't do anything with WW when the V4 support is added - at all?  Most certainly doubtful.  So, several of your three thousand V3 wardrobes will fail - consider the cost of all over those few equated to the cost of WW (!!!).  If you can convert ten or twenty, that pays for WW and pays you back.  Where is the downside of this?

C makes it easy to shoot yourself in the foot. C++ makes it harder, but when you do, you blow your whole leg off.

 -- Bjarne Stroustrup

Contact Me | Kuroyume's DevelopmentZone