And always make sure the BSP settings are correct. The default values
are for scenes without motion blur.
Motion blur scenes that require too much memory are almost always caused
by bad BSP settings.
Alan Jones wrote:
Be sure to use the rasterizer if you're trying something as
potentially intensive as ambocc with motionblur. Otherwise think
number of AO samples multiplied by number of motion blur samples
multiplied by number of pixel samples.... Ouch....
Cheers,
Alan.
On 6/28/07, Lee Hallett <Lee.hallett(at)bbc.co.uk> wrote:
Whilst I'm making noise on the list, is it just the way it is, or a
bug/issue with rendering anything with ambient occlusion and motion
blur? The rendertimes went into the decades when I had both activated
for a (comically assumed) quick job last week. With ambient occlusion
and no motion blur, frames were sub minute, add on a little motion blur,
and expect retirement to hit home before the render...
Surely this shouldn't be - also getting emormous memory requests from
mental ray (7 Gig for a very simple scene).
Has anyone else had problems with motion blurr and ambient occlusion?
Worked around it, bt it was a bit of a concern.
http://www.bbc.co.uk/
This e-mail (and any attachments) is confidential and may contain
personal views which are not the views of the BBC unless specifically
stated.
If you have received it in error, please delete it from your system.
Do not use, copy or disclose the information in any way nor act in
reliance on it and notify the sender immediately.
Please note that the BBC monitors e-mails sent or received.
Further communication will signify your consent to this.
---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in
body:
unsubscribe xsi
---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in
body:
unsubscribe xsi
---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi
