In Unity 2019.1.1 when I import your beautiful transitions, I get tons for compile errors:
assets/FlipWebApps/BeautifulTransitions/Scripts/Transitions/PlayMakerActions/GameObject/BT_Move.cs(107,36): error CS0131: The left-hand side of an assignment must be a variable, a property or an indexer
Assets/FlipWebApps/BeautifulTransitions/Scripts/Transitions/PlayMakerActions/GameObject/BT_Move.cs(91,20): error CS1729: The type `Move' does not contain a constructor that takes `2' arguments
Assets/FlipWebApps/BeautifulTransitions/Scripts/Transitions/Components/GameObject/TransitionMoveTraget.cs(56,20): error CS0029: Cannot implicitly convert type `Move' to `BeautifulTransitions.Scripts.Transitions.TransitionSteps.AbstractClasses.TransitionStep'
Assets/FlipWebApps/BeautifulTransitions/Scripts/Transitions/Components/GameObject/TransitionMove.cs(105,36): error CS0131: The left-hand side of an assignment must be a variable, a property or an indexer
Please advise as your asset is almost useless for me in this case.
Beautiful Transitions Compile Errors
Re: Beautiful Transitions Compile Errors
Hi,
Many thanks for your support in purchasing Beautiful Transitions. Such errors typically occur if there is a conflict with another asset that has a similar class name. Do you get the same errors if you import into a blank project?
I include namespaces on all my scripts to try and avoid such conflicts, however unfortunately if there are other scripts in the project that don't follow this best practice then it might cause such errors.
Regards,
Mark
Many thanks for your support in purchasing Beautiful Transitions. Such errors typically occur if there is a conflict with another asset that has a similar class name. Do you get the same errors if you import into a blank project?
I include namespaces on all my scripts to try and avoid such conflicts, however unfortunately if there are other scripts in the project that don't follow this best practice then it might cause such errors.
Regards,
Mark