Re: [Flightgear-devel] Automatic runway selection broken by weather interpolation
Hi Guys, I think I've found a bug in the new weather environment code. I started up at Austin Bergstrom International (KAUS), a fairly large Texas airport with runways 17L/R, 35L/R. The METAR had wind of 9 knots at 190 degrees. I would expect FG to start on runway 17. Instead it starts on 35L. Looking at the Global Weather dialog immediately after startup shows the wind passing through 260 degrees as it veers around to 190. I suspect that when the runways selection code is run, the wind is still at 0 heading, causing runway 35L to be chosen. That's a timing problem. The METAR arrives _after_ /sim/signals/nasal-dir- initialized is fired which triggers the runway selection code in startup.nas. This code uses the raw, not interpolated wind values from the metar, so it's definitely not an interpolation issue. I am currently working on a solution. Given this and the previously reported problem with pressure settings (which still changes too slowly IMO - the pressure is often still changing after I've set the altimeter) I think we need to be explicitly setting the environment on initialization, rather than relying on the interpolation XML to interpolate to the current METAR or config. This needs some thinking about when interpolation is required and when it should be avoided. The scenarios to think about are: - System startup - System reset - Transition from manual input to real-weather - Transition from real-weather to manual input - Change in manual-input data - Teleporting to another position - to be continued And for each scenario probably distinguish between in-air and on-ground. Any suggestion how to handle these is appreciated. Torsten -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Automatic runway selection broken by weather interpolation
That's a timing problem. The METAR arrives _after_ /sim/signals/nasal-dir- initialized is fired which triggers the runway selection code in startup.nas. This code uses the raw, not interpolated wind values from the metar, so it's definitely not an interpolation issue. I am currently working on a solution. The timing issue should be fixed now (needs fg git-pull). The initialization sequence of subsystems now waits for arrival of a METAR. Please check, if this works correctly. Torsten -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Automatic runway selection broken by weather interpolation
Hi Guys, I think I've found a bug in the new weather environment code. I started up at Austin Bergstrom International (KAUS), a fairly large Texas airport with runways 17L/R, 35L/R. The METAR had wind of 9 knots at 190 degrees. I would expect FG to start on runway 17. Instead it starts on 35L. Looking at the Global Weather dialog immediately after startup shows the wind passing through 260 degrees as it veers around to 190. I suspect that when the runways selection code is run, the wind is still at 0 heading, causing runway 35L to be chosen. Given this and the previously reported problem with pressure settings (which still changes too slowly IMO - the pressure is often still changing after I've set the altimeter) I think we need to be explicitly setting the environment on initialization, rather than relying on the interpolation XML to interpolate to the current METAR or config. -Stuart -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
