Planetary Systems - Revision history

Cholmondely: Links!

2021-08-09T13:11:23Z

Links!

Cholmondely: /* Planet Data Interface */ Added screen shot of Planet Data Sheet

2021-07-19T14:02:32Z

‎Planet Data Interface: Added screen shot of Planet Data Sheet

Cholmondely: /* System layout and orbital mechanics */ Link!

2021-05-25T22:10:00Z

‎System layout and orbital mechanics: Link!

Cholmondely: /* Known issues */ typo

2021-02-22T16:14:37Z

‎Known issues: typo

Cholmondely: Links & Tags, Structure

2021-02-22T16:13:42Z

Links & Tags, Structure

Show changes

Cholmondely: Tagged as Stranger's World

2021-01-31T09:45:02Z

Tagged as Stranger's World

Cholmondely: /* System layout and orbital mechanics */ Tweaks

2020-12-28T15:06:44Z

‎System layout and orbital mechanics: Tweaks

Cholmondely: Tweaks! Links!

2020-12-10T21:05:42Z

Tweaks! Links!

Cholmondely: Page Created, but links need fixing

2020-12-10T20:58:56Z

Page Created, but links need fixing

New page

Core package:

*Current OXZ version 1.7.0
*Uploaded 06 July 2020

[b]Planetary System Texture Pack A...Z[/b]

*Current OXZ version 1.6.0
*Uploaded 23 November 2020

This project was started as tweaked [b]Orbits[/b]. Old good [b]Orbits[/b] (authors Ebi and Kaks) with textured planets and improved compatibility with large moons. Now it is heavy mod of original [b]Orbits[/b] but original [b]Orbits[/b] script, realizing generation of solar system and orbital dynamics, remains as crucial component of [b]Planetary Systems[/b] OXP. So let’s start presentation from [b]Orbits[/b] script modifications.

== System layout and orbital mechanics ==

Maximal additional planet number in system raised from 7 to 8.
Like original [b]Orbits[/b] script generates planet subset, selecting planets from planetinfo.plist on pseudo-random base, but technically there are 10 variants for every planet class in planetinfo.plist. Mini-terra for example presented with radii 2750, 2775, 2800...2975 km. Script preudo-randomly selects one from ten variants for every planet class in generated subset. Ten radius variants for every planet class is not just for visual diversity (it is hard to notice visual difference between 3400 and 3600 km radius without specially planned experiment). Main reason is provide more diversity for initial data, used by PlanetEngine (about PlanetEngine a bit later)
These planets are divided onto classes based on radius:

*Miniterra – Mercury analog
*Venus-like planet or desert Terra-like planet
*Subterra – Mars-like planet
*Superterra aka Super-Earth
*Two gas giants like Jupiter or Saturn without rings
*Ice giant – Neptune analog
*Dwarf terra – Pluto analog

It seems to be similar to our Solar system layout with exception of super-earth, but really [b]Orbits[/b] generates wide range of possible layouts. You can see systems with only gas giants except main planet or with only terrestrial planets.

Discriminating borderline between large moon and small planet is raised from 1000 to 2500 km (from 10,000 to 25,000 m in game units). So you can simulate large moons such as Titan or Ganymede.

Original [b]Orbits[/b] has fixed orbital period of main planet 300 days (standard year of canonic Lave). Modified script uses orbital period of main planet calculated on base of sun mass and distance (this part of work is provided by AstroLibrary external function in [b]Sun Gear[/b]). So you’ll have not only unique planet layout for every system, you’ll have unique value of local year.

Like the original [b]Orbits[/b], [b]Planetary Systems[/b] generates more compact systems than our real Solar system. Tionisla for example has almost all planets except Neptune analog, but with following arrangement:

*0.63 OU – Miniterra
*1.00 OU – Main planet
*2.20 OU – Terra
*3.04 OU – Subterra
*3.79 OU – Superterra
*4.77 OU – Gas Giant
*5.94 OU – Gas Giant
*6.67 OU – Dwarf Terra

[b]Planetary Systems[/b] script, inherited from [b]Orbits[/b], limits possible layouts. You’ll never have two planets between sun and main planet as in our Solar system, only one is possible. You’ll never have second planet close enough to habitable zone so you’ll never generate lovely sci-fi setting with two or more habitable planets in system. And you’ll never generate systems expanding beyond 9 OU or so.
[b]Planetary Systems[/b] like original [b]Orbits[/b] is not intended for simulation of elongated elliptical orbits, high inclination orbits, orbital resonances etc. All planets orbited in same plane without any dynamic interaction. Extremely simplified model from school astronomy handbook, of course.
Technically more complex model is possible to realize by code upgrading, but some crucial parts of original code are too hard for me to clearly understand it and to modify without risk of breaking. So I was focused on more evident tasks.

== PlanetEngine ==

Planet mass and chemical composition are two initial parameters, determining planet appearance. For moons and terrestrial planets you have such building materials as water ice (density 0.9), rock (density approx 2.5) and iron-nickel alloy (density approx 8.0). So for planets and moons composed mainly from these materials you’ll have mean density between these extreme values. In inner region of Solar system where solar irradiation is enough to sublimate volatiles you have mostly mix of rock and metal with only few volatiles and mean density of terrestrial planets are between 3.940 for Mars and 5.515 for Earth. In outer region of Solar system beyond frost line all three building materials are present so moons of gas and ice giants composed mainly from mix of water ice, rock and metal and mean density is from 0.98 (Tethys, composed mainly from water ice) to 3.53 (extremely dehydrated due to volcanic activity Io).
There are also more exotic materials such as dry ice (solid carbon dioxide), nitrogen ice, water-ammonia brine, high pressure water ice modifications etc. But as rule of thumb: more distance from sun – less insolation – less equilibrium temperature – less sublimation effects – more volatiles – less mean density.

Situation with planet mass is more complex. Mean density of terrestrial planet depends not only from its bulk composition. More massive planet with same composition will be more dense due to gravitational compression. From a different standpoint, more massive planet in the same region of space can capture more volatiles, thus reducing mean density.
Having sufficient mass planet can effectively capture hydrogen and helium from primordial nebula, so super-earth with critical mass above 10 Earth mass will develop extremely massive atmosphere and will transforms onto ice giant or gas giant. Difference between ice giants like Uranus and Neptune and gas giants as Jupiter and Saturn mainly in inner composition, not in visual appearance. Uranus for example consists mainly from water, ammonia and methane ices (approx 9.3...13.5 Earth masses) and rocky core (0.5...3.7 Earth masses). Hydrogen and helium in Uranus atmosphere are only 0.5...1.5 Earth mass. Jupiter, for contrast, contains relatively small core – 12...45 Earth mass. Most of Jupiter’s 318 Earth mass consists from metallic, liquid and gaseous forms of hydrogen.

This is real astronomy. In Oolite we have no planet masses nor planet density simulated, so PlanetEngine deals with some retro-engineering: taking planet radius and planet density (calculated as function of insolation and radius) it calculates planet mass. There are really three functions for planet density in PlanetEngine: for terrestrial planet, for ice giants and for gas giants (in case of ice and gas planets located deeply outside frost line insolation is not taken into account, just planet radius). Having planet mass and radius, calculations of surface gravity and escape velocity are trivial tasks.
Just one note. PlanetEngine uses planet with 6400 km radius as Earth analog for simplicity, not 6371 km real Earth mean radius (6378 km, mentioned in [b]Sun Gear[/b] topic, is Earth equatorial radius), so calculated surface gravity and escape velocity will be slightly different from real values based on precise calculations using gravitational constant G.

Atmosphere parameters are less formalized data on project. Look on our Solar system. Extremely thin and cold Mars atmosphere (6 mbar pressure on “sea level”) is a present result of dissipation of more dense initial atmosphere. Extremely dense and hot Venus atmosphere (93 bar and 735 K on surface level) is a result of limestone degassing caused by runaway greenhouse effect. Extremely oxygen enriched Earth atmosphere (21% oxygen) is result of activity of life on planet. We have no yet exact knowledge of initial atmosphere parameters for these planets nor accurate general model of atmosphere evolution during 4.6 billions years from formation of Solar System. So this part of PlanetEngine is a bit wild and, honestly, oversimplified speculation based on some assumptions.
PlanetEngine calculates atmosphere mass per unit of surface square based on initial atmosphere pool (more planet mass and less insolation – more fraction of volatiles) and rate of dissipation (again more planet mass and less insolation – more atmosphere remains). Atmosphere pressure is calculated as weight of atmosphere mass per surface unit (you can calculate it having only atmosphere mass per surface unit and surface gravity).
Atmosphere temperature calculation is not so simple. Greenhouse effect is roughly calculated based on atmosphere mass per surface unit. Final temperature on surface level is a sum of equilibrium temperature of planet surface without atmosphere and greenhouse offset. This is oversimplified model, not taking into account planet albedo nor atmosphere composition. But it simulates diversity of conditions, generating planets with extremely rarefied cold atmosphere like Mars, dense cold atmospheres like Titan or superdense extremely hot atmosphere like Venus.

== Planet Data Interface ==

Let’s enough about details of PlanetEngine internal functions. How it will be manifested in game?
If you have [b]PlanetFall [/b]OXP (author Thargoid) or my [b]PlanetLand[/b] (OXP with similar functionality, based on [b]PlanetFall[/b]) installed, after docking with planet/moon surface port you’ll have access to new F4 screen Planet Data interface. It generates pages with slightly different output for planets and moons.

== Planet Data Sheet for planet ports ==

ORBITAL DATA
Orbit radius in OU
Orbit period in days
PHYSICAL DATA
Radius, km
Mean density, g/cm^3
Mass, TU – Terran Units
Escape velocity, km/s
Surface gravity, g
Atmosphere pressure, bar
Surface temperature, K

Output for Moon Data Sheet is almost the same, but orbit radius is displayed in host planet radius units, not in OU.

There are two tricks in case of super-earths, ice giants and gas giants.
Gas giants has no surface in common sense. Gas deeply below cloud layers smoothly reaches state of supercritical fluid. So Planet Data Sheet page takes 1 bar atmosphere pressure level as reference point in case of gas and ice giants.
Non-linear scale is implemented to large planets (super-earths, ice and gas giants). Being only 172,500 m radius in game really, largest gas giant is displayed in Planet Data Sheet page as gas giant of 72,500 km radius instead 17,250 km of default planet scale. Planet mass, escape velocity and surface gravity is displayed scaled too. This non-linear scale is used for display purposes only. Any calculation are based on internal scale. This is forced decision. Honest simulation of planet with 72,500 km radius (slightly more than Jupiter’s 71,500 km equatorial radius) will create too wide zone of mass-lock. Starting from surface port on Cobra Mk III, you’ll need 34.5 min on full throttle to leave mass-lock zone. Honest displaying of real 17,250 km radius of Jupiter analog will lead to too low mass of planet: having density 1.325 like real Jupiter its analog will have only 4.7 mass in Earth units, not real 318!
There is also bias in small planet parameters. Mercury and Pluto analogs in Planetary Systems are larger than prototypes. Initially it was implemented as simple way to avoid confusion between small planets and large moons.

There are two parameters, extremely important for good sci-fi setting and completely missing in PlanetEngine yet.

=== Planet axial rotation period (local day) ===
Typical value of rotation_speed parameter in planetinfo.plist included in game is between 0 and 0.005 radians/s. Having rotation_speed 0.0045 and radius 4116 km (case of vanilla Lave), you’ll have rotation period only 23 min 16 s and linear rotation velocity on equator 18.5 km/s! Such planet in reality will be ripped off by centrifugal forces. Of course, this is setting just for visual appearance. It seems nice idea to give player opportunity to observe almost all planet during short trip from witchpoint to main station. But if you have [b]PlanetFall[/b] and descending to low altitude, the things seems to be wrong – planet rotation looks too fast comparing with ship speed.
Setting rotation_speed to honest value 0.0001 or so (rotation period 17 hours 45 mins) will solve this problem, but at the cost of visual appearance – it is problematic to note subtle changes in planet details visibility during few minuts of flight. I have no idea to solve this conflict.

=== Planet axis tilt ===
This parameter is crucial for climate modeling. But in Oolite planet orientation seems to work unpredictable – despite the same orientation declared for all additional planets in planetinfo.plist some of them are almost upright, some are lying on side. I have no idea how to fix it. Honestly.

Smart selection of planet texture

Initially [b]Planetary System[/b] has predetermined set of textures for every planet class such as Martian texture set for analogs of Mars, Venusian for analogs of Venus and so. Mercury analog orbit always created between sun and orbit of main planet, so it is safe to give Mercury analog texture of heavy cratered dry world such real Mercury or Moon. Terra-like planet in absence of Mercury analog will be be inside main planet orbit and looks like Venus, but if Mercury analog is present, Terra-like planet will be placed outside main planet orbit and looks like snowball Earth. Pluto analog is extreme case: in rare events of absence of other additional planets it occupies place of Mercury and looks like dry hot airless world, not icy cold airless one. These variations were implemented in next iteration of [b]Planetary Systems[/b].
Now textures for terrestrial planets selected using not planet positions per se but surface temperature and atmosphere pressure, calculated by PlanetEngine. So we have more possible variants in planet appearance: it may looks like Mars with polar ice caps or without ones, like cold windy rocky desert or hot sandy desert, like snowball Earth or volcanic world. I hope it will be fun to explore these variations.
There a five variants of every type of texture (60 in sum), selected for every system pseudo-randomly.

== Dependencies ==

This OXP uses AstroLibrary functions in [b]Sun Gear[/b] OXP to calculate properties of system planets and moons. So [b]Sun Gear[/b] OXP is obligatory.
[b]Habitable Main Planets[/b] OXP is highly recommended to provide more reliable data for main planet. This is no way to match calculated atmosphere density and surface temperature for planet of 3000 km radius, for example, with vanilla game classification of such world as agricultural/tropical paradise. :-)

== Known issues ==

*Interaction of '''Planetary Systems''' with planets added by other OXPs can cause inflation of system far beyond planned size. '''Diso.oxp''' with 4 additional planets is a good example of such a system.
*'''Planetary Systems''' is incompatible with '''Additional Planets SR''' due to the same reason.
*Like the original '''Orbits''', '''Planetary Systems''' needs some time to generate a solar system, so problems with the positioning of moons, stations and ships added by third party OXPs or system populators can appear. See more details discussed in my [http://aegidian.org/bb/viewtopic.php?f=4&t=8216 post] from Dec 23, 2018

* A specific case of incompatibility is the '''Market Cooldown''' OXZ (author [[User:Spara|Spara]]). It uses the sum of station distances to the witchpoint and the sun as a unique key for port identification. This method works in static deterministic system, but fails in dynamic systems with a changing psw triangle.
*'''Planetary Systems''' in combination with [[Sun Gear]] generates really vast solar systems. Having a planet with radius 6400 km and the sun at a distance of 695 planet radii, planets on the outer 7.5 OU edge of the system will be at a distance of 333,600,000 m in game units – slightly less than distance between Earth and Moon in reality. This takes 8 hours 16 minutes for a Cobra Mk III to fly on a Torus drive, so you need special instruments for the exploration of such distant planets such as Norby’s [[Torus to Sun]] or my own ''warp drive,'' implemented in [[Hard Way]]. Navigation in such vast systems is almost impossible without the ASC ([[Advanced Space Compass]]) upgrade. These considerations, however, are implemented only for intra-system navigation: the distance between the main planet and the witchpoint remains unaffected, and so therefore so does inter-system navigation.

== OXP structure ==

To provide easy updating all planet textures have been repacked as separate texture packs.

*Planetary Systems.oxp - core package.
*Planetary Systems Texture Pack A.oxp - Ice Deserts
*Planetary Systems Texture Pack B.oxp - Cold Deserts
*Planetary Systems Texture Pack C.oxp - Sand Deserts
*Planetary Systems Texture Pack D.oxp - Volcanic Deserts
*Planetary Systems Texture Pack E.oxp - Cold Mars Analogs
*Planetary Systems Texture Pack F.oxp - Hot Mars Analogs
*Planetary Systems Texture Pack G.oxp - Gas and Ice Giants
*Planetary Systems Texture Pack H.oxp - Miscellaneous (Mercury, Pluto, Venus analogs and super-earths).

The original planet textures were reprocessed. Reprocessing included converting the JPG file format into PNG, rescaling the image size to standard aspect for lat-long maps 2:1 with size 2 * 2^n width and 2^n height, using color saturation and lights/shadows level correction filters.
Texture size 4096x2048 was used as a compromise between file size and visual quality, but due to the shortage of high-res texture files, medium-res 2048x1024 textures were also used to complete the texture sets.

== Credits ==

*Orbits main script - Ebi, Kaks.
*Textures - Celestia Motherlode and freebitmaps.blogspot.com.
*See more detailed texture credits in Texture Pack Readme documents.

@@ Line 9: / Line 9: @@
 *Uploaded 23 November 2020
-This project was started as a tweaked version of [http://aegidian.org/bb/viewtopic.php?f=4&t=8216 Orbits]. Good old Orbits (authors Ebi and Kaks) had textured planets and improved compatibility with large moons. Planetary Systems is a major modification of the original Orbits  - but the original Orbits script, realizing the generation of the solar system and its orbital dynamics, remains as a crucial component of Planetary Systems. So let’s start our presentation from Orbits' script modifications.
+This project was started as a tweaked version of [[Orbits]]. Good old Orbits (authors Ebi and [[User:Kaks‎|Kaks‎]]) had textured planets and improved compatibility with large moons. Planetary Systems is a major modification of the original Orbits  - but the original Orbits script, realizing the generation of the solar system and its orbital dynamics, remains as a crucial component of Planetary Systems. So let’s start our presentation from Orbits' script modifications.
 == System layout and orbital mechanics ==

@@ Line 69: / Line 69: @@
 That’s enough about the details of PlanetEngine's internal functions. How it will it be manifested in game?<br>
 If you have [[PlanetFall]] OXP (author [[User:Thargoid|Thargoid]]) or my '''PlanetLand''' (OXP with similar functionality, based on PlanetFall) installed, after docking with planet/moon surface port you’ll have access to new F4 screen Planet Data interface. It generates pages with slightly different output for planets and moons.
 ==== Planet Data Sheet for planet ports ====
 *ORBITAL DATA

@@ Line 15: / Line 15: @@
 The maximum additional number of planets in a system has been raised from 7 to 8.
-Like the original '''Orbits''', this script generates a planet subset, selecting planets from the planetinfo.plist on pseudo-random basis: but technically there are 10 variants for every planet class in the planetinfo.plist. Mini-terra, for example, are presented with radii of 2750, 2775, 2800, and 2975 km. The script preudo-randomly selects one from ten variants for every planet class in the generated subset. Ten radius variants for every planet class is not just for visual diversity (it is hard to notice visual difference between 3400 and 3600 km radius without a specially planned experiment!). The main reason is provide more diversity for the initial data, used by PlanetEngine (about PlanetEngine a bit later)
+Like the original [[Orbits]], this script generates a planet subset, selecting planets from the planetinfo.plist on pseudo-random basis: but technically there are 10 variants for every planet class in the planetinfo.plist. Mini-terra, for example, are presented with radii of 2750, 2775, 2800, and 2975 km. The script preudo-randomly selects one from ten variants for every planet class in the generated subset. Ten radius variants for every planet class is not just for visual diversity (it is hard to notice visual difference between 3400 and 3600 km radius without a specially planned experiment!). The main reason is provide more diversity for the initial data, used by PlanetEngine (about PlanetEngine a bit later)
 These planets are divided onto classes based on radius:

← Older revision		Revision as of 09:45, 31 January 2021
Line 140:		Line 140:
	*Textures - Celestia Motherlode and freebitmaps.blogspot.com.		*Textures - Celestia Motherlode and freebitmaps.blogspot.com.
	*See more detailed texture credits in Texture Pack Readme documents.		*See more detailed texture credits in Texture Pack Readme documents.
		+
		+	[[Category:Stranger's World]]

@@ Line 123: / Line 123: @@
 * A specific case of incompatibility is the '''Market Cooldown''' OXZ (author [[User:Spara|Spara]]). It uses the sum of station distances to the witchpoint and the sun as a unique key for port identification. This method works in static deterministic system, but fails in dynamic systems with a changing psw triangle.
-*'''Planetary Systems''' in combination with [[Sun Gear]] generates really vast solar systems. Having a planet with radius 6400 km and the sun at a  distance of 695 planet radii, planets on the outer 7.5 OU edge of the system will be at a distance of 333,600,000 m in game units – slightly less than distance between Earth and Moon in reality. This takes 8 hours 16 minutes for a Cobra Mk III to fly on a Torus drive, so you need special instruments for the exploration of such distant planets such as Norby’s [[Torus to Sun]] or my own ''warp drive,'' implemented in [[Hard Way]]. Navigation in such vast systems is almost impossible without the ASC ([[Advanced Space Compass]]) upgrade. These considerations, however, are implemented only for intra-system navigation: the distance between the main planet and the witchpoint remains unaffected, and so therefore so does inter-system navigation.
+*'''Planetary Systems''' in combination with [[Sun Gear]] generates really vast solar systems. Having a planet with radius 6400 km and the sun at a  distance of 695 planet radii, planets on the outer 7.5 OU edge of the system will be at a distance of 333,600,000 m in game units – slightly less than distance between Earth and Moon in reality. This takes 8 hours 16 minutes for a Cobra Mk III to fly on a Torus drive, so you need special instruments for the exploration of such distant planets such as Norby’s [[Torus To Sun]] or my own ''warp drive,'' implemented in [[Hard Way]]. Navigation in such vast systems is almost impossible without the ASC ([[Advanced Space Compass]]) upgrade. These considerations, however, are implemented only for intra-system navigation: the distance between the main planet and the witchpoint remains unaffected, and so therefore so does inter-system navigation.
 == OXP structure ==

@@ Line 15: / Line 15: @@
 The maximum additional number of planets in a system has been raised from 7 to 8.
-Like original [b]Orbits[/b] script generates planet subset, selecting planets from planetinfo.plist on pseudo-random base, but technically there are 10 variants for every planet class in planetinfo.plist. Mini-terra for example presented with radii 2750, 2775, 2800...2975 km. Script preudo-randomly selects one from ten variants for every planet class in generated subset. Ten radius variants for every planet class is not just for visual diversity (it is hard to notice visual difference between 3400 and 3600 km radius without specially planned experiment). Main reason is provide more diversity for initial data, used by PlanetEngine (about PlanetEngine a bit later)
+Like the original '''Orbits''', this script generates a planet subset, selecting planets from the planetinfo.plist on pseudo-random basis: but technically there are 10 variants for every planet class in the planetinfo.plist. Mini-terra, for example, are presented with radii of 2750, 2775, 2800, and 2975 km. The script preudo-randomly selects one from ten variants for every planet class in the generated subset. Ten radius variants for every planet class is not just for visual diversity (it is hard to notice visual difference between 3400 and 3600 km radius without a specially planned experiment!). The main reason is provide more diversity for the initial data, used by PlanetEngine (about PlanetEngine a bit later)
 These planets are divided onto classes based on radius:
@@ Line 27: / Line 27: @@
 *Dwarf terra – Pluto analog
-It seems to be similar to our Solar system layout with exception of super-earth, but really [b]Orbits[/b] generates wide range of possible layouts. You can see systems with only gas giants except main planet or with only terrestrial planets.
+It seems to be similar to our Solar system layout with exception of super-earth, but really '''Orbits''' generates wide range of possible layouts. You can see systems with only gas giants except main planet or with only terrestrial planets.
 Discriminating borderline between large moon and small planet is raised from 1000 to 2500 km (from 10,000 to 25,000 m in game units). So you can simulate large moons such as Titan or Ganymede.
-Original [b]Orbits[/b] has fixed orbital period of main planet 300 days (standard year of canonic Lave). Modified script uses orbital period of main planet calculated on base of sun mass and distance (this part of work is provided by AstroLibrary external function in [b]Sun Gear[/b]). So you’ll have not only unique planet layout for every system, you’ll have unique value of local year.
+Original '''Orbits''' has fixed orbital period of main planet 300 days (standard year of canonic Lave). Modified script uses orbital period of main planet calculated on base of sun mass and distance (this part of work is provided by AstroLibrary external function in [b]Sun Gear[/b]). So you’ll have not only unique planet layout for every system, you’ll have unique value of local year.
-Like the original [b]Orbits[/b], [b]Planetary Systems[/b] generates more compact systems than our real Solar system. Tionisla for example has almost all planets except Neptune analog, but with following arrangement:
+Like the original '''Orbits''', '''Planetary Systems''' generates more compact systems than our real Solar system. [[Tionisla]] for example has almost all our planets except the Neptune analog, but with the following arrangement:
 *0.63 OU – Miniterra
@@ Line 44: / Line 44: @@
 *6.67 OU – Dwarf Terra
-[b]Planetary Systems[/b] script, inherited from [b]Orbits[/b], limits possible layouts. You’ll never have two planets between sun and main planet as in our Solar system, only one is possible. You’ll never have second planet close enough to habitable zone so you’ll never generate lovely sci-fi setting with two or more habitable planets in system. And you’ll never generate systems expanding beyond 9 OU or so.
+The '''Planetary Systems''' script, inherited from '''Orbits''', limits possible layouts. You’ll never have two planets between sun and main planet as in our Solar system, only one is possible. You’ll never have second planet close enough to the habitable zone so you’ll never generate a lovely sci-fi setting with two or more habitable planets in the system. And you’ll never generate systems expanding beyond 9 OU or so.
-[b]Planetary Systems[/b] like original [b]Orbits[/b] is not intended for simulation of elongated elliptical orbits, high inclination orbits, orbital resonances etc. All planets orbited in same plane without any dynamic interaction. Extremely simplified model from school astronomy handbook, of course.
+'''Planetary Systems''' like the original '''Orbits''' is not intended for simulation of elongated elliptical orbits, high inclination orbits, orbital resonances ''etc''. All planets orbit in the same plane without any dynamic interaction. An extremely simplified model like that of a school astronomy handbook, of course.
-Technically more complex model is possible to realize by code upgrading, but some crucial parts of original code are too hard for me to clearly understand it and to modify without risk of breaking. So I was focused on more evident tasks.
+It is possible to realize a technically more complex model by upgrading the code, but some crucial parts of the original code are too hard for me to clearly understand and to modify without risk of breaking it. So I focused on more obvious tasks.
 == PlanetEngine ==