Ballistic Unity Tools
|This article is a stub. You can help BallisticNG Wiki by .|
Ballistic Unity Tools is a suite of tools integrated into Unity which allow you to prepare tracks exported from the Layout Creator for use in the game. As the tools are integrated into Unity, you will need a copy of Unity installed to use them. The game runs on Unity 2017.2.1. Do not use Unity 2017.3 or above!
DirectX 9 support was removed, which will prevent shader swapping from functioning.
- 1 getting started
- 2 ballisticNG 1.0.3 - ballisticNG 1.1 upgrade guide
- 3 essential knowledge
- 4 supplemental knowledge
If you've already imported
BallisticUnityTools.unitypackage, you can skip to Updating.
To install the tools, you need to import the package. Once you have Unity installed and a new project open, go to the toolbar at the top of the window and then navigate to
Import Package ->
Custom Package. After this, navigate to
BallisticNG and open
BallisticUnityTools.unitypackage from the
When a new version of the Ballistic Unity Tools package is ready, the package file on your PC will be automatically updated thanks to Steam. However, your Unity project will not automatically change to the latest package version.
You can switch your Unity project to the latest package version by importing the package again. This will update any files that have changed.
ballisticNG 1.0.3 - ballisticNG 1.1 upgrade guide
Between 1.0.3 and 1.1 BallisticNG updated from Unity 2017.2.3f1 to Unity 2018.3.8f1 and you need to do the same. There has been some changes to Unity which require manual modifications of your project folder before you can safely upgrade. Follow these steps for a smooth upgrade, and remember to always make a backup of your project folder!
- Install the new version of Unity but DO NOT open your project with it yet!
- Navigate to your project folder and open the
- Delete the
- Open the project with Unity 2018.3.8f1
- Re-import the Unity Tools package and restart Unity
manifest.json file points to external dependencies for your project. In Unity 2017 this was only used for packages that you could manually install but in 2018 this is also used to point to internal Unity libraries. If you don't delete this file so Unity regenerates it, Unity will not include it's own internal libraries and your project will break.
Custom tracks cannot contain custom scripts. Custom tracks are compiled as Unity asset bundles, which do not allow scripts to be built into them.
It is possible to save scripts into an assembly and load the scripts from that assembly, but components attached to game objects have asset references serialized (which means that loading a script from an assembly will result in Unity not knowing that the script is actually loaded and usable).
Because of this, it is a goal to over time keep adding new behaviours that modders can use. If you have a behaviour you'd like to see implemented, let Vonsnake know!
Essential knowledge that must be understood to create a playable track.
If this is your first time launching Unity, it is recommended to read the pages below in order.
Supplemental knowledge to enhance track quality.
Unlike the essential knowledge pages, each page in this section:
- can be read in any order
- can be read on demand whenever you want to read up on a specific topic
- is less of a user guide & more of a technical guide
- is ordered alphabetically