• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Autopilot turn opposite direction

kv0i

kv0i

Messages
58
Country
us-nebraska
For years I have noticed that when I initially click the Auto Heading Hold on the stock autopilot the aircraft turns the opposite direction needed for the turn about 3 degrees and bank angle of about 3 degrees. After four seconds or so it then does turn to the desired direction and completes the turn to the desired heading. Other heading changes using the autopilot heading hold function during the session work as they should. I see this in both my P3DV4 and FSXA simulators. As best I remember same was true in FS2004 also, It use to be just an annoyance but now that I am developing a automated precision ILS system where I use the heading hold function for glidepath guidance it has become very concerning.

Has anyone know of a way to overcome this fault in the autopilot? Is there a better autopilot available?

Bill
 
Yes, Bill,
that made me also crazy!!
I send you my AP_Ctrl.xml.

From line 145 to 270 there you will find a solution. Fare away from being perfect, but much better then MS!

Edi
 
Edi,

Wow!!! That certainly fixed the problem. I use Karol's F111 Autopilot because of the Terrain Following capability built into to it. We use it for our low altitude flying and bombing in the BNS system we worked together on. I will send him a copy of the modified autopilot. I am sure he will appreciate it.

Is there anything else in your AP_Ctrl that I should consider using? I just added the lines of code you mentioned.

Thanks so much,

Bill
 
Hi there. I am another one who is interested in getting an auto-ILS version working, based on Karol's fabulous AILA gauge.

I guess my aim is slightly different because I am trying to hitch it up with a voice assisted module issuing vocal GCA-type instructions. Unlike, I understand, your version, it will be largely aircraft-specific.

As you will probably know if you have followed the original thread over at Flightsim.com, where Karol presented AILA, the FSX gauge analyzer throws up a few errors. I managed to get rid of most of them (and they were trivial anyway) , but there is one that presents an issue which I am at a loss at how to resolve. It is line 2553 reading

Code: 
<TerrainShadow>True</TerrainShadow>

What, if anything is wrong with that?
 
Would be happy to provide a copy of my application. I will also have to provide you a new copy of Karol's gauge because I had to make some minor edits there to get it work with my application. Actually the auto-ILS is not aircraft specific. I run it in a minipanel system that will work with any aircraft in your simulator.

I developed it on P3D but it works fine with FSXA on my system. Another simmer testing for me has run into some unusual issues on his FSX simulator that I can not duplicate. So the more folks that test for me would certainly be appreciated.

As far as the Terrain Shadow error I have no idea what would cause that to show as an error.

Bill
 
From my recollection the "turn" you refer to is is deflection correlation. This is the GP checking alignment is accurate as in real life the Ac will NOT follow a absolute altitude or direction due to the array of environmental forces at play at anyone time. The moving off the "straight line" allows the the instrument conditions to be met i.e checking its actually following a track line, accounting for windirection, drift etc. As an example a pilot following a VOR signal will deviate at least 3 to 5 degrees manually based on the same "line". Even the best GPs drivers have to have a tolerance established - As the creator of Quality Management (W. Edwards Deming ) stated NOTHING is 100% - 99% is about as perfect as you can.
 
mjahn said:
....... the FSX gauge analyzer throws up a few errors. I managed to get rid of most of them (and they were trivial anyway) , but there is one that presents an issue which I am at a loss at how to resolve. It is line 2553 reading

Code: 
<TerrainShadow>True</TerrainShadow>

What, if anything is wrong with that?
Click to expand...
Try replacing " True " with " 1 " .

It might be something as simple as " the FSX gauge analyzer " prefers the use of 0 and 1 rather than False and True .
Test to see if using " 1 " rids you of the error indication .

Cheers
Karol
 
Hi Karol, good to have your continued support on this. It is great fun working with AILA.

Indeed, replacing True by 1 does the trick!! Love it, the gauge analyzer now gives a clean bill of health.

In addition to the GCA talkdown I am now also planning a voice-assisted Approach Control Service that guides an aircraft flying in the general direction of the destination airport to a suitable Intercept location at the correct altitude. In that context, is there any way to get at the Tower or Ground Control frequency of an airport? It would be nice if the controller could be heard to say "Contact ground/tower on ...". Here is a pic:

R_H5=&Hzkk.jpg


Bill, Edi: yes the initial heading wobble is awkward, having a cure for that would be great.

--Manfred
 
Last edited by a moderator:
Manfred,

Your GCA talkdown sound very intriguing.

The heading wobble fix provided by Edi is awesome. I use Karol's version of the Microsoft Autopilot and would be happy to share with you if you want to try it.

Bill
 
Have asked Edi for the heading lock wobble fix, but generally I shy away from wholly replacing the default AP stuff. Gotta admit that I am not a very good test pilot either, so wouldn't be of much use to you.
--Manfred
 
You must log in or register to reply here.
Back
Top