8,564
edits
Howto:Understand console output: Difference between revisions
Jump to navigation
Jump to search
m
+ Error: [Screen #0] GraphicsWindowWin32::setPixelFormat() - No matching pixel format found based on traits specified
m (+ Error: [Screen #0] GraphicsWindowWin32::setPixelFormat() - No matching pixel format found based on traits specified) |
|||
| Line 3: | Line 3: | ||
===Could not find at least one of the following objects for animation:=== | ===Could not find at least one of the following objects for animation:=== | ||
This means that FlightGear is unable to find an object in a .ac file. Check the .xml file (where the animation is stored) to see if the object-names match those in the .ac file. If you are not the aircraft's author you can safely ignore such warnings. | This means that FlightGear is unable to find an object in a .ac file. Check the .xml file (where the animation is stored) to see if the object-names match those in the .ac file. If you are not the aircraft's author you can safely ignore such warnings. | ||
===Error: [Screen #0] GraphicsWindowWin32::setPixelFormat() - No matching pixel format found based on traits specified==== | |||
Try changing the [[FlightGear Launch Control#Page Four - Options and Run|BPP]] value of your FlightGear setup. If that does not work, your graphics card is probably not able to run FlightGear 1.9 and higher. Another graphics card, or an older FlightGear version will likely "fix" the problem. | |||
===Error: bind() failed in make_server_socket()=== | ===Error: bind() failed in make_server_socket()=== | ||