Hello,

I'm trying to use the generic protocol feature of FlightGear, but I'm 
having issues to send input to FlightGear. To do that, I defined my own 
protocol. My protocol has an input and output sections. I use this 
protocol to control an aircraft with a Java application I developed. I 
first tried my application with the Mac OS X version of FlightGear and 
it worked.

However, I'm now trying to do the same on Windows XP, but it does not 
work. I can't even start FlightGear. I got the following error message 
just before FlightGear stops:

Error: bind() failed in make_server_socket()
SG_IO_IN socket creation failed
Error opening channel communication layer.
I/O Channel config failed.

For information, I launch FlightGear with the following options:

--generic=socket,out,20,localhost,5600,udp,autopilot 
--generic=socket,in,20,localhost,5660,udp,autopilot

If I remove the input option, I receive correctly the information sent 
by FlightGear.
I also first launch my Java application so that it binds on the 5660 
port before FlightGear starts. If I do not do that, I get the following 
message:

FGMultiplayMgr - No receiver port, Multiplayermode disabled

Do you know what could be the problem ? I really do not understand why 
it works on Mac but not on Windows... Or else, is it possible to input 
values to FlightGear with a file instead of a socket by writing in the 
file each time I receive a new output from the simulator ?

Thanks,
Julien

------------------------------------------------------------------------------
Gaining the trust of online customers is vital for the success of any company
that requires sensitive data to be transmitted over the Web.   Learn how to 
best implement a security strategy that keeps consumers' information secure 
and instills the confidence they need to proceed with transactions.
http://p.sf.net/sfu/oracle-sfdevnl 
_______________________________________________
Flightgear-users mailing list
Flightgear-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-users

Reply via email to