Re: [Flightgear-devel] New Bugs at SourceForge

[David M. <da...@me...>]

Curtis L. Olson writes:

 > Take a look at the comments.  I think having flightgear sync it's time
 > to real time is a 'feature'.  Having real time stop when paused would
 > disrupt this syncronization.  Thus, I'd prefer that the current
 > behavior remain the default.

I disagree; I think that there are only two combinations that make
sense:

1. FlightGear remains sync'd to real-world time, and the FDM cannot be
   paused.

2. FlightGear is set to any arbitrary time (possibly real-world time
   initially), and when the FDM is paused, the clock stops as well.

I don't think there is any value in staying synced with real-world
time when the FDM is not progressing; what research or entertainment
value comes from leaving the plane suspended in the air while the
clock keeps going?  Note that when you save and restore a flight, it's
the original time that's restored, not the current one.

Even if someone can think up a use case for running the clock when the
FDM is stopped, I doubt it will apply to most users, so it should not
be the default -- if I'm halfway through a cross-country flight and
the phone rings, I want to hit 'pause' and have *everything* stop;
otherwise, the times in my whole flight plan will be off.


All the best,


David

-- 
David Megginson
da...@me...