20,741
edits
FGRadar: Difference between revisions
Jump to navigation
Jump to search
no edit summary
mNo edit summary |
No edit summary |
||
| Line 8: | Line 8: | ||
| writtenin = C++ | | writtenin = C++ | ||
| os = Cross platform | | os = Cross platform | ||
| developmentstatus = | | developmentstatus = Put on hold (as of 01/2013) | ||
| developmentprogress = {{Progressbar|20}} | | developmentprogress = {{Progressbar|20}} | ||
| license = [[GNU General Public License]] v3 | | license = [[GNU General Public License]] v3 | ||
| website = https://gitorious.org/fgradar | | website = https://gitorious.org/fgradar | ||
}} | }} | ||
== Status (01/2013) == | |||
'''Project stopped for a while. Use [[OpenRadar]] instead.''' | '''Project stopped for a while. Use [[OpenRadar]] instead.''' | ||
The project may be continued in the future by integrating its building blocks into fgfs mainline, using the new [[Radio Propagation]] framework: | |||
{{cquote|I've seen a couple of external radar clients for Flightgear being developed | |||
right now. | |||
I think that these days, with the advent of Canvas and other improvements, it | |||
should be possible and desirable to have a realistic radar station inside | |||
Flightgear. | |||
At the moment, I'm only concerned about radar ranges and interference of | |||
terrain obstructions, weather, ground clutter. | |||
For this purpose, I propose a template implementation of radar transceivers | |||
and transponders: | |||
It is not possible to provide a detailed terrain picture on every antenna | |||
rotation. Sampling all terrrain 360 degrees around the station would cripple | |||
performance. Thus, I would just take all positions of aircraft inside the | |||
nominal range and perform radio calculations on them, using larger sampling | |||
distances and simpler routines for aircraft above a treshhold flightlevel. | |||
If terrain around the antenna is obstructing the signal, or weather affects | |||
it, we can simulate that correctly. | |||
Transponder responses are also a candidate for the new radio code. Like in | |||
reality, it is possible to have radar contact but lose transponder id because | |||
of radio issues.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38839.html |title=Implementing realistic radar inside the Flightgear engine|author=Adrian Musceac |date= Tue, 27 Nov 2012 05:03:46 -0800}}</ref>|Adrian Musceac}} | |||
<references/> | |||
== Description == | |||
'''FGRadar''' is a free, open-source, multi-platform and stand-alone [[air traffic control]] (ATC) client for [[FlightGear]] currently under development (10/2012). It makes use of the [[SimGear]] library and the Nasal scripting language. | '''FGRadar''' is a free, open-source, multi-platform and stand-alone [[air traffic control]] (ATC) client for [[FlightGear]] currently under development (10/2012). It makes use of the [[SimGear]] library and the Nasal scripting language. | ||
| Line 20: | Line 51: | ||
On the scripting side, it uses the GTK+ and Cairo wrappers for [[Nasal]] in order to perform GUI rendering and drawing operations, respectively. | On the scripting side, it uses the GTK+ and Cairo wrappers for [[Nasal]] in order to perform GUI rendering and drawing operations, respectively. | ||
Under development as of October 2012 (no public release yet): | Under development as of October 2012 (no public release yet): | ||