On Sunday 13 January 2008 06:46, K. Hoercher wrote: > On Sat, Jan 12, 2008 at 09:22:15PM +0000, LeeE wrote: > > On Saturday 12 January 2008 21:12, LeeE wrote: > > > On Saturday 12 January 2008 15:28, Curtis Olson wrote: > > > > On Jan 11, 2008 7:09 PM, LeeE wrote: > > > >From just a quick check, removing the explicit call to > > > > build() after > > > > > > init() in reinit() seems to work here:) > > > > > > New configs seems to be read in ok when the autopilot is > > > updated via the menu - I deliberately drove an controller > > > into oscillating and backed it back out again. Didn't notice > > > the filter > > > output 'oscillating' either. That was just a few minutes > > > check though - bit short of time atm. > > > > > > Can some other people try the same change in xmlauto.xml > > > (comment out/remove the call to build() at line 801) and > > > confirm it's ok? > > I'd like to confirm. I had been learning/tuning/messing around > with some autopilot here too. Before I could come down to a firm > conclusion I seemed to have odd effects on reloading changed > configurations, like apparently "fighting" of different > controllers. When I noticed your observation here, I successfully > tried the suggested commenting out (cvs of 28122007) and at least > now the stuff seems to work and does also pick up changed > configurations when reloading. > > > It makes the output from --log-level=info pretty useless > > because everything else is scrolled away - I use a 2k line > > scroll buffer but even so, anything from start-up is very > > quickly lost. > > > > LeeE > > You could single out the logging class (seemingly only at > runtime) by manipulating /sim/logging/classes. On a side note: I > don't think the usage of SG_ALL for a couple of SG_LOG statements > is a desired one. They pretty much defy that filtering out > especially at higher debug levels. Imho SG_ALL is not (or should > not be) a valid class for SG_LOG but a mere convenience on the > logging output side of things. > > regards > K. Hoercher
Thanks for confirming - this bug has been troubling me for some time:) As this bug, and it's associated fix, will only have an effect when the autopilot is reloaded i.e. when reinit() is called, it won't have any effect in normal operation and existing autopilot controllers etc. should continue to function exactly as before. In view of this, and if no one else can find any problems with it, could this fix be applied? It's likely that some people will be developing aircraft against SG/FG v1.0 (plib) so it should probably be applied to that branch as well, in readiness for the next update to v1.0. LeeE ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
