Hi, I've written a more detailed reply to your forum post: https://forum.unity.com/threads/released-silantro-flight-simulator.522642/page-22#post-8572445 Basically, I've had to combine duplicated components and implemented proper inheritance-based logic. The old functions and script components are still there, they're just in namespaces now. I've harmonized the scripts and components common to the \rotary-wing and \fixed-wing systems into the ".Common" namespace. These are components that function exactly the same whether they're on helicopters or aircraft. Components specific to helicopters are now in the ".RotaryWing" namespace Components specific to Aircraft are in the ".FixedWing" namespace Changes or connections that have to be made to any of these components can be done in one script and then copied over to other projects irrespective of whether the user has Helicopter Only, Aircraft Only or Both. Each helicopter, drone, aircraft etc. is now a vehicle that derives from the Controller class and uses the exact same core scripts and components as other vehicles. This makes working with multiple vehicles so much easier since the base setup follows the same pattern whether you're configuring a fixed or rotary aircraft. Regards the upgrade path for this new logic, I've designed it in a way that the new logic slot into your project irrespective of the previous version you're running and you should get no errors from the merge. The folders are different and the scripts are arranged into namespaces which avoids them from clashing with old ones. This way you can manually upgrade your old aircraft whenever you're ready or need to. Here are the new setup tutorials; 1: Fixed: https://youtu.be/riUq4W08RdM 2: Rotary: https://youtu.be/qoyW-9yJEas Note to anyone else reading this: If you're an old or new user and you're having any problems with anything in the asset, require clarification, or need help with any script/component please send me an email (silantrosimulator@gmail.com)