I have recently purchased Poser 11 and have been viewing tutorials for the clothroom specifically... I have followed the tuts to the letter and after calculating a simulation to the 30th frame the screen quickly flashes a Poser character (torso) and quickly flashes back to the beginning of the simulation as if it hadn't been calculated.... When I play the simulation that was just calculated, it clicks through frames 1-30 and nothing happens as if the simulation had not been calculated... I checked the Poser forum at Daz and it was suggested that I check the Smith Micro download manager to see if there was a specific installer for the clothroom that I had overlooked during the program installation... but of course there was no such animal in the SMDM.... I contacted support at Smith Micro and he suggested that I, in the render settings in the preview tab uncheck the OpenGl and check the SreeD... which I did and I stlll got the same non-results... His latest suggestion is for me... after the simulation is calculated I should save the project... I am not on the computer with Poser right now... I will try that later today, but does anyone here have a similar issue that you perhaps resolved? I am on Windows 10... Poser 11...AMD Radeon graphics processor ... and just learning Poser... Help please Steve

Failure to calculate can be caused by many different things. How current is the tutorial and what exactly are you trying to drape on the figure? Provide as much information as possible to correctly determine the best course of action.

Well, as it turns out ... the wisdom from Smith Micro was spot on... after calculating the simulation I saved the project... I played the simulation and ... there you go... the simulation played as if I had done something correctly ... So for me this issue is resolved

However, you should be able to play any simulation immediately after completion. Have done that many times in the past. Strange behavior, but glad it worked out.

Wow! you've gotten some bad advice!
The Cloth room is part of the Poser program and not a separate download.
ScreeD is the legacy render engine used in Poser 4 or so. it's older than FireFly.

The Cloth room works fine for me.
This is a Truly BAD simulation of a Disk over Andy's head... it pokes becuase there aren't enough polys for it to bend correctly.. So the Poser 11 Cloth room does work. It's just not behaving for you! ;(

Sometimes I have seen the play LOOP get turned on by mistake, which gives you a FAST version of the simulation, but you can generally see the fabric simulation.

Can you try a one frame simulation and see if that works?

STarting with poser 11, you have to have the scene saved before you run a simulation otherwise poser resets it. Unfortunately, most of the tutorials were written before p11 so they don't include this step. I also think it might be a bug but have no proof of it.

thanks... yeah, saving the scene did it for me...

RedPhantom posted at 2:37AM Sun, 05 August 2018 - #4333456

STarting with poser 11, you have to have the scene saved before you run a simulation otherwise poser resets it. Unfortunately, most of the tutorials were written before p11 so they don't include this step. I also think it might be a bug but have no proof of it.

Huh? I've done lots of simulations without saving the scene first?

TrekkieGrrrl posted at 6:30AM Sun, 05 August 2018 - #4334207

RedPhantom posted at 2:37AM Sun, 05 August 2018 - #4333456

STarting with poser 11, you have to have the scene saved before you run a simulation otherwise poser resets it. Unfortunately, most of the tutorials were written before p11 so they don't include this step. I also think it might be a bug but have no proof of it.

Huh? I've done lots of simulations without saving the scene first?

I've done some too. One of the patches fixed it somewhat, but not entirely. I still lose some and it seems others are too. It usually seems to be the fix that works.

Another thing ... I made a new dress for PE tonight. And the cloth simulation kept failing at Frame 1. I couldn't understand it (still can't, really ...) - but I managed to fix it by pulling the obj into UVMapper. It claimed some vertices (or whatever) was out of bounds, so I asked it to fix it. And then it worked like a charm.

I won't claim that this is a solve-all, but if it's some home made garment that fails, it¨'s worth a try :)