20,741
edits
No edit summary |
m (→Summary) |
||
Line 28: | Line 28: | ||
}} | }} | ||
== Objective == | |||
Implement a realistic radio propagation model inside FlightGear | |||
==Summary== | ==Summary== | ||
Line 39: | Line 42: | ||
* mostly realistic radio reception of localizer and glideslope signals, making landings more interesting for certain airports. | * mostly realistic radio reception of localizer and glideslope signals, making landings more interesting for certain airports. | ||
* configuration and realistic reception of radio beacons located anywhere in the 3D world, while presenting calculated signal values according to different official guidelines, including but not limited to the FAA. | * configuration and realistic reception of radio beacons located anywhere in the 3D world, while presenting calculated signal values according to different official guidelines, including but not limited to the FAA. | ||
== Roadmap == | |||
We are currently looking into updating the code base, to ensure that things still work with FG 3.0+ | |||
Some of the steps involved are detailed below: | |||
* rebase against git HEAD (next) {{Not done}} | |||
* modify build system to make the feature entirely optional via build-time option that defaults to disabled {{Not done}} | |||
* Address issues pointed out by TorstenD on the devel list {{Not done}} | |||
* implement SGPropertyChangeListener to change the SGSubsystem and make the feature runtime-configurable [[Howto:Create new subsystems]] {{Not done}} | |||
* investigate potentia threading/HLA benefits {{Not done}} | |||
* investigate exposing a [[Nasal/CppBind]] interface for people working on features that benefit from having a radio propagation model [[Canvas Radar]] {{Not done}} | |||
==Using Flightgear as a general purpose, 3D, radio signal propagation and terrain analysis tool== | ==Using Flightgear as a general purpose, 3D, radio signal propagation and terrain analysis tool== |