[Radiance-general] rvu: too many modifiers in ambient list

[Greg Ward]

Hi Lars,

As long as your modifiers are named differently, you can have as many  
as you like and use the -ae option successfully.  There is no limit  
to the number of modifiers or the reuse of modifier names in  
Radiance, but if a modifier appears hundreds of times with the same  
name, the -ae option takes the one name and translates it into a  
hundred instances of that name as necessary to form the exclusion set.

Hopefully, what you have done already should suffice.

-Greg

P.S.  I will be out of town and out of contact for the next week, so  
if you write with a question and get no response, I'm not ignoring  
you.  I'm just gone.

> From: Lars O. Grobe <grobe at gmx.net>
> Date: July 15, 2005 7:12:54 AM PDT
>
> Hi Greg.
>
> I followed your suggestion and used sed to replace all the  
> modifiers in my cad files. So marble_grey in object plane_1 is  
> renamed to plane_1_marble_grey now. However, there is one question  
> left (in fact I didn't really understand the overflow condition I  
> am causing). If I reduce the modifiers that will be included in all  
> the object files to a lower number (in fact, only the mappings are  
> included into each, as they are used in most cases). I wonder if I  
> will get the "too many modifiers" if I have e.g. three modifiers  
> defined in all object files. Is the overrun depending on the total  
> number of modifier definitions, or is it the limit that ONE  
> modifier can't be defined more than the fixed number? The latter  
> means that I have to change a lot, as I would have to examine the  
> cad files also for the most common colorpict modifiers (which I  
> include into each object file so far). From what I understood, I am  
> afraid that will be necessary, but before spending some hours on  
> this, I would like to understand the nature of this limit of  
> modifier ids.
>
> TIA+CU. Lars.
>
>
>> If you can avoid duplicating your entire material library with  
>> each object, this should solve all your problems.
>
> (This is the key point - I don't duplicate the entire material  
> library with each object any more now, but still some modifiers of  
> the library.)
>