Howto:Understand console output: Difference between revisions

Jump to navigation Jump to search

Howto:Understand console output (view source)

Revision as of 23:48, 10 March 2012

193 bytes added ,  10 March 2012
m
→‎Errors with known solutions
Line 89: Line 89:


'''Hint for Developers:''' Pre-test all your .xml files in Windows by opening them with Internet Explorer (usually by double clicking). IE can tell you if a comment/token is not closed.
'''Hint for Developers:''' Pre-test all your .xml files in Windows by opening them with Internet Explorer (usually by double clicking). IE can tell you if a comment/token is not closed.
=== FGMultiplayerMgr::Open - Failed to bind receive socket ===
This means FlightGear was unable to open the listening network socket required by the --multiplay=in option. Frequently this option can be omitted and FlightGear will figure out the necessary parameters automatically.
Common reasons are:
* Address given in the option does not resolve to one of the IP addresses of the local machine. This parameter should only be required if you want to fine-tune the network behavior. Omitting it directs FlightGear to listen on all local interfaces automatically. Example:
--multiplay=in,10,,5001
Notice that you still need the comma.
* The UDP port given in the option (or the default port 5000 if no option given) is already in use. Verify nothing is using the port.


=== FGMultiplayMgr::MP_ProcessData: No such file or directory ===
=== FGMultiplayMgr::MP_ProcessData: No such file or directory ===
Line 233: Line 241:
There is a problem in the [[FDM]]. A fuselage section with similar ax and ay was created. Change the ax and/or ay values to match the aircraft.
There is a problem in the [[FDM]]. A fuselage section with similar ax and ay was created. Change the ax and/or ay values to match the aircraft.


=== FGMultiplayerMgr::Open - Failed to bind receive socket ===
=== YOU HAVE AN INCOMPATIBLE CFG FILE FOR THIS AIRCRAFT. RESULTS WILL BE UNPREDICTABLE !! ===
 
Make sure the [[JSBSim]] [[FDM]] of the aircraft has a <code><fdm_config version="2.0"</code> tag.
This means FlightGear was unable to open the listening network socket required by the --multiplay=in option. Frequently this option can be omitted and FlightGear will figure out the necessary parameters automatically.
Common reasons are:
* Address given in the option does not resolve to one of the IP addresses of the local machine. This parameter should only be required if you want to fine-tune the network behavior. Omitting it directs FlightGear to listen on all local interfaces automatically. Example:
--multiplay=in,10,,5001
Notice that you still need the comma.
* The UDP port given in the option (or the default port 5000 if no option given) is already in use. Verify nothing is using the port.


== Errors without known solutions ==
== Errors without known solutions ==
Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/44028"

Navigation menu