I have a strange behavior of the corona splash screen. It is shown very short and I have a black screen after the corona splash screen which immediately disappears.
Video:
Looks like a bug to me because you should see Corona splash screen for like 2 seconds. I guess it should make things go faster if you could share the Corona build number you are using before any of the staff comes.
The issue hit me at a very unfavorable time. The only thing I could figure out at the moment is, that the problem is related to composer. If I load a larger scene within the main.lua, I have the issue with the corona splash screen. Does here exist a workaround maybe?
The splash screen should be happening pre-main.lua. I’m not sure what all conditions impact it and I’ve asked engineering about it. Have you run a test using something like our Hello World sample app?
Rob
Yes, I did. I have no issue with the splash screen as long I don’t load a large scene with composer in my main.lua.
Interesting. What do you mean by “large scene”? If I have some specifics (number of objects, image sizes, audio, etc.), it might help in my conversation with Engineering.
Rob
Today I had the time to modify the loaded scene a bit. I have about 50 display objects, mainly text and small images. After I comment out finally over a half of them, it worked, what means the splash screen was shown about 2s as expected. It seems that not the size of the objects is crucial but the amount. But this is just a perception. More detailed tests would be necessary to verify this.
Fact is, that the complexity of the loaded scene influences the display of the splash screen. My first thought on this is just to make a little delay of loading the intended first scene, but I didn’t tried that so far. This would be just a workaround of course as long as the procedure wasn’t improved.
Well display.newText() is one of the more expensive APIs. Do you think you could build a simple test case that we could get to the Engineers?
Thanks
Rob
Simply add something like this to the create event listener of scene1.lua at the composer sample code:
local textArray = {} for i=1,5000,1 do textArray[i] = display.newText("Hello World", display.contentWidth/2, (i-1)\*10, "HelveticaNeue", 6) textArray[i]:setFillColor(118/255,122/255,130/255) sceneGroup:insert( textArray[i] ) end
This is of course far away from a real scenario, but anyway, this should not affect the display of the splash screen.
And main.lua basically calls scene1?
Yes, I tried this extension with the corona sample code for composer. Only the above lines to the create listener in scene1.lua. No other changes. That made the same behavior that I have in my project.
I am also experiencing the same problem. Is there any solution for this ?
Looks like a bug to me because you should see Corona splash screen for like 2 seconds. I guess it should make things go faster if you could share the Corona build number you are using before any of the staff comes.
The issue hit me at a very unfavorable time. The only thing I could figure out at the moment is, that the problem is related to composer. If I load a larger scene within the main.lua, I have the issue with the corona splash screen. Does here exist a workaround maybe?
The splash screen should be happening pre-main.lua. I’m not sure what all conditions impact it and I’ve asked engineering about it. Have you run a test using something like our Hello World sample app?
Rob
Yes, I did. I have no issue with the splash screen as long I don’t load a large scene with composer in my main.lua.
Interesting. What do you mean by “large scene”? If I have some specifics (number of objects, image sizes, audio, etc.), it might help in my conversation with Engineering.
Rob
Today I had the time to modify the loaded scene a bit. I have about 50 display objects, mainly text and small images. After I comment out finally over a half of them, it worked, what means the splash screen was shown about 2s as expected. It seems that not the size of the objects is crucial but the amount. But this is just a perception. More detailed tests would be necessary to verify this.
Fact is, that the complexity of the loaded scene influences the display of the splash screen. My first thought on this is just to make a little delay of loading the intended first scene, but I didn’t tried that so far. This would be just a workaround of course as long as the procedure wasn’t improved.