[Radiance-general] rpict, rtrace start up time and number of sources

[Greg Ward]

Hi Lars,

I also have quite a few instances in my scene, so I don't think  
that's it.  I don't know why meshes would be any different, unless  
loading all the meshes and colorpicts takes a long time by itself.   
I'm not sure what you mean when you say the light sources are grouped  
into spheres.  Do you have many light sources per each of your 1850  
illum's?  If so, these should be defined with a glow material with a  
restricted radius.  Otherwise, there is no point to using mkillum.   
Can you send me the description of one of your light sources in a  
separate e-mail (off-list)?

-Greg

> From: "Lars O. Grobe" <grobe at gmx.net>
> Date: April 17, 2008 2:52:31 PM PDT
>
>> My 1800 sources are in a large scene -- the octree is a few  
>> hundred megs, I think.
>
> OK, that is strange. I try to list the more or less special  
> characteristics.
>
> - use of instances
> - use of mesh primitives
> - colorpict mappings
> - lots of lights (about 1850)
> - light sources are grouped into spheres, that are processed by  
> mkillum. the illum alt material is an invisible trans type
>
> The rpict process takes about 510MB, already being optimized for  
> memory using instances as mentioned.
>
> Should I get some debugging tools installed to check which  
> functions use up all the time at the beginning of occluder-cached  
> renderings?
>
> CU Lars.