20,741
edits
Telnet usage: Difference between revisions
Jump to navigation
Jump to search
m
→subscribe and unsubscribe: very sound advice: https://sourceforge.net/p/flightgear/mailman/message/37263821/
(+-link: Interactive traffic → AI Traffic; Spelling; minor cleanup) |
m (→subscribe and unsubscribe: very sound advice: https://sourceforge.net/p/flightgear/mailman/message/37263821/) |
||
| Line 245: | Line 245: | ||
=== subscribe and unsubscribe=== | === subscribe and unsubscribe=== | ||
{{See also|Improved J661 support}} | {{Caution|You may want to think about updates that happen every frame but are not | ||
significant. | |||
Several properties are constantly re-calculated but vary only at a very | |||
high level of precision per frame. One can subscribe constant flood of | |||
updates that do not show up in a meaningful way on actual instruments and | |||
represent changes in value that are neither visible nor actionable. Fuel | |||
is a good example, but also items like the attitude indicator and | |||
altimeter. | |||
You can observe these properties easily through a subscription in the | |||
telnet interface or by refreshing individual items in the phi interface. | |||
Just start the Cessna 172 and set the parking brake. | |||
I think the ability to subscribe to changes at a specific level of | |||
precision for updates to each property might prove useful.<ref>https://sourceforge.net/p/flightgear/mailman/message/37263821/</ref> | |||
}} | |||
{{See also|Data_Distribution_Services_Support#Property_tree|Improved J661 support}} | |||
{{Note|{{FGCquote | {{Note|{{FGCquote | ||