On Sun, 2007-02-11 at 00:16 +, leee wrote:
> I couldn't see a parameter to enable dynamic view in the command line but it
> seemed ok if I enabled it via the menu. The view pitched a small amount when
> I enabled it and pitched back when I disabled it.
>
> LeeE
>
Dynamic view from the com
On Saturday 10 February 2007 16:04, Ron Jensen wrote:
> On Sat, 2007-02-10 at 10:53 +0100, Roy Vegard Ovesen wrote:
> > On Saturday 10 February 2007 01:08, gh.robin wrote:
> > > Hello Roy,
> > > I do not notice any differences regarding /autopilot/new-config dir
> > > between first load values (af
I couldn't see a parameter to enable dynamic view in the command line but it
seemed ok if I enabled it via the menu. The view pitched a small amount when
I enabled it and pitched back when I disabled it.
LeeE
On Friday 09 February 2007 20:51, Maik Justus wrote:
> Hi LeeE,
>
> can you start fli
On Sun 11 February 2007 01:01, Roy Vegard Ovesen wrote:
> On Sunday 11 February 2007 00:29, gh.robin wrote:
>
> The autopilot is holding the wings level, right. I think characterizing
> this as "crazy" is very misleading. One might think that it was turning
> left and right.
Yes , in that case "
On Sunday 11 February 2007 00:29, gh.robin wrote:
> I have settled Heading Bug =180
> autopilot does not work (crazy)
>
> I get messages
> here an extract
>
> ..
> Updating Heading Bug Hold (DG based) Stage 2 Ts 0.017
> input = -0.128936 ref = 0
> ep_n = 0.1
On Sat 10 February 2007 10:53, Roy Vegard Ovesen wrote:
> On Saturday 10 February 2007 01:08, gh.robin wrote:
> > Hello Roy,
> > I do not notice any differences regarding /autopilot/new-config dir
> > between first load values (after FG loaded) and after reload autopilot.
> >
> > i get two pi-s
On Sat, 2007-02-10 at 10:53 +0100, Roy Vegard Ovesen wrote:
> On Saturday 10 February 2007 01:08, gh.robin wrote:
> > Hello Roy,
> > I do not notice any differences regarding /autopilot/new-config dir
> > between first load values (after FG loaded) and after reload autopilot.
> >
> > i get two
On Saturday 10 February 2007 01:08, gh.robin wrote:
> Hello Roy,
> I do not notice any differences regarding /autopilot/new-config dir
> between first load values (after FG loaded) and after reload autopilot.
>
> i get two pi-simple-controllers and sixteen pid-controllers.
OK, you said that th
On Sat 10 February 2007 01:15, gh.robin wrote:
> On Fri 9 February 2007 20:22, leee wrote:
> > It's difficult to imagine a system problem that might cause this
> > behaviour, in view of the fact that resetting appears to fix the problem.
> >
> > However, I know that there are a few problems that I'
On Fri 9 February 2007 20:22, leee wrote:
>
> It's difficult to imagine a system problem that might cause this behaviour,
> in view of the fact that resetting appears to fix the problem.
>
> However, I know that there are a few problems that I've seen here that no
> one else appears to have experi
On Fri 9 February 2007 20:04, Roy Vegard Ovesen wrote:
>
> Could you check the property browser before and after you reload the
> autopilot? Look at the /autopilot/new-config dir. Are all the controllers
> there prior to reloading the autopilot? (In the cd3 I see two
> pi-simple-controllers and si
Hi LeeE,
can you start flightgear with the bo105 and dynamic-view enabled? If the
view direction is ok during the first second or is it spinning around?
Maybe this bug has a similar cause.
Maik
leee schrieb am 09.02.2007 20:22:
> On Friday 09 February 2007 19:04, Roy Vegard Ovesen wrote:
>
On Friday 09 February 2007 19:45, Roy Vegard Ovesen wrote:
> On Friday 09 February 2007 20:22, leee wrote:
> > It's difficult to imagine a system problem that might cause this
> > behaviour, in view of the fact that resetting appears to fix the problem.
> >
> > However, I know that there are a few
On Friday 09 February 2007 20:22, leee wrote:
>
> It's difficult to imagine a system problem that might cause this behaviour,
> in view of the fact that resetting appears to fix the problem.
>
> However, I know that there are a few problems that I've seen here that no
> one else appears to have exp
On Friday 09 February 2007 19:04, Roy Vegard Ovesen wrote:
> On Friday 09 February 2007 19:26, gh.robin wrote:
> > Hello Roy ,
> > Every Aircraft which basicaly use the Generic autopilot (no KAP140 or
> > else).
> >
> > I tested it with a lot of the nice aircraft from Lee which do not work
> > and
On Friday 09 February 2007 19:26, gh.robin wrote:
> Hello Roy ,
> Every Aircraft which basicaly use the Generic autopilot (no KAP140 or
> else).
>
> I tested it with a lot of the nice aircraft from Lee which do not work
> and among the others examples
> the dc3 Autopilot is right with Altitude but
On Friday 09 February 2007 18:14, Roy Vegard Ovesen wrote:
> On Friday 09 February 2007 18:24, leee wrote:
> > Hi Roy,
> >
> > I am getting this with the SU-37 and I believe the version in cvs
> > displays the problems. This is a pretty complex A/P setup with cascading
> > up to three levels and i
On Fri 9 February 2007 18:07, Roy Vegard Ovesen wrote:
> On Friday 09 February 2007 02:54, Dave Perry wrote:
>
> I believe that the problem Gérard and Lee has seen is not specific to the
> KAP140 autopilot. apInit in kap140.nas _only_ initializes the properties
> that belong to the KAP140 autopilo
On Friday 09 February 2007 18:24, leee wrote:
>
> Hi Roy,
>
> I am getting this with the SU-37 and I believe the version in cvs displays
> the problems. This is a pretty complex A/P setup with cascading up to
> three levels and it also includes filters to un-tie some tied nodes so that
> I could u
On Friday 09 February 2007 17:07, Roy Vegard Ovesen wrote:
> On Friday 09 February 2007 02:54, Dave Perry wrote:
> > On Fri, 2007-02-09 at 00:25 +, leee wrote:
> > > Just checked again, with current cvs osg/simgear/flightgear, and I
> > > still got the same problems. As before, re-setting the
On Friday 09 February 2007 01:54, Dave Perry wrote:
> On Fri, 2007-02-09 at 00:25 +, leee wrote:
> > Just checked again, with current cvs osg/simgear/flightgear, and I still
> > got the same problems. As before, re-setting the A/P via the menu seems
> > to kick everything into life. There als
On Friday 09 February 2007 02:54, Dave Perry wrote:
> On Fri, 2007-02-09 at 00:25 +, leee wrote:
> > Just checked again, with current cvs osg/simgear/flightgear, and I still
> > got the same problems. As before, re-setting the A/P via the menu seems
> > to kick everything into life. There als
On Fri, 2007-02-09 at 00:25 +, leee wrote:
> Just checked again, with current cvs osg/simgear/flightgear, and I still got
> the same problems. As before, re-setting the A/P via the menu seems to kick
> everything into life. There also seems to be a random element to this
> problem - in ha
leee wrote:
> On Thursday 08 February 2007 23:22, gh.robin wrote:
>
> Just checked again, with current cvs osg/simgear/flightgear, and I still got
> the same problems. As before, re-setting the A/P via the menu seems to kick
> everything into life. There also seems to be a random element to
On Thursday 08 February 2007 23:22, gh.robin wrote:
> On Thu 8 February 2007 23:09, Martin Spott wrote:
> > "gh.robin" wrote:
> > > On Thu 8 February 2007 11:13, Thomas F?rster wrote:
> > > > I hit on a strange problem when using the --flight-plan commandline
> > > > option with the default c172. A
On Thu 8 February 2007 23:09, Martin Spott wrote:
> "gh.robin" wrote:
> > On Thu 8 February 2007 11:13, Thomas F?rster wrote:
> > > I hit on a strange problem when using the --flight-plan commandline
> > > option with the default c172. All controls are working except the
> > > ailerons, which makes
"gh.robin" wrote:
> On Thu 8 February 2007 11:13, Thomas F?rster wrote:
> > I hit on a strange problem when using the --flight-plan commandline option
> > with the default c172. All controls are working except the ailerons, which
> > makes flying around a bit challenging... ;-)
> If it is FG cvs
Am Donnerstag 08 Februar 2007 18:35 schrieb gh.robin:
> On Thu 8 February 2007 11:13, Thomas Förster wrote:
> ...
> If it is FG cvs with OSG, it is not a surprise to me, i told before on
> several topics regarding autopilot, that it is not working.
> Nobody but Lee answered to confirm that it is n
On Thu 8 February 2007 11:13, Thomas Förster wrote:
> Hi,
>
> I hit on a strange problem when using the --flight-plan commandline option
> with the default c172. All controls are working except the ailerons, which
> makes flying around a bit challenging... ;-)
>
> command line: fgfs --airport=EDDT
29 matches
Mail list logo
