Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
As you all know, android has a memory limit of 16mb per application (or higher on other devices).
I started to develop an rpg and as you also should know, these kinds of games need more than 16 MB because of the graphics.
When you write parts of the code in C with the NDK, there is no memory limit (making games as dungeon defenders possible). libGDX is partly coded in C for better performance.
So, here’s my question:
Does it store the textures in the Java part or in the native C part?
Textures are stored in the VRAM on your device’s GPU. When your graphic engine loads textures they are probably loaded from a native method, but your textures are still in the VRAM.
Important, it doesn’t explicity store the textures in the “Java” or “C” part and there are no such parts where they are stored. When you’re getting back an
intfrom aloadTexture()function that’s only a “key” to access the texture on the VRAM.Maximum amount of textures (and VBO:s) depends on the maximum level of VRAM on your device’s GPU.