ehofman [Sun, 8 Nov 2009 13:41:03 +0000 (13:41 +0000)]
John Denker:
Together with previous patch, make view reference frame, view offset,
and current view visible in property tree.
Also some comments about the concepts behind these variables.
torsten [Sun, 25 Oct 2009 14:45:23 +0000 (14:45 +0000)]
Ron Jensen:
This little patch makes the KT-70 read 888-8888 when in self-test mode.
This is the correct behavior, the current behavior, where it reads the
flight level and squawk code in self-test is incorrect.
ehofman [Thu, 5 Nov 2009 09:18:27 +0000 (09:18 +0000)]
John Denker:
Add a view debugging functions and represent the viewer quats in the property tree for debugging.
Do a nontrivial calculation, demonstrating how to find the 12:00 orientation given the view and the view offset. it, and observe that the 12:00 direction does not change when you change the view offset, which is a nontrivial result.
Erik: This already proved to be useful since I now obserbed that the sky and fog coloring code depends on view offset rather that the view orientations. This is why those effects are out of line in some views.
Tim Moore [Sat, 31 Oct 2009 23:15:14 +0000 (00:15 +0100)]
Add support for high speed trains. Change update rate to main frame rate, and move framerate-heavy functions to a 20Hz update cycle. Jitter is much reduced, at a small cost to framerate
Signed-off-by: v meazza <vivian.meazza@lineone.net>
Conflicts:
ehofman [Sat, 24 Oct 2009 08:31:37 +0000 (08:31 +0000)]
Don't make the SoundManager a memebr of the subsystem manager; It needs to be initialized very early and destroyed as late as possible. That doesn't work as a subsystem meber onless some sort of priority scheme gets implemented. Get rid of auto_ptr which doesn work for the samples either.
torsten [Wed, 21 Oct 2009 20:20:03 +0000 (20:20 +0000)]
This is one leftover from Tat's patch from 2009-09-16:
I believe these patches are really important for Mac users since they don't have to wait for my updating xcode project files.
these also saves up to 50% of build time since most of users don't have to make universal binaries.
daveluff [Sat, 17 Oct 2009 13:04:21 +0000 (13:04 +0000)]
My non-precision approach model had been one or more IAFs and then a common core approach from the IF. In fact, there can be one or more initial approach routes from the IAFs to the IF, then the core approach. Replace the IAFs with initial approach routes. NOTE it is assumed in the code that there is a unique IAF per initial approach route.
daveluff [Sat, 17 Oct 2009 11:48:17 +0000 (11:48 +0000)]
Change one of the default flight plans to something more convenient for development. These will eventually all be removed from the code and read from preferences anyway.
jmt [Thu, 15 Oct 2009 21:30:10 +0000 (21:30 +0000)]
Further GPS and route manager behavioural fixes
* When the nav-radio is slaved, calculated radial/target-hdg-deg
(needed by some autopilot logic)
* Handle editing (including deletion) of route waypoints correctly,
including deleting the active waypoint
* Add a signal to the route manager when the last wpt is reached, and
use it in the GPS to revert to OBS mode.
* Change the altitude handling to use the specified cruise altitude
* Fix a bug where autopilot/locks/altitude was treated as a boolean
jmt [Wed, 14 Oct 2009 06:50:06 +0000 (06:50 +0000)]
Route-manager: remove any interaction with the autopilot, or internal sequencing; assume the GPS always handles this (it should, now). Also fix waypoint altitude handling, which was broken. If not altitude is supplied for a waypoint, default to the requested cruise altitude.