Hooray wrote in Wed Sep 19, 2012 1:56 pm:zakalawe wrote in Wed Sep 19, 2012 1:34 pm:There's also a long-requested feature to use the replay-code to extract the historical aircraft position, which would be another kind of data to show.
That's definitely a good idea, accessing the replay/flight recorder buffers via a dedicated Nasal/property tree interface would be pretty cool, not just for showing historical path data, but also for computing a flight profile, or even for doing a full flight evaluation - which could also be done via Nasal/Canvas then, we just need Nasal hooks (i.e. ghosts) to access the replay/flight recorder subsystem and get data from it.
I've been talking to ThorstenB about exposing the system to Nasal a while ago, and when Tom and I played around with graph plotting, we also figured that it would be kinda cool to access such info from Nasal.
The combination of these features (replay/flight recorder access + Nasal + Canvas), would also make it possible to create a full flight instructor console. The original graph-plotting experiments were pretty encouraging:
And 2D plotting is another long-standing feature request, originally brought up by Curt:
http://www.mail-archive.com/flightgear- ... 03651.htmlcurt wrote:But, I was just thinking today that it might be cool to have a built
in grapher for simple / quick graphing needs.
With the property system it would be trivial to pick an arbitrary
property from the property tree and graph it over time -- superimposed
on top of everything else.
With the Canvas, it has now become trivial to create such graphs, but we still need to have Nasal-space access to the corresponding subsystems and data, i.e. the replay/flight recorder system.