Скачать или смотреть CUTSCENES: How and when to use CUTSCENES | COMPOSER SCENE MANAGEMENT

TIC TAC TOE [Lesson 15]
[S1E24] CUTSCENES: How and when to use CUTSCENES | COMPOSER SCENE MANAGEMENT


// In This Video,
I walk you through the invisible challenge many new developers have, once they start to involve movement between different scenes.
AND how this hidden problem only surfaces as a result of NOT managing your scenes remove/destroy process the correct way.
This can result in many instances of the same .lua file being called, but the new instance is trying to load whilst the old instance is still being removed, and as both instances have the same file name the composer closes the all instances when it should not.
To resolve this issue, the need to transverse momentarily to a third scene, a cutscene is a simple clean way to allow old scenes to completely be destory in memory, before a news instance gets created!



[00:00] Introduction
[01:24] Recap of Game Build Status
[02:35] Understanding behind the scenes file management
[03:15] Logic errors in your app if you don't "GET" this Composer Scene/File Management process
[04:48] Demo of this Videos Task (how Cutscenes will ensure smooth game play)
[05:40] Cutscene Documentation / Scene Flow Management
[10:18] Demo: Toon Blast Game Play, including a cutscene live demo.
[10:48] Printing to the Console each .lua files scene event name to track game logic
[14:21] composer.gotoScene() command (finishing the btnPlay from the previous video)
[15:17] Walkthrough (going directly to GP1 and NOT using a cutscene problem demo
[16:27] Calling the second instance of GP1.lua this way, means part of the scene does not get re-called!
[18:38] Remove the scene GP1.lua via destroy entirely
[21:33] Destroy the Overlay scene entirely
[22:26] Error: Because we've still not finished handling the file management
[23:09] Fix: The Cut Through Scene!!
[23:30] btnPlay change to gotoScene cutscene instead!
[23:45] cutscene composer.gotoScene & removeScene management
[24:55] (also setting the message.text variable to nil) and successful walkthrough
[25:40] console review of composer scene logic managment
[27:06] (set message.text variable to invisible)
[27:45] Summary, close and outro





==== OPEN SOURCE & FREE ONLINE TOOLS ====
In my next few videos, I will look at these in more detail.
► Lua Website: http://www.lua.org/
► Solar2D (game engine): https://solar2d.com/
► Solar2D (aka Corona SDK) Documentation: https://docs.coronalabs.com/



==== SUBSCRIBE ====
► Please subscribe (& Stay NOTIFIED) to my channel - so you don't miss out:
https://www.youtube.com/c/PointClickP...
► My other YouTube Channel McCall Media TV:
https://www.youtube.com/c/McCallMedia...



==== SERVICES USED TO MAKE/MENTIONED IN THIS VIDEO ====
► Streamyard: https://streamyard.com?pal=5713946426...
► Tubebuddy: https://www.tubebuddy.com/McCallMediaTV
► VidIQ: https://vidiq.com?afmc=5bz
► Answer The Public: https://answerthepublic.com?via=angel...
► Epidemic Sounds: https://www.epidemicsound.com/referra...
► Envato Elements: https://1.envato.market/McCallMediaTV



==== VISIT MY WEBSITES ====
► https://www.PointAndClickPuzzle.games
► https://www.McCall.media
► https://www.TheWhiteboardAnimation.biz



==== VISIT MY SOCIAL PROFILES ====
♥ Facebook Business Page:   / pointclickpuzzlegames  
♥ Instagram: instagram.com/pointclickpuzzlegames
♥ Patreon:   / pointandclickpuzzlegames  



==== HASHTAGS ====
#Variables
#LuaProgramming
#LuaCoding
#Solar2D



==== DISCLAIMER ====
Many of the links on this page are affiliate links, meaning if you were to make a purchase after using this link, then I would be paid a commission for that recommendation. However, I am in no way associated with the companies listed, please use your own judgement, and research before making a purchase. I use these links as a way to help fund my business, so I can continue to provide free content like this video. Your support is greatly appreciated.