On Thu, 1 Apr 1999 18:49:00 +1000, Lance Birch <lan### [at] usanet> wrote:
>I thought it was just an operator... like, it just switches it on, it
>doesn't have a value supplied...  I also thought that the metallic keyword
>sets the shading mode of the object, so it can't reallt have a float
>associated with it anyway... but I could be wrong on that one.

Use the source, Luke!  I've pasted the part of parstxtr.c that parses
this below.  Briefly, when POV sees the word "metallic" it sets the 
"metallicness" of the texture to one, then looks to see if the next
token is a number.  If it is, it sets the "metallicness" to that number;
otherwise, it puts the next token back and ignores it.  If the docs 
don't mention this, then it was omitted and the docs should be fixed.

CASE (METALLIC_TOKEN)
  New->Metallic = 1.0;
  EXPECT
    CASE_FLOAT
      New->Metallic = Parse_Float();
      EXIT
    END_CASE

    OTHERWISE
      UNGET
      EXIT
    END_CASE
  END_EXPECT
END_CASE

Post a reply to this message