@normen said:
Did you all deactivate niftys excessive logging on android? Logging can bog down the performance on android immensely.
Yeah i did, it’s not logging.
@iwgeric said:
I updated my app as you did with threading for the initiation of the game. I do not have Nifty yet. From what I can tell from the log, the splash screen displays 1.5 sec after the app is started and then the initial display of the app starts after another 1.5 sec (roughly).
I think I have a way to have the splash screen start immediately by changing the way “view” is attached to the activity layout, but it would require an engine change. Is that a possibility? If not, I won’t bother figuring out the details, but roughly, the idea is the following:
- change the activity layout to have a framelayout that contains both the surfaceview created by AndroidHarness and a ImageView that is overlaid on top of the surfaceview
- make the ImageView full screen to hide the SurfaceView
- have a callback from the context to AndroidHarness to remove or hide the ImageView when the app initialization is done (ie. just before simpleUpdate is called the first time
I think it can all be done within AndroidHarness except for the callback. I’m not sure where that would come from, maybe the Android specific OGLESContext (that’s where the SurfaceView Renderer code is).
Would that be a completely bad idea from an engine standpoint?
I did that at first, but you gain like 0.2 seconds…IMO it does not worth the effort of a listener to notify the view that the game is loaded.
I have similar times than you, 1.5 sec before something appear. My game though takes around 13 seconds to load.