> That sounds like you're using TCP, since if you were using UDP, the > master would not know if the slave(s) received the message -- UDP is an > unreliable protocol and the master > does not know if it is transmittiing into oblivion or reaching an actual > slave instance of FlightGear. Provided the native protocol doesn't have > a mechanism to provide feedback of received messages to the master, that > is. It's udp I swear by the life of my dog (mine is to precious):
The commandline pasted fresh from the clipboard: fgfs --native=socket,out,20,localhost,5556,udp --aircraft=c172p --geometry=640x480 --timeofday=noon --native-ctrls=socket,out,20,localhost,5557,udp And the output of netstat -un after the above command (sorry - german output. s/VERBUNDEN/CONNECTED/g): Proto Recv-Q Send-Q Local Address Foreign Address State udp 0 0 127.0.0.1:32817 127.0.0.1:5556 VERBUNDEN udp 0 0 127.0.0.1:32818 127.0.0.1:5557 VERBUNDEN Torsten ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
