Windows seems to detect a . (full stop) as a , (comma) in a vector if you
give it an invalid number, e.g <1,1,0.0.5> I think this used to give the
warning 'strange expression after rgb' or something of the sort in 3.1,
sorry can't check it (no 3.1 anymore).
Try the following two scenes with the different rgb statements:

Also notice how (in windows anyway) the editor interprets every other full
stop differently (first '.' green i.e. number, second '.' black i.e. text)

POV 3.5.beta.10.icl.win32
Windows 98
Athlon 1.333GHz
512 MB ram

Kev

//Scene start here

#declare TestScene=1; // 1 for 3d vectors or 2 for 2d vectors

#if(TestScene=1)
box {
  -1,1
  pigment {
    //rgb <1,1,0.5> //solid yellow as expected
    rgb <1,1,0.0.5> //partially transparent yellow (should give error)
    //rgb <1,1,0.0.0.5> //solid yellow (should give error)
    //rgb <1,1,0.0.0.0.5> //partially transparent yellow (should give error)
for this and all that follow
  }
}
#end
#if(TestScene=2)
box {
  -1,1
  pigment {
    //rgb <1,0.5> // solid orange
    rgb <1,0.0.5> // solid magenta
    //rgb <1,0.0.0.5> // partially transparent red
    //rgb <1,0.0.0.0.5> // partially filtered red
    //rgb <1,0.0.0.0.5> // partially transparent red and for all others

  }
}
#end
camera {location -4*z look_at 0}
plane {y,-1.001 pigment {green 1}}
light_source {<10000,10000,-10000> color rgb 1}

//Scene end here

Post a reply to this message