tag:blogger.com,1999:blog-1591823016636842474.post6331530640402781896..comments2023-10-12T08:54:45.814-07:00Comments on indie game development adventures: Android NDK loading resources and PNGsegofluxhttp://www.blogger.com/profile/18431847765946714275noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-1591823016636842474.post-73592071506913674682012-06-18T06:58:27.582-07:002012-06-18T06:58:27.582-07:00The Ids may be because of Java's big endiannes...The Ids may be because of Java's big endiannes compared to GL which is reversed ?Cippyboyhttps://www.blogger.com/profile/13374712611258016537noreply@blogger.comtag:blogger.com,1999:blog-1591823016636842474.post-45780171626365917192012-04-11T09:25:43.610-07:002012-04-11T09:25:43.610-07:00The same texture IDs were on the device afterward ...The same texture IDs were on the device afterward as well, which I think is sort of strange, but apparently has something to do with the opengl drivers on the device itself? I wish I had a more solid answer on this one, but I can't really think of anything else.<br /><br />Strangely, my Samsung Galaxy tablet has the same odd high texture ids coming back just like the Motorola Razr, yet in the emulator it acts as expected (1, 2, 3, 4, 5...)<br /><br />I'm curious as to why actual devices have such crazy id numbers coming back - or maybe I just happen to have two devices with the same "feature"?egofluxhttps://www.blogger.com/profile/18431847765946714275noreply@blogger.comtag:blogger.com,1999:blog-1591823016636842474.post-32139361205497035142012-04-09T06:24:14.462-07:002012-04-09T06:24:14.462-07:00What textures ids were on device after fix?What textures ids were on device after fix?Anonymousnoreply@blogger.com