On Sunday 13 January 2008 06:46, K. Hoercher wrote:
> On Sat, Jan 12, 2008 at 09:22:15PM +, 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, re
On Sunday 13 January 2008 05:14, Ron Jensen wrote:
> On Sat, 2008-01-12 at 21:22 +, LeeE wrote:
> > Oops - forgot to mention also that with '--log-level=info' the
> >
> > 'Processing registration HA-LHA with callsign MAH096/5'
> >
> > type messages still seem to be continuously output. Is thi
On Sat, Jan 12, 2008 at 09:22:15PM +, 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()
On Sat, 2008-01-12 at 21:22 +, LeeE wrote:
> Oops - forgot to mention also that with '--log-level=info' the
>
> 'Processing registration HA-LHA with callsign MAH096/5'
>
> type messages still seem to be continuously output. Is this right?
>
> It makes the output from --log-level=info pr
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:
> > > Spoke too soon - I thought I'd update SG & FG from cvs before
> > > trying this and now FG won't get past the 'loading scenery
> > > objects' phase.
On Saturday 12 January 2008 15:28, Curtis Olson wrote:
> On Jan 11, 2008 7:09 PM, LeeE wrote:
> > Spoke too soon - I thought I'd update SG & FG from cvs before
> > trying this and now FG won't get past the 'loading scenery
> > objects' phase.
>
> My understanding is that OSG 2.2.0 and earlier has s
On Jan 11, 2008 7:09 PM, LeeE wrote:
> Spoke too soon - I thought I'd update SG & FG from cvs before trying
> this and now FG won't get past the 'loading scenery objects' phase.
My understanding is that OSG 2.2.0 and earlier has some bugs that cause
problems with the new OSG random objects code.
On Friday 11 January 2008 23:49, LeeE wrote:
> On Friday 11 January 2008 21:50, Curtis Olson wrote:
> > On Jan 11, 2008 3:14 PM, Roy Vegard Ovesen wrote:
> > > On Friday 11 January 2008, LeeE wrote:
> > > > I've had a look at the relevant code but as I'm not up on
> > > > c++ I'm not sure about wha
On Friday 11 January 2008 21:50, Curtis Olson wrote:
> On Jan 11, 2008 3:14 PM, Roy Vegard Ovesen wrote:
> > On Friday 11 January 2008, LeeE wrote:
> > > I've had a look at the relevant code but as I'm not up on c++
> > > I'm not sure about what I'm looking at but at lines 798-802
> > > there's:
>
On Friday 11 January 2008, Curtis Olson wrote:
> On Jan 11, 2008 3:14 PM, Roy Vegard Ovesen wrote:
> > Try commenting out the call to build() from the code that you quoted
> > above.
> > build() is called inside init(), so there should be no need to call it
> > again
> > after init().
>
> I suspect
On Jan 11, 2008 3:14 PM, Roy Vegard Ovesen wrote:
> On Friday 11 January 2008, LeeE wrote:
> > I've had a look at the relevant code but as I'm not up on c++ I'm
> > not sure about what I'm looking at but at lines 798-802 there's:
> >
> > void FGXMLAutopilot::reinit() {
> > components.clear();
On Friday 11 January 2008, LeeE wrote:
> I've had a look at the relevant code but as I'm not up on c++ I'm
> not sure about what I'm looking at but at lines 798-802 there's:
>
> void FGXMLAutopilot::reinit() {
> components.clear();
> init();
> build();
> }
>
> I could find init() & buil
Hi all,
I've been experiencing some more weird behaviour from pid
controllers and filters.
I had a pid controller that was working ok (but had some room for
further fine-tuning) but after amending the config and re-loading
the autopilot it seemed to be working randomly. I reverted back to
th
13 matches
Mail list logo