Re: [Flightgear-devel] Re: very long startup time
On August 25, 2005 04:12 pm, AJ MacLeod wrote: I don't know if this is exactly what you noticed, but I've just found that with today's CVS, if you have real-weather-fetch true in preferences.xml, FG won't start properly at all, but hangs immediately after startup in a manner almost identical to the current cygwin problem. AJ I think that problem is due to metar data being too old. Ampere ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: very long startup time
On Thu, Aug 25, 2005 at 10:05:25AM -0700, Alex Romosan wrote: i've been looking at the metar code but it's a hopeless mess. Oh, thanks. So we can hope that you'll provide something better and add it to the long list of your quality contributions. (Did you contribute *anything* so far?) m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: very long startup time
On Friday 26 August 2005 07:34, Ampere K. Hardraade wrote: I think that problem is due to metar data being too old. I don't know; however, 0.9.8 seems perfectly happy with the same data. Also, I've not once managed to get yesterdays' CVS to start with METAR enabled - surely the data would be unlikely to be out of date for every station (in several countries) I've tried over almost 24 hours? I've just noticed that starting 0.9.8 at KSFO I get the following output in the terminal Altitude = 13 Temp at alt (C) = 12 Temp sea level (C) = 12.0251 Altitude = 13 Dewpoint at alt (C) = 11 Dewpoint at sea level (C) = 11.0026 And seconds later, starting yesterdays CVS I get Altitude = 13 Temp at alt (C) = 0 Temp sea level (C) = 0.0240539 Altitude = 13 Dewpoint at alt (C) = 0 Dewpoint at sea level (C) = 0.0026 So something's messed up there somewhere; does FG just set the variables it thinks are out of date to zero? No proxies of any sort involved here I should add. Anyway, since it's probably outside my capabilities to fix it, I'm sticking to testing and reporting. Would be happy to try any tests or patches required to get to the bottom of it though. AJ ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: very long startup time
On Wed, Aug 24, 2005 at 01:47:12PM -0700, Alex Romosan wrote: http://weather.noaa.gov/pub/data/observations/metar/stations/KSFO.TXT 2005/08/24 17:56 KSFO 241756Z 04005KT 10SM FEW010 19/12 A2983 RMK AO2 SLP101 T01940122 10194 20122 51005 but right now the time is: Wed Aug 24 20:45:35 UTC 2005 so this would make the metar data too old indeed. The date from the data set says when the data were acquired. If you are sure that your computer has the time correctly set, then this simply *is* old data. Could be that NOAA hasn't updated in time, or that you are running over a proxy that doesn't work correctly. Try without http proxy. m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: very long startup time
Alex Romosan wrote: code but it's a hopeless mess. in the meantime i've lost my temperature and visibility etc. (they are all set to zero). it must be some change i made but a cvs diff doesn't show any relevant changes. strange, very strange. I noticed this too. You will need to set the weather scenario to a different value than none. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: very long startup time
Erik Hofman wrote: Alex Romosan wrote: code but it's a hopeless mess. in the meantime i've lost my temperature and visibility etc. (they are all set to zero). it must be some change i made but a cvs diff doesn't show any relevant changes. strange, very strange. I noticed this too. You will need to set the weather scenario to a different value than none. Perhaps none is not the best default value to come up with? Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: very long startup time
On Thursday 25 August 2005 18:12, Erik Hofman wrote: I noticed this too. You will need to set the weather scenario to a different value than none. I don't know if this is exactly what you noticed, but I've just found that with today's CVS, if you have real-weather-fetch true in preferences.xml, FG won't start properly at all, but hangs immediately after startup in a manner almost identical to the current cygwin problem. AJ ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: very long startup time
On Tue, Aug 23, 2005 at 11:56:13AM +0200, Christian Mayer wrote: Melchior FRANZ schrieb: Check if your system time is set correctly. or it could ask an NTP-server for the correct time... but that's problaby going too far. That's definitely going too far. Much too far. The OS is supposed to deliver the right local time. We aren't going to add another security layer for people who are too lazy/stupid to maintain their operating system. But what I added on top of my TODO list is more verbose and helpful error messages, and saner timeout behaviour. m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: very long startup time
On Mon, Aug 22, 2005 at 03:03:11PM -0700, Alex Romosan wrote: looking at the trace logs it looks like fgfs goes through every metar station out there: Initializing environment subsystem 2005/08/22 14:56 KSFO 221456Z 0KT 10SM SCT007 OVC010 13/11 A2995 RMK AO2 SLP142 T01280106 53002 METAR from weather.noaa.gov METAR data too old no metar at metar = KSFO Check if your system time is set correctly. If it's running in the future or past, every metar data set will be too old/new and fgfs searches for an acceptable one. (It should probably stop trying after the first 10 failed sets.) m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: very long startup time
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Melchior FRANZ schrieb: On Mon, Aug 22, 2005 at 03:03:11PM -0700, Alex Romosan wrote: looking at the trace logs it looks like fgfs goes through every metar station out there: Initializing environment subsystem 2005/08/22 14:56 KSFO 221456Z 0KT 10SM SCT007 OVC010 13/11 A2995 RMK AO2 SLP142 T01280106 53002 METAR from weather.noaa.gov METAR data too old no metar at metar = KSFO Check if your system time is set correctly. If it's running in the future or past, every metar data set will be too old/new and fgfs searches for an acceptable one. (It should probably stop trying after the first 10 failed sets.) or it could ask an NTP-server for the correct time... but that's problaby going too far. CU, Chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (MingW32) iD8DBQFDCvK9lhWtxOxWNFcRAj3zAJ93ZV0x+zMqM+93TwvPrg9JPiUf0gCeMGL9 Z2CM5WoSuRpF/0w4M55GL1Q= =FSrU -END PGP SIGNATURE- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
