Scripting question (3)

[jsh3d]

Hello

I am trying out scripting for the first time, so this question might not be relevant. My problem that I'm having is that I have a particle simulation that after about 1000 frames causes XSI to crash. I think this is happening because it overloads. So, it there that you could script this:

go to next frame
wait 10 seconds for it to calculate

I have found out how to make it to go to the next frame, but I haven't been able to find the command to get it to wait. I think this script would solve my problem, because my guess is that if I were to go frame by frame through the animation it wouldn't overload. But, since the animation is several thousand frames long, I don't want to have to click the next frame button for 3 days. Thank you in advance for any help you can give me.

-JSH3D

[cowsmanaut]

I don't think it's a problem with 1000 paricles.. I have scenes that range past 5000 particles from an emmiter and have several emitters runing in the same scene without a crash.

Though it takes forever for it to update and just as long or longer to render. Are particles the only thing in your scene? perhaps it's a conflict with something else.

XSI has so many quirks it's insane. It could be a corrupt scene which can be fixed by exporting and importing back into an empty scnene. or it could simply be an argument between particles and a shader.. which could be fixed by hiding the shader untill render time.

[cowsmanaut]

oops you said frames.. but I've had them go to 1500 frames too without a crash so my suggestion still stands.

[wolfinger]

check your memory usage, while going ahead maybe 100 frames at a time. Just use the time slider to advance about 100 frames at a time. If you run out of memory in the progress then you know what went wrong...

Also, I'd have thought that XSI would "wait" automatically when you change the frame number in a script, because it has to calculate the particles for that frame before it can do anything else.

[jsh3d]

Hi

Thank for your responce, what you have said has helped. I will try going in intervals of 100 frames. The problem I have with just "nextframe" without some kind of wait is that it goes through all the "nextframes" (I copied and pasted) and then celculates the frams it just went throught

Thanks again
-JSH3D