34
« on: January 16, 2018, 05:54:47 pm »
No, ATM just only one big object with 262.144 polygons, and only 1 texture, not mipmapped with 16 bits (but even that won't make any difference being only 1 so far).
the problem is that I'm running on a 32-bit vm system, and can only get 1500 MB of memory to the max.
I could switch to a 64-bit but this project was trying to be compatible due to its specs.
Results:
Config.maxPolysVisible = 100000; -> yields Memory Used: 367MB
Config.maxPolysVisible = 1000000; -> yields Memory Used: 721MB
Config.maxPolysVisible = 10000000; -> java.lang.OutOfMemoryError: Java heap space
using xms = 1200 MB and xmx = 1200 MB
so I can assume that each zero will boost up exponentially, which was the issue with the memory. So far it's not a problem, but later on it will be when I need more textures and non-vbo objects (they are this way so that I can work with vertices and texture maps in real time). S I was getting a bit scared. But seeing there is no possibility to ingore this property checking, I don't know what to do to.