quote:

---

Original post by Null and Void

The way I set it up, I load the textures in to the linked list, and each object has a pointer to the texture that it is using. After all of the objects that are to be rendered are determined, I quicksort them (so that the least amount of state changes are required) and then render them.

It is very fast, and I doubt there is more than a millisecond lost of speed per frame. How do you think professional games store textures? The certainly don''t do it with an array.

---

Since OpenGL stores textures as integers, i doubt they even bother, and just include it(the int) as a field with the primative they are rendering.

i mean with the pointer.

i mean with the pointer.

i mean with the pointer.

Thanks for the code... If I gave you an email address could you please mail me the complete code that you have for loading textures?

That would be greatly appreciated!

for Now I will look over what is currently here...

Thanks Again!

Thanks!

John William Blair

You''re probably write about storing a TexID for each object, I think I could implement that fairly easily actually. It would make unloading textures (using my reference system at least) slower though, I''ll have to think about that.

Jwblair, I''d rather not release my engine''s source code until it is completed, and I would have to release a good portion of it for that texturing code to work since the engine is so blended in to itself. If you go to Nehe''s you can find example code for loading textures (if you already know OpenGL, just skip to the TGA Loading tutorial, that''s what I based my above code off of).

"Finger to spiritual emptiness underlying everything." -- How a C manual referred to a "pointer to void." --Things People Said

http://www.gdarchive.net/druidgames/