Vivian Meazza schrieb:

Ampere K. Hardraade wrote

A rather strange method at getting FlightGear to run, but some users have
confirmed that it worked.

I'm one of the victims, too.

Starting FGFS under Windows XP on my laptop results in the lines:

...
Loading sound information for: squeal
From file sounds sample = F:/Programme/FlightGear/data/Sounds/squeal.wav
Loading sound information for: flaps
From file sounds sample = F:/Programme/FlightGear/data/Sounds/flaps.wav
Fatal error: Failed to gen source.
 (received from )
Deleting a sample
Deleting a sample
Deleting a sample
Deleting a sample
...

But when I start FGFS twice at the same time one instance stops with these lines and the other one runs fine.

May be it will be a good idea to make stack tracing mandatory on Windows
executable.  It will also be a good idea to add more error catching
statements into the code.

Yes!! The given error report doesn't help a thing as user.

FGFS 0.9.6 starts and runs without weird procedures so far as I am aware
(or, to put it another way: it works for me) under both Cygwin and Windows
xp sp2.If it doesn't, then either:

a. it hasn't been installed correctly.

I used the 0.9.6 Windows installer that is provied on the homepage.

b. the system has some incompatibility.

Maybe - but then FGFS isn't multiplatform anymore. And an Acer Travelmate 800 is a real mainstream laptop so we can't say that it is incompatible...


I would first suspect video card driver compatibility with OpenGL or sound
card with OpenAl.

I suspect OpenAL. But as I've never worked with OpenAL (is that still under active development?) and I haven't compiled FGFS for a long time I can't really help to figure out the problem :(


An incompatibility between SP2 and the BIOS is also possible - I had to
update my BIOS to get SP2 to install properly.

My SP2 installed without a problem.

CU,
Christian


_______________________________________________ Flightgear-users mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d

Reply via email to