[Radiance-general] mkillum useage with large scenes

[Gregory J. Ward]

Hi Lars,

The alias type demands a valid (previously defined) identifier, and  
will not accept "void" in the current version.

You are introducing too many artificial constraints, such as  
requiring your scene files to have everything intermingled, with  
illum surfaces visible beforehand then invisible afterwards, etc.,  
etc.  Separating the surfaces you want to render and treat  
differently in separate files is by far the easiest way to go.  You  
are making life unnecessarily difficult by bundling it all together  
in one stream.

-Greg

> From: "Lars O. Grobe" <grobe at gmx.net>
> Date: March 19, 2006 8:29:32 AM PST
>
> Hi!
>
> Thank you for the help, mkillum is somehow still one of the radiance
> secrets.
>
> Ok, I am trying that now. I am curious about the "complicated way"  
> using
> -o settings for mkillum. Still, now I want it to work first ;-)
>
> One question arised now. I had been filtering my scene for the
> mkillum-faces' modifier, replacing it by void, and than run mkillum  
> with
> -i=void. I would prefer not to filter, but still, I need a modifier  
> that
> will actually never be used to define my mkillum-faces. Can I  
> define an
> alias to void for that? E.g. void alias mkillum_faces void? So that
> before I run mkillum, these faces just are not visible, but I can  
> still
> run oconv on the scene? Or should I better use a dummy material for  
> them
> (e.g. a glass with 100% transmittance? So far I like to be able to run
> rvu on the scene before using mkillum, so I prefer not to have some
> thousand of these faces with a dummy modifier, but I guess that  
> alias to
> void could cause problems?
>
> Thank You, CU Lars.