8,827
edits
m (+ errors) |
m (extended) |
||
| Line 45: | Line 45: | ||
===osgDB ac3d reader: could not find texture...=== | ===osgDB ac3d reader: could not find texture...=== | ||
See [[#Failed to open file ...|Failed to open file ...]] | See [[#Failed to open file ...|Failed to open file ...]] | ||
===Scaling image...=== | |||
This means a texture, whether in the scenery on your aircraft or anyone elses (when multiplayer is enabled), is not sized to powers of two. All textures in FlightGear have to be sized to power of two (eg. 16*16, 32*64, 32*1024). As of version 1.9 textures are resized automaticly, but it does slow your computer down, so it's better to resize the noted textures. | |||
===ssgInit called without a valid OpenGL context=== | |||
In short, your GL libraries are broken. So far only Red Hat 7.x users have experienced this (see http://www.redhat.com/bugzilla/show_bug.cgi?id=18867). The only solutions are possibly complicated ones: you can either change distributions (most of us prefer Debian) or upgrade/downgrade your Mesa libs. | |||
===The system cannot find the file specified=== | ===The system cannot find the file specified=== | ||
| Line 50: | Line 56: | ||
'''Hint:''' you may need to go under Tools and Folder Options to specify "Show Hidden/System Files and Folders" in order for AppData to be visible. | '''Hint:''' you may need to go under Tools and Folder Options to specify "Show Hidden/System Files and Folders" in order for AppData to be visible. | ||
===Time zone reading failed=== | |||
This is probably caused by a line-ending problem in the timezone files. Win32 users can resolve the problem by downloading a DOS to UNIX conversion utility available at http://www.nottingham.ac.uk/~eazdluf/d2u.zip. Run as `d2u *.tab` from within the timezone directory to fix your timezone files | |||
===Unable to choose requested pixel format=== | ===Unable to choose requested pixel format=== | ||
| Line 60: | Line 69: | ||
This error could have a variety of sources, among them missing files but also other things. Increasing the [[FlightGear_Launch_Control#Debugging|log level]] to debug might provide some more information on what FlightGear was doing when the error occurred. | This error could have a variety of sources, among them missing files but also other things. Increasing the [[FlightGear_Launch_Control#Debugging|log level]] to debug might provide some more information on what FlightGear was doing when the error occurred. | ||
Setting your [[FlightGear Launch Control#Page Four - Options and Run|BPP]] to a lower value might work. | Setting your [[FlightGear Launch Control#Page Four - Options and Run|BPP]] to a lower value might work. | ||
===WARNING: Couldn't convert texture...=== | ===WARNING: Couldn't convert texture...=== | ||