Hi All,
As we've discussed before, I'm working on merging the old ATC/AI code from
David Luff (ATCDCL) with our AIModels system. As part of the rewrite, I have
added a new "--disable-atcdcl" option to my configure script. The default
behavior is that ATCDCL will be enabled. Disabling the build
On Tuesday 22 Dec 2009, Alan Teeder wrote:
[snip...]
> The Ercoupe and certain other aircraft (e.g. TSR2) may have an
> aileron-rudder interconnect, but this is very aircraft specific
> and should be part of the aircraft FCS model.
The YASim BAC-TSR2 doesn't/didn't/shouldn't have an aileron-rudde
On Tue, 2009-12-22 at 14:10 +, James Turner wrote:
> A few things that will certainly help:
> - not adding the departure airport if no runway is selected
> - not adding the departure airport for an in-air route activation
Perhaps a quicker workaround, just set
the /autopilot/route-manag
Durk Talsma wrote:
> the file for LFPG is probably still the original one that I made; I'm not
> sure, off the top of my head, where KNUQ.parking.xml comes from. But, I'll
> have a look tonight/tomorrow.
Indeed, the 'L/F/P/LFPG.parking.xml' is certainly still the old one,
something of December
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
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 t
On Tuesday 22 December 2009 06:10:48 pm Csaba Halász wrote:
> Exactly. So the file scenery/Airports/[I]/[C]/[A]/[ICAO].parking.xml
> will *never* be loaded, as FG only looks for groundnet.xml.
> parking.xml files should only live under AI/Airports and not under
> scenery/Airports. Hence my questio
On Tue, Dec 22, 2009 at 2:35 PM, Durk Talsma wrote:
>
> Whenever this boolean property is set to false, ground network data will be
> read from AI/Airports/[ICAO], and when set to true, it is read from
> scenery/Airports/[I]/[C]/[A]/[ICAO].groundnet.xml.
Exactly. So the file scenery/Airports/[I]/
James,
>From what I've read, and like the original, your route manager uses the
>airport center point as the destination. What is the reason for selecting a
>runway? If the destination point is center-runway of the specified runway,
>I'm not sure of the benefit over center-airport. Like you
On Tue, Dec 22, 2009 at 8:10 AM, James Turner wrote:
> What do you think would be a sensible course of action, in the situation
> you describe? Even if I choose not to add the departure airport for in-air
> route activation, there's no guarantee that the first route waypoint is
> where you actuall
On 22 Dec 2009, at 12:23, John Denker wrote:
> I won't bother to ask why some people consider a discussion
> of auto-coordination to be "hijacking" an auto-coordination
> thread.
I think that comment was because you replied to the 'autopilot broken' thread
to start the auto-coordination discuss
On 21 Dec 2009, at 18:55, Curtis Olson wrote:
> What do you think would be a sensible course of action, in the situation you
> describe? Even if I choose not to add the departure airport for in-air route
> activation, there's no guarantee that the first route waypoint is where you
> actually w
Hi Alex, Csaba,
On Tuesday 22 December 2009 12:44:41 pm Alex D-HUND wrote:
> On Mon, 21 Dec 2009 22:17:03 +0100
>
> Csaba Halász wrote:
> > I wonder if these files are there by mistake or if there is some reason.
>
> Only thing I know 'bout them is Martin's mail bout this:
> http://sourceforge.n
On 12/22/2009 02:35 AM, Stuart Buchanan wrote:
> I think all that is required is that we make clear that auto-coordination is
> designed to help people without any rudder control axis, and that a proper
> rudder axis (or even a twist axis on a joystick) is preferable.
On 12/21/2009 08:59 PM, Cur
On Mon, 21 Dec 2009 22:17:03 +0100
Csaba Halász wrote:
> I wonder if these files are there by mistake or if there is some reason.
Only thing I know 'bout them is Martin's mail bout this:
http://sourceforge.net/mailarchive/message.php?msg_name=g87kri%24u4q%241%40osprey.mgras.de
hth
Alex
--
Al
Moving the joystick or throttle should override the autopilot/autothrotle
and cause it to disconnect.
Yaw dampers, stick pushers and other stability augmentation demands are
added to the pilots´s joystick/rudder input, they would not normally
override it.
In a "training mode" there is a case
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
Ron Jensen wrote:
> > > Are you sure you don't have some noisy input
> > > device like a joystick or pedals connected that might affect the
> > > rudder axis?
> > > If two input axes are bound to the same control the last write wins.
> >
> > Thanks for the hint. That helps. It makes sense fro
18 matches
Mail list logo
