Celestia Forums

I don't remember if this has already been discussed, so in this case I beg your pardon (I found something related to this in the post (2003)
http://www.shatters.net/forum/viewtopic.php?t=3800&highlight=seturl+command
but it doesn't solve my problems.
I would like to know what are the single parameters that we find in a seturl cel script command.
Let me make an example: the following one shows the Earth rising from the Moon lighted limb, while staying in orbit around the Moon (as Apollo astronauts have seen during Apollo flights):

cel://Follow/Earth/2519-09-08T11:21:52.50832?x=7tpJtizMpH/MDA&y=nkojQA6QWAE&z=bpR32NLxP+IF&ow=0.318819&ox=-0.490562&oy=0.787903&oz=0.192125&select=Earth&fov=5.981928&ts=-100.000000&ltd=0&rf=6931&lm=49152

Obviously I can see there the date/time settings
19-09-08T11:21:52. and that we are following Earth

Follow/Earth/25 (yes, but what are the last two digits=25?)
I can see the FOV, but all the other numbers/letters?

My question is due to the info given by Chris Laurel in his Cel_Script_Guide_v1-0g.doc, regarding the seturl command:

"When you use the seturl command, all of the saved settings stored in the Cell://URL are transferred to the user's currently running copy of Celestia."
I would like the contrary.
If I insert in a script a celurl taken fron somewhere else, so not created in my script, I would like to "smooth" the celurl settings as possible, according to the ones already given in my script.
Just to make an example: if in my script I have
setvisibilitylimit { magnitude 6.8 }
and the celurl gives too many and bright stars on the screen, I need to change the url magnitude settings to reduce them as given in my script setvisibilitylimit command.
And obviously the same thing for any other parameter available in celurl.
Is it possible to have the celurls decoding?
Thanks a lot.
Bye

Andrea

ANDREA wrote:Obviously I can see there the date/time settings
19-09-08T11:21:52. and that we are following Earth

Follow/Earth/25 (yes, but what are the last two digits=25?)
I can see the FOV, but all the other numbers/letters?

The url format is:
cel://<Mode>/<Primary body>[/<Secondary body>]/<Date>?<variables>

The date follows the ISO 8601 standard : 2519-09-08T11:21:52.

The variables are:
- x, y, z: Absolute (universal) coordinates in 64bit precision encoded in base 64.
- ow, ox, oy, oz: orientation quaternion
- select: selected body
- fov: field of view
- ts: time scale
- ltd: Light Time Delay (boolean)
- rf: render flag
- lm: label mode

As you can see, the url doesn't alter the visibility limit. It may, however enable or disable the automag feature (part of the render flag). And by altering the FOV it may also change the rendering of stars.

You may safely remove variables from the url, the user's current settings will be preserved.

Christophe wrote: The url format is:
cel://<Mode>/<Primary body>[/<Secondary body>]/<Date>?<variables>.......
As you can see, the url doesn't alter the visibility limit. It may, however enable or disable the automag feature (part of the render flag). And by altering the FOV it may also change the rendering of stars.
You may safely remove variables from the url, the user's current settings will be preserved.

Wow Christophe, a very quick and exhaustive reply!
Thanks a lot, you solved my problem.
Bye

Andrea

Christophe, in my example I have

rf=6931&lm=49152
- rf: render flag
- lm: label mode

Can you please explain the relationship among these numbers and the
render flag and label mode settings? ?
Thanks a lot.
Bye

Andrea

Cf render.h for the list of label and render flags.

6931=b 1 1011 0001 0011=
ShowStars | ShowPlanets | ShowCloudMaps | ShowAtmospheres | ShowSmoothLines | ShowStarsAsPoints | ShowRingShadows

49152=b 1100 0000 0000 0000=
OpenClusterLabels | I18nConstellationLabels

Christophe wrote:Cf render.h for the list of label and render flags.....

Thanks a lot once again, Christophe.
Bye

Andrea

?©h cel:url

symaski62 wrote:

Code: Select all

   22 Barycenter "Solar System Barycenter:SSB"
   23 {
   24    RA 0
   25    Dec 0
   26    Distance 0
   27 }
   28
   29 0 "Sol:Sun"
   30 {
   31    OrbitBarycenter "Solar System Barycenter"
   32    CustomOrbit "vsop87-sun"
   33
   34    SpectralType "G2V"
   35    AbsMag 4.83
   36
   37    RotationPeriod      609.12  # 25.38 days
   38    Obliquity             7.25  # correct orientation relative to ecliptic
   39    EquatorAscendingNode 75.77  #
   40    RotationOffset       23.00  # standard meridian
   41 }


?©h cel:url

Symaski62, nice, but did you mistake the topic?
Or, as usual, you express something in a way that none except you can understand?
Just once, please, show me (us!) that you are able to write a full text line, and in a way that be intelligible for normal people like me (and probably many other, IMHO).
Thank you.

Andrea

Hi everybody,

the universal coordinates x, y, z seem to have different origins in Celestia 1.4 and 1.5. E.g. a cel:// like this

cel://SyncOrbit/Sol:Earth/1880-01-01T02 ... f=919&lm=0

which should take me near earth works fine in 1.4 while in 1.5.0pre4 it beams me to a position some 206.28 au from earth.

Has anybody a tip how to convert these old coordinates into new values i.e. constants to translate the origins?

BTW: how can I easily convert base64 encoding into something human readable?

Thanks for now
Kai.

Corben Dallas wrote:the universal coordinates x, y, z seem to have different origins in Celestia 1.4 and 1.5.

Yes. -> See http://shatters.net/forum/viewtopic.php?t=11852

Adirondack

Thanks, Adirondack.

Bye, Kai.

Well, given the known incompatibility between Celestia 1.4 and Celestia 1.5 celurls, is there any possibility to convert automatically the old celurls to the new configuration, with no more the Sun as reference, but its orbit barycenter?
I'm absolutely ignorant on the matter, so beg your pardon if I'm saying nonsenses , but I think that avoiding to prepare once again all those old celurls could be a very interesting target, IMHO.
Is it possible?
Thanks a lot

Andrea