 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Using version 3.1g, I can't seem to create checker textures properly, at
least for planes. If I specify
pigment {checker X White}
where X is any pre-defined colour, I always get a plane which appears to
have
pigment {checker Green White}
Is this a known bug, as I've only just started using POV-Ray and am not up
to speed yet? Thanks
Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Chris Howlett wrote:
>
> Using version 3.1g, I can't seem to create checker textures properly, at
> least for planes. If I specify
>
> pigment {checker X White}
>
> where X is any pre-defined colour, I always get a plane which appears to
> have
>
> pigment {checker Green White}
>
> Is this a known bug, as I've only just started using POV-Ray and am not up
> to speed yet? Thanks
>
> Chris
It is not a bug. You MUST specify both colors with a comma seperating
them.
In your case it should be pigment { checker X, White }
--
Ken Tyler - 1400+ POV-Ray, Graphics, 3D Rendering, and Raytracing Links:
http://home.pacbell.net/tylereng/index.html http://www.povray.org/links/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Wed, 31 May 2000 10:52:56 -0700, Ken wrote:
>It is not a bug. You MUST specify both colors with a comma seperating
>them.
Though I consider the fact that a comma is necessary a bug. I think
I posted the fix to bugreports, but it was a long time ago. Basically,
POV sees "Puce Chartreuse" as just "Chartreuse".
--
Ron Parker http://www2.fwi.com/~parkerr/traces.html
My opinions. Mine. Not anyone else's.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Ron Parker <ron### [at] povray org> wrote:
: Though I consider the fact that a comma is necessary a bug.
I would consider not throwing a syntax error when there isn't a comma a bug.
If you see "comma expected but blah blah found instead" you will probably
see quite fast what is the problem.
--
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 1 Jun 2000 13:33:27 -0400, Warp wrote:
>Ron Parker <ron### [at] povrayorg> wrote:
>: Though I consider the fact that a comma is necessary a bug.
>
> I would consider not throwing a syntax error when there isn't a comma a bug.
>If you see "comma expected but blah blah found instead" you will probably
>see quite fast what is the problem.
That would be true if commas were required anywhere else in the language.
As it is, they're only required when it's necessary to disambiguate the
elements of a vector ( <1,-2,3> vs. <1 -2 3>, one of which is a 3-vector
and one of which is a 2-vector.)
Besides, the problem stems from the fact that POV doesn't recognize a
difference between
Puce Chartreuse
and
red 1 green .7 blue .1 green 1
If the latter followed "checker", where would you expect to find the comma?
--
Ron Parker http://www2.fwi.com/~parkerr/traces.html
My opinions. Mine. Not anyone else's.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Ron Parker <ron### [at] povrayorg> wrote:
: red 1 green .7 blue .1 green 1
: If the latter followed "checker", where would you expect to find the comma?
Well, that's why I think comma should be required. That is, support for
a checker statement with only one parameter instead of two should be
removed. It will only do good.
--
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 2 Jun 2000 04:54:24 -0400, Warp wrote:
>Ron Parker <ron### [at] povrayorg> wrote:
>: red 1 green .7 blue .1 green 1
>
>: If the latter followed "checker", where would you expect to find the comma?
>
> Well, that's why I think comma should be required. That is, support for
>a checker statement with only one parameter instead of two should be
>removed. It will only do good.
I suggested a transparent (i.e. doesn't break most existing scenes) workaround
in .bugreports when I originally posted the problem:
|Unfortunately, you can also say "color Red Green" and get green. This
|is not documented, and is probably a bug (the docs do say COLOUR_IDs
|should come first.) Parse_Colour should probably UNGET and EXIT when
|it gets a second instance of any of COLOUR_ID, rgb, rgbt, rgbf, rgbft,
|or a bare vector expression. This would make rgb 1 red 0 legal as a
|shortcut for cyan, but make rgb 1 rgb 0 become two separate colors,
|suitable for use in checkers or bricks or hexagons.
--
Ron Parker http://www2.fwi.com/~parkerr/traces.html
My opinions. Mine. Not anyone else's.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Ok, thanks for that. Just one remaining question - why the hell does it
replace the "unspecified" colour with Green?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Fri, 2 Jun 2000 18:16:54 +0100, Chris Howlett wrote:
>Ok, thanks for that. Just one remaining question - why the hell does it
>replace the "unspecified" colour with Green?
Because the rather unintuitive defaults for checker are, IIRC, yellow and
green.
--
Ron Parker http://www2.fwi.com/~parkerr/traces.html
My opinions. Mine. Not anyone else's.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
