Blueriver wrote:Hello,
thank you cartrite for your answer but i think that a separate spice .bsp-file only don`t work. It works only together with an .lbl-file connected with the .bsp content.
The simple SPICE kernels that i generated when Chris first added SPICE support to Celestia need only BSP files. No separate LBL files are needed. You can verify this by changing the extension from .LBL to .NOTLBL. The SPICE kernels will still work.
I verified this just now with the SPICE trajectories that I use for testing.
http://www.lepp.cornell.edu/~seb/celest ... 0-test.zip(1.1MB)
This Addon uses trajectories for Cassini, Earth, Saturn and several of Saturn's moons which all are defined in a single SPICE kernel BSP file.
LBL files are plain text files. LBL files are generated from BSP files using a utility program. The program dumps some of the information records that are inside the BSP files into LBL text files so a human being can read them.
In the meantime where i tried out the little script i don`t know how Celestia puts together different xyz-data and spice-.bsp data and some model data?€¦
I`m confused?€¦
xyz data files and SPICE bsp data files are two entirely different methods of defining trajectories.
If you want to include an object which uses an xyz trajectory, you should not define an SSC object which has the same object name and which uses a Spice kernel.
If you use the same name for both xyz and Spice objects, you will cause much confusion. Celestia won't stop you from doing it, but it won't know which object you mean when you try to select it.
This is why I always use the prefix SPICE_ in the names of the objects that have SPICE trajectories.
If you really want to create an object which has the same name as one that Celestia already defines, then you must edit Celestia's SSC file and delete the object that already uses that name.
(I suspect this is what the people at NASA and ESA do.)
But maybe I've misunderstood what you wrote.
If by "model data" you mean the 3D model file which provides the image of the object., this 3D model is specified in the Mesh statement.
You can use the same 3D Mesh for any number of SSC objects that you want. The name of the Mesh file and the name of the SSC object it is used for have nothing whatsoever to do with one another.
Here is an example of an SSC catalog which uses the same model for three different objects. One happens to use an xyz trajectory. The other uses a Spice trajectory. This is just a simplified example. I'm not including all of the details needed to make it work.
Code: Select all
"MyProbe" "Sun" {
Mesh "galileo.3ds" Radius 0.1
EllipticalOrbit { ... }
}
"MyProbeXYZ" "Sun" {
Mesh "galileo.3ds" Radius 0.1
SampledOrbit "myprobe.xyz"
}
"MySpiceProbe" "Sun" {
Mesh "galileo.3ds" Radius 0.1
SpiceOrbit { ... Kernel "myprobe.bsp" ...}
}
You can even make a planet look like a spacecraft:
Code: Select all
Modify "Mars" "Sol" {Mesh "galileo.3ds"}
(This ssc file is not simplified. It will work as it is to change the appearance of Mars.)
Btw. i can see galileo.3ds and huyens.3ds in the Model-folder .but i can`t see a spaceprobe on the screen -the probe is not shown. I don`t know why it is so?
You have to set Celestia's date to a date when those spaceprobes were in orbit. In other words, you have to set Celestia's date to a date that is after the Beginning date and before the Ending date in the SSC files for those objects. If Celestia's date is set to today's date, you cannot see them. Those spaceprobes are no longer in orbit. Galileo crashed into Jupiter and Huygens landed on Titan. Today's date is after the Ending dates for those objects.
When I go to Mars i can see the the MRO-probe orbit but I can`t see the MarsExpress or the MarsSurveyor orbit?€¦
Which version of Celestia are you running?
Which orbit do you mean?
Do you mean the ShroxMars orbits included in Celestia's CVS archive?
Or do you mean SPICE orbits that you created?
Or did you use SpiceOrbits that someone else created? If so, where did you get them?
I'm sorry, but I really don't feel like guessing. There are too many different mistakes that would cause objects and orbit paths not to be drawn.
Maybe that there are some further improvements in the final 1.5 or a kind of celestia-spice-manual showing perhaps a example how the Cassini model included in the 1.5 install is working together with a current Cassini-spice data file from NAIF.
The only planned improvements that I remember Chris mentioning will be to support the orientation information which is included in some Spice kernels. My understanding is that this improvement won't happen until after Celestia v1.5.0 final is released.
The test Addon I list above (spice-cassini-150-test.zip) can be used with Celestia's model of Cassini if you want. You have to change the definition of Spice_Cassini. Add a Mesh entry and change its Radius entriy.
e.g.
Code: Select all
"Spice_Cassini" "Sol/Spice_SSB/Spice_Saturn_bary"
{
Class "spacecraft"
Mesh "cassini.3ds"
Radius 0.011
OrbitFrame { EclipticJ2000 { Center "Sol/Spice_SSB/Spice_Saturn_bary"}}
Beginning "2005 07 06 00:00"
Ending "2005 07 22 00:00"
SpiceOrbit
{
Kernel "050825R_SCPSE_05186_05205.bsp"
Target "-82"
Origin "6"
Beginning "2005 07 06 00:00"
Ending "2005 07 22 00:00"
BoundingRadius 1e10
}
}