HJ1AN wrote in Thu May 15, 2014 11:27 am:That's a shame. It'd be great if there is an option to track just one or two flights though, and follow it around or formation flight
We now have HTTP client bindings available to Nasal, which basically means that you can process JSON/XML feeds directly from FG.
So you can download some live data, parse it and populate Nasal data structures.
so you can still do something like this with less than 50 lines of code - it would just be running locally obviously.
In fact, as a quick hack, you can simply use the MapStructure framework to do this: copy the TFC.lcontroller file and change its searchCmd() to run such a query regularly.
Rename the whole thing to "FEED.lcontroller" and change the name at the top of the lcontroller/symbol files
As long as you're adding a MapStructure-based instrument (e.g. Gijs' ND) to your aircraft (not just as a GUI dialog), that traffic feed will be regularly processed.
If in doubt, use the 747-400 or the 777-200
That alone would just make the traffic show up on your ND or map. But then it's roughly 5 lines of Nasal code to adapt the tanker.nas code to "inject" traffic into our AI system, coming from those MapStructure controllers - i.e. the searchCmd return result would be passed onto the AI system.
It's a hack, but not even an ugly one, and not even difficult - it involves under 50 lines of Nasal code in total, and you'll be able to parse arbitrary traffic feeds, even without fgms.
Technically, it would obviously be better to have one central server, rather than possibly dozens of clients doing that - but this will work,and it's not very much work either.