 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Povray 3.5 beta2, Windows 98 SE, Pentium MMX, 256 Mo.
According to doc 6.7.8, there could be a comma between the texture identifiers.
But the parser refuse it.
--
camera {
location <0.0, 0.5, -4.0>
direction 1.5*z
right x*image_width/image_height
look_at <0.0, 0.0, 0.0>
}
light_source {
<-30, 30, -30>
color rgb <1, 1, 1> // light's color
}
#declare T1=texture { pigment {color rgb <1,1,0>} }
#declare T2=texture { pigment {color rgb <1,0,0>} }
#declare T3=texture { pigment {color rgb <0,1,1>} }
mesh {
triangle { <-1,0,0>,<0,1,0>,<0,0,0> texture_list { T1 T2 T3 } }
triangle { <0,0,0>,<0,1,0>,<1,1,0> texture_list { T3 T2 , T1 } }
triangle { <0,0,0>,<1,1,0>,<1,0,0> texture_list { T3 , T1 , T2 } }
}
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> According to doc 6.7.8, there could be a comma between the texture
> identifiers. But the parser refuse it.
Could somebody on the Team tell me, should I change the docs for this
or will POV-Ray be changed?
Ingo
--
Photography: http://members.home.nl/ingoogni/
Pov-Ray : http://members.home.nl/seed7/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"ingo" <ing### [at] home nl> wrote...
>
> > According to doc 6.7.8, there could be a comma between the texture
> > identifiers. But the parser refuse it.
>
> Could somebody on the Team tell me, should I change the docs for this
> or will POV-Ray be changed?
Please change the docs.
-Nathan
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
in news:3ba54b2e@news.povray.org Nathan Kopp wrote:
>> > According to doc 6.7.8, there could be a comma between the
>> > texture identifiers. But the parser refuse it.
>>
>> Could somebody on the Team tell me, should I change the docs for
>> this or will POV-Ray be changed?
>
> Please change the docs.
>
Does the same apply to the texture_list in mesh2 ?
Ingo
--
Photography: http://members.home.nl/ingoogni/
Pov-Ray : http://members.home.nl/seed7/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"ingo" <ing### [at] homenl> wrote...
> in news:3ba54b2e@news.povray.org Nathan Kopp wrote:
>
> >> > According to doc 6.7.8, there could be a comma between the
> >> > texture identifiers. But the parser refuse it.
> >>
> >> Could somebody on the Team tell me, should I change the docs for
> >> this or will POV-Ray be changed?
> >
> > Please change the docs.
> >
>
> Does the same apply to the texture_list in mesh2 ?
I don't think so. Do you think we should require commas in "mesh" for
consistency?
-Nathan
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
in news:3ba7dbc1$1@news.povray.org Nathan Kopp wrote:
> Do you think we should require commas in "mesh" for
> consistency?
>
Yes, as in most places you can use commas if you wish.
Ingo
--
Photography: http://members.home.nl/ingoogni/
Pov-Ray : http://members.home.nl/seed7/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Nathan Kopp <nat### [at] koppcom> wrote:
: I don't think so. Do you think we should require commas in "mesh" for
: consistency?
As long as it doesn't make it harder to create items in a loop/macro/etc.
The greatest thing of commas being optional in most lists is exactly that:
You don't have to worry about extra commas at the end of the list when creating
the lists automatically.
Another possibility is that a #-command could work effectively as the same
kind of separator as a comma.
--
#macro N(D,I)#if(I<6)cylinder{M()#local D[I]=div(D[I],104);M().5,2pigment{
rgb M()}}N(D,(D[I]>99?I:I+1))#end#end#macro M()<mod(D[I],13)-6,mod(div(D[I
],13),8)-3,10>#end blob{N(array[6]{11117333955,
7382340,3358,3900569407,970,4254934330},0)}// - Warp -
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"ingo" <ing### [at] homenl> wrote...
> in news:3ba7dbc1$1@news.povray.org Nathan Kopp wrote:
>
> > Do you think we should require commas in "mesh" for
> > consistency?
>
> Yes, as in most places you can use commas if you wish.
Good point. Done.
-Nathan
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Initial problem solved (no more comma in the doc, OK).
But it seems that one of the texture (the first texture) disappears, or at least
is not put on the first point. Instead, the second texture is on the first point
and the third texture is used on the second and third points.
Povray 3.5.beta.8.icl.win32, Win98, Pentium MMX, 256 Mo
Demo scene (T1 is red, T2 green and T3 blue)
=======================================================
camera {
location <0.0, 0.5, -4.0>
direction 1.5*z
right x*image_width/image_height
look_at <0.0, 0.0, 0.0>
}
light_source {
<-30, 30, -30>
color rgb <1, 1, 1> // light's color
}
#declare T1=texture { pigment {color rgb <1,0,0>} }
#declare T2=texture { pigment {color rgb <0,1,0>} }
#declare T3=texture { pigment {color rgb <0,0,1>} }
mesh {
triangle { <-1,0,0>,<0,1,0>,<0,0,0> texture_list { T1 T2 T3 } }
triangle { <0,0,0>,<0,1,0>,<1,1,0> texture_list { T3 T1 T2 } }
triangle { <0,0,0>,<1,1,0>,<1,0,0> texture_list { T2 T3 T1 } }
}
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> But it seems that one of the texture (the first texture)
> disappears, or at least is not put on the first point. Instead, the
> second texture is on the first point and the third texture is used
> on the second and third points.
Confirmed.
> triangle { <-1,0,0>,<0,1,0>,<0,0,0> texture_list{ T1 T2 T3 } }
> triangle { <0,0,0>,<0,1,0>,<1,1,0> texture_list { T3 T1 T2 } }
> triangle { <0,0,0>,<1,1,0>,<1,0,0> texture_list { T2 T3 T1 } }
If you put commas in the texture list, the result changes and not for
the better.
Ingo
--
Photography: http://members.home.nl/ingoogni/
Pov-Ray : http://members.home.nl/seed7/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
