"Marc-Hendrik Bremer" wrote:
> Rune, I think I get your point, but don't you
> think you have beaten this horse enough?

I think the behavior is wrong and if it isn't fixed before the final release
of POV-Ray 3.5, then we will be stuck with this annoyance forever to ensure
backwards compatibility.

I just don't get it. I make an image in a paint program. It's correctly
aligned (the image is not upside down). I use this image as an image_map.
It's still correctly aligned.

I use this image in a function and use the function as a pattern in a
pigment. It's still correctly aligned.

Now I use the image in a function in an image_map. Now it's upside down! And
*that* is consistency???

Thorsten keeps saying that the function image type use "image space"
coordinates, but he has not yet explained why the function image type has to
use the same definition of image space, when the concept of up and down is
the opposite in function coordinates than it is in all external image
formats.

But no, I can't get any explanation despite of how long this thread has been
running by now...

I also would have liked to hear other people's thoughts on what would be the
correct behavior, but apparently no one have anything to say about it.

Rune
--
3D images and anims, include files, tutorials and more:
Rune's World:  http://rsj.mobilixnet.dk (updated Mar 19)
POV-Ray Users: http://rsj.mobilixnet.dk/povrayusers/
POV-Ray Ring:  http://webring.povray.co.uk

Post a reply to this message