Hi, and welcome! * Denise Schaefer -- Thursday 07 July 2005 16:51: > I read in the documentary that you friendly people would surely help with > problems.
That was only to attract new "customers". All just marketing lies! :-) > When starting, the main loop is aborted either stating the cause as "no > error" or stating the cause as file not found. This differs depending on > the selection of aircraft and runway. That's ugly. Normally, all errors in fgfs and friends do either throw exceptions and/or exit/abort with error messages. No part of fgfs does "successfully abort". This makes me believe that it's a bug in some other piece of the puzzle, such as the openal lib, the sound hardware driver, or the graphics card driver. In all similar cases (or similarly weird cases), it was indeed one of the non-flightgear components. (By which I don't mean to say that fgfs is bugfree, of course. :-) > However the files and directories seem to be all there. In the debug level > log I also found the statements "bad entry parms in materials.xml skipped" Hmm ... I couldn't find the word "parms" in any of FlightGear's code files. Nor "bad entry" or "skipped" (except once in an unrelated message). What I see is "Skipping bad material entry" followed by the name of the bad entry. Did you copy this error message into this email? What entry did it complain about? Is the file corrupted (as in: contains binary garbage or something)? Is your RAM broken? (try memtest, or something similar: http://www.memtest86.com/) > and the interpolator lookup claims x to small when doing model iterations. Which aircraft model? Or better: which command line? (It's displayed in the fgrun launcher window.) > I read someone else had problems with this aborting the main loop and > updated the audio driver. > So I tried this too (updating to wdm3516b_Cadenza (Intel / Soundmax) but > that didn´t change anything. See above. The graphics card driver is also a hot candidate. Those do often run with so many permissions that they can break the whole system. Now, why would fgfs trigger that, but not the other 3D apps? Because fgfs uses the driver's OpenGL interface. This seems often to be badly tested on Windows. The manufacturers care mostly about MICROS~1's DirectX. > Can you maybe specify a driver (and location) that I should use ? Hmmm ... a more recent Matrox graphics card driver? :-) > No combination of deafult aircrafts and runways at KFSO seem to work > unfortunately That's bad. Those (few) of the developers that use Windows don't run into such problems, so it's really hard to guess/fix the reason. Even more so for the Unix/Linux using majority. If you were running Unix, we could give some instruction to track this down. On Windows that's very hard. But the breakage is probably not caused by fgfs at all. m. PS: it's "summer hibernation" time, so answers may take a bit longer than normal. In urgent cases you may always want to consider joining the IRC channel: irc://irc.flightgear.org/#flightgear _______________________________________________ Flightgear-users mailing list [email protected] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
