Thank you very much. [import]uid: 8159 topic_id: 18556 reply_id: 94562[/import]
I also hope that storyboard API will be someday fixed regarding another problems like 12002 or 11895 which are also related to transitions in storyboard API and are same problem like this delay issue.
Anyway great info !!
Tom [import]uid: 111283 topic_id: 18556 reply_id: 94566[/import]
Big thanks to the team, great to see this sorted. Just in time for me to submit my binary! [import]uid: 87138 topic_id: 18556 reply_id: 94575[/import]
“And there was much rejoicing!”
[import]uid: 19626 topic_id: 18556 reply_id: 94587[/import]
Hurrah! Thanks guys! Can’t wait to try it. [import]uid: 42417 topic_id: 18556 reply_id: 94632[/import]
Thanks for working on this guys! Im just trying build 769 which says it has the fix. It seems like something is not quite right with the transitions, I use “slideLeft” and “slideRight” in my game, sometimes it is working as expected and others it seems to scale the scene smaller as it moves away.
Also, in the simulator it does this scaling every time, on the device it is only occasionally. I have never tried them but it looks like what I imagine the zoom fades would look like. Thats a complete guess though as ive never used them 
I also tried creating a new game using the “Game” template, that uses the “fade” transition, this seems to scale the image to the left hand side and then fade, it certainly does not look the same as before the fix.
This is on an original iPad running 5.1. [import]uid: 8600 topic_id: 18556 reply_id: 94781[/import]
I bet build 770 will fix that. 
[import]uid: 103624 topic_id: 18556 reply_id: 94785[/import]
By using an effecTime of 2000, you can see that transition efects has bugs, the start position on screen is all wrong. [import]uid: 10141 topic_id: 18556 reply_id: 94787[/import]
Ya my transitions are buggy on Android. Specifically the crossfade. It does some weird scaling as well as fading. Build 769 here.
edit - and sad to report, the delay is still present. [import]uid: 42417 topic_id: 18556 reply_id: 94798[/import]
769 actually breaks my app. It works much better up to 768. I am only using slide to left and right transitions. 769 moving it too far. So most of the screen is actually blank. [import]uid: 19297 topic_id: 18556 reply_id: 94799[/import]
I’m looking into these issues and trying to get them resolved asap for you guys…
Thanks for all the reports, it helps [import]uid: 84637 topic_id: 18556 reply_id: 94800[/import]
Danny,
i am using fade transition with time about 350ms which seems very good for an average user. before 769 it took about 500 ms on iphone3GS device to even start transition.
Now after 769 reaction is almost instant so its great !! but i can see additional artifacts:
- screen is changing yScale for 100ms during transition which looks very strange
- screen is suddenly fading to black without particular reason instead of normal fade out, it looks like device is power down
- i found about reaction to clicking button to execute storyboard.goto() does not respond to user action in about 2-3% of taps, which never happened before 769
From user point of view experience from app is lower in 769 then before due to this problems.
Regards
Tom [import]uid: 111283 topic_id: 18556 reply_id: 94838[/import]
Just tried build 723 and it seems to have fixed the scaling issue I was seeing, my transitions are now working as they did and the simulator matches the device.
The delay is looking better now too, its been reduced enough that I dont think the player would be wondering whether they had pressed the button, which was my concern before.
Thanks for all the hard work on this! Its a shame it took such a long time but storyboard now seems useable [import]uid: 8600 topic_id: 18556 reply_id: 95449[/import]
I am on build 773, Android device build, and the transitions have some strange artifacts at the top of the screen, like the images are being loaded and flashed on just a tiny portion of the screen. Then the expected screen appears, but all that “stuff” happening during the screen transition is very annoying and strange.
[import]uid: 8159 topic_id: 18556 reply_id: 95611[/import]
I’m having similar issues on Android Gingerbread with 773. The delay is less now which is great but it’s still doing some odd scaling of graphics during the transition (crossfade). [import]uid: 42417 topic_id: 18556 reply_id: 95613[/import]
I built an app for Kindle Fire with build 775. The delay is still awful. I dont know if that’s because of Kindle Fire’s hardware or is it corona sdk bug? [import]uid: 77183 topic_id: 18556 reply_id: 97757[/import]
it still has a delay issue on device. i built an app for android tablet using bild 776,
it is a little bit faster the previous daily build version.
faster about 0.3~0.5sec maybe?. but still takes about 1.5 ~ 2sec when gotoScene() API is called [import]uid: 39429 topic_id: 18556 reply_id: 97846[/import]
-edit- deleted by duplicate posts [import]uid: 39429 topic_id: 18556 reply_id: 97845[/import]
This is frustrating to hear. Is it faster or cleaner than build 773?
-edit- trying it now and will report back. I was getting those odd screen movements on 773 so I’m hoping this fixes it.
-update- the transition delay seems to be addressed however 776 breaks the app. Stage objects seem to be removed or lost and then everything breaks. 
I am testing on Android Gingerbread Nexus S.
With 773 everything works as it should except the transition delay is present and images were getting nudged around where they shouldn’t.
With 776 the delay seems to be fixed and no images get nudged around but pretty much everything is broken. [import]uid: 42417 topic_id: 18556 reply_id: 97850[/import]
build 776 fixed the delay on iPad, but delay on Kindle Fire is still over 1 sec long - not acceptable
I can also agree with Hive about build 776 breaking up app every here and there. [import]uid: 77183 topic_id: 18556 reply_id: 98097[/import]