Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
I don't see the point of making island and Animated3D.. anyway
. So, they use double memory. Could this be possible: use the Animated3D, but consume almost the same memory of Object3D.dispose() definitely isn't useless. Even if you don't see any effect in this situation, it's mandatory to call it before the FrameBuffer goes out of scope. The same is true for world.dispose() in case you are creating a new one.So, you do this in finalize() and i needn't to call FrameBuffer.dispose() or world.dispose() manually if i ensure they could be recycled correctly by GC. Is that right?
Do these 500kb add up each time you do the switch or does it happen only once?Each time.
//onSurfaceCreated
if(modelsPreloded)
use preloadedModels and textures;
else
loadModels() and initTextures();
initWorldAndOthers();
addAllModelsToWorld();
buildAllObjctes();
// onSurfaceChanged
mFrameBuffer = new FrameBuffer(width, height);
// onDrawFrame
animate();
mWorld.renderScene(mFrameBuffer);
mWorld.draw(mFrameBuffer);
mFrameBuffer.display();
// onTouchEvent
if(touch down)
mActivity.setContentView(new MyGLSurfaceView(mActivity));
// onDrawFrame
animate();
//mWorld.renderScene(mFrameBuffer);
//mWorld.draw(mFrameBuffer);
mFrameBuffer.display();
// new MyRenderer, when running this, free-mem is 3-4M.
initWorld();
initTexture();
initLight();
loadModel();
initCamera();
initAllAnimations();
// onSurfaceCreated
//do nothing
// onSurfaceChanged
initFrameBuffer(gl, width, height);
initFpsShown();
mFpsShown.fpsStart();
Main3DScene scene = SceneManager.getInstance().buildScene(SceneManager.SCENE_BEGIN, mWorld, mFrameBuffer, mDog);
SceneManager.getInstance().setCurrentScene(scene);
try
{
System.gc();
Log.d("jPCT-AE", "gc");
// free-mem will jumped from 3M to 12M, which means there are some mem was recycled by GC. So in this point, there was a 12-3=9M mem-increase.
Thread.sleep(10000); // waitting for GC
}
catch (InterruptedException e)
{
e.printStackTrace();
}
// onDrawFrame
SceneManager.getInstance().getCurrentScene().onDrawFrame(gl); // will call world.renderScene and world.draw, and the OOM happened here(world.draw).
mFpsShown.drawFps();
mFrameBuffer.display();
mFpsShown.calacFps();
I think it may be helpful for someone.Take in account Mali-400 does not support high precision floating point number in fragment shader. So if you have some device with Mali-400 or you want full compatibility with this GPUs, you can not use default depth shader. But its easy rewrite them (my rewritten shader is little bit faster). If you want, I can share them. And if you want some numbers, one per-pixel point light, one per-pixel spot light, post-processing image effects (distortion), one rendering of depth buffer, one rendering of motion vectors and motion blur effect (4 samples)... game is running 49fps on Samsung Galaxy S3, without motion blur (and everything needed for this effect) it is 60fps. So your app can running smooth with shadows too. But take in account, this numbers comes from high-end phone.