FAQ - MOARdV/AvionicsSystems GitHub Wiki

How do I make custom action group names?

MAS supports the RasterPropMonitor "AGMEMO" feature. This feature reads the vessel's description (from the Editor) and interprets specifically-formatted lines as action group memos. The format of the line is simple:

AG1 = ACTION
AG2 = ON ACTION | OFF ACTION

The line must begin with "AG" (upper case) followed immediately by a number between 0 and 9 to identify which action group the memo is for. After the equal sign '=' is the description of the action. Different names for the ON action and the OFF action may be specified be separating the descriptions with the '|' character. The ON action is the text that is displayed when KSP says the action group is "on". The OFF action is when that AG is "off".

Any action groups that do not have memos specified for them use 'AG#' for the memo (with the number replaced by the action group number, such as 'AG2' for action group 2.

What about CKAN?

I do not plan on maintaining CKAN metadata for this mod. For one thing, this mod requires the ASET Props and ASET Avionics packs, which have not been updated for several KSP versions. Last time I checked, CKAN won't install them without intervention.

Any CKAN metadata for this mod was submitted by a third party. I do not guarantee the correctness or completeness of that data. For support with a CKAN installation, please refer to the CKAN forum thread.

Where are the IVAs?

Since MAS is a toolkit, like alexustas's ASET Props and ASET Avionics packs, this mod is geared primarily towards modders who want to create advanced functional IVAs. I include IVAs to illustrate the mod's capabilities.

Currently, MAS includes IVAs for a few stock parts: the Mk1 (Mercury-like) command pod, a partial IVA for the Mk1-3 (Apollo-like) command pod, and the Mk1 lander can.

The MOARdVPlus mod includes a 1960's-style Apollo command pod for use with the Bluedog Design Bureau, as well as a modernized Apollo IVA (still under development). The Kerbal Flying Saucers mod includes a MAS cockpit as well.

Will you add support for Mod X?

This is most commonly asked in association with BD Armory. Short answer, probably not. If it is not a mod I use, I really do not want to spend my time learning how to use it, and then figuring out how to write an interface with it, and then coming up with an IVA I can use for testing (much less to demonstrate that support).

MAS allows for interfaces with mods using the same mechanism as RasterPropMonitor. If someone wants to incorporate mod support that works with MAS, I am willing to provide advice on how best to accomplish that.

Why doesn't This Mod Work?

Please follow these basic troubleshooting steps before asking for help on the forum:

  1. Are you on the current version of Kerbal Space Program? Are you using the latest version of Avionics Systems? Are your other plugin mods up to date? Incorrect mod versions cause problems that are not always obvious in-game. I do not support prior versions of KSP, nor do I provide support for prior versions of Avionics Systems.

  2. Did you use CKAN to install? Due to past problems with CKAN, I do not support installation via CKAN. Any CKAN metadata for this mod was created by a third party, and I do not guarantee that it is complete and correct. Please uninstall MAS through CKAN and install the mod manually. The Installation page contains the short list of instructions for installing this mod. If you do not know how to install a mod manually, check on the KSP forum for additional help.

  3. If the problem persists with a correct manual installation, please follow the forum's troubleshooting tips.

  4. If you followed these tips, you should have seen information about The Logs. Provide those logs, and contact me either on the KSP forum or on GitHub. No logs = no support.

What about RasterPropMonitor?

I have stopped all development work on RPM. I do not intend to release any more updates for it.

JohnnyOThan adopted RPM, and continues maintaining it. Refer here on the forum for more information.

Localization?

MAS supports the KSP localization features for user interface features (right-click context menus, the MAS configuration page). I have not had any offers for translations yet, so these UI features only support en-us. I do not expect to extend localization to the prop labels, MFDs, and so forth.

Why Lua? Why MoonSharp?

Lua is a well-known scripting language, particularly in game environments. It provides a great deal of flexibility and extensibility for IVA creators.

MoonSharp was selected because it was still active while I was researching C# Lua interpreters, and it includes pre-made DLLs for use with Unity, with an easy-to-locate repository on GitHub.

Due to inactivity in MoonSharp development, I may migrate to a different C# Lua interpreter.