kerbal space program unity bundle asset extractor

This is OK for simpler UIs, but can become prohibitively tedious for more complex UIs. Things like the function called by a button, or the string of a text element will all have to be manually assigned. When you load this UI into KSP you will need to manually hook up all of the elements through code. You can create the UI in Unity without importing any assemblies into the Unity editor.

There are also two options for how to handle this. The other option is to build your UI in the Unity editor, export it as an AssetBundle, and load it into KSP. There is a thread with more details on PopupDialogs and some examples. This is the PopupDialog system, it uses notations similar to the old GUILayout system, but generates a new Unity UI object. One is built into KSP and is perfect for creating relatively simple windows that don’t require much customization. So there are basically two options for using the new UI. The only problem is that building the new UI entirely through code is extremely tricky, to the point of being impractical in all but the simplest cases. This significantly improves performance, reduces the garbage created, and allows for some fancy effects that weren’t practical with OnGUI. Rather than rebuilding the UI every frame using the esoteric GUILayout and GUI system, the new Unity UI is built using standard Unity objects and hierarchies. Newer versions of KSP support Unity’s updated UI system (technically available since KSP 1.0, but only really practical since 1.1), which is a major improvement over the old OnGUI system.

Kerbal space program unity bundle asset extractor