Loading textures in an Android OpenGL ES App.
Posted
by Omega
on Stack Overflow
See other posts from Stack Overflow
or by Omega
Published on 2010-03-23T15:36:41Z
Indexed on
2010/03/24
7:03 UTC
Read the original article
Hit count: 287
I was wondering if anyone could advise on a good pattern for loading textures in an Android Java & OpenGL ES app.
My first concern is determining how many texture names to allocate and how I can efficiently go about doing this prior to rendering my vertices.
My second concern is in loading the textures, I have to infer the texture to be loaded based on my game data. This means I'll be playing around with strings, which I understand is something I really shouldn't be doing in my GL thread.
Overall I understand what's happening when loading textures, I just want to get the best lifecycle out of it. Are there any other things I should be considering?
© Stack Overflow or respective owner