Hash Fellow robcat2075 Posted October 1, 2014 Hash Fellow Posted October 1, 2014 Here's a comparison of different size drops 4cm, emission rate 500, took a few minutes to simulate 2cm, emission rate 4000, took somewhat more than an hour to simulate 1cm, emission rate 32000, took seven hours to simulate Actual render times are from 10 seconds to a few minutes. 4cm2cm1cm.mov Quote
Admin Rodney Posted October 1, 2014 Admin Posted October 1, 2014 Ouch. Well, that would explain why A:M was 'locking up' on me when using small size particles. Regarding the jittering... I was experimenting with stepped rendering and in my test that helped tame that considerably. The idea being to render every five frames or so out of the sequence rather than every frame. Quote
Hash Fellow robcat2075 Posted October 1, 2014 Author Hash Fellow Posted October 1, 2014 Regarding the jittering... I was experimenting with stepped rendering and in my test that helped tame that considerably. The idea being to render every five frames or so out of the sequence rather than every frame. that sounds interesting. Can you explain it a bit more? I'm not sure I understand "out of sequence" Quote
Admin Rodney Posted October 1, 2014 Admin Posted October 1, 2014 Can you explain it a bit more? I'm not sure I understand "out of sequence" I should have said 'leaving frames out of the sequence'. In other words, setting the step option to some other number than 1 in the Render Options. I was playing with options of Multipass and Motion Blur too but my patience level wasn't sufficient. I don't know how effective that method is as I've been running into odd behavior of other sorts. I keep thinking I've got some settings that work well only to find out they don't. Example: A:M wants to keep computing dynamics for every frame of the Chor so I set the frame range to 1 frame for the length. This seems (seemed?) to suspend the computing of dynamics but then... it didn't. Quote
detbear Posted October 1, 2014 Posted October 1, 2014 One of my last waterfall sims in A:M has an emmission rate of 200,000. I think thats what it was. Very long render. Quote
Hash Fellow robcat2075 Posted October 1, 2014 Author Hash Fellow Posted October 1, 2014 I'll note that on my computer, at least, if I have any sort of simulation in progress and I do a mouse-click, in or out of the window, or if there is any other program running that is updating its screen, A:M will go to "Not Responding" and appear to be frozen. It's still working and will come back when it finishes but if you want to monitor the simulation in progress you need to just let it be and not do anything else on the computer. Quote
Recommended Posts
Join the conversation
You are posting as a guest. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.