Re: [nbos] [AS] Binary Star SystemsNadinB-at-aol.comFri Dec 8th, 2006
In a message dated 12/8/2006 6:20:50 A.M. Pacific Standard Time,
>At 10:04 AM 12/7/2006, you wrote:
>>Ideally I'd like to be able to use the system display to see the two stars
>>orbiting each other and the planets each star individually and the
>>gravitational center to get a grand overview of the system.
>Thats something I'd like to do, but havent gotten a grip on the physics of
>it yet. A binary star system isnt a problem to model... but throw in a
>third star and all bets are off :-)
Well see, that's why I'm a project manager and not a developer. I like to
dream up the system specifications and leave the hard stuff to someone else.
Seriously, though, even adding in close binary support would be a huge
advancement. Even though it may not be able to handle trinaries and beyond,
would still be very useful. As far as I know there aren't that many close
trinaries. If you have a system that has 5 stars like I'm dealing with in Xi
Scorpii there are usually two or more pairs and the remaining stars are very
distant and don't need to be included in the system display.
And, if you have a close trinary there usually isn't any stable orbit left
habitable planet so those systems aren't as interesting. To me anyway.
At the same time, being able to define a distance from star to star in a
dispersed system, where the distance from AB to C is 210 AU, and use that
distance in the existing travel calculators would also be very nice.
>>Also, I'd like to see AU used as the display orbital distance for top
>>children at least. Or is there anyway that I can change it in the display
>I _was_ working on AU being an option in the system data fields setup as
>part of the next minor update, but for some reason ended up not adding
>in. The specific reason escapes me right now. But it is on my to-do list
>as quite a few people have asked for that.
I look forward to it. For me getting my head around 2.0 AU is easier than
trying to contemplate 3 billion Km or whatever it converts to.
Just remember, just because of the idiosyncrasies of the KF drive, finding a
null G spot will be fun on this multiple system, especially if you are
looking at a pirate point, technically a more or less stable lagrange point
Of course you could use another FTL tech that does not care for matters such
Nbossoftware mailing list