v3.0 is now out and is a complete rewrite that also exposes the asset through a new scripting API (shown in the post above). We have some pretty cool things planned so keep an eye out here for updates.
NOTE: To update you will need to remove the old /FlipWebApps/BeautifulTransitions/ folder before updating, or delete the file
/FlipWebApps/BeautifulTransitions/Scripts/Transitions/GameObject/TransitionMoveAnchoredPosition.cs after updating.
- Rewritten from the ground up to expose the whole API through scripting including calls and notifications.
- GameObject: Removed deprecated TransitionMoveAnchoredPosition component
- Demo: New scripting demo
- Demo: Added auto transition in / out button to GameObject demo
Major documentation update is underway… Display Item and shake documentation and demos are now online
http://www.flipwebapps.com/unity-assets/beautiful-transitions/display-items/
http://www.flipwebapps.com/unity-assets/beautiful-transitions/shake/
More to followin the next couple of days for the rest of the features within the asset…
General transition overview and screen and camera transitions documentation is ready:
http://www.flipwebapps.com/unity-assets/beautiful-transitions/transitions/
http://www.flipwebapps.com/unity-assets/beautiful-transitions/transitions-screen-and-camera/
Also the full set of demos from the asset are compiled and online on this page:
Just gameobject and UI transitions documentation to go…
Finalising the next release which will allow for user defined smoothing on screen and camera wipes, including setting the smoothing strength (shown below at 50%).
Next version is now submitted for review. Several updates including the smoothing shown above, an attention state for UI animations and several internal improvements.
How to do a screen fade from code (without using a component)?
var screenFade = new ScreenFade(gameObject, Color.blue, delay: 1, duration: 1);
screenFade.StartValue = 1;
screenFade.EndValue = 0;
screenFade.Start();
You can also add an onComplete callback to the constructor to be notified when complete. Next release I will add a ‘direction’ flag to the constructor to avoid the need for the start / end values.
When transitioning to / from a target it can be useful to just transition along a particular axis (e.g. move several items horizontally from a start target location). The next release will let you do just this:
v3.1 is released with support for smoothing on wipes and several other improvements.
NOTE: To update you will need to remove the old /FlipWebApps/BeautifulTransitions/ folder before updating, or delete the file
/FlipWebApps/BeautifulTransitions/_Demo/DisplayItem/Scripts/TestController.cs after updating.
Improvements
- Demo: Added attention button to the DisplayItem demo scene
- Demo: Shake demo updated with visual controls for modifying the shake settings
- DisplayItem: Removed unnecessary DisplayItemSetInitialState component
- DisplayItem: Added SetAttention and SetActiveAnimated functions to DisplayItemHelper.cs
- General: Added links to documentation and support to the editor menu
- Shake: Moved scripts from ShakeCamera to Shake folder and namespace.
- Shake: Improved tooltip text for ShakeCamera component
- Shake: Renamed Shake method to ShakeCoroutine and added new replacement Shake method that is callable from code.
- Shake: Code documentation improved
- Transitions: Updated component menu name
- Transitions: Screen & Camera wipes now support smoothing.
Fixes
- Fix: Correctly handle transitions that outlive a scene change causing error when transition targets are destroyed.
v3.2 is submitted for review with some small but useful updates including a RepeatWhenEnabled option for auto running transitions multiple times, the option to specify the axis on which MoveTarget should work so you can easier move multiple items and just-in-time initial transition setup to avoid issues when a transition component is started from script before it has change to setup…
v3.2 is now released and contains some important internal improvements and fixes along with the ability to specify an axis for MoveTarget to easier move multiple items. Details are below:
NOTE: This version contains an important updates relating to initial transition setup. While this should not give any noticeable impact we advise taking a backup copy before upgrading. If you have any issues or problems then please contact us as listed above.
Improvements
- Shake: Updated comments
- Transition: Updated tooltips
- Transition: Deprecated MoveTarget TransitionStep as the functionality is provided by Move (Note: MoveTarget component remains)
- Transition: Added option to specify the axis on which MoveTarget should work so you can easier move multiple items (see GameObjectTransitionsDemo)
- Transitions: Added RepeatWhenEnabled option for auto running transitions multiple times.
Fixes
- Transition: Moved initial transition setup to before transition call to avoid possible execution order issues when using the API
v4.0 is now released. The big new feature this time is cross scene transitions. Working on finalising the next update that will feature cross camera transitions.
NOTE: Several components and classes have been moved to different namesapces and so if you access the transitions through code you may need
to change your ‘using’ statements to reflect the new locations. See the change details below for further details.
Improvements
- Demo: SceneSwap demo now demonstrates use of cross scene transitions
- Demo: GameObjectTransitionsDemo demo now demonstrates use of sprite fading
- Transitions: Cross scene transitions added for scene wipes and fades
- Transitions: Fade now works with Sprites.
- Transitions: All components have updated namespaces and are move under FlipWebApps.BeautifulTransitions.Scripts.Transitions.Components.xxx
- Transitions: All abstract classes and components have updated namespaces and are move under FlipWebApps.BeautifulTransitions.Scripts.Transitions.Components.xxx.AbstractClasses
- Transitions: TransitionHelper added TakeScreenshot and LoadScene methods.
- Transitions: TransitionStep Completed method renamed TransitionCompleted
- Transitions: TransitionStep TransitionInternal method renamed TransitionLoop
- Transitions: TransitionStep SetProgress call moved from Start to TransitionLoop for better control
A bit of a quiet period recently whilst I have been working on some big changes to Game Framework. That said there is a lot of good stuff coming to Beautiful Transition soon. First up here is a preview of Color Transitions using either fixed colors or gradients.
Added support for both normal and unscaled time so transitions can now run even if you have paused the rest of your game.
Beautiful Transitions now supports using Game Framework (free) Game Actions when a transition starts or ends. In addition you can add your own code callbacks for more custom functionality.
Fade transition now supports RawImage, TextMeshPro and MeshRenderer
Transitions are now available as Game Framework actions so can be called directly from within Game Framework. Shown below as part of a Game Framework Conditional Action component:
