Hi Stuart, I saw the variable wind in the METAR after I had posted, it is indeed a red herring. It happens (as you can see with Georg's post) no matter what the wind.
We have some more information from IRC. The properties you asked for don't change, as you're aware, but some other properties exhibit interesting behaviors. /environment/wind-from-heading-deg is the one flopping back and forth from e.g. 270 and 280. This corresponds to the windsock dance. /environment/config/boundary/entry/wind-from-heading-deg stays at 270. If you change this value, it ramps back to 270 smoothly, which I assume is the intended behavior. /environment/config/boundary/entry[1]/wind-from-heading-deg stays at 280 (10 degrees difference). If you change this one, it snaps back immediately. If you change entry[0], then this one changes as well to maintain the 10 degrees separation, and they both ramp together back to 270/280. As you can see, /environment/wind-from-heading-deg flips back and forth between the values of the boundary entries. Hopefully that gives you a clue as to what's going on. Thanks! On 8/9/07, Stuart Buchanan <[EMAIL PROTECTED]> wrote: > > Hi Hans, Georg, > > --- Hans Fugal wrote: > > Hi Stuart, > > On 8/8/07, Stuart Buchanan wrote: > > > I'd be very grateful if you could help me diagnose the problem, as I > > did quite a lot of testing, but didn't encounter this myself. > > > > Happy to help. > > > > > One possibility is that my interpolation is "fighting" with something > > else trying to write to the weather properties. > > Thanks very much for the log files from you both. From what I can see, the > interpolation itself looks fine, except that that it is continually > writing the final wind values. I think there must be something fighting > the interpolation, possibly to add some variation. However, as it isn't > writing to the property itself (otherwise we'd see the other value being > written), I wonder if it is the function that is tied to the "get" of the > property? > > Re-reading the code, I think continual writing of the wind values might > represent a small bug in that the inteprolation code doesn't first check > if the wind is already correct, but I wouldn't expect that to result in > any osscillations. > > Hans's log showed the wind varying (27012KT 240V310), which I initially > thought might be related, but Georg's log doesn't show this, so I think > that is probably a red herring. > > I will investigate further myself. Unfortunately I am away from my FG > computer at the moment, so I may not manage to look at it in more detail > until the weekend. > > Thanks > > -Stuart > > > > ___________________________________________________________ > Yahoo! Mail is the world's favourite email. Don't settle for less, sign up for > your free account today > http://uk.rd.yahoo.com/evt=44106/*http://uk.docs.yahoo.com/mail/winter07.html > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > -- Hans Fugal Fugal Computing ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
