Talk:Radio propagation: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
(→Some of the code is in the code base: New section) |
||
Line 28: | Line 28: | ||
* investigate exposing a [[Nasal/CppBind]] interface for people working on features that benefit from having a radio propagation model [[Canvas Radar]] {{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}} | ||
* add unit tests to the cmake build system {{Not done}} | * add unit tests to the cmake build system {{Not done}} | ||
== Some of the code is in the code base == | |||
I was looking around in the source code of FlightGear after the integrated FGCom code and found that there is radio propagation code in {{flightgear source|path=src/Radio}} (currently at commit {{flightgear source|path=src/Radio|commit=a0f47c151ca4341f14bd198384542b95a025abba|text=a0f47c15}}). | |||
—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 16:38, 6 September 2020 (EDT) |
Latest revision as of 20:39, 6 September 2020
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:
- integrate with navaid/radio code[1] Done
- rebase against git HEAD (next) Done
- rebase into a set of smaller self-contained patches [2] Pending
- modify build system to make the feature entirely optional via build-time option that defaults to disabled [3] [4] Done
- Address issues pointed out by TorstenD on the devel list:
- provide a startup option to enable/disable the system [8] [9] [10] [11] Done
- implement SGPropertyChangeListener to change the SGSubsystem and make the feature runtime-configurable Howto:Create new subsystems
- add a setting to the realism dialog[12] Not done
- explore allowing aircraft developers to specify and customize a "radio equipment" profile for their aircraft (e.g. 747 vs. c172p antenna/power etc) [13]
- support different propagation models by coming up with an interface: Done
- https://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg33692.html
- https://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38798.html
- https://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38907.html
- https://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40534.html
- https://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40537.html
- turn the whole thing into a dedicated SGSubsystem[14] Done
- explore what is involved in allowing fgcom-standalone to use the same system [15] Pending
- investigate potential 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
- add unit tests to the cmake build system Not done
Some of the code is in the code base
I was looking around in the source code of FlightGear after the integrated FGCom code and found that there is radio propagation code in flightgear/flightgear/next/src/Radio (currently at commit a0f47c15).