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.