Known Issues:

If you encounter any planets or moons with ugly blue textures, this is caused by what appears to be a texture bug.  In short, when you specify certain textures (mercury, tethys, possibly a few others) with a .* extension rather than the actual file extension of the image, Celestia appears to treat them as Bump or Normal maps instead, and gives the planet a blue color for some reason.  To fix this, change the .* to whatever the actual extension is in your SSC file (probably .jpg).  The spreadsheet does not do this automatically.

Laguna:
Laguna V and VI are supposed to be a double planet system.  This is interpreted as two planets with the same semimajor axis, but different eccentricities and a MeanAnomaly to place one ahead of the other.  There are other ways of doing this.  I could make an invisible planet and set both of the visible pair up as moons (con: extra orbital data and a special texture, increases file size), or set one planet as a moon of the other (con: this messes up the ability to use number keys to select the planets in order, and hides one planet in the Solar System Browser).  Celestia 1.5.0 has the ability to set up a reference point and make both planets orbit that (con: it doesn't work with 1.4.1, and 1.5.0 isn't officially out yet).  I'll probably set up the latter as a 1.5-only file later, and eventually make this the permanent solution (once 1.5 comes out)


Alpha:
Under 1.5.0, some of the planets exhibit shader errors (bright red border around the body where the atmosphere would be drawn).  This is probably a Celestia bug, and binary star systems tend to make it worse (especially certain planets closest to the other star).


Alshain:
See the note under Alpha concerning shader errors.

For planets V and VI, see the note under Laguna for double-planet systems.  In this case, the planets are supposed to be in irregular orbits that makes them a near double.  I'm too lazy to define a SampledOrbit or some such.
