Here is a mod spotlight, kindly provided by buzz66boy
here is a small plugin I've been working on in the last few days. It adds working (but ugly) PAPI (Precision approach path indicator) arrays to the end of the runway at KSC.
It is currently configured for a glidepath of 6° which means that the array will show two red and two white lights when you are on a 6° glidepath with your plane.
Download: https://github.com/asarium/PAPIPlugi...PAPIPlugin.zip (install by unzipping the contents into your KSP folder)
Source code: https://github.com/asarium/PAPIPlugin
The code and the plugin is licensed under the MIT license.
- angavrilov fixed the unresponsive array bug
- Fixed placement of PAPI lights for 0.22 compatibility
- Added GUI to modify the glideslope values interactively
- Replaced the light rectangles with actual spheres, looks way better now
- Changed some config values, see below
- Changed internal API to be modular
- Added configurable light arrays
- Compatibility update for KSP 0.21
Config file documentation:
Version 0.2 added the possibility to add light arrays within a config file. This is done by the LightGroup config node type. Every node represents an object which groups multiple lights together.
You can find an example of that config file here: https://github.com/asarium/PAPIPlugi...gin/lights.cfg
The options on a LightGroup are:
- Name: The name of the group (optional)
- Body: The name of the body the group is located on (e.g. Kerbin) (required)
To add actual light arrays you need to add LightArray entries inside the group node. Each entry needs a Type value and may have a Namespace value. These are used to identify the class which is used for the light array.
Possible values are:
- Type: PAPIArray
- Latitude: The latitude of the array location (required)
- Longitude: The longitude of the array location (required)
- Heading: The heading the array points to. This is used to aligned the array and also to make the array fade out when viewed from behind.(required)
- TargetGlideslope: The target path where the array will be half white half red, default is 6. (optional)
- GlideslopeTolerance: The difference from the target glidepath where the array will not be entirely red or white, default is 1.5.(optional)
- Height: The actual height of the array above the terrain below (optional)
- PartCount: The number of lights in the array (optional)
- LightRadius: The radius of the lights (optional)
- LightDistance: The distance between two lights, excluding the actual light radius (optional)
- KerbTown usage for array placement
- "meatball"/OLS light array
- full runway lighting which means the addition of editable generic light array
- TaranisElsu - Author of the used TacLib UI library
Please give me feedback, positive and negative so I can improve the plugin in the future.
If you find bugs please use the issue tracking of github, that will help me fix them as soon as possible and will also keep the thread clean.