In my app, Sharks Vs. Subs I use the crossFade storyboard effect almost universally. However, when I updated to build 771, (and made no changes to my code) the transitions still appear, but with the center of the old scene in the top left corner of the screen. This looks like a problem with the reference point of the display group, but I don’t think I did anything in my code to change that. Is there anything that has changed in this build that would cause that problem? Or is it a bug in the build itself?
Thanks,
Peter [import]uid: 38000 topic_id: 23661 reply_id: 323661[/import]
Update (regarding transition bugs):
The storyboard transition issues that were introduced after the “delay bug” was resolved are now fixed. They should be in one of the next few daily builds (keep an eye out for “Storyboard” in the daily build changelogs). [import]uid: 52430 topic_id: 23661 reply_id: 95006[/import]
Hi.
I’m having the transition issue in my app. I updated to build: 2012.772 and then started seeing this?
I was using the 2011.704a build and did not see this!?
From the build notes I read this?!:
CoronaSDK 2012.769
Post date: Tue, 2012-03-20 10:48
Release notes for build 2012.768 through 2012.769
Fixed delay that occurred during scene change, as well as transition issues where storyboard would push the current scene and next scenes to the top left reference point, breaking transitions Casenums: 10346, 12193
Cases affected:
But I still see this? Maybe it will be in the next daily build 
[import]uid: 18310 topic_id: 23661 reply_id: 95109[/import]
Transitions are still wonky in 772. Just a basic SlideRight and SlideLeft between two scenes, you can see the old scene shrinking off into the distance during the transition, and then a third scene sits on the stage all cockeyed with something like 80 pixels of black nothing at the left edge.
Even Crossfades show the old scene shrinking down into a corner for some reason.
EDIT: of course, the release notes for 772 don’t say anything about “Storyboard”. [import]uid: 44647 topic_id: 23661 reply_id: 95164[/import]
I’m experiencing the same issue in 772. Touch events seem to be accepted at the non transformed (expected) location, but the display shows things at different positions each time i enter a mode. Objects that are not added to a storyboard scene show up in the correct location. [import]uid: 122310 topic_id: 23661 reply_id: 95169[/import]
Which build should we use until while this bug is being fixed? [import]uid: 122310 topic_id: 23661 reply_id: 95172[/import]
I’ve worked around the bug by redefining gotoScene in my main.lua file. Use something like this before any scenes are used:
local storyboard = require(“storyboard”)
local oldGoto = storyboard.gotoScene
storyboard.gotoScene = function(sceneName)
return oldGoto(sceneName)
end
it removed the transition type (which seems to cause all the weirdness). Straight up transitions with no animation seem to be working fine. [import]uid: 117383 topic_id: 23661 reply_id: 95243[/import]
FYI:
We just checked-in an important storyboard update that should fix the transitioning bugs, and also introduces a couple new features. Here’s a description of the changes that will be in the next build (after 2012.772):
-
Fixed bug where certain transitions would behave incorrectly if there were off-screen objects.
-
Added new function: storyboard.loadScene( sceneName [, doNotLoadView] ), which is similar to storyboard.gotoScene(), but no transition is initiated (useful for pre-loading scenes).
-
Added two scene events: “enterBegan” (dispatched before scene transition occurs) and “exitEnded” (dispatched after scene has exited).
And for those interested, these updates address ticket casenums: 12827 and 12954
Once again, these changes will appear in the build that posts after 2012.772. [import]uid: 52430 topic_id: 23661 reply_id: 95277[/import]
Those will be welcome additions to the Storyboard API. I’ve got a problem with an app where it’s taking 1.5 - 2 seconds to do *anything* when changing scenes the first time, even on build 772 with no transition animation.
I’ll be interested to see if I can do a better job of preloading scenes instead of just assets and get this delay solved.
I have a title scene with a “Play Now” button. In the enterScene of this scene, I’m prefetching the visual assets for the game scene from an imageSheet so it’ll already be loaded and ready to go – then I load a native.newVideo cutscene (a native object, not in any groups, and separate from any storyboard stuff).
When I hit the Play Now button, the following is supposed to happen:
* unhide the video and start playing it.
* gotoScene(“game”)
What actually happens is the app sits there for 1-2 seconds before displaying the video (which has already been playing for 2 seconds by the time it shows up). This delay happens whether I play the video or not, and I keep trying to use the video to “hide” the delay (it’s a 6-second cut scene, so I don’t really care if it takes 2 seconds to load the game scene or whatever). It’s weird, since ( 1 ) there’s nothing going on that should take 2 seconds to perform and ( 2 ) I’m telling corona to show me the video *before* doing anything that *might* take 2 seconds to perform (e.g., goto a new scene).
[import]uid: 44647 topic_id: 23661 reply_id: 95291[/import]
@toby2: That sounds really strange, as most people have reported the delay issues going away after the fix came out. Could you send in a sample test-case that demonstrates the delay you’re speaking of, and submit a bug report? Be sure to mention “storyboard” and “delay” somewhere in the title.
Here’s the bug report form:
http://developer.anscamobile.com/content/bug-submission
Now that we have the internal infrastructure ready, I’d like to get any and all delay issues sorted out. Once you submit the bug, please send the casenum to jonathan [at] anscamobile.com so I can have a look.
Thanks! [import]uid: 52430 topic_id: 23661 reply_id: 95298[/import]
@ fading i also bugged for me in 772. [import]uid: 86417 topic_id: 23661 reply_id: 95304[/import]
There are definitely still issues in 773. Transitions, while resulting in usable screens, have very odd behaviours at the edge of letterboxed screens. If I had to describe the effect it would be that the area to the left of the screen offset is transitioned properly while the remainder of the scene stays the same (but shifted by the offset) until the transition completes.
Also, there’s another issue where a scene that was created fails to show up at all. This works on a build as of a few days ago. I’ve traced through and it does appear that the lifecycle of the new scene is followed properly the view just doesn’t show up unless I call self.view:toFront() in the enterScene function. I’ve only found this behaviour with one of our scenes, however, and I’m not sure how that scene is any different from other scenes. [import]uid: 117383 topic_id: 23661 reply_id: 95439[/import]
I am using 2012.773 and I am having transition problems as well.
On Android, the fades dont seem to fade anymore… the screen “drops” down to the bleed area (if I am explaining that correctly) and displays the next screen without a fade.
I cant test this on iOs at this time, so not sure if this is happening on the apple side. [import]uid: 114363 topic_id: 23661 reply_id: 96625[/import]
I’m still having Storyboard transition issues myself.
My scene jumps to the top left corner in the middle of a transition.
(2012.774)
EDIT: My transition issues have been fixed as of build 2012.776. [import]uid: 73951 topic_id: 23661 reply_id: 96683[/import]
@Mort – glad your issues are fixed in 776; everything else appears to be broken. It’s probably the least functional storyboard build yet. [import]uid: 44647 topic_id: 23661 reply_id: 97543[/import]
I am having similar issues in 776 on Android (Kindle Fire).
Fade/CrossFade/Zoom transitions don’t seem to work at all.
SlideLeft and SlideRight do work. But with SlideLeft/SlideRight, on first re-entering a scene “enterScene” fires, but the scene does not show (it appears under another scene). The second time and afterward it works fine. It also works fine all the time in the simulator.
Unfortunately I don’t know whether I should be hunting a bug or waiting for the transitions to be fixed…
[import]uid: 94304 topic_id: 23661 reply_id: 97841[/import]
I have lots of new problems with storyboard in 776:
776 note: “Storyboard: Fixed several scene transition bugs. Fixed delay issues”:
Up till 775 my transitions (slide left, right) worked fine.
I think that before exitScene is called a capture of the scene view was made.
This was good, because in exitScene I remove all of the visual stuff from the scene, like LevelHelper levels etc.
The capture then was moved off screen and the new scene appeared.
Now it seems that there is no capture anymore, when I remove all the LevelHelper stuff in exitScene this only leaves a black screen that is moved off screen while the new scene appears.
If I move LevelHelper level to the new exitEnded event, the transition works, but crashes half the time…
Additionally, because now the complete LevelHelper scene is moved off screen, I have problems with all the level elements that are positioned outside the visible screen (parallax scrolling, etc.). This elements appear in front of the new scene that gets transitioned in.
I of course applied a mask to the scene that is moved off screen and with the mask I was able to hide these elements, but I don’t like this solution.
MY QUESTION:
Did you intentionally remove the automatic screen capture functionality? Was this maybe the reason for the slight delay?
If yes, please tell us if you are changing core functionality of the storyboard API.
If not, please have a look at it - why isn’t it working anymore?
I just started to do my own fix using screenCapture, but this will take ALL elements on screen, not only the elements of the scene view (so my navigation buttons etc. are captured, too)…
But thank you for now looking at and debugging the storyboard API!
Best,
Andreas [import]uid: 107675 topic_id: 23661 reply_id: 98005[/import]
Danny has asked that we post our storyboard problems to this thread:
https://developer.anscamobile.com/forum/2012/03/30/storyboard-issues-thread-please-post-any
What I found is that if I have a gotoScene and DO NOT specify a transition then that screen seems to stay on top and I can see the other sliding underneath.
Adding transitions to all my gotoScene calls seems to have addressed it. I however am having reference point and rotation problems on Android that may be related.
Again, post these over in the other thread so Ansca can gain some intel on the problem. [import]uid: 19626 topic_id: 23661 reply_id: 98021[/import]