> After 18 minutes sitting on the runway with the altimeter setting > matching the current METAR, the altimeter is still showing 100 ft too high. > > Questions: > Q1: Since there has not been a METAR change, why is interpolation > smoothing necessary at launch. > Q2: The rate of interpolation seems excruciatingly slow. Can this be > increased? I'm off for work right now and can't look into it. You should see the raw data in /environment/metar
>From there it gets interpolated over time into /environment/config/aloft[n] and /environment/config/boundary[n] This is done in $FGDATA/Environment/metarinterpolator.xml >From here, the code in environment_ctrl.cxx interpolates over altitude/elevation into /environment/config/interpolated without any interpolation over time. The last step is done in $FGDATA/Environment/interpolator.xml, this interpolates over time into /environment A1: This is on my todo-list and needs some thinking about. A2: That's easy, the timing rates are in the mentioned xml-files. They definitely need some tuning and I am open for suggestions. Greetings, 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
