🚀 go-pugleaf

It seems to me that just like in advanced 3D rotations, in texture
mapping everybody and their dog are experts, but when it comes down to
the all-important details, nobody has a clue. 
	I'm writing a 3D game and a major part of all modern 3D games is the
texture mapper. The thing is 80% of mappers/FAQs/tutorials out there
assume I'm writing DOOM. 	I'm not. I'm writing a polygon drawing engine
for TRIANGLES only, which can have any orientation in space and each
vertex has a seperate texture space co-ordinate (u,v) in the texture
pixmap. This allows stretched, distorted and scaled textures without
hassles. A scanline renderer would be prefferable, but is not necessary.
(Constant Z lines mean a lot of buffer changes in SVGA unless I use
double buffering) Also, linear interpolation will NOT do, it is far too
inaccurate to give satisfactory results. This game will be realease (if
ever) at a time P6s/K6s will be popular and therefore will have a tad
more power than your avarage computer today. Double precision floating
point is used everywhere so far, so no fixed point rubbish please.
(A lot of FAQs assume you're writing for a 386sx, which is NOT true.)
Quake's monsters use the method I just described. And no, John Carmack
doesn't want to tell me how he did it.
	If you have ANY information, wether it is just some maths you saw once,
a URL, or a FAQ that is more practical than the comp.graphics.algorithms
FAQ, or a tutorial that has more than how to do a DOOM engine, please
email me. A book title is totally useless.

                                   thanx in advance . . . the Lord
Shaman.
    
----------------------------------------------------------------------
            "My aim is life is to become immortal, or die trying."
          http://www.nlc.net.au/~shaman  or  mailto:shaman@nlc.net.au
    
----------------------------------------------------------------------