Torsten
Have you any more thoughts on this?
Alan
From: Alan Teeder
Sent: Sunday, July 28, 2013 2:21 PM
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] Autopilot filters
Torsten
Thanks for looking at my code.
Yes – there is already an integrator in the PI and PID
*To:* flightgear-devel@lists.sourceforge.net
mailto:flightgear-devel@lists.sourceforge.net
*Subject:* Re: [Flightgear-devel] Autopilot filters
Post a diff or the modified files or a link to a tarball here and I'll
have a look.
Probably a good start for me to get back into the loop after almost
two
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] Autopilot filters
Hi Alan,
thank you for your patch. I have a few, probably dumb questions:
* Isn't the your new integrator filter the same as a pi-simple-controller with
Kp=1 and no min/max clamping?
* What would you think about
On 26 Jul 2013, at 20:11, Alan Teeder ajtee...@v-twin.org.uk wrote:
I have added a washout/high-pass filter and an integrator to the XML
autopilot. Also I have added aliases to the exponential filter so that it may
be also called low-pass or lag and an alias to the noise-spike filter so
Post a diff or the modified files or a link to a tarball here and I'll
have a look.
Probably a good start for me to get back into the loop after almost two
years of absence...
Torsten
Am 26.07.2013 21:11, schrieb Alan Teeder:
I have added a washout/high-pass filter and an integrator to the
From: Torsten Dreyer
Sent: Saturday, July 27, 2013 8:47 AM
To: flightgear-devel@lists.sourceforge.net
Subject: Re: [Flightgear-devel] Autopilot filters
Post a diff or the modified files or a link to a tarball here and I'll have a
look.
Probably a good start for me to get back into the loop
I have added a washout/high-pass filter and an integrator to the XML autopilot.
Also I have added aliases to the exponential filter so that it may be also
called low-pass or lag and an alias to the noise-spike filter so that it can
also be called rate-limit.
README.digitalfilters is updated to
Hello, James
Back to the topic.
Thanks for the fix , right now we can use again the Autopilot with the GPS.
However the altitude is lost at each WP loading, set to Zero.
We could, before, keep on the original defined AP altitude, all over the
trip.
I know it was not realistic.
May be that
Hello,
Autopilot with Route manager is Longer broken, it is missing
/autopilot/settings/gps-driving-true-heading triggered to true and the
right /true-heading-deg which goes with it.
Since the feature has not been removed from the GUI, i guess it had been
broken elsewhere .
Your update the
though not sure
gps.cxx line 774
if (!_config.driveAutopilot() || !_defaultGPSMode) {
_apDrivingFlag-setBoolValue(false);
isn't it that strange ?
_apDrivingFlag is ever set to false
On 17 June 2013 14:22, grtuxhangar team hohora...@gmail.com wrote:
Hello,
Autopilot with Route
On 17 Jun 2013, at 14:41, grtuxhangar team hohora...@gmail.com wrote:
though not sure
gps.cxx line 774
if (!_config.driveAutopilot() || !_defaultGPSMode) {
_apDrivingFlag-setBoolValue(false);
isn't it that strange ?
_apDrivingFlag is ever set to false
Yes, the problem is I
Anyway, for now the fix is just to go back to the old situation, where we
assume the user wants the GPS to |drive the AP all the time
If you refer to your last fix (yesterday) , it is not sufficient,
since like said the /autopilot/settings/gps-driving-true-heading property
is not set to true.
On 17 Jun 2013, at 15:41, grtuxhangar team hohora...@gmail.com wrote:
If you refer to your last fix (yesterday) , it is not sufficient,
since like said the /autopilot/settings/gps-driving-true-heading property is
not set to true.
No, I need to make further tweak this evening, don't worry
Just tested with the Cub, working perfectly.
Thank a lot
Ahmad
On 17 June 2013 16:42, James Turner zakal...@mac.com wrote:
On 17 Jun 2013, at 15:41, grtuxhangar team hohora...@gmail.com wrote:
If you refer to your last fix (yesterday) , it is not sufficient,
since like said the
Hello,
For the record
With FG Git :
I cannot get working the autopilot with the route manager, we had an
automatic update of the autopilot box , by getting a GPS button , when a
way point was activated within the route manager.
That feature is not longer working.
We had within the GPS box ( menu
The autopilot and route manager are working for me in Boeing 777-200,
but the airport/waypoint lookup box in the GPS window is missing.
Saikrishna Arcot
On Sun 16 Jun 2013 07:09:22 AM CDT, grtuxhangar team wrote:
Hello,
For the record
With FG Git :
I cannot get working the autopilot with
On 16 Jun 2013, at 13:09, grtuxhangar team hohora...@gmail.com wrote:
For the record
With FG Git :
I cannot get working the autopilot with the route manager, we had an
automatic update of the autopilot box , by getting a GPS button , when a way
point was activated within the route
Hello,
It will help to have very precise test cases in the bug-tracker, since
when I did some limited testing two weeks ago, I found searching by
nearest or name did work. So really I would like to see very exact steps to
reproduce, not simple 'is not working'.
Which become an other topic :)
On 16 Jun 2013, at 13:09, grtuxhangar team hohora...@gmail.com wrote:
I cannot get working the autopilot with the route manager, we had an
automatic update of the autopilot box , by getting a GPS button , when a way
point was activated within the route manager.
That feature is not longer
Yes, i can
first,
the screenshot done with my working FG version ( was an old GIT version )
with its own fgdata
https://3291185c-a-62cb3a1a-s-sites.googlegroups.com/site/grtuxhangarctd/other-download/fgfs-screen-511.jpg
you can notice within the autopilot box Heading setting
the GPS/FMS
On 16 Jun 2013, at 15:46, grtuxhangar team hohora...@gmail.com wrote:
Both same place , same computer..
I've just pushed a fix to FlightGear, which fixes part of this for the Cub.
Please test and let me know if things are improved!
Regards,
On Fri, 7 Oct 2011 14:48:50 +0100, Alan wrote in message
3978EF975F29409FA9418725F2E83743@AlanPC:
-Original Message-
From: Arnt Karlsen
Sent: Friday, October 07, 2011 1:12 PM
To: flightgear-devel@lists.sourceforge.net
..chk output of fgfs -v -h |less , should offer frame rate
On Thu, 13 Oct 2011 00:50:40 +0200, Arnt wrote in message
20111013005040.7edb5...@nb6.lan:
On Fri, 7 Oct 2011 14:48:50 +0100, Alan wrote in message
3978EF975F29409FA9418725F2E83743@AlanPC:
-Original Message-
From: Arnt Karlsen
Sent: Friday, October 07, 2011 1:12 PM
On Fri, 7 Oct 2011, Alan Teeder wrote:
I am also having problems in this area.
If you look at the time dependant filters they use a very simple code
which easily explains the problem. It would be much better to use the
Tustin substitution which is practically guaranteed to be stable, and
On Fri, 7 Oct 2011 02:46:22 +0100, Peter wrote in message
CADt7PXMjc9znKOo5XStyyUt7BHYRAuJ9=qt+85smq-YsP=y...@mail.gmail.com:
Would it be possible to make the autopilot work at a reliable freq..
The autopilot atmo in my suspicion is bound to a frame rate.. this
explains why it wobbles on my
-Original Message-
From: Arnt Karlsen
Sent: Friday, October 07, 2011 1:12 PM
To: flightgear-devel@lists.sourceforge.net
..chk output of fgfs -v -h |less , should offer frame rate throttling
on recent and git versions of FG.
Arnt
I assume you mean fgfs --model-hz=n
This will run the
There is also a frame rate throttling option, but it's pretty buried
/sim/frame-rate-throttle-hz
Also consider setting your sync to vblank option in your video hardware.
That can help limit FlightGear to run at your display's refresh rate.
Curt.
On Fri, Oct 7, 2011 at 8:48 AM, Alan Teeder
Would it be possible to make the autopilot work at a reliable freq..
The autopilot atmo in my suspicion is bound to a frame rate.. this explains
why it wobbles on my low frame rate machine.. ie laoder card..
IMHO the autopilot.. should be set at a freq eg 10hz or less and fised inc
calculation
Hi All,
Currently there are a number of key bindings to enable various
auto-pilot modes, e.g.:
Ctrl-A Altitude lock
Ctrl-H Heading lock
Ctrl-G Glideslope lock
Ctrl-N NAV1 lock
Ctrl-P Pitch hold
Ctrl-S Autothrottle
Ctrl-T Terrain lock
Ctrl-W Wing level
F6 - Heading lock
Unfortunately, it is all
On 27/09/10 21:29, Stuart Buchanan wrote:
Hi All,
Currently there are a number of key bindings to enable various
auto-pilot modes, e.g.:
Ctrl-A Altitude lock
Ctrl-H Heading lock
Ctrl-G Glideslope lock
Ctrl-N NAV1 lock
Ctrl-P Pitch hold
Ctrl-S Autothrottle
Ctrl-T Terrain lock
Ctrl-W
Willie wrote:
On 27/09/10 21:29, Stuart Buchanan wrote:
Hi All,
Currently there are a number of key bindings to enable various
auto-pilot modes, e.g.:
Ctrl-A Altitude lock
Ctrl-H Heading lock
Ctrl-G Glideslope lock
Ctrl-N NAV1 lock
Ctrl-P Pitch hold
Ctrl-S Autothrottle
On 27/09/10 22:11, willie wrote:
btw the help option (?) on the Command Mode Dialog doesn't work for me,
can anyone else confirm?
It works OK - it just sends the help message to the console, which is
not much use in full-screen mode.
Willie
Sorry for replying late, I was out of town.
I'm posting in haste so I apologize if I'm missing something, but was there
a recent change to the autopilot system that now ignores stages if they
have the same name tag as a previous stage? Previously this wasn't the
case, but if it's a new
I'm posting in haste so I apologize if I'm missing something, but was there
a recent change to the autopilot system that now ignores stages if they have
the same name tag as a previous stage? Previously this wasn't the case,
but if it's a new addition, it could possible break some configurations
Greetings,
I did a GIT update and rebuild recently and have noticed that no
properties under /autopilot/internal/ are being set or updated.
Quite a few autopilot XML files use the lookahead speed and
fdm-heading-bug-error amongst some others.
Does anyone know where they went and if
On 1 Jul 2010, at 19:53, Torsten Dreyer wrote:
Please check if you have something like
autopilot
pathAircraft/Generic/generic-autopilot-helper.xml/path
/autopilot
near line 226 of preferences.xml
If not: do a git pull on the fgdata.
If yes: You found is is a bug.
And if you're
Perhaps the PI anti-windup change could be re-visited. When the output is
clamped and anti-windup is active, at xmlauto.cxx:625, the line:
int_sum = clamped_output - prop_comp;
seems to introduce the Kp, proportional gain factor, into the integral
sum. With the proportional gain much
Perhaps the PI anti-windup change could be re-visited. When the output is
clamped and anti-windup is active, at xmlauto.cxx:625, the line:
int_sum = clamped_output - prop_comp;
seems to introduce the Kp, proportional gain factor, into the integral
sum. With the proportional gain much
Perhaps the PI anti-windup change could be re-visited. When the output is
clamped and anti-windup is active, at xmlauto.cxx:625, the line:
int_sum = clamped_output - prop_comp;
seems to introduce the Kp, proportional gain factor, into the integral
sum. With the proportional gain much
Hello ...
After the recent autopilot update , altitude hold doesn't work anymore for
me , (using pi-simple-controller)
Im not sure what effect to expect with the anti-windup addition , but my
guess is it's just exposing my poor
configuration.
Cheers
Hello ...
After the recent autopilot update , altitude hold doesn't work anymore for
me , (using pi-simple-controller)
Im not sure what effect to expect with the anti-windup addition , but my
guess is it's just exposing my poor
configuration.
Syd,
if you are referring to the b1900d
Thanks for the explanation , that does help clear a few things .I'll
probably redo these files again shortly .
Cheers
On Tue, Mar 16, 2010 at 2:34 AM, Torsten Dreyer tors...@t3r.de wrote:
Hello ...
After the recent autopilot update , altitude hold doesn't work anymore
for
me , (using
Thanks James.
It seems to work with my test buzzing london and associated VOR/ILS
am now trying to refine autopilot in concert.
pete
James Turner wrote:
On 28 Jan 2010, at 04:00, syd adams wrote:
you can also check the instrumentation/nav/nav-loc , but it seems to stay
stuck on true
Ok, and then the final step is the bits.test(bar,0). I spent a couple of
minutes searching the web but could not find docs for the bits.test
function. I assume bits.test(oddnumber,0) returns 1 and something else
for even numbers, presumably 0?
Jari - learning Nasal
On 1/29/10 2:34 AM, Ron
On Fri, 29 Jan 2010, Jari Häkkinen wrote:
Ok, and then the final step is the bits.test(bar,0). I spent a couple of
minutes searching the web but could not find docs for the bits.test
function. I assume bits.test(oddnumber,0) returns 1 and something else
for even numbers, presumably 0?
You'll
On Fri, 2010-01-29 at 15:34 +0100, Anders Gidenstam wrote:
On Fri, 29 Jan 2010, Jari Häkkinen wrote:
Ok, and then the final step is the bits.test(bar,0). I spent a couple of
minutes searching the web but could not find docs for the bits.test
function. I assume bits.test(oddnumber,0)
Thanks.
Jari
On 1/29/10 4:07 PM, Ron Jensen wrote:
On Fri, 2010-01-29 at 15:34 +0100, Anders Gidenstam wrote:
On Fri, 29 Jan 2010, Jari Häkkinen wrote:
Ok, and then the final step is the bits.test(bar,0). I spent a couple of
minutes searching the web but could not find docs for the
On 28 Jan 2010, at 04:00, syd adams wrote:
you can also check the instrumentation/nav/nav-loc , but it seems to stay
stuck on true if you tune another frequency that's out of range or invalid...
not sure when that broke.
My fault, just checked the code and it's trivial to fix. WIl commit
On 28 Jan 2010, at 03:45, Ron Jensen wrote:
Here is a nasal function to determine if a frequency is a localizer. It
accepts a frequency in megahertz and returns 1 if the frequency is an
ILS frequency.
var isILS=func(freq) {
if(freq 108.10) return 0;
if(freq 111.95) return 0;
var
On 28 Jan 2010, at 09:18, James Turner wrote:
My fault, just checked the code and it's trivial to fix. WIl commit it ASAP.
Committed now - also made the same fix for 'has-gs' which was similarly getting
stuck on the old value when no valid station was tuned.
James
I can't read Nasal so I can't say if the function below is correct. For
what it is worth: A frequency between 108.100 and 111.950 (including end
points) is a localizer frequency if the first decimal is an odd number.
Jari
On 2010-01-28 04.45, Ron Jensen wrote:
On Wed, 2010-01-27 at 09:06
Nasal is like C, C++, perl, and php in many ways so if you can read any of
those, you should be pretty confident that what you think nasal is doing is
what it's actually doing. Writing nasal code from scratch is harder of
course because it requires knowledge of all the picky language syntax
For me the Nasal function looks strange. I can't understand what the
addition of 0.001 to freq does? For me it seems to be a waste of
precious CPU time.
Jari
On 2010-01-28 21.39, Curtis Olson wrote:
Nasal is like C, C++, perl, and php in many ways so if you can read any
of those, you
On Thu, 2010-01-28 at 21:21 +0100, Jari Häkkinen wrote:
I can't read Nasal so I can't say if the function below is correct. For
what it is worth: A frequency between 108.100 and 111.950 (including end
points) is a localizer frequency if the first decimal is an odd number.
Jari
Right,
On Thu, 2010-01-28 at 21:59 +0100, Jari Häkkinen wrote:
For me the Nasal function looks strange. I can't understand what the
addition of 0.001 to freq does? For me it seems to be a waste of
precious CPU time.
Jari
var bar=int((freq+0.001)*10)-int(freq)*10;
The 0.001 ensures we get the
2010/1/26 syd adams adams@gmail.com:
I wouldnt spend too much time on the b1900d , as Ive already redone most of
it ,and added the CLM /DSC modes , and will probably commit tonight .
OK, I tuned only implemented modes on old aircraft :)
My patches are only suggestions
The main problem
Yes Ive sorted some of that out .
What makes it a bit more difficult is that all pitch modes have to be output
to target-pitch-deg to run the flight director bars .
If you want to experiment with the version I just uploaded , I'm sure it
could be greatly improved.
But I'd prefer if you posted
you can also check the instrumentation/nav/nav-loc , but it seems to stay
stuck on true if you tune another frequency that's out of range or
invalid... not sure when that broke.
On Wed, Jan 27, 2010 at 7:45 PM, Ron Jensen w...@jentronics.com wrote:
On Wed, 2010-01-27 at 09:06 +, Pete
It works, but the behaviour is unexpected, or I got it wrong about VOR
navigation.
Sounds like it could be a faulty config file ,,, but the proper way to do a
VOR navigation is :
Set your (VOR/LOC) frequency set your desired course / radial.
Set your heading bug to intercept the course
On Tue, Jan 26, 2010 at 2:36 AM, syd adams wrote:
It works, but the behaviour is unexpected, or I got it wrong about VOR
navigation.
Sounds like it could be a faulty config file ,,, but the proper way to do a
VOR navigation is :
Set your (VOR/LOC) frequency set your desired course
Curtis Olson wrote:
On Tue, Jan 26, 2010 at 2:36 AM, syd adams wrote:
It works, but the behaviour is unexpected, or I got it wrong
about VOR
navigation.
Sounds like it could be a faulty config file ,,, but the proper
way to do a VOR navigation is :
Hi!
I would like to join the discussion about AP tuning. I recently posted
a message on the forum
(http://www.flightgear.org/forums/viewtopic.php?f=4t=6853) for
b1900d. With enclosed files, action is quite smooth and autopilot
seems stable, at least on my conputer.
For vertical stabilization
I wouldnt spend too much time on the b1900d , as Ive already redone most of
it ,and added the CLM /DSC modes , and will probably commit tonight .
The main problem i found on that is the yaw damper was fighting any turn in
roll modes,so at the moment Ive disabled it.
I'm still tuning the pitch
Wonderful, brilliant stuff Giuseppe,
The way that the autopilot works with those patches is the way I expected.
Hope this stuff makes its way into CVS so at least there's a good
reference implementation.
pete
Giuseppe Venanzoni wrote:
Hi!
I would like to join the discussion about AP
On Monday 25 Jan 2010, Pete Morgan wrote:
I'm having a successful time tuning my first autopilot on the
787.
I've managed to get rid of the jerks and wobbles, mainly by
using a noise-spike filter with max-rate-of-change. That
thanks to Syd Adams for that wonderful tip.
All flight level
thanks lee for the reply, particular about the thinking it through
part; and am already thinking about a problem I've encountered, although
I'm still trying to get the hang of the autopilot.
VNAV. - (don't know how to explain the problem well)
I've managed to get the Altitude hold, Vertical
On Monday 25 Jan 2010, Pete Morgan wrote:
thanks lee for the reply, particular about the thinking it
through part; and am already thinking about a problem I've
encountered, although I'm still trying to get the hang of the
autopilot.
VNAV. - (don't know how to explain the problem well)
Thanks leee..
for all the tips..
Is one of you aircraft in CVS so I cant study the autopilot.
pete
leee wrote:
On Monday 25 Jan 2010, Pete Morgan wrote:
thanks lee for the reply, particular about the thinking it
through part; and am already thinking about a problem I've
encountered,
On Monday 25 Jan 2010, Pete Morgan wrote:
I'm having a successful time tuning my first autopilot on the
787.
I've managed to get rid of the jerks and wobbles, mainly by
using a noise-spike filter with max-rate-of-change. That
thanks to Syd Adams for that wonderful tip.
All flight
Am trying to get the autopilot to follow a NAV1 course, correctly.
It works, but the behaviour is unexpected, or I got it wrong about VOR
navigation.
Please have a look at the image link below as I am not good at explaining.
http://imgur.com/LL6b9
Approaching a VOR, from say 50nm away, just
Would it be possible to wire up the VNav autopilot as follows, or is it
a bad idea.
http://i.imgur.com/UkGHG.png
I'm trying to figure out a way that will allow smooth switching between
the pids, which would mean taking into account the current elevator
position.
Also is it possible to make
I'm having a successful time tuning my first autopilot on the 787.
I've managed to get rid of the jerks and wobbles, mainly by using a
noise-spike filter with max-rate-of-change. That thanks to Syd
Adams for that wonderful tip.
All flight level changes, and NAV, heading can be tuned very
Hi,
Okay, that's a useful data point, I'll take a look at that
in the next few days (in between eating too much...). I
assume all interactions with the system are occurring
through the radios and autopilot *dialogs* (F12 and F11),
not the cockpit panel?
The cockpitpanel isn't working
I already took a look into several times, but if I would able to use the
Bravo-flightdirector as an example I wouldn't have said this. Syd's
flightdirector seems to dependant on other things ( not always other
simlated systems) so I wasn't able yet to use this.
I guess a short explanation of
Hi,
With the aircraft I test with, that's what I see - the
C172, the Seneca, the B1900 and, to a lesser degree, the
777-200 (though it has some other problems). I guess the
problem may be, that all of those aircraft have quite well
developed, non-generic autopilots.
Unfortunately they
On 23 Dec 2009, at 11:42, Heiko Schulz wrote:
737-300 (Using the autopilot.panel via F11)- in 19.1 the 737-300 was the
airliner with the best autopilot behavior recommended for ILS-approaches done
by ap. with my last built from 11/27/2009 the aircraft didn't responded
anymore on NAV1-Hold
S Andreason wrote:
configured autopilots like the senecaII, c172p, PA24-250.
Well yes, but I expected the default aircraft to work.
Since the manual and help windows give instructions on using Ctrl-A,
Ctrl-W,
Ctrl-H, etc, and F11 does open the autopilot settings, I would expect
Stuart Buchanan wrote:
The wing leveler and heading autopilot that are part of the KAP140 work
well for the c172p. However, using the generic autopilot instead is not
something that I would expect to work, so they should be disabled
for the c172p.
Agreed.
And the help keys removed from the
James Turner wrote:
Okay, so that's where the bug has come from, I need to fix the logic to only
drive this property when GPS 'leg' mode is active.
Yes, and it works now. Thank you very much!
Stewart
--
This
Hi,
Why is the autopilot broken?
Specifically on my models like bluebird (or ufo if you prefer), I
started to implement a requested feature, but found it does not work
like it used to.
The property:
/autopilot/settings/true-heading-deg
acts like it is being set by something else that
Hi,
There were major changes on the GPS and Route-Manager since August (3 Months
ago already!)
So this has affected the the use of the autopilot as well.
All aircrafts using the generic Autopilot-panel are affected, but not those
with an own written flightdirector like Syds Aircrafts
S Andreason wrote:
Hi,
Why is the autopilot broken?
Specifically on my models like bluebird (or ufo if you prefer), I
started to implement a requested feature, but found it does not work
like it used to.
The property:
/autopilot/settings/true-heading-deg
acts like it is being set by
On 21 Dec 2009, at 16:33, Heiko Schulz wrote:
There were major changes on the GPS and Route-Manager since August (3 Months
ago already!)
So this has affected the the use of the autopilot as well.
All aircrafts using the generic Autopilot-panel are affected, but not those
with an own
Hi,
Why is the autopilot broken?
Specifically on my models like bluebird (or ufo if you prefer), I
started to implement a requested feature, but found it does not work
like it used to.
The property:
/autopilot/settings/true-heading-deg
acts like it is being set by something else that
On Mon, Dec 21, 2009 at 11:17 AM, James Turner wrote:
For the record, my perception is that entering a value in the generic
autopilot dialog for 'true heading' has never worked, because the value
would **always** be over-written by the route manager.
This would only have been the case if
Heiko Schulz wrote:
Hi,
There were major changes on the GPS and Route-Manager since August (3 Months
ago already!)
So this has affected the the use of the autopilot as well.
All aircrafts using the generic Autopilot-panel are affected, but not those
with an own written flightdirector
Hi James,
As far as I know, the old route-manager code behaved much
the same as my code does now - but it sounds as if you
disagree?
Yep, and Torsten already decribed it well:
The GPS code sets the property /autopilot/settings/true-heading-deg if
Hi,
Heiko Schulz wrote:
Hi,
There were major changes on the GPS and Route-Manager
since August (3 Months ago already!)
So this has affected the the use of the autopilot as
well.
All aircrafts using the generic Autopilot-panel are
affected, but not those with an own written
One note on using route manager - in a 12/13 CVS - if includes the departure
airport as a waypoint automatically. If you activate it on the ground it
will move past it on the takeoff roll and proceed to the next waypoint. If you
don't activate it until in the air it will circle back to the
On 21 Dec 2009, at 17:59, Heiko Schulz wrote:
It worked as long we didn't use the Route-manager. Like Curt already said,
with pending waypoints the values are overwritten, but only then.
That hasn't changed.
Okay, so that's where the bug has come from, I need to fix the logic to only
drive
On 21 Dec 2009, at 18:10, Peter Brown wrote:
One note on using route manager - in a 12/13 CVS - if includes the departure
airport as a waypoint automatically. If you activate it on the ground it
will move past it on the takeoff roll and proceed to the next waypoint. If
you don't
On Mon, Dec 21, 2009 at 12:43 PM, James Turner zakal...@mac.com wrote:
It is not my intention, or expectation, that many aircraft should need to
be changed at all. Aircraft that used the old gps or route-manager directly
will need changes (eg, the 787, and Concorde INS code, but that's
Hi James,
There were major changes on the GPS and Route-Manager since August (3 Months
ago already!)
I had not noticed because I have not tried using the autopilot
for many months.
written flightdirector like Syds Aircrafts (Citation Bravo works perfect) or
with own
yes, Citation
On Mon, Dec 21, 2009 at 12:48 PM, James Turner wrote:
I thought I'd fixed that back at the start of October, soon after the
initial commit - Curt complained that h couldn't start a route 'in-air' so I
removed the need for departure/destination airports.
Ah, I get it - you're specifying a
James, this is what I've found too. Perhaps I don't understand the proper
setup method, but I tend to clean it up as well. Sometimes I get a FL value,
others times the point adds with a zero altitude. (or two dep. airport
waypoints, one with each altitude)
It may be a result of most times
Hey,
could we all agree it's not my fault? :)
Erik
--
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market
Erik Hofman wrote:
Hey,
could we all agree it's not my fault? :)
Sorry Erik,
You are only guilty of submitting the most number of files in that 36
hour period. :)
I guessed wrong.
Stewart
--
This SF.Net email
Hi,
Hey,
could we all agree it's not my fault? :)
Erik
Only if you will correct the airport name:
http://wiki.flightgear.org/index.php/File:Tu154Innsbruck.png - pretty flat for
LOWI ! :-P
Cheers
HHS
__
Do You Yahoo!?
Sie sind Spam
I'll have to add also that I'm a bit confused by the recent changes (I'm
sure I'll eventually figure it out) ,
but how is this new route manager dialog supposed to work ?
I try the normal k...@35000 , and hit activate , and then I get my departure
airport suddenly added to the list , which causes
Heiko Schulz wrote:
Hi,
Hey,
could we all agree it's not my fault? :)
Only if you will correct the airport name:
http://wiki.flightgear.org/index.php/File:Tu154Innsbruck.png - pretty flat
for LOWI ! :-P
Admittedly I already wondered about it :)
But i never thought it would
1 - 100 of 204 matches
Mail list logo
