Celestia Forums

I'm upgrading my Celestia installation from 1.51 (and in-between-builds) to the official 1.60 build.

I have a problemn dat Celestia refuses to show a planet's orbit if it has a spice orbit.
I've just started with Mercury, the ssc is as follows:



Am I overlooking something?

Anyone?

--- edit ---

CAP-Team wrote:Anyone?

The problem might be with the BoundingRadius of 1e10 kilometers. BoundingRadius is a hint that tells Celestia roughly how big an orbit is. Celestia uses this information to speed up drawing: if the a sphere containing an object's orbit is completely out of view, Celestia knows that the object is out of view without having to compute it's position. The bounding sphere radius is also used when drawing an orbit, when Celestia needs a rough estimate of the size of the orbit.

The bounding sphere radius must be at least large enough to contain the orbit. If it's too small, the object might not be drawn at some points when it should in fact be visible. A little larger doesn't hurt too much, though it makes Celestia slightly less efficient. Too large, though, and you may see problems with orbit rendering. 1e10 kilometers is an enormous overestimate of Mercury's orbit. Try 1e8 instead--still too large, but the right order of magnitude.

Celestia automatically computes bounding spheres for other orbit types. But, for SPICE orbits and ScriptedOrbits, it isn't possible to reliably compute the bounding radius without computing positions at every time at which the orbit is valid (you don't want to wait that long... ). For planets and moons, you can get a reasonable bounding radius by taking the semimajor axis of the mean orbital elements and increasing it by 10%.

--Chris

I tried decreasing the BoundingRadius for Mercury to 1e8, but with no success.
Funny thing is, that moon orbits (also with spice kernels) are drawn correctly.

Chris, do you or Volcanopele use spice kernels for planets? I tried several pre-1.6.0 builds and even the newer post-1.6.0 builds but no orbits for planets, even when correcting the bounding radius values.

So is it an error in my .scc file or is it a bug in Celestia?

--- edit ---

John, any luck with testing?

--- edit ---

--- edit ---

That's great. I put the planet textures in the default location and that works fine.

Could you post a .scc for a planet in your configuration?

--- edit ---

I tried a CLEAN official 1.6.0 release with the SolarSystemSPICE addon, with just Saturn for testing.
All planets show orbits, except Saturn.

Strange.. or a bug after all?

--- edit ---

Maybe it's a Windows-only bug ?

Sorry for kicking this old thread of mine, but I was cleaning my installations (I had several for testing purposes ).
I really think it's strange that planet orbits are not drawn when using spice kernels.
My whole solar system is based on spice kernels.

Today I found out that the orbit of dwarf planet Ceres is drawn when using spice kernels. The only difference between this .ssc and the .ssc of a planet is that Ceres doesn't use a reference point.

Venus:


Ceres:


I suspect that this reference point is preventing the orbit being drawn. Is the way I use Venus' .ssc the correct way? I actually suspect that Venus' orbit is drawn, but it is drawn around the barycenter, which lies inside Venus.
Plutos orbit around its barycenter is drawn when I toggle dwarfplanet orbits.

--- edit ---

I used one of the spice tools to extract venus' data into a separate kernel.
I may have merged it together with some other kernels to extend the time the kernel spans.

I did this about two years ago, so I don't remember the exact details, but I'm sure de421 (or some previous version) was the basis for it.

I did the same with all the other planets.

Well I finally fixed this. Sort of.
By adding two lines to the reference point of the .ssc orbits are now shown:

[code]
Visible true
Clickable false
[code]

Orbits only have the name of the bary center, not the name of the planet.