|
From: Curtis L. O. <cu...@fl...> - 2001-09-06 10:53:47
|
John Wojnaroski writes: > > Has anyone ever tried the multi-window display option? If so has it worked? > > Right now the data is coming across from the client to the server via the > sockets. Both > a small test program I wrote and the one provided by Norm confirms that the > fdm state > vector is available at the server socket and matches what the client sent. > However the > server screen initializes (just sky with no tile) and that's it.... > > Client -> fgfs --native=socket,out,30,192.168.2.255,udp (this is the > broadcast address, any machine > on tht 192.168.2.xxx network can see the datagram. I've also tried setting a > specific address and the result > is the same) > > Server -> fgfs --native=socket,in,30,,udp --disable-panel --fdm=external > > I notice that the writeup in the installation guide states: > > -protocol= medium,direction,hz,medium_options,...: I/O options, useful for > running FlightGear over a network or in interaction with external programs > (preliminary). > > Can I (should I) assume that this function may not be fully debugged and > operational? > > Regards > Jack W. I have had this working many times, however, I"ve not managed to get it to work with broadcast. The plib net module supports <broadcast> as a destination machine so at some point I'd like to convert to using that for the underlying network layer. Regards, Curt. -- Curtis Olson Human Factors Research Lab FlightGear Project Twin Cities cu...@hf... cu...@fl... Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org |