FlightGear wiki

Troubleshooting problems: Difference between revisions

Page Discussion

Troubleshooting problems (view source)

Revision as of 20:56, 17 May 2014

3,554 bytes removed ,  17 May 2014
m
moved slow graphics to Troubleshooting performance issues
m (link update)
m (moved slow graphics to Troubleshooting performance issues)
Line 6: Line 6:
** If you are having a problem with software crashes, please read [[System Crashes]]
** If you are having a problem with software crashes, please read [[System Crashes]]
** If you are having problems with video, please check the list of [[Problematic Video Cards]] and [[Troubleshooting graphics artifacts]]
** If you are having problems with video, please check the list of [[Problematic Video Cards]] and [[Troubleshooting graphics artifacts]]
** If FlightGear performance is slow, see: [[Howto:Use the system monitor]]
** If FlightGear performance is slow, see: [[Troubleshooting performance issues]] and [[Howto:Use the system monitor]]
** Check out [[Hardware Recommendations]] for more information about video cards and other hardware that works with FlightGear  
** Check out [[Hardware Recommendations]] for more information about video cards and other hardware that works with FlightGear  


Line 15: Line 15:
= Common FlightGear Problems and Solutions =
= Common FlightGear Problems and Solutions =
{{main article|Howto: Get rid of common errors}}
{{main article|Howto: Get rid of common errors}}
== 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.
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 in FlightGear launcher's console window:
(before you need to enable log in info mode,
FlightGear launcher (fgrun.exe) -->button "advanced" in the third window -->
tab "debuuging", select info for "log level" --> click button OK )
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 SOFTWARE OpenGL support, your CPU work a lot to display the graphics.
Source : http://ocw.mit.edu/ans7870/6/6.370/contestants/software.htm#issues
c) Optimize FlightGear [[settings for slower graphics cards]]
d) check that the Throttle Frame Rate is not set to low values. Check via Rendering Options or sim/frame-rate-throttle-hz.
Default value is 30, but can set up to 100.
== Slow Framerate with Graphic Card with Nvidia chip ==
a) First, Identify if your graphic card use software OpenGL support
When Flightgear was launched, it display a message like this in FlightGear launcher's console window:
(before you need to enable log in info mode,
FlightGear launcher (fgrun.exe) -->button "advanced" in the third window -->
tab "debuuging", select info for "log level" --> click button OK )
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 SOFTWARE OpenGL support, your CPU work a lot to display the graphics.
Source : http://ocw.mit.edu/ans7870/6/6.370/contestants/software.htm#issues
b) Second, use this workaround for Windows 2000/XP to correct this problem.
I have a nvidia Geforce 4 MX440-AGP 8x and this workaround correct the slow framerate with my graphic card.
The detailed problem analysis is here :
http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg14993.html
This workaround is to downgrade your nvdia driver to 45.33 or 4.5.3.3.
You can find it here :
http://www.nvidia.com/object/pc_winxp-2k_45.33.html
This 45.33 driver supports over five generations of NVIDIA GPUs - from TNT to GeForce FX(Geforce Fx = Geforce5).
Don't use driver upper than 45.33, because in the upper version, there is a software OpenGL support. It was not the GPU (nvidia chip) that work to support the software OpenGL features but your CPU. And with this configuration, your CPU is used at 98% by fgfs.exe or the flightgear binary.
Note : I do tests with Graphic card with Nvidia Geforce 6200-AGP8X-256MB (NV44A2) and with 7.7.7.2 and 9.4.2.4 nvidia drivers on Windows 2000 SP4 (CPU : Celeron D 2,66Ghz, RAM : 512 MB).
I made tests with Flightgear 0.9.10 and 1.0.0, I have only 1 fps with these 2 drivers and 2 FlightGear versions.
This card is not yet powerful for flightgear and there is no workaround for it.




Bigstones
573

edits

Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/71567"