Hi Chris,
thanks for your hints.
I had checked the system and app-logs
before but found nothing. Will try the Dr. Watson.
Can you recommend a working video
driver from your experience ?
Thanks a lot
Best regards
Denise
-----Ursprüngliche
Nachricht-----
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]Im Auftrag von C Ridley - OnCall Solutions
Gesendet: Dienstag, 12. Juli 2005
00:31
An: FlightGear user discussions
Betreff: Re: [Flightgear-users]
Re: FG 0.9.8.a - runtime error on win 2K
Hi Denise,
I have setup FG on quite a few W2K boxes and have had similar experiences with
the less than stellar video drivers for Win2K.
Have you checked the system & app logs under Admin Tools for any errors or
info that might be generated? Probably nothing there, but worth looking.
You can also try the Dr Watson Agent, it might help get the big picture as to
what exactly is generating the error. Dr. Watson is used to diagnose a
program error. A text file (Drwtsn32.log) is created whenever an error is
detected (supposedly). You also have the option of creating a crash dump
file, which is a binary file that a programmer can load into a debugger.
If a program error occurs, Dr. Watson will start automatically (again,
supposedly). I prefer to start it manually. To start Dr. Watson manually,
click Start, click Run, and then type drwtsn32. To start Dr. Watson from a
command prompt, change to the root directory, and then type drwtsn32.
You should have Dr Watson running, then run FG and check the log.
Here is a link to setting up Dr Watson. Get some caffiene first!
http://windows.microsoft.com/windows2000/en/professional/help/default.asp?url=""
Link to how to read the log file:
http://windows.microsoft.com/windows2000/en/professional/help/default.asp?url=""
Various options you can set:
http://windows.microsoft.com/windows2000/en/professional/help/default.asp?url=""
--
Chris Ridley
[EMAIL PROTECTED]
---------------------------------------------------------
We make a Living by what we get.
We make a Life by what we give.
We usually make a mess by what we do.
On
7/11/05, Denise Schaefer <[EMAIL PROTECTED]> wrote:
Hi ,
and thank you Melchior for helping inspite of the marketing trick
;-)
I´ve taken up your questions and below you can find 2 detailed cases and
logs.
For all that would like a challenge ;-)), I'd appreciate more tipps
if
possible.
I found how to set the log to debug level but not what to enter in read
/write trace. Any special variables?
Can I specify a file somewhere, where the log gets written to?
Anyway here´s the two main reaction cases
1)
Cessna 172 skyhawk 1981 model
Airport KFSO
Runway default
CMDline:
C:\Programme\FlightGear\bin\Win32\fgfs.exe
--fg-root=C:\Programme\FlightGear\data
--fg-scenery= C:\Programme\FlightGear\data\Scenery
--airport-id=KSFO
--aircraft=c172p
--control= keyboard
--disable-random-objects
--disable-specular-highlight
--disable-ai-models
--disable-clouds
--geometry=800X600
--log-level=debug
Log around the Error
Initialize Subsystems
Adding subsystem interpolator
Adding subsystem properties
Reading materials from C:/Programme/FlightGear/data/materials.xml
Skipping bad material entry params
C:/Programme/FlightGear/data/Textures/Runway/grass_rwy.rgb
Loading material grass_rwy
C:/Programme/FlightGear/data/Textures/Runway/dirt_rwy.rgb
Loading material dirt_rwy
C:/Programme/FlightGear/data/Textures/Runway/lakebed_taxiway.rgb
Loading material lakebed_taxiway
C:/Programme/FlightGear/data/Textures.high/Runway/pa_taxiway.rgb
Loading material pa_taxiway
C:/Programme/FlightGear/data/Textures.high/Runway/pa_tiedown.rgb
Loading material pa_tiedown
C:/Programme/FlightGear/data/Textures.high/Runway/pa_dspl_thresh.rgb
Loading material pa_dspl_thresh
C:/Programme/FlightGear/data/Textures.high/Runway/pa_dspl_arrows.rgb
Unknown exception in the main loop. Aborting...
Possible cause: No such file or directory
Remark: file
C:/Programme/FlightGear/data/Textures.high/Runway/pa_dspl_arrows.rgb
Is present in the directory and 198 kb in size.
2)
Piper Cherokee Warrior II (1979 model)
Airport KFSO
Runway 28R
CMDLine:
C:\Programme\FlightGear\bin\Win32\fgfs.exe
--fg-root=C:\Programme\FlightGear\data
--fg-scenery= C:\Programme\FlightGear\data\Scenery
--airport-id=KSFO
--runway=28R
--aircraft=pa28-161
--control= keyboard
--disable-random-objects
--disable-specular-highlight
--disable-ai-models
--disable-clouds
--geometry=800X600
--log-level=debug
Log around the Error
Elapsed time interval is 138000,previous remainder is 7343
Model iterations needed = 17, new remainder = 3677
Updating adjusted fog paramters
Interpolate <>: lookup error, x to small = -9.68574
Interpolate <>: lookup error, x to small = -6.68574
FGTileMgr::update<>
State==Running
Unkonwn exception in the main loop. Aborting...
Possible cause: No error
Deleting a
sample /* (repeated
15 times, so 16 alltogether,
looks like this happens in the last
iteration)
I will try and update the matrox driver too.
Thanks
Best regards
Denise
-----Ursprüngliche Nachricht-----
Von: [EMAIL PROTECTED]
[mailto:
[EMAIL PROTECTED]] Im Auftrag von Melchior
FRANZ
Gesendet: Samstag, 9. Juli 2005 15:45
An: [email protected]
Betreff: [Flightgear-users] Re:
FG 0.9.8.a - runtime error on win 2K
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
_______________________________________________
Flightgear-users mailing list
[email protected]
http://mail.flightgear.org/mailman/listinfo/flightgear-users
2f585eeea02e2c79d7b1d8c4963bae2d
