Re: [Flightgear-devel] socket communication

[Erik Hofman]

Charu Sharma wrote:
Hi All,

Can anyone tell me which part of FlightGear code deals
with programming of socket communication(which we use
for multiple displays)?
I want to run flightgear on a computer(slave machine)
which has no controls like keyboard, joysticks etc
from a machine(server) which has all these controls.  

Any ideas and suggestions would be very helpful?
See FlightGear/docs-mini/README.IO

Socket Communication:

    --native=socket,dir,hz,machine,port,style

    machine = machine name or ip address if client (leave empty if server)
    port = port, leave empty to let system choose
    style = tcp or udp
    example to slave one copy of fgfs to another

    fgfs1:  --native=socket,out,30,fgfs2,5500,udp
    fgfs2:  --native=socket,in,30,,5500,udp --fdm=external
This instructs the first copy of fgfs to send UDP packets in the native 
format to a machine called fgfs2 on port 5500.

The second copy of fgfs will accept UDP packets (from anywhere) on port 
5500.  Note the additional --fdm=external option.  This tells the second 
copy of fgfs to not run the normal flight model, but instead set the FDM 
values based on an external source (the network in this case.)

Erik

_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel