20,741
edits
FlightGear Newsletter April 2021: Difference between revisions
Jump to navigation
Jump to search
→Development news
| Line 31: | Line 31: | ||
<!-- News about FlightGear itself. The FlightGear mailing list and/or core developers are a good source. --> | <!-- News about FlightGear itself. The FlightGear mailing list and/or core developers are a good source. --> | ||
=== Data Distribution Services Update: Property tree support === | |||
{{Main article|Data Distribution Services Support}} | |||
As of 04/2021, Erik has implemented an initial implementation of a [[Property|property server]] using '''Data Distribution Service'''. And he has also taken the time to implement it [[Remote Properties|like he once envisioned the remote property tree]]. | |||
The idea is as follows: | |||
You request a property path, the server responds with the property value and a property index. | |||
Successive requests now can use the index to access the property removing the need to send the full property path every request saving both | |||
bandwidth and lookup time. | |||
As an example, there is the fg_dds_prop utility in {{Flightgear source|src/Network/DDS/fg_dds_prop.cpp}} which can be used to either request a property path or a know property property ID. | |||
And there is {{Flightgear source|src/Network/DDS/fg_dds_log.cpp}} which is able to log all DDS samples passing over the DDS network layer, including the new | |||
property sample format. | |||
To access properties from a running version of FlightGear use the following command line parameter: | |||
<code>--dds-props=dds,out,<hz></code> | |||
All this is 'next' only. <ref>https://sourceforge.net/p/flightgear/mailman/message/37263034/</ref> | |||
<!-- == Related Software tools and projects == --> | <!-- == Related Software tools and projects == --> | ||