hello everyone
I work on my projects recently, it’s about to demonstrate constructing method to my company’s client, I use 3ds max 2012 (64-bit) to animate the procedure, the animation is a sequential targa files, after the rendering completed , I checked out every single image , found some of them have strange black spot, so I just re-rendered the strange black spot image file (only the each single frame one at a time), the black spot gone, shown as 01 and 02 , the render setting shown as 03,04 and 05 , here I explain my scene setting a little more detail , because my camera moving along path , so I set project points from positions along camera path , interpolate over number fg points set to 100 (the preset is 30), no caculate gi since it’s an outside scene , and not reuse fg and gi , filter type set to mitchell and bucket to 128 (the preset is box and 48) , and I just use arch_design and autodesk material library to assign object , and simple pf to simulate welding effect plus glow and glare shader , the scene is about 6 million polys and verts, but fps still about 80 (shown as 06), my machine is i7-2600, 16 gigabyte ram , quadro 2000, win 7 (64-bit), and only single machine do the rendering session (no net or distributed rendering).
Because the strange black spot is square , looks like the mental ray can’t caulate the fg points correctly, I supposed my render setting about bucket is too high , so I set back to 96 to render the animation is targa sequence again (shown as 07) , 3ds max still gave me the black spot in different frames(shown as 08) , but as long as I re-render those images each one at a time , the black spot disappeared , it’s only the solution I can figure out now , does anyone have the same experience ?? what’s going on in 3ds max or mental ray?? and how to solve the issue?? please help me, thanks in advance.

	Attachment

	Attachment

	Attachment

	Attachment

	Attachment

	Attachment

	Attachment

	Attachment

I never had the issue, but from what I have seen and heard by other users it is oft a kind of memory management issue.
Which BSP option are you using (BSP or BSP2)?
Why is the bucket width that large? The default 48 is usually enough and the recommendation is to go down (not up) in some particular cases; 24 or even 12 could
be a bit better on multi-core machines (according the theory).

ivan

Thanks for reply. The reason I set bucket to 128 and 96 due to I’d like to decrease rendering time, because bucket 48 is to small for me to render a full HD resolution images as I just have 3 computers to render a bunch of animations and no local net connection to each other , no any chance to do net render or distributed render (my boss doesn’t allow me to connect them to form a local network.) , and one of them is for my daily work which can join render session only when I off the day.

Which BSP option are you using (BSP or BSP2)?
Why is the bucket width that large? The default 48 is usually enough and the recommendation is to go down (not up) in some particular cases; 24 or even 12 could

Since you mentioned the bucket is too large , I already set back to 48 to test rendering now , not to check the result yet (off the day at present), and raytrace acceleration method is BSP2 , I never change it , and finally I will post the test result tomorrow .

hi again!
After long time test render , set bucket to 48 is just fine . no black spot any more. Finally solve it.

cheejowdee 11 May 2012 02:54 AM

hi again!
After long time test render , set bucket to 48 is just fine…

Solutions come with a price, that’s life. :)

ivan
(PS: try Gauss filter with value size of 2.0 Mitchell is too slow and in animation the quality is actually the same one.)