![]() If you can't read the Menu titles (because of corrupted graphics) you can manually edit the config files $FG_HOME/autosave.xml and/or $FG_ROOT/preferences.xml before even starting FlightGear. When you come to quit FG, do so by menu: File.Exit, rather than closing the window to save this setting. Uncheck 'Use Point Sprites for Runway Lights' (fourth check-box) Select 'Rendering Options' (fourth choice) Select 'View' drop-down menu (one from the left- you may not be able to read the labels!) The ATi drivers are the subject of intensive improvement, but can still be problematic for some users. Several users have reported corrupted textures running FlightGear on ATi graphics cards. This card is not yet powerful for flightgear and there is no workaround for it. I made tests with Flightgear 0.9.10 and 1.0.0, I have only 1 fps with these 2 drivers and 2 flighgear versions. 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). And with this configuration, your CPU is used at 98% by fgfs.exe or the flightgear binary. It was not the GPU (nvidia chip) that work to support the software OpenGL features but your CPU. This 45.33 driver supports over five generations of NVIDIA GPUs - from TNT to GeForce FX(Geforce Fx = Geforce5).ĭon't use driver upper than 45.33, because in the upper version, there is a software OpenGL support. The detailed problem analysis is workaround is to downgrade your nvdia driver to 45.33 or 4.5.3.3. I have a nvidia Geforce 4 MX440-AGP 8x and this workaround correct the slow framerate with my graphic card. Slow Framerate with Graphic Card with Nvidia chipĪ) First, Identify if your graphic card use software OpenGL supportī) Second, use this workaround for Windows 2000/XP to correct this problem. If you have SOFTWARE OpenGL support, your CPU work a lot to display the graphics. 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. GeForce4 MX 440 with AGP8X/AGP/SSE2/forceSW Tab "debuuging", select info for "log level" -> click button OK ) (before you need to enable log in info mode,įlighgear launcher (fgrun.exe) ->button "advanced" in the third window -> When Flightgear was launched, it display a message like this in Flighgear launcher's console window: 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.Ĭhange the color depth to match that of your OS's desktop!ī) Identify if your graphic card use software OpenGL support 2 Possible pitfalls when modifying base package filesĬommon FlightGear Problems and Solutions See Howto: Get rid of common errors for the main article about this subject.1.6 Configuring CH Products Under Windows Vista.1.5 USB Joystick exhibits permanent offset / requires repeated recalibration.1.2 Slow Framerate with Graphic Card with Nvidia chip.1 Common FlightGear Problems and Solutions.Been only a few days on internet, so not sure how to send my xml to other sim pilots to test fly. The trigger is used as a modifier so every other switch function is doubled. My xml enables me to do a lot more than when I used the keyboard as I can operate left and right engines on 2 throttle levers, panview left and right and up and down, toggle tailwheel lock, reverse thrust, parking brake, airbrake,HUD,Glidepath markers etc also start or autostart pistons and jets left and right brakes, elevator trim, aileron trim, set 2D/3D view (as per keyboard "c"), swiftly return to view ahead from any panviewpoint and control engine boost, winch and release gliders, all on buttons at the top of the stick! There are 4 x 2way toggle switches on the Aviator stick for switching magnetos on and off, gear or flaps up and down, adjust prop pitch, mixture, close canopy, hatch pre take off etc. My present Aviator stick has a twist grip for rudder and it is possible to get good coordination without resorting to peddles. You do need to set co-ordinated controls as trying to coordinate the ailerons with the rudder is impossible on a keyboard. I was delighted with my initial encounter with flightgear and found it very realistic even though I had to use a mouse as the stick and keyboard buttons for throttle, gear,flaps and views. Unfortunately the Aviator file in Flightgear did not work with my vista setup so I built my own AV8R xml which works well. You need a good joystick like Saitek Aviator and then you can use Saitek profile editing to namewhat each axis and button does. Don't think you can do a lot with your setup as you need several other button functions to realistically fly a plane.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |