15
edits
Troubleshooting problems: Difference between revisions
Jump to navigation
Jump to search
m
→Slow Framerate with OpenGL Card: add information for the forceSW parameter
m (link) |
m (→Slow Framerate with OpenGL Card: add information for the forceSW parameter) |
||
| Line 84: | Line 84: | ||
=== Slow Framerate with OpenGL Card === | === Slow Framerate with OpenGL Card === | ||
a) | |||
If you have a card that fully supports OpenGL and FlightGear is still running slow, then there may be a somewhat esoteric fix to your problem. | If you have a card that fully supports OpenGL and FlightGear is still running slow, then there may be a somewhat esoteric fix to your problem. | ||
Change the color depth to match that of your OS's desktop! | Change the color depth to match that of your OS's desktop! | ||
b) Identify if your graphic card use software OpenGL support | |||
When Flightgear was launched, it display a message like this : | |||
Finished command line arguments | |||
Initializing splash screen | |||
GeForce4 MX 440 with AGP8X/AGP/SSE2/forceSW | |||
Max texture size = 2048 | |||
Depth buffer bits = 16 | |||
Loading Airport Database ... | |||
Data file version = 810 | |||
Warning! If you see anything like "ForceSW" or "Software Emulation", it was a bad thing for you because you do not have HARDWARE OpenGL support, or your drivers are not configured properly. If you have HARDWARE OpenGL support, your CPU work a lot to display the graphics. | |||
Source : http://ocw.mit.edu/ans7870/6/6.370/contestants/software.htm#issues | |||
=== USB Joystick Fails to Work === | === USB Joystick Fails to Work === | ||