[wzhang11]

Help>
Hi guys, im using the starccm+ to oscillate a cylinder in x direction, the period is 20s, whole physical time is 100s. the images show cylinder stop moving at 68.89s, but the plot shows it still moving, so im confused now, where am i wrong?
P.S. DFBI> general planar motion>2*sin(0.314*$Time)
Using update in the scalar scene to export the images
The physical time in the images afterwards the 68.89s is the same. 68.89s

Cheers
Jason

[me3840]

What version are you using? This is likely a consequence of the combination of your hardware and how often you render the image. If you render the image fewer times per several timesteps, it will probably start working again.

The server doing the calculation can get ahead of the client which renders the graphics - so much so that the client gets 'stuck' rendering the same thing over again. In newer versions the client will force the server to wait until it's completed rendering images.

[wzhang11]

Originally Posted by me3840

What version are you using? This is likely a consequence of the combination of your hardware and how often you render the image. If you render the image fewer times per several timesteps, it will probably start working again.

The server doing the calculation can get ahead of the client which renders the graphics - so much so that the client gets 'stuck' rendering the same thing over again. In newer versions the client will force the server to wait until it's completed rendering images.

Hi me
im using the version 9, The i set time-step size to 0.01s and the other settings are default under the updates. so how could i force the server to wait?

cheers
Wei

[me3840]

You need to increase the frequency that you save images at. Look a the properties for each scene.