26
edits
Howto:Understand console output: Difference between revisions
Jump to navigation
Jump to search
→Errors with known solutions: added "Failed to bind receive socket"
m (→Errors without known solutions: fix typo) |
(→Errors with known solutions: added "Failed to bind receive socket") |
||
| Line 182: | Line 182: | ||
===YASim SOLUTION FAILURE:<br>Zero length fuselage=== | ===YASim SOLUTION FAILURE:<br>Zero length fuselage=== | ||
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=== | |||
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== | ||