f r e e f a c

Well, somehow I managed to make this a page and not a post when I wrote it, and just noticed… so here it is again:

quick blog from a (wirelessly connected!) train from amsterdam.
in bug 17902 (which he fixed) ton made some quick tips about making raytracing less slow- mostly common sense, but I thought I’d capture them here in case they don’t get noticed on the bugtracker:
” Tips for using Blender Octree well:

• exclude anything from being “traceable” if it doesn’t *cast* shadow (it will receive) like floors
• make sure the bounding box of the total environment is small as possible (you had a curve lying around far away in bottom)
• use larger octree resolutions on bigger scenes.”

Probably old information, but it is rather helpful, so worth repeating.

1. IamInnocent Says:
   17-11-2008 at 6:54 pm

   Yes, it is useful to remind such things.

   Thanks

   Jean

2. Reynante M. Martinez Says:
   17-11-2008 at 9:47 pm

   Thanks again for that friendly reminder. I noticed a year ago that increasing the octree resolution on larger and complex scenes like the one I have here http://vimeo.com/681571. But using larger octree resolutions on smaller and less complex scenes seems to have a reverse effect on it.

   Thanks so much. ^_^

   -Reyn

3. Bassam Says:
   17-11-2008 at 11:55 pm

   Thanks Jean
   Reynante, what was “the visitor” ? I was trying to figure out from the type of motion, my guess was some kind of insect…

4. Virgilio Says:
   18-11-2008 at 11:21 am

   Indeed, very cool to remind that.

   Besides the first tip is one of the most obvious, it is also easy to forget that.

   Thanks, Bassam.