Re: [Flightgear-devel] Props: /environment/wind-* obsolete?
Ahoy Torsten, I think I figured out what bugged me here. Last night I ran FG 2.2.0 and it still had the issue with the non working real-weather. By looking at its .fgfsrc I realised there is a second still enabled entry for '--random-wind'. Removing it also removed the issue. I must have 'accidently' removed it from the FG git .fgfsrc and that's why it suddenly started working. Would an option, --random-wind, even be necessary with the new weather stuff or could it be safely removed? (Which I would then, if I could. ;-)) Griassla Alex Am Tue, 3 May 2011 22:32:11 +0200 schrieb Alex D-HUND f...@beggabaur.de: Last night, when I was flying around LOWI, suddenly the textures for the cloud layers changed. I checked the values for the wind in prop tree and they were updating according to the ones of the real-weather metar string. After restarting FG I was positively surprised that it still worked. Checking the console output of the session where I realised that it suddenly worked brought up nothing. Log level was set to 'debug' though there was not much output. And even less that could have been related to this besides: Loading local weather routines... Compatibility layer: testing for hard coded support * can set light saturation:yes * hard coded terrain presampling: yes * terrain presampling initialized: no * can disable global weather: yes Compatibility layer: tests done. I was to dumb to think about saving the complete output to a file though. OTOH I am very certain that I didn't miss anything because there really wasn't much there. I have absolutely no idea what could have changed here. I am very certain that I had not had touched fgdata since my previous message, just because I did not have time for FG at all. Only thing that was altered is .fgfsrc of which you'll find a copy enclosed. -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Props: /environment/wind-* obsolete?
I would assume that random-wind is there by intention and I wouldn't remove it just to prevent user-error ;-) Good to hear realwx is working now for you. Torsten Ahoy Torsten, I think I figured out what bugged me here. Last night I ran FG 2.2.0 and it still had the issue with the non working real-weather. By looking at its .fgfsrc I realised there is a second still enabled entry for '--random-wind'. Removing it also removed the issue. I must have 'accidently' removed it from the FG git .fgfsrc and that's why it suddenly started working. Would an option, --random-wind, even be necessary with the new weather stuff or could it be safely removed? (Which I would then, if I could. ;-)) Griassla Alex Am Tue, 3 May 2011 22:32:11 +0200 schrieb Alex D-HUND f...@beggabaur.de: Last night, when I was flying around LOWI, suddenly the textures for the cloud layers changed. I checked the values for the wind in prop tree and they were updating according to the ones of the real-weather metar string. After restarting FG I was positively surprised that it still worked. Checking the console output of the session where I realised that it suddenly worked brought up nothing. Log level was set to 'debug' though there was not much output. And even less that could have been related to this besides: Loading local weather routines... Compatibility layer: testing for hard coded support * can set light saturation:yes * hard coded terrain presampling: yes * terrain presampling initialized: no * can disable global weather: yes Compatibility layer: tests done. I was to dumb to think about saving the complete output to a file though. OTOH I am very certain that I didn't miss anything because there really wasn't much there. I have absolutely no idea what could have changed here. I am very certain that I had not had touched fgdata since my previous message, just because I did not have time for FG at all. Only thing that was altered is .fgfsrc of which you'll find a copy enclosed. --- --- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Props: /environment/wind-* obsolete?
And even less that could have been related to this besides: Loading local weather routines... Compatibility layer: testing for hard coded support * can set light saturation:yes * hard coded terrain presampling: yes * terrain presampling initialized: no * can disable global weather: yes Compatibility layer: tests done. Identifies itself as 'local weather' and is local weather - unless you started it from the menu explicitly, it is quiet and does nothing. If you started it, it would be capable of altering the winds to something else than the METAR, but you'd have seen lots of rather different clouds... The message you see indicates that your binary has lots of features not in a 2.0.0 binary, but that you haven't initialized terrain presampling in the commandline. Next thing I tested was Torstens metar string which still failed. Again I made some screenshots, one with working real-weather [4] and one with the said metar [5]. Gauging from the screenshots, it seems the manually entered METAR isn't actually parsed - note that not only the winds are not set, but that also the cloud layers are all 'clear' in spite of FEW070 BKN130 - not so for the automatically fetched METAR. Also, the tickbox 'Data is valid' isn't ticked in the second case. So, it seems a parsing problem - maybe check the contents of 'Environment/metar/' to see how it's chopped up. Should one be worried that in all cases 'weather-scenario' is set to 'Fair weather'? Cheers, * Thorsten -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Props: /environment/wind-* obsolete?
Am Wed, 04 May 2011 10:27:07 +0200 schrieb Torsten Dreyer tors...@t3r.de: I think it's an issue with enclosing the string with Yes it is, without them it works pretty well. Sorry for the trouble I caused, I think life is playing jokes on me. :-/ Alex -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Props: /environment/wind-* obsolete?
Am Sun, 24 Apr 2011 16:00:59 +0200 schrieb Torsten Dreyer tors...@t3r.de: Your METAR reports VRB07G18 which is variable at 7kt with gusts up to 18kts. Our current weather implementation is not very creative about variable winds. They are currently picked as north at constant 7kts. This should result in /environment/wind-speed-kt=7 and /environment/wind-from-heading-deg=0 (and this is what I observe on my machine when setting your LOWI METAR). Could you please check the entire weather-path when starting fgfs --metar=LOWI 123456Z VRB07G18KT FEW070 BKN130 18/06 Q1013 Ok, and, to be more precise as in my former posts (oblivious me), I don't have any other weather related option in use. Like --random-wind or --turbulence=. I start with option --timeofday=noon. I am not certain if this matters but I read something about a 240 minutes 'expiration' or such for the METAR string. At least screenshot [1] is inside that timeframe. $ fgfs --disable-real-weather-fetch \ --metar=LOWI 123456Z VRB07G18KT FEW070 BKN130 18/06 Q1013 /environment/metar/data (LOWI 123456Z VRB07G18KT FEW070 BKN130 18/06 Q1013) 1.) /environment/metar/base-wind-from-north-fps=11.8 /environment/metar/base-wind-from-east-fps=0.0 /environment/metar/base-wind-from-north-fps (0) /environment/metar/base-wind-from-east-fps (0) Hmh, I guess the filter is not the issue. 2.) /environment/config/boundary/entry[0]/wind-from-north-fps=11.8 /environment/config/boundary/entry[0]/wind-from-east-fps=0.0 /environment/config/boundary/entry/wind-from-north-fps (-9.301369226e-16) /environment/config/boundary/entry/wind-from-east-fps (-5.063429571) 3.) /environment/config/interpolated/wind-from-north-fps=11.8 /environment/config/interpolated/wind-from-east-fps=0.0 /environment/config/interpolated/wind-from-north-fps (0.00714730596) /environment/config/interpolated/wind-from-east-fps (-5.104049682) 4.) /environment/wind-from-north-fps=11.8 /environment/wind-from-east-fps=0.0 /environment/wind-from-north-fps (0.2743804315) /environment/wind-from-east-fps (0.06240915831) From step 2. to 4., these values are fed through a low-pass filter and values may vary over time but should approach the numbers above. Please also check that /environment/presets/wind-override=false (or empty) /environment/presets does not exist /environment/config/presets/wind-override () /environment/config/enabled=true /environment/config/enabled (true) /environment/params/metar-updates-environment=true /environment/params/metar-updates-environment (true) Thank you Alex [1] http://fgfs.beggabaur.de/daten/fgfs-metar01.jpg Torsten Ahoy Torsten, thank you for taking your time on this issue and sorry for bothering you again. ;-) The HUD showing those values is a personal modification. I made another screenshot to confirm that it is just showing the roundet to interger values of the named properties [1] and you'll find the xml code enclosed. [1] http://fgfs.beggabaur.de/daten/fgfs-metar03.jpg Am Sat, 23 Apr 2011 21:25:17 +0200 schrieb Torsten Dreyer tors...@t3r.de: To compensate the lack of feel and indirect visual indicators of the wind conditions in the simulator I am monitoring the properties /environment/wind-from-heading-deg and wind-speed-kt. This worked out pretty good the past two years. I cannot tell when it stopped working but last night I realised it didn't anymore, see marked values at screenshot [1]. The ones from the HUD (255@25kt) are totally different from the ones in the METAR string (33007KT). Please, could someone point to the actual used properties for the wind conditions right next to the aircraft? Thanks. The wind at the aircraft's location is still in /environment/wind-from-heading-deg et. al. This does not necessarily match the reported wind in the METAR as it changes with altitude. However, I can't figure out from your screenshot why your hud reports 255@25 as it does not come close to any of the winds in boundary and aloft layers. Being a complete HUD ignorant: how did you manage to make the HUD show wind, anyway? If I cycle through the HUD styles (h-key), there is no such information!? Torsten -- Fulfilling the Lean Software Promise Lean software platforms are now widely adopted and the benefits have been demonstrated beyond question. Learn why your peers are replacing JEE containers with lightweight application servers - and what you can gain from the move. http://p.sf.net/sfu/vmware-sfemails ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Props: /environment/wind-* obsolete?
Ah - was somewhat puzzled that I wasn't able to locate a HUD with a configured wind label :-P Your screenshot shows, that the HUD displays the correct wind values: 270@1, so this part looks good. Your METAR reports VRB07G18 which is variable at 7kt with gusts up to 18kts. Our current weather implementation is not very creative about variable winds. They are currently picked as north at constant 7kts. This should result in /environment/wind-speed-kt=7 and /environment/wind-from-heading-deg=0 (and this is what I observe on my machine when setting your LOWI METAR). Could you please check the entire weather-path when starting fgfs --metar=LOWI 123456Z VRB07G18KT FEW070 BKN130 18/06 Q1013 1.) /environment/metar/base-wind-from-north-fps=11.8 /environment/metar/base-wind-from-east-fps=0.0 2.) /environment/config/boundary/entry[0]/wind-from-north-fps=11.8 /environment/config/boundary/entry[0]/wind-from-east-fps=0.0 3.) /environment/config/interpolated/wind-from-north-fps=11.8 /environment/config/interpolated/wind-from-east-fps=0.0 4.) /environment/wind-from-north-fps=11.8 /environment/wind-from-east-fps=0.0 From step 2. to 4., these values are fed through a low-pass filter and values may vary over time but should approach the numbers above. Please also check that /environment/presets/wind-override=false (or empty) /environment/config/enabled=true /environment/params/metar-updates-environment=true Torsten Ahoy Torsten, thank you for taking your time on this issue and sorry for bothering you again. ;-) The HUD showing those values is a personal modification. I made another screenshot to confirm that it is just showing the roundet to interger values of the named properties [1] and you'll find the xml code enclosed. [1] http://fgfs.beggabaur.de/daten/fgfs-metar03.jpg Am Sat, 23 Apr 2011 21:25:17 +0200 schrieb Torsten Dreyer tors...@t3r.de: To compensate the lack of feel and indirect visual indicators of the wind conditions in the simulator I am monitoring the properties /environment/wind-from-heading-deg and wind-speed-kt. This worked out pretty good the past two years. I cannot tell when it stopped working but last night I realised it didn't anymore, see marked values at screenshot [1]. The ones from the HUD (255@25kt) are totally different from the ones in the METAR string (33007KT). Please, could someone point to the actual used properties for the wind conditions right next to the aircraft? Thanks. The wind at the aircraft's location is still in /environment/wind-from-heading-deg et. al. This does not necessarily match the reported wind in the METAR as it changes with altitude. However, I can't figure out from your screenshot why your hud reports 255@25 as it does not come close to any of the winds in boundary and aloft layers. Being a complete HUD ignorant: how did you manage to make the HUD show wind, anyway? If I cycle through the HUD styles (h-key), there is no such information!? Torsten - - Fulfilling the Lean Software Promise Lean software platforms are now widely adopted and the benefits have been demonstrated beyond question. Learn why your peers are replacing JEE containers with lightweight application servers - and what you can gain from the move. http://p.sf.net/sfu/vmware-sfemails ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Fulfilling the Lean Software Promise Lean software platforms are now widely adopted and the benefits have been demonstrated beyond question. Learn why your peers are replacing JEE containers with lightweight application servers - and what you can gain from the move. http://p.sf.net/sfu/vmware-sfemails ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Props: /environment/wind-* obsolete?
To compensate the lack of feel and indirect visual indicators of the wind conditions in the simulator I am monitoring the properties /environment/wind-from-heading-deg and wind-speed-kt. This worked out pretty good the past two years. I cannot tell when it stopped working but last night I realised it didn't anymore, see marked values at screenshot [1]. The ones from the HUD (255@25kt) are totally different from the ones in the METAR string (33007KT). Please, could someone point to the actual used properties for the wind conditions right next to the aircraft? Thanks. The wind at the aircraft's location is still in /environment/wind-from-heading-deg et. al. This does not necessarily match the reported wind in the METAR as it changes with altitude. However, I can't figure out from your screenshot why your hud reports 255@25 as it does not come close to any of the winds in boundary and aloft layers. Being a complete HUD ignorant: how did you manage to make the HUD show wind, anyway? If I cycle through the HUD styles (h-key), there is no such information!? Torsten -- Fulfilling the Lean Software Promise Lean software platforms are now widely adopted and the benefits have been demonstrated beyond question. Learn why your peers are replacing JEE containers with lightweight application servers - and what you can gain from the move. http://p.sf.net/sfu/vmware-sfemails ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Props: /environment/wind-* obsolete?
Ahoy Torsten, thank you for taking your time on this issue and sorry for bothering you again. ;-) The HUD showing those values is a personal modification. I made another screenshot to confirm that it is just showing the roundet to interger values of the named properties [1] and you'll find the xml code enclosed. [1] http://fgfs.beggabaur.de/daten/fgfs-metar03.jpg Am Sat, 23 Apr 2011 21:25:17 +0200 schrieb Torsten Dreyer tors...@t3r.de: To compensate the lack of feel and indirect visual indicators of the wind conditions in the simulator I am monitoring the properties /environment/wind-from-heading-deg and wind-speed-kt. This worked out pretty good the past two years. I cannot tell when it stopped working but last night I realised it didn't anymore, see marked values at screenshot [1]. The ones from the HUD (255@25kt) are totally different from the ones in the METAR string (33007KT). Please, could someone point to the actual used properties for the wind conditions right next to the aircraft? Thanks. The wind at the aircraft's location is still in /environment/wind-from-heading-deg et. al. This does not necessarily match the reported wind in the METAR as it changes with altitude. However, I can't figure out from your screenshot why your hud reports 255@25 as it does not come close to any of the winds in boundary and aloft layers. Being a complete HUD ignorant: how did you manage to make the HUD show wind, anyway? If I cycle through the HUD styles (h-key), there is no such information!? Torsten -- Fulfilling the Lean Software Promise Lean software platforms are now widely adopted and the benefits have been demonstrated beyond question. Learn why your peers are replacing JEE containers with lightweight application servers - and what you can gain from the move. http://p.sf.net/sfu/vmware-sfemails ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel !-- Wind -- label nameWind direction/name x95/x y-204/y width1/width height1/height input property/environment/wind-from-heading-deg/property factor1/factor damp0.0/damp /input format%5.0f/format prefixWind/prefix halignleft/halign /label label nameWind speed/name x177/x y-204/y width1/width height1/height input property/environment/wind-speed-kt/property factor1/factor damp0.0/damp /input format%3.0f kt/format prefix@/prefix halignright/halign /label-- Fulfilling the Lean Software Promise Lean software platforms are now widely adopted and the benefits have been demonstrated beyond question. Learn why your peers are replacing JEE containers with lightweight application servers - and what you can gain from the move. http://p.sf.net/sfu/vmware-sfemails___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
