Unexpected behaviour of Track Selection

Report bugs, bug fixes and workarounds here.
Topic author
DT
Posts: 49
Joined: 27.08.2007
With us: 17 years 2 months
Location: In Orbit...

Unexpected behaviour of Track Selection

Post #1by DT » 30.08.2007, 12:43

If you track a selected object and then try to accelerate in the hope of reaching that object, you actually move away from the object. Go fast enough and you will leave the solar system in reverse.

Why?
A whack in the face with a fish can solve a whole manner of problems.

Avatar
LordFerret M
Posts: 737
Joined: 24.08.2006
Age: 68
With us: 18 years 3 months
Location: NJ USA

Post #2by LordFerret » 30.08.2007, 20:04

I've never noticed that before, but yes it does on mine too (v1.4.1).

Avatar
Fenerit M
Posts: 1880
Joined: 26.03.2007
Age: 17
With us: 17 years 7 months
Location: Thyrrenian sea

Post #3by Fenerit » 31.08.2007, 00:48

Yeah, Celestia 1.4.1counteract. It'gravity is repulsive. Being massive than other mass.
Never at rest.
Massimo

Topic author
DT
Posts: 49
Joined: 27.08.2007
With us: 17 years 2 months
Location: In Orbit...

Post #4by DT » 01.09.2007, 18:15

I've never noticed that before, but yes it does on mine too (v1.4.1).


The same issue exists in the current cvs release of 1.5.0. The base code has not changed.

The code needs to be modified so that you will approach an object you are tracking, deaccelerate and halt. Or perhaps, even sync orbit.

Anyone have a preference?
A whack in the face with a fish can solve a whole manner of problems.

Avatar
selden
Developer
Posts: 10192
Joined: 04.09.2002
With us: 22 years 2 months
Location: NY, USA

Post #5by selden » 01.09.2007, 20:02

The velocity vector controlled by the Spaceflight keyboard comands should not be changed when Celestia's viewpoint changes. It should be changed only by the Spaceflight keyboard commands.

Tracking an object should only keep that object in the center of the field of view. It should not change the direction of travel of the viewpoint.

Typing one of the Spaceflight Function keys should set the specified speed in the current direction of travel. (if 0, then travel in the direction of the viewpoint.) Perhaps typing Capital-A should add to the speed in direction of the center of the field of view, modifying the current viewpoint velocity vector, not replacing it unless the user types a Capital-X.
Selden


Return to “Bugs”