I'm not sure if I'm just being thick but is there a way to #declare an
entire material in 3.1 including both textures and interiors?  I've
looked for such a thing but can't find it.

Thanks, PoD.

Post a reply to this message

PoD wrote:

> I'm not sure if I'm just being thick but is there a way to #declare an
> entire material in 3.1 including both textures and interiors?  I've
> looked for such a thing but can't find it.
>
> Thanks, PoD.

  I too would be interested in the answere to that question.
Otherwise I have 60 #declared glass textures I've created
that are now obsolete.

Thanks K.Tyler

Post a reply to this message

K. Tyler wrote in message <35B10EC4.194795D4@pacbell.net>...
>PoD wrote:
>
>> I'm not sure if I'm just being thick but is there a way to #declare an
>> entire material in 3.1 including both textures and interiors?  I've
>> looked for such a thing but can't find it.
>>
>> Thanks, PoD.
>
>  I too would be interested in the answere to that question.
>Otherwise I have 60 #declared glass textures I've created
>that are now obsolete.
>
>Thanks K.Tyler
>

This is untested but should contain enough to get you started in
the right direction. All your declared textures should be rewritten
to take out what now belongs in interiors ... A little cut and paste
should do that ....

Make a collection of declared interiors ...

You could invoke the texture and interior collections with a couple
of #include statements and then

#declare MyTexture = _name_of_texture_in_include_file_
#declare MyInterior =  _name_of_interior_in_include_file_

#macro TextureWithInterior()
 MyTexture
 MyInterior
#end

#declare MyObject = ...

Object{
 MyObject
 TextureWithInterior()
}

/* For the next object ... */

#declare MyObject2 = ...

#declare MyTexture = _name_of_next_texture_in_include_file_
#declare MyInterior =  _name_of_next_interior_in_include_file_
Object{
 MyObject2
 TextureWithInterior()
}

Once the macro is defined you should be able to redefine
its components so that on subsequent invocations the
macro operates using the new settings

Recall that macros take *zero* or more
parameters when declared or invoked, so
as long as you put the parantheses in
you should be ok

I am sure there are some mistakes in what I have hurriedly
written here ... I hope others will add to (or subtract from)
this quick note. The basic idea should be correct.

des

Using arrays could make it even more fancy ...

Post a reply to this message