Celestia Forums

Do you really want to replace the Solar System?
Or would a separate stellar system do as well?
I suspect a separate system would be more appropriate. Otherwise you'll have to prevent Celestia from using its own solarsys.ssc (e.g. rename it to be solarsys.sscNO).

At any rate, you can replace the Sun by providing an STC file that defines a Star with HIP number 0, just as is done in Celestia's own nearstars.dat

Radius and Texture declarations have been valid in STC files starting with Celestia v1.4.0. For a description of these and other newer STC parameters, see http://www.lepp.cornell.edu/~seb/celest ... eters.html

How about resetting the color in your posts to something that is readable!?

Bye Fridger

t00fri wrote:How about resetting the color in your posts to something that is readable!?

Just dropped in after almost a year: Still the same problems as ever...

I made a file called newstar.stc and put this in it:


star 0 "esun"
{ RA 0
Dec 0
Distance 0.003
Radius 6378
Texture "earth.png"
}

Nothing happened. What am I doing wrong?

BTW Selden, is the cyan color on my posts hard to read to you?

You didn't specify a SpectralType and a magnitude (either AbsMag or AppMag)

[edit]

Yes, cyan is hard to read: I use the subSilver board style, which has a light-blue background. Using the mouse to highlight the text makes it readable, though.

Celestia has two board-style options: subSilver or Solaris. Although it looks attractive at first, the Solaris color scheme is much more tiring than subSilver for long term use.

If you don't specify a color for the text, then the board style code picks the color most appropriate for maximum contrast no matter which board style is being used.

Do i need to tell Celestia that i have a new file called newstar.stc or will it just pick it up during the load at startup?

I did add those other parameters and nothing happened, but here is the current file:


star 0 "esun"
{ RA 0
Dec 0
Distance 0.003
SpectralType "G2V"
AbsMag 4.83
Radius 6378
Texture "earth.png"
}


also, i made sure there is a blank line at the end.

Star needs to be capitalized and the STC file needs to be in /extras/ -- it works on my system.

Fantastic!! It worked. Now how do I get rid of that "corona" effect on the new earth/sun object? Change the SpectralType parameter?

I just took the flare.jpg file and made it all black and it took the starburst effect away but now there is still a corona.

The corona effect is because it's defined as a Star.

A workaround may be to define a very tiny, dim Star and define your central Earth as a planet orbiting the Star, with a Radius much larger than the Star, and with a very tiny SemiMajorAxis (e.g. 1e-32). The star will still 'glow' but the effect will be buried inside the planet.

Selden, I really want to thank you for taking the time to help me. I think I've got it figured out now.

If you would be interested, I would like to show you last summer's project I made. It is a 53MB animation (2 minute AVI) that shows seasonal polar ice migration along with the specular reflection from many different situations. The only thing is....I used the INTEL INDEO codec to capture the video and you'll need it to view the file. I went to get the codec and they want 15 bucks for it now! SHEESH!

Anyway, I think you'll be impressed as to what we got Celestia to do.

Let me know if your interested,
Thanks again,
Charles

Is there a limit to the size, number of lines of data, or number of years that a SampledOrbit (.xyz) file can have?

We have a 10,000 year integration we're trying to get Celestia to read.

I don't think there's any limit other than the total amount of memory on your system. xyz trajectories currently are stored internally as single precision (32bit) values, although Chris is planning to make double precision (64bit) values an option in a future version of Celestia. The values in the trajectory file can be double precision although that precision isn't used yet.