John, > > change the define in ogcFMC.cpp from > > #define SERV_HOST_ADDR "192.168.2.10" > > to > > #define SERV_HOST_ADDR "your_NIC_address" for the machine running fgfs. >
As I see it, I've to hard code the NIC at build time, right? This might be a pity for people like me sitting on a (home) network with dynamically assigned addresses (DHCP). Even though I certainly can read off my present address I'll have to recompile every time....? Does it only concern the FMC? Or am I even completely mistaken here? BTW, http://www.opengc.org/ is alive again. :-) Sincerely, Michael -- Michael Basler, Jena, Germany [EMAIL PROTECTED] http://www.geocities.com/pmb.geo/ > -----Urspr�ngliche Nachricht----- > Von: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]Im Auftrag von John > Wojnaroski > Gesendet: Samstag, 23. Februar 2002 19:26 > An: [EMAIL PROTECTED] > Betreff: [Flightgear-devel] Re: FG/Opengc Interface > > > > Hi, > > A question was asked last week on running FG and OpenGC on the > same machine. > Well, the one way is to > run each app in it's own window and use the loopback address of > 127.0.0.1 to > communicate via sockets. > > fgfs .......... --opengc=socket,out,24,127.0.0.1,5800,udp ........... > > Shift-5 engages the Flight Mgmt Computer (FMC) which will not work in the > stand-alone mode. Keep the focus in the FG window and fly via the > keyboard/joystick/yoke > > Point of clarification. the FMC can be enabled if you have a network > interface card (NIC) in you machine. You need to set the IP address in > ogcFMC.cpp to your card's address. > > change the define in ogcFMC.cpp from > > #define SERV_HOST_ADDR "192.168.2.10" > > to > > #define SERV_HOST_ADDR "your_NIC_address" for the machine running fgfs. > > then the command line becomes > fgfs > .......... --opengc=socket,out,24,127.0.0.1,5800,udp > --native-ctrls=socke > t,in,24,,5700,tcp > > The source in the repository is a little behind my local copy, > but it should > work. Check ogcRenderWindow.cpp for > the keyboard callback routine and keyboard commands/functions. > > Regards > John W. > > > > > _______________________________________________ > Flightgear-devel mailing list > [EMAIL PROTECTED] > http://mail.flightgear.org/mailman/listinfo/flightgear-devel > _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
