I am making some experiments with the cloth simulation in Poser and I have a question about the "steps per frame" thing. In the manual it says that the default steps per frame value is 0.2 and that one can decrease it to a very small value to create a more refined animation. However my default value is 2, and I can't decrease it, only increase it (I am using a value of 25 right now). Was there a change on this in any of the service packs or is my Poser acting weird?

Looks more like a duff screenshot in the manual (maybe the value was originally step size).

This value is the number of iterations per frame, the higher the number (which has to be an integer) the longer calculating each frame will take.
You should only need to increase it if the item the cloth is attached to, is moving very quickly and/or the cloth is very stiff and highly stretched (25 is probably excessive, if your having problems, try 3 or 5, but it's much more likely that you need to do something else to improve the simulation).
(More smaller steps equals better solution to the equations of motion for the cloth, but at the expense of taking longer)

Two or three steps per frame works fine for most cloth simulations. Setting this number up to 30 or 40 is useful only for certain specialized simulations -- for instance, when "shrink-wrapping" an item you don't want to slip down towards the floor at the same time.

Thanks a lot. I tried a value of 5 and 3 and it works perfectly.
Another question :)
I saved the dress to my library and all that. However it seems to me that you have to setup the solver and the colliders again when you reload it? Just making sure there was no way to automate the proccess ;)  (although I suppose I could automate it with a python, if I knew how to script python...)

Any time the pose will change, you need to re-run the cloth simulation.  Re-saving the prop does not include the geometry changes that cloth simulation will make to it, although exporting to OBJ will (pretty sure).  The poserPython methods manual lists codes for setting all the dynamic cloth simulation settings, so I expect it could be automated that way, although I've never experimented with that.

In a recent issue I had with importing a piece of dynamic cloth into Vue, the "Export as Object" option was suggested a number of times. Haven't tried it, but over in that thread everyone seemed convident it would work (and suggested much better solutions to my particular problem).

  Hey, nemirc.... try posting at the Python forum, they're always up for suggestions.... Hells, they may already have something. Lou.