20,741
edits
Telnet usage: Difference between revisions
Jump to navigation
Jump to search
http://www.mail-archive.com/flightgear-devel@flightgear.org/msg27071.html
(http://www.mail-archive.com/flightgear-devel@flightgear.org/msg27071.html) |
|||
| Line 1: | Line 1: | ||
{{PropertyTree}} | {{PropertyTree}} | ||
FG has a low bandwidth "command" (aka telnet) interface where you can interactively (or automatically via an external program) examine and modify just about any internal variable in the sim. This gives you a great capability to do external scripting, external operater gui's, etc. For instance, if you have your own GUI for operating the sim and want to use it to set weather conditions, you can leverage the FG telnet interface to have your own program remotely configure the environmental settings in all your FG based visual channels. | |||
FlightGear can be configured to act like a telnet or even an http "server". It can watch a port for incoming connections and respond appropriately, these built-in daemons support multiple connections. | FlightGear can be configured to act like a telnet or even an http "server". It can watch a port for incoming connections and respond appropriately, these built-in daemons support multiple connections. | ||