September 14th, 2015

Created by: - Bryce C Schroeder ([email protected]) - Nathaniel R. Lewis ([email protected])

Maintained by: - Thomas P. - NathanKell

Additional Content by: Gravitasi, aftokino, KCreator, Padishar, Kragrathea, OvenProofMars

• finalizeOrbits only recalculates the SOI, if it is not set in Properties { }
• Optimizations for non spherical oceans
• Kopernicus now sets the altitude where the "space-music" starts
• Fixed a bug with SpaceCenter and recovery distances.
• Fixed a bug with the flightGlobalsIndex patcher, now every body's flightGlobalsIndex is fixed.
• Other minor improvements

Note - reparenting Kerbin or the Sun causes the sky to be incorrect in the space center view. It is, however, correct in the flight view and the flight map view. Reparenting the sun causes other stars positions to not update in the tracking station for some reason.

Kopernicus is a KSP add-on that allows for modification of stock planets and the creation of new planets via modification of the system prefab. Why is this advantageous you might ask? Previous planet adder mods, such as Planet Factory, modified the live planetary system and had to keep multiple hacks actively running to provide these worlds. We strive to provide the least hacky solution by introducing planets into the game in the exact same manner Squad would.

Kopernicus is a one step process. It is started before the planetary system is created and rewrites a property called PSystemManager.Instance.systemPrefab. The game itself then creates our planetary system as if it were blessed by Squad themselves. The mod’s function ends here, and it terminates. Kopernicus introduced worlds require zero maintenance by third party code, all support is driven entirely by built in functionality. This yields an incredibly stable and incredibly flexible environment for planetary creation.

One caveat exists that prevents absolute control over a planetary system. Due to the way Squad defines how launch control and ship recovery work, a planet called Kerbin must exist and must have a reference body id of 1. While it is easy to provide this scenario, as a star to orbit and a single planet satisfies this, any would be universe architect needs to be aware so they don’t get mystery errors. The displayed name of the body (i.e. the celestialBody.bodyName property) can be changed after the spawn of the PSystem

Each celestial body in KSP has a property called “flightGlobalsIndex.” This number does not directly correspond to the reference id, but is related. Once all of the celestial bodies have been spawned, references to them are written into the localBodies list. This list is then sorted in increasing order of the flight globals index. The index the body is located at after the sort becomes the reference body id.

We have yet to see if removing or rearranging the other bodies causes any sort of errors in the science or contracts system.

1. Copy the contents of the GameData/ folder to KSP’s GameData/ folder

2. Launch KSP and enjoy!

3. Please report any bugs you may find to either or both of the email addresses above.

Selectively copy folders inside KopernicusExamples/ into a GameData/KopernicusExamples/ folder. There are a number of examples of how to use Kopernicus.

Coming Soon

After the Kopernicus.Injector behavior rewrites the system prefab and terminates, a behavior called Kopernicus.RuntimeUtility is started to provide debugging functions.

PQS Inspector (Mod-P): Pressing Mod-P will explode your console with information about the PQS controller of the body currently being orbited

PQS Quad Visualizer (Mod-;, Mod-/): Pressing Mod-; will draw green lines on the normal vectors to the surface of the planet at the PQ nodes. This lets the LOD structure be visualized. Used for testing LOD levels and whether your temperamental ocean just wants to be invisible or is decidedly non present. Pressing Mod-/ will remove the lines (and save your framerate).

Map Exporter (Mod-E-P): Pressing Mod-E-P will open the Kopernicus Map Export. The first, empty, line is for the name of the body, that you want to export. The second one is the resolution of the exported maps. The textures will be saved to GameData/Kopernicus/Cache/PluginData