"Kenneth" <kdw### [at] earthlinknet> wrote:
> The only problem with a function image is the really odd 'upside-down mirror
> image' behavior of the resulting pattern 'slice' (at least when it's used to
> make a HF, anyway.) Try making a function image from an image_map to see what I
> mean.

Ah, so *that's* why I found myself in need of a scale <1,1,-1> when I migrated a
particular scene from an auto-generated mesh to an auto-generated-df3-based
height field these days...

I actually have an Idea how this came to be so:

Where's <0,0> in an image?

In a POV context, for some reason I'd be quite quick to claim that it must be
the bottom left corner.

In an image editing context, however, (0;0) classically designates the top left
corner.

So height field code, normally dealing with images, might have to swap around
the image's y co-ordinate for proper operation. And it might do just the same
for function images - but the function images may fail to do a similar
re-normalization for the input pattern.

So the issue may actually be in function images in general, not patterns in
height fields (after all, if I'm not mistaken, function images are the only way
to create a height field from a pattern in the first place).

Post a reply to this message