Hi,

The bug tracker is now closed... we move to a new server for projects.blender.org.

Anyhoo, I cannot redo this bug, the file renders far too slow to be of use for a bug report. Please tell Shige this:

- For larger scenes you need to set a larger octree subdivision too, use "256" or "512" in your case.
- Worst of all, you have a sort of sky-dome (giant grey sphere) which is still "Traceable", which means the octree is being filled in very inefficiently. For efficient ray trace, set all materials "Traceable" off when the object doesn't *cast* shadow or has to be visible in a mirror.

But most important:
You have to help us preparing files for bug reports better. We need the artists to remove everything from a file, to reduce it to the simplest possible case which takes the shortest possible render time. That saves us a lot of work.
for this file, I already had to spend a lot of time on only making it render a bit faster.

But, still could not redo the bug (mac OSX, G5, latest cvs). It renders OK for me. (render time insane still (24 minutes)... you can make such images so much faster!)

Let him test the RC build on blender.org frontpage? And if the bug still appears, just remove render options and simplify things until it is clear and easy case to redo.

-Ton-