Hi all, UltraZexe Zexeonyo wrote: > In Windows, the graphics are great! With all the rendering options available, > I am able to run FG at around 50 FPS, on average that is. However, unlike > the OS X version, metar doesn't seem to want to update automatically. With > everything enabled (fetch-weather, or real-time weather fetch) and METAR > selected, metar doesn't want to update. It freezes and no matter how many > times I click Metar, over and over again, over a period of an hour, the metar > doesn't update.
I may have the same METAR issue since FlightGear v1.0.0 for Windows. I suspect that FG users whose time zone setting of Windows PC between GMT+4 to GMT+13 are often affected by this problem. My time zone setting on Windows XP is usually set to Japanese Standard Time (JST = GMT+9). By changing <metar-max-age-min type="long"> value in $FG_ROOT/preferences.xml from 240 (default) to 780 (540 mins longer than default), metar issue was dissapeared for me. So, as a quick fix, try to change your <metar-max-age-min> value in your preferences.xml. Note that I'm using a dual-boot PC with Windows and Ubuntu, and Ubuntu has no metar issue (at least for my PC). Using following options and <metar-max-age-min> value of 240, I tested both time zone setting of JST and GMT using my Windows XP machine: --enable-real-weather-fetch --log-level=warn --airport=KSFO --aircraft=UFO In case of JST, just after launched FlightGear, /environment/metar/real-metar was: 2010/01/13 14:56 KSFO 131456Z 25005KT 10SM FEW007 13/09 A3008 RMK AO2 SLP187 T01280094 53031 After 2 mins flight from KSFO with UFO, following conslole messages appeard: METAR data too old (559 min). no metar at station = KSTS METAR data too old (556 min). no metar at station = KSFO METAR data too old (559 min). no metar at station = KOAK METAR data too old (559 min). no metar at station = KCCR METAR data too old (558 min). no metar at station = KAPC METAR data too old (558 min). no metar at station = KHWD METAR data too old (556 min). no metar at station = KUKI METAR data too old (559 min). no metar at station = KLVK METAR data too old (557 min). no metar at station = KSUU METAR data too old (556 min). no metar at station = KNUQ METAR data too old (560 min). Error fetching live weather data: More than 10 stale METAR messages in a row. Ch eck your system time! Stop fetching data permanently. These message tell that all METAR datas were judged to be 540 min. older than their real age. In case of GMT, just after launched FlightGear, /environment/metar/real-metar was: 2010/01/13 14:56 KSFO 131456Z 25005KT 10SM FEW007 13/09 A3008 RMK AO2 SLP187 T01280094 53031 2 minutes later: 2010/01/13 14:53 KSTS 131453Z 22003KT 6SM BR SCT020 BKN030 10/09 A3003 RMK AO2 SLP164 T01000089 53025 Pretty good! Cheers, Toshi ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
