131p9, Windows, .cel, goto, upframe

Report bugs, bug fixes and workarounds here.
Topic author
don
Posts: 1709
Joined: 12.07.2003
With us: 21 years 7 months
Location: Colorado, USA (7000 ft)

131p9, Windows, .cel, goto, upframe

Post #1by don » 10.08.2003, 07:31

Not sure if this is a bug, or as-designed ...

Is the upframe parameter in the goto command in .cel scripting supposed to set the specified Coordinate System or merely use it for the goto?

For example:
* Select Earth (Interactively)
* Goto Earth (Interactively)
* Set Follow, Track or whatever (Interactively)
* Manually rotate the Earth in 2 directions
* Run the following script:

Code: Select all

{
select { object "Earth" }
goto   { time 3
         distance 10.0
         upframe  "chase" }
wait   { duration 3 }
}


The script produces the following:
* The Earth is rotated in some direction
* The mode(s) you set interactively are not cleared
* The upframe value (chase) is not set as the active CoordSys

Is this what goto/upframe is supposed to be doing? Or should the new Coordinate System be Chase?
-Don G.
My Celestia Scripting Resources page

Avatar: Total Lunar Eclipse from our back yard, Oct 2004. Panasonic FZ1 digital camera (no telescope), 36X digital zoom, 8 second exposure at f6.5.

Topic author
don
Posts: 1709
Joined: 12.07.2003
With us: 21 years 7 months
Location: Colorado, USA (7000 ft)

Post #2by don » 13.08.2003, 08:18

Any idea Chris?

-Don G.


Return to “Bugs”