Storyboard/Composer gotoScene fading effects

Why do scene fading effects fade each display object individually, instead of fading the whole scene as a single object? It ends up looking horrible when fading to another scene and objects fade independently of the background. In what cases is this useful?

Is there an option for making the fading apply to the whole scene as one object or will I have to do this manually?

Storyboard and Composer do transition the entire group at once.  But it could be how transition.to() transitions groups.  We used to make a screen capture and transition that but it’s performance wasn’t that good. 

You could put in a feature request to see if there is a way to do this at http://feedback.coronalabs.com.

Rob

Thanks, Rob. The obvious way to do this for me would be using overlays instead of transitioning the actual scene group. You fade in a black overlay first, then change scenes, then fade out the overlay. I’m doing this now manually, but it would be much better if done internally at the right moments:

if not flow.\_fadeScreen then   flow.\_fadeScreen = ui.newRectFullScreen({0,0,0})   flow.\_fadeScreen.alpha = 0   transition.to(flow.\_fadeScreen, { time = duration / 2, alpha = 1, onComplete = function()     storyboard.gotoScene(scene)     transition.to(flow.\_fadeScreen, { time = duration / 2, alpha = 0, onComplete = function()      flow.\_fadeScreen:removeSelf()       flow.\_fadeScreen = nil     end})   end}) end

It works quite well.

Storyboard and Composer do transition the entire group at once.  But it could be how transition.to() transitions groups.  We used to make a screen capture and transition that but it’s performance wasn’t that good. 

You could put in a feature request to see if there is a way to do this at http://feedback.coronalabs.com.

Rob

Thanks, Rob. The obvious way to do this for me would be using overlays instead of transitioning the actual scene group. You fade in a black overlay first, then change scenes, then fade out the overlay. I’m doing this now manually, but it would be much better if done internally at the right moments:

if not flow.\_fadeScreen then   flow.\_fadeScreen = ui.newRectFullScreen({0,0,0})   flow.\_fadeScreen.alpha = 0   transition.to(flow.\_fadeScreen, { time = duration / 2, alpha = 1, onComplete = function()     storyboard.gotoScene(scene)     transition.to(flow.\_fadeScreen, { time = duration / 2, alpha = 0, onComplete = function()      flow.\_fadeScreen:removeSelf()       flow.\_fadeScreen = nil     end})   end}) end

It works quite well.

Hi George,

Thanks for sharing your solution it helped a lot. I had the same issue “fade” and “cross fade” transitions when I upgraded to graphics 2,0.

Sincerely,

Scott

Hi George,

Thanks for sharing your solution it helped a lot. I had the same issue “fade” and “cross fade” transitions when I upgraded to graphics 2,0.

Sincerely,

Scott

Does anyone know whether the gotoScene fade has been fixed? It’s not working for me.

I have a gotoScene fade that appears to fade bg first, then buttons. In this test, there is only one Group. It looks horrible. With all due respect, if I could program my own fades, I wouldn’t need Corona SDK.

@Rob, in my experience, fade has been a standard beginner-intermediate tool feature for 25 years, from HyperCard 1989 to Director-enabled Ansca Corona. It sounds like Corona Labs views an industry-standard fade as a “special feature” request, indicating a target-audience shift. Is that right? Making this happen is not a priority?

I’ve asked about this, but they are going to want a bug report on it.  Can someone produce a simple test case that shows these fades not working correctly?  Please include **all assets**, the config.lua and build.settings you are using and put it into a .zip file (no .bz2 files, .rar files, or any other format please)

Rob

Bumping.  We need a bug report on this please.

Rob

Use the “Report a bug” feature at the top of the page.  You need to include your build.settings, config.lua and any assets needed for it to run. 

Thanks

Rob

You should have gotten a confirmation email that had the bug ID number.  Please post it hear as a reference.

Thanks

Rob

(Case 34995) Graphics 2.0/Composer Fade and Video Problems

Thanks!

Due to virtually the same result when executing under Graphics1.0+Director and Graphics2.0+Composer, I filed another report and sample using the G1/D code. Only difference b/t G1/D and G2/C is that G1/D is “almost” usable. Just need to enable SDK-build to execute coded fade vs. system(?)-imposed slide effect. Report filed under:

(Case 35082) Graphics 1.0 Mode - Video Fade Bug

Hi, Rob Miracle. Hope you had a nice long weekend. When you have a minute, could you please post the status of these 2 cases? Is there a better way to track these? Based on what I’ve read so far, there is no real way to track bug reports; but, that doesn’t seem right. Thanks very much.

34995 has been assigned to an engineer to work on.  I don’t know where in the queue it is to be worked on.

35082 is still being investigated.

Rob

Thanks, Rob.

Is there any way to communicate progress with whomever is working on these? Working in G2 and changing scenes using director 1.3 + fade-effect anchorX/Y edits (thank you, @davidcondolora), I now have beautiful transitions everywhere, except in&out of the video module where …

Touch to enter vid mod still stores current screen, ignores fade, slides with curr screen into vid mod, video ends, ignores fade, slides with outdated stored screen, and snaps to destination.

Otherwise “this” close to working. Thanks for your help.

Does anyone know whether the gotoScene fade has been fixed? It’s not working for me.

I have a gotoScene fade that appears to fade bg first, then buttons. In this test, there is only one Group. It looks horrible. With all due respect, if I could program my own fades, I wouldn’t need Corona SDK.

@Rob, in my experience, fade has been a standard beginner-intermediate tool feature for 25 years, from HyperCard 1989 to Director-enabled Ansca Corona. It sounds like Corona Labs views an industry-standard fade as a “special feature” request, indicating a target-audience shift. Is that right? Making this happen is not a priority?

I’ve asked about this, but they are going to want a bug report on it.  Can someone produce a simple test case that shows these fades not working correctly?  Please include **all assets**, the config.lua and build.settings you are using and put it into a .zip file (no .bz2 files, .rar files, or any other format please)

Rob