Hi all,
I have the same problem as listed below. When I select a plane, the error dialog
box says "ssgInit called without a valid OpenGL context".
I am running Windows XP Home Edition (5.1, Build 2600) on a Dell Dimension 4550 with
a Pentium 4 2.40GHz CPU.
My graphics card is an NVidia GeForce 4 MX 420 and under the Control Panel it says
that the driver is up-to-date and working correctly (main driver is nv4_disp.dll)
I'm guessing that it is the graphics card that is causing the problem. Does anyone
know if this card is openGL compatible or what setup/driver is required to make it so?
Thanks for any help,
Mick.
Hi Frank,
On XP you will find the config files in C:\Documents and
Settings\{USER}\Application Data\flightgear.org You should also find
the log there as well.
What video card & driver do you have? Can you give some system specs?
--
Chris Ridley
caridley at gmail.com
---------------------------------------------------------
FIGHT TERRORISM
WITH YOUR BARE HANDS
www.citizenwarrior.com
On 8/1/05, Efraim Yawitz <fyawitz at actcom.co.il> wrote:
> I'm having problems running Flightgear-0.9.8a on WinXP, and the problem
> seems to have at least two parts:
>
> 1)When I try to start it with fgrun, the GUI window comes up, but as soon
> as you select a plane, it crashes with an error box. If you don't select
> a plane (leaving it with the previous setting), you can finish the wizard
> but nothing happens.
>
> 2)From the command line using runfgfs.bat, I get "Unknown exception in
> main loop. Possible causes: no error." From previous posts to the
> mailing lists, this is supposed to be caused by sound driver problems, but
> I doubt that this is the case here, since I tried running it with
> --disable-sound and it was no help. I have a VIA 97 sound card with the
> standard driver.
>
> In general, I'm a Linux user and I'm trying to get this to work on Windows
> for my kids, so I'm a bit unused to some of the XP interface. In
> particular, where does FG put its config files under Windows? Also, I
> tried running it with --log-level=5, but couldn't find where the log info
> was going.
>
> Thanks,
>
> Frank Yawitz
>
>
