Any chance this could be the result of the source texture not having power-of-two dimensions? I believe support for non-binary dimensions can vary from phone to phone. To be pedantic, I mean the source image for the texture should be 256x256, 512x256, 256x128, etc, and not 417x203 etc.
On Jan 20, 6:25 am, pedr0 <[email protected]> wrote: > Hi at all, > I have some strange behavior issues on texture-mapping with OpenGL ES > 1.1 > > 1)This is the right picture (Samsung Galaxy S): > http://i.imgur.com/j00Zy.png > > 2)This an wrong picture (HTC Magic): > http://i.imgur.com/P8NCW.png > > 3)This is another wrong picture (Ideos): > http://i.imgur.com/aOAza.png > > I am very disappointed for that, could someone help me? > I have mapped a texture in a Sphere using OpenGL ES 1.1, the OpenGL > need version is write in the AndroidManifest.xml file. > > In the 2th case I can read a lot of this message: > > E/libEGL ( 2372): called unimplemented OpenGL ES API > > I configured the checkError flag in OpenGLViewRender, but I cannot see > the OpenGL call which > cause this message. > > Thanks a lot in advance. > > pedr0 -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
