Menu-Scene´s 'show'-function is called while default Splash-Screen is showing?

Getting Started Newbie Questions
#1

Hi everyone :slight_smile:

I´ve run into a problem which seems to only occur on an actual Android-Device (Sony Xperia Z3 Compact). 

My Main-Menu scene has an animation for the title, where every single character of the title pops up after a certain delay. It all works fine on the Simulator, but now I´ve tried it on my Android-Device and somehow the title animation is nearly finished after the Splash-Screen has been shown.  

main.lua:

math.randomseed( os.time() ) local composer = require( 'composer' ) composer.gotoScene( 'scenes.menu' )

menu.lua:

function scene:show( event )    local sceneGroup = self.view     local phase = event.phase     if( phase == "will" ) then     elseif ( phase == "did" ) then         for i = 1, self.titleGroup.numChildren do             local char = self.titleGroup[i]             transition.from( char, { y = 200, time = 1000, alpha = 0, transition = easing.outElastic, delay = (i - 1) \* 200 } )         end     end end

It seems to me that the animation has already been started when the Splash-Screen is showing, although I started the animation in the ‘did’-Phase of my menu scene, where the scene should be visible. Any ideas?

Thanks a lot :slight_smile:

#2

The splash screen should be gone before the first frame with main.lua executes. Maybe you could add at transition effect to your composer.gotoScene() call:

composer.gotoScene(“scenes.menu”, {effect=“fade”, time=500})

To give a little delay to the start of your animation, but If you have a reproducible test case, I would invite you to zip up the project (main.lua, build.settings, config.lua and any assets needed to make it run) in to a .zip file (please no other formats) and use the Report a bug link at the top of this page so our QA team can take a look at it and pass it to an engineer for repair if it’s a bug. In the mean time you can try the technique above to mask the issue. 

Rob

#3

The splash screen should be gone before the first frame with main.lua executes. Maybe you could add at transition effect to your composer.gotoScene() call:

composer.gotoScene(“scenes.menu”, {effect=“fade”, time=500})

To give a little delay to the start of your animation, but If you have a reproducible test case, I would invite you to zip up the project (main.lua, build.settings, config.lua and any assets needed to make it run) in to a .zip file (please no other formats) and use the Report a bug link at the top of this page so our QA team can take a look at it and pass it to an engineer for repair if it’s a bug. In the mean time you can try the technique above to mask the issue. 

Rob