feature wish:
after each landing flightgear should display vertical and horizontal speed
at the moment of touchdown
so that it's easier for me to judge it it was a good or not so good landing.
maybe such a nasal script exist already ?
Hooray wrote:To get you started, I have added a little tutorial and a screen shot, demonstrating that it's definitely possible to add a Nasal/Canvas-driven "fgplot" application to FlightGear, using just a simple XML dialog (because you're using FG 2.10, that doesn't yet have the more recent features):
http://wiki.flightgear.org/Howto:Adding ... log#FGPlot
It's just proof of concept, and pretty simple for now - but should get you going pretty quickly.
Hooray wrote: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.
pommesschranke wrote in Sat Sep 07, 2013 9:23 pm:...after each landing flightgear should display vertical and horizontal speed
at the moment of touchdown...
Hooray wrote in Sat Sep 07, 2013 9:48 pm:...these already record all required data - but currently they are not exposed to Nasal yet.
Johan G wrote in Sun Sep 08, 2013 3:54 pm:Hooray wrote in Sat Sep 07, 2013 9:48 pm:...these already record all required data - but currently they are not exposed to Nasal yet.
I'm not sure I follow you, since TAS and VS for sure is available in the property tree.![]()
![]()
Hooray wrote in Sun Sep 08, 2013 10:13 pm:It is not about properties being in the tree, they are all there, it's about them having to be recorded for any type of evaulation.
Hooray wrote in Sat Sep 07, 2013 9:48 pm:a better option would be hooking into the replay/flight recorder systems, because these already record all required data - but currently they are not exposed to Nasal yet.
Users browsing this forum: YandexBot [Bot] and 1 guest