Re: [AD] polygon3d patch - and small mixer patch

[Jason Wilkins <fenix@xxxxxxxxxx>]

Ben, how exactly does your patch effect texture coordinate alignment?  I
followed a bit of the argument, and even added my 2 cents, but I don't
recall exactly what the change you proposed was.  So, I don't know if I
support it or not ^_^

My vote is for integer texture coordinates to map to integer pixel
coordinates, with the origin being in the upper left corner of the bitmap.  
If the distance between two vertexes (in texels) is 32, then 32 texels
should be between them (in other words, one to one between texture coords
and texels).

Allegro's current conventions and conformity with other 3D libs like
OpenGL and DirectX dictate this.

On Fri, 29 Dec 2000, Ben Davis wrote:

> Uhm... it's been 5 days since I posted two patches, one for the polygon3d()
> function and one for the mixer. I'm wondering why they haven't been
> applied - especially the mixer, as I know the poly3d one was controversial.
> If there is a reason why they haven't been committed, please tell me - also
> I may be missing some crucial e-mails. Outlook's fault :-)
> 
> Note that the poly3d patch does not only alter texture alignment (the
> controversial bit) - it also fixes a bug to do with coincident vertices.
> 
> Also note that, if the poly3d patch is to be applied, it will have to be
> fiddled a bit. See my last e-mail for details.
> 
> If you need me to repost and/or redo the patches, please don't hesitate to
> ask.
> 
> Ben Davis
> 

-- 
               The Phoenix -- The Artistic Intuition Company
 Runica * Phoenix Quake * Caelius * Zen-X * Mirror Reflex * Infinite Realms