Hello Curtis: Windows comes with a debugger. It's an operation in from the IE browser > Internet Options > Advanced then you can able or disable bugging information. I use it a lot because of the vast number of sites where the creators have no idea how to set up script! It will pinpoint the line and the error. Is this what you have in mind?
By the way, how do I get to the "Nimitz" or rather where is it? Thank you Martin -----Original Message----- From: Curtis L. Olson [mailto:[EMAIL PROTECTED] Sent: Monday, November 21, 2005 7:23 PM To: FlightGear user discussions Subject: Re: [Flightgear-users] Windows FGv9.9 and FGTools - Help Me to HelpYou dene maxwell wrote: > Hi > What happens in the code after the "Generating Sky Elements" message > is displayed? What external elements could influence the program's > behaviour in this area? (Screen Res, Clouds, computer peripherals..what?) > > I would down load the source files but I only have dial-up access and > would still be downloading it when the discussion was about v2.9.9!!! > > I really want to help, but need some guidance to get started.... Perhaps turn up the logging level so you can get more fine grained (and a higher volume of) messages and that might isolate your crash a bit more. Also useful would be to run the code in a debugger and get the exact location of the crash, but that's probably beyond what we can ask of non-developers (especially on windows platforms that don't ship with any kind of default compiler or debugger.) Curt. -- Curtis Olson http://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text: 2f585eeea02e2c79d7b1d8c4963bae2d _______________________________________________ Flightgear-users mailing list [email protected] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
