Here are the detailsFlight Gear 0.9.6Windows XP + SP2Athalon XP2700Radeon 9500Recently update graphics driversFlightGear reports the following on startup:Object PanelInstruments not foundObject ControlsGroup not foundUnknown exception in the main loop. Aborting...Using a number of different aircraft types.e.g.system.fgfsrc:--fg-root=C:Program FilesFlightGeardata--fg-scenery=C:Program FilesFlightGeardataScenery;C:Program FilesFlightGearscenery--airport-id=KSFO--aircraft=737--disable-random-objects--disable-ai-models

Try unplugging your CH Yoke and Pedals.http://baron.flightgear.org/pipermail/flig...ber/009611.html

Just got a mouse and keyboard at the moment, plus a USB scanner and a parallel printer.I have now added --control=keyboard and I still get the same.

I set the log level to DEBUG and it dropped out just after initialising the OPENGL Sound Manager.Having reread some of the recent posts I am investigating the availability of updated onboard sound drivers for my Leadtek Nvidia motherboard.

OK so it was the sound drivers. Upgraded to flashy new Nvidia drivers and everything seems to be working.A few lessons learned for other newbies and a few for the documentation.1) Debug mode is useful in identifying the problem, but turn it off once it works, it hits the frame rate seriously.2) As everybody keeps saying, ensure that your drivers are up to date, but this includes sound drivers, even though they may otherwise appear to be working OK.3) The installation documentation is a bit out of date, it doesn't know about the installer or fgrun and it refers to a batch file that no longer exists.4) fgrun creates a command window, but it if fgfs aborts it disappears before you can read the error message. You need to set FG_ROOT if you run it yourself. This is different to the --fg-root parameter.5) fgadmin wants to install the scenery in the scenery directory under C:/Program File/FlightGear, that does not exists, I created one and everything was then ok. If it does not exists it installs it where you run it.