POV-Ray : Newsgroups : povray.general : interior_texture -- #declare problem : Re: interior_texture -- #declare problem Server Time
21 Dec 2024 21:51:43 EST (-0500)
  Re: interior_texture -- #declare problem  
From: Leroy
Date: 4 Dec 2024 15:55:00
Message: <web.6750c0e9bc94733558f60ff3f712fc00@news.povray.org>
"Kenneth" <kdw### [at] gmailcom> wrote:
> [Running Windows 10]
>
> This might be old news, although I could not find a reference to it in a
> newsgroup search.
>
> An interior_texture cannot be pre-#declared in the usual way. The following
> constructs do not parse in either 'official' v3.7.0 or 3.8 beta 1, fatal errors:
>
> #declare INT_TEX_1A =
> interior_texture{pigment{rgb <.2,.2,1>} finish{ambient .1 emission 0 diffuse
> ..8}}
>
> or...
>
> #declare TEX_2 =
> texture{pigment{rgb <.2,.2,1>} finish{ambient .1 emission 0 diffuse .8}}
> #declare INT_TEX_2 = interior_texture{TEX_2}
>
> or as a #default...
>
> #default{interior_texture{pigment{rgb <1,.4,.1>} finish{ambient .1 emission 0
> diffuse .8}}}
>
> However, it *can* be pre-#declared by using a 'material' wrapper, which is
> undocumented:
>
> #declare TEX_4 =
> material{
> interior_texture{
> pigment{rgb <.2,.2,1>}finish{ambient .1 emission 0 diffuse .8}
> }
> }
>
> I assumed that an interior_texture and a 'regular' texture were similar entities
> under-the-hood, but apparently not(?)

A shot in the dark!
Did you try
 texture{TextureA}
 interior_texture{TextureB}
in an object?


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.