Spica SSC - help, and some feature requests
Posted: 26.09.2004, 18:34
I'm trying to make an SSC of the Spica system (see the Spica thread in Physics & Astronomy)... what's the orbital period of the B5 V companion at 4 AU and the B7 V companion at 40 AU? I'm guessing their radii are a little smaller than the innermost B4 V companion?
I guess I'll make it so that they orbit the B1 V itself, I suppose I can't set it so that everything orbits a common barycentre because the B1 V is fixed?
Here's what I got so far...
And can someone remind me if there's a way to stick a lens flare on a planet? (or in this case, a star that's pretending to be a planet
).
One thing that drove me nuts when I was making this SSC was that the orbital periods and orbital distances for each body were in different units. Can we just have a standardised system instead? Is there any way to specifically classify objects in SSCs as "stars" or "planets", and from that determine what sort of units to use (e.g. AU and years for the orbital distance and period of all objects orbiting things that are classed as "stars" in the SSC, and km and days for the orbital distance and period of all objects orbiting things that are classed as "planets"?). That'd save having to get horribly confused by switching between different units when making systems like this, with stars orbiting other stars, and planets orbiting those stars, and moons orbiting those planets.
Again, I found it rather annoying that Spica A was the light source for this system, despite the fact that the planet orbited the K5 V companion star (and was tidelocked to it). The view below from the surface of the planet near the twilight zone on the day side illustrated this - it thinks it's sunset because Spica A is low on the horizone, while Spica E (its actual primary) is fairly high up in the sky.
I know Celestia can't handle multiple light sources, but what could be rather awesome would be the ability to specify in the SSC which star out of many nearby (such as in this case) to use as the light source. So for Spicaworld I could say that the light source is Spica E , and override the default. Would something like that be even remotely possible?
I guess I'll make it so that they orbit the B1 V itself, I suppose I can't set it so that everything orbits a common barycentre because the B1 V is fixed?
Here's what I got so far...
Code: Select all
"SpicaB" "Spica"
{
Texture "bstar.jpg" # B4 V
Radius 2785060 #
Emissive true
EllipticalOrbit {
Period 0.01099 # 4.0145 days
SemiMajorAxis 0.12
Eccentricity 0.0
ArgOfPericenter 0
MeanAnomaly 0
}
RotationPeriod 3
}
"SpicaC" "Spica"
{
Texture "bstar.jpg" # B5 V
Radius 2600000 # ????
Emissive true
EllipticalOrbit {
Period 1 # ????
SemiMajorAxis 4.0
Eccentricity 0.0
ArgOfPericenter 0
MeanAnomaly 0
}
RotationPeriod 3
}
"SpicaD" "Spica"
{
Texture "bstar.jpg" # B7 V
Radius 2200000 # ????
Emissive true
EllipticalOrbit {
Period 50 # ????
SemiMajorAxis 40.0
Eccentricity 0.0
ArgOfPericenter 0
MeanAnomaly 0
}
RotationPeriod 3
}
"SpicaE" "Spica"
{
Texture "gstar.jpg" # K5 V
Radius 417759 # ????
Emissive true
EllipticalOrbit {
Period 1000000 # ????
SemiMajorAxis 10000.0
Eccentricity 0.0
ArgOfPericenter 0
MeanAnomaly 0
}
RotationPeriod 30
}
"Spicaworld" "Spica/SpicaE"
{
Texture "mars.*"
Radius 6000
Atmosphere {
Height 60
Lower [ 0.43 0.52 0.65 ]
Upper [ 0.26 0.47 0.84 ]
Sky [ 0.40 0.6 1.0 ]
Sunset [ 1.0 0.6 0.2 ]
# Sunset [ 0.3 1.0 0.5 ]
CloudHeight 7
CloudSpeed 65
CloudMap "earth-clouds.*"
}
EllipticalOrbit {
Period 82.98
SemiMajorAxis 60000000
Eccentricity 0.00
Inclination 0.00
AscendingNode 0.0
LongOfPericenter 0.0
MeanAnomaly 0.0
}
Albedo 0.30
RotationPeriod 1991.474348
}
And can someone remind me if there's a way to stick a lens flare on a planet? (or in this case, a star that's pretending to be a planet
).
One thing that drove me nuts when I was making this SSC was that the orbital periods and orbital distances for each body were in different units. Can we just have a standardised system instead? Is there any way to specifically classify objects in SSCs as "stars" or "planets", and from that determine what sort of units to use (e.g. AU and years for the orbital distance and period of all objects orbiting things that are classed as "stars" in the SSC, and km and days for the orbital distance and period of all objects orbiting things that are classed as "planets"?). That'd save having to get horribly confused by switching between different units when making systems like this, with stars orbiting other stars, and planets orbiting those stars, and moons orbiting those planets.
Again, I found it rather annoying that Spica A was the light source for this system, despite the fact that the planet orbited the K5 V companion star (and was tidelocked to it). The view below from the surface of the planet near the twilight zone on the day side illustrated this - it thinks it's sunset because Spica A is low on the horizone, while Spica E (its actual primary) is fairly high up in the sky.
I know Celestia can't handle multiple light sources, but what could be rather awesome would be the ability to specify in the SSC which star out of many nearby (such as in this case) to use as the light source. So for Spicaworld I could say that the light source is Spica E , and override the default. Would something like that be even remotely possible?
