Hi, trying to remove error messages, I realised I always get this one ("pigment
type unspecified or not 1st item") because my scene makes use of the #default
directive early on to define the generic pigment and then uses pigment{} to call
it, is there another way we should call the default pigment, like a keyword? or
is this feature going to be deprecated? If not, I don't see why should it
generate an error message?

Post a reply to this message

Am 18.05.2016 um 15:02 schrieb Mr:
> Hi, trying to remove error messages, I realised I always get this one ("pigment
> type unspecified or not 1st item") because my scene makes use of the #default
> directive early on to define the generic pigment and then uses pigment{} to call
> it, is there another way we should call the default pigment, like a keyword? or
> is this feature going to be deprecated? If not, I don't see why should it
> generate an error message?

To get a texture with the default pigment, just use

    texture {
      // note: no pigment at all!
    }

That's why it is called the default pigment ;)

Post a reply to this message

clipka <ano### [at] anonymousorg> wrote:
> Am 18.05.2016 um 15:02 schrieb Mr:
> > Hi, trying to remove error messages, I realised I always get this one ("pigment
> > type unspecified or not 1st item") because my scene makes use of the #default
> > directive early on to define the generic pigment and then uses pigment{} to call
> > it, is there another way we should call the default pigment, like a keyword? or
> > is this feature going to be deprecated? If not, I don't see why should it
> > generate an error message?
>
> To get a texture with the default pigment, just use
>
>     texture {
>       // note: no pigment at all!
>     }
>
> That's why it is called the default pigment ;)

thanks, that's cleaner no more yellow message!

Post a reply to this message