jwace: That''s quite a good point, the only problem that I can see is keeping two copies of each texture in memory, because I''m not sure which ones I''ll want to modify. I''ll play with it and see if the extra memory it takes isn''t too much, if not, hehe, then thanks!

email

Something kinda sad about
the way that things have come to be.
Desensitized to everything.
What became of subtlety?
--Tool

> the only problem that I can see is keeping two copies of each texture in memory

2 copies ? Why two RAM copies ? You have one copy of each texture in your local RAM and one on the 3D card.

Or do you want to copy a texture on the 3D boards memory to host RAM (with glGetTexImage), process it, and reupload it ? That''s gonna be slow as hell.

Yeah, NOT 2 RAM copies, one 3d card copy, and one RAM copy.
Basically I want to know the fastest way to modify a texture already stored by OpenGL on the 3d card. It seems right now that it''s having two copies so I don''t get slowed by glReadPixels or glGetTexImage.


email

Something kinda sad about
the way that things have come to be.
Desensitized to everything.
What became of subtlety?
--Tool

quote:

---

Original post by Lord Karnus
Basically I want to know the fastest way to modify a texture already stored by OpenGL on the 3d card.

---

   ^  /|\ / | \/  |  \   |   |   |   | 

Doesn''t anybody read my posts??

^
| That was me...

Sorry Wolfman, I wasn''t implying that your post wasn''t helpful, just attempting to explain the reason of my original post to the Anon Poster

email

Something kinda sad about
the way that things have come to be.
Desensitized to everything.
What became of subtlety?
--Tool