Accurate textures cause the entire triangle to be textured with a single
color from the image. I'm using 0154 Beta on WinXP.

Can be replicated by adding hint(ENABLE_ACCURATE_TEXTURES); to any of the
Examples>>3D>>Textures sketches.

eric, any ideas on this one?

Yup - hint(ENABLE_ACCURATE_TEXTURES) is to be nuked before 1.0, and I
probably did something that made it stop working, but I forgot to get rid
of the hint. The replacement will be smooth(), the implementation of which
I'm finishing up (fixing the edge problems).

I wonder if we should put support for that hint back for the moment, and
only remove it when the smooth() implementation is complete? (would only be
a couple lines of code, I think) But I'll see if I can finish smooth() up
tomorrow, then maybe we can avoid the issue; honestly, I didn't know anyone
was even using the hint, so it never occurred to me that pulling that stuff
out was a bad idea! Sorry about that.

I wouldn't spend any time making the hint work again--if you have the time,
please just spend it on those fixes for smooth(). I think it'll just be
better in the long run.

Agreed - working on that as we speak, trying to hook up the edge stuff so
that it works right (getting there, slowly). While I'm in there, I'll pull
out the old accurate texture code.

Should we throw an exception upon setting that hint to let people know that
the right approach from now on will be to use smooth()? I forget what the
preferred approach is for disabling hints...

- Eric

(In reply to comment #3)
>
>
>
> Additional Comment #3 From
>
> fry
> 2008-11-06 07:28
>
> <!--
> addReplyLink(3); //-->[reply]
>
>
>
>
> I wouldn't spend any time making the hint work again--if you have
the time,
> please just spend it on those fixes for smooth(). I think it'll just be
> better in the long run.
>
>

the correct method (as of recent releases) is to use showWarning(), so that
it displays an error in the console, and does so just once.

as of recent releases, exceptions are only thrown when a choice made by a
user will cause a later, more significant problem and throwing the
exception actually clarifies the problem. warnings are shown when the code
can continue running (albeit inefficiently in some cases) with only minor
visual loss or something similar.

Alright, I'll change it so that it shows the warning, and then does nothing
(defaulting back to the non-perspective-corrected rendering). I'll go back
and deal with this after I've handled the rest of the smooth stuff; barring
any major unforeseen problems, this should all be ready very soon.

cool, thanks.