Thanks John for the reply. I was hoping that there existed a simple solution to this issue but I have no problem enjoying flightgear as is on the linux platform.
Just a thought, is there an accessible (i.e., downloadable) and pre-built combination of flightgear and opengc that would allow me to establish the control channel executing on the windows xp platform? Rick -----Original Message----- From: [EMAIL PROTECTED] [mailto:flightgear-devel-admin@;flightgear.org] On Behalf Of John Wojnaroski Sent: Tuesday, October 29, 2002 3:40 PM To: [EMAIL PROTECTED] Subject: Re: [Flightgear-devel] flightgear 0.8 under linux and --opengc option ----- Original Message ----- From: Rick Marsico To: [EMAIL PROTECTED] Sent: Tuesday, October 29, 2002 9:34 AM Subject: [Flightgear-devel] flightgear 0.8 under linux and --opengc option <When attempting to use -opengc. I see repeated data errors and errors attempting to write to socket. This is the only <network option that I've come across so far that does not want to cooperate. Is anyone successfully using the linux-<based fgfs 0.8.0 with opengc? If so, did you do anything special (related to opengc) at flightgear build time? < <Rick Sigh... the fgfs and opengc versions are out-of-sync. Changes to the socket code in May broke the interface and I've had to resort to a work around using older Simgear socket code. Obviously, such a local solution is not suitable for general consumption and things have only gotten worse. If you are interested in only sending data from fgfs to the glass displays you should be able to set up a UDP channel. Probably also need to check the data structures(classes) across the interface. In flightgear take a look at opengc_data.hxx in ~/src/Network and in the opengc source look in ~/Source/DataSources for the file with the same name. Chances are these are not the same If you want to setup a control channel from opengc to fgfs via TCP things are a little more messy since the new socket code forks and something is amiss in binding the child to the port or whatever such that the data packets are lost. One of these days I'll find the time to dig into the problem. Again, using an earlier veresion of the SimGear socket code (pre-May) is possible. Sorry, the source is out of sync, but it gets a little frustrating to set up a working interface and have folks come by willy-nilly and break it. After about the fourth time, one just gives up. If you still want to get a working version, I'll try to help, but it will most likely not be in sync with the stable or development version. 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
