Howto:Multi-computing FlightGear: Difference between revisions

Jump to navigation Jump to search
(Typo)
Line 67: Line 67:
* "native-fdm" and "native-ctrls" are now sockets using the "in" parameter because they do listen on your network interface for incoming traffic.
* "native-fdm" and "native-ctrls" are now sockets using the "in" parameter because they do listen on your network interface for incoming traffic.
'''!!! Make sure to configure your firewall to accept incoming traffic on the above mentioned protocols/ports/sender IPs !!!
'''!!! Make sure to configure your firewall to accept incoming traffic on the above mentioned protocols/ports/sender IPs !!!
* "update frequency, port and protocol" are identical to the settings of "leader". Regard '''two commas''' between frequency and port. This is where normally the IP is placed and two commas here are intended because now the socket "listens" on your configured IP (on "slave1" 192.168.1.11) and on localhost (which is always 127.0.0.1 and used for internal networking). You can verify this on the slave by opening a console window and use If you want that FlightGear is just listening on your external interface you may add the address instead so you get line like:
* "update frequency, port and protocol" are identical to the settings of "leader". Regard '''two commas''' between frequency and port. This is where normally the IP is placed and two commas here are intended because now the socket "listens" on your configured IP (on "slave1" 192.168.1.11) and on localhost (which is always 127.0.0.1 and used for internal networking). You can verify this on the slave by opening a console window and use a socket monitor like "netstat" to verify that the sockets are running on the proper interface and correct ports. If you want that FlightGear is just listening on your external interface you may add the address instead so you write a line like:
  --native-fdm=socket,in,60,192.168.1.11,5510,udp
  --native-fdm=socket,in,60,192.168.1.11,5510,udp
* "fdm=null" tells FlightGear not to use any flightmodel as this is given by "leader"
* "fdm=null" tells FlightGear not to use any flightmodel as this is given and calculated by "leader"
* "enable-panel" does exactly what it says: it's enabling the instrument panel. That's what we want here
* "enable-panel" does exactly what it says: it's enabling the instrument panel. That's what we want here
* "disable-hud" will remove the heads up display. We have this on "leader". Here it's just not needed
* "disable-hud" will remove the heads up display. We have this on "leader". Here it's just not needed
172

edits

Navigation menu