Are you using Developer Mode or made changes in it? NO
Brief description of the issue: Not just FLC mode not working… now sometimes AP will not disengage or reengage. Annunciator “AP” above the Attitude indicator will not extinguish.
ALSO… CDI course needle locked up in opposite direction while on Rwy heading. would not move when turning the course knob in ILS approach. . I am still investigating as to whether this is just certain airports.
Detailed steps to reproduce the issue encountered:
PC specs and/or peripheral set up if relevant: NA doesn’t work on Cockpit AP panel either
Build Version # when you first started experiencing this issue: SU 8
Yes, I noticed it as well that the AP green light stays on , no matter what.
I have just done some approaches at ellx and the pointer of the cdi course needle showed the correct heading (Not opposit)
Could you please state at which airport you experienced this?
That the CDI course needle does not respond anymore to the course knob when working with ILS frequencies is noticable in other aircraft as well.
The amount of deflection to the centerline of the approach on an HSI has always been independant of the course you set with the course knob.
It seems that nowadays setting the correct course is automated. No need to do this manually anymore.
I was already wondering, whether this is done for us simmers to make it easier, or is it a consequence of the digitization of aircraft instruments (Starting from analogue gauges)
No mods installed, PC user
I understand that modern Nav systems have access to databases that match the NAV Freq you type in to the ILS Rwy and heading on file and can theoretically auto switch to ILS appr mode and set the CDI needle to the actual magnetic approach heading. In MSFS I have only seen this in the Commercial and Business jets that use an FMC. I don’t remember the King Air’s system being one of them.
Happened at two places, (only tried it at two airports)
One was…KMSY Rwy 11 (109.9)
Second one was KASE Rwy 15 (111.15)
EDIT: So I tried KMSY again and apparently 109.9 is the same for Rwy 29 also. Neither approach plate (Rwy 11 or 29 ILS) states it’s a BC approach. So the Nav system defaults to rwy 29 when you set the freq to 109.9 and does not allow you to adjust the CDI to Hdg 106 (Rwy 11) and there is no BC button on the King Air AP panel. So I guess you just have to pull over and hop into another plane in order to do an AP instrument appr to KMSY Rwy 11. Seems reasonable.
Well, tried it also at KMSY, trying to reproduce what you are experiencing.
At the holding point for Rwy11 I set the ILS frequency. The needle jumps to 106, and the CDI is slightly of centre.
After lining up at rwy11 the CDI is perfectly centered and the needle points in the right direction (106).
After taking off and maintaining runway heading the needle turns 180 degrees. This happens above the treshold of rwy29.
Then I made a 180-turn to come back over/parallel to the field and the needle jumps back to 106, at which point I could make a perfect ILS approaches for Rwy11.
I could not find any abnormal behauviour of the CDI, except the auto set of the CDI needle in an aircraft that has no FMS?
Same behaviour at Aspen (VOR-DME approach only)
I tried this with navigraph data installed and uninstalled.
I am going to jump back in the sim and see what is going on the ILS approach for Rwy29 at KMSY
So far no need of jumping in another aircraft. All seems okay
I did exactly the same for take off at Rwy29. All is good. I tuned the frequency at the treshold of Rwy29 and the needle jumps to 286.
No problems encountered for the ILS approach
In short, when you are west of the airfield, the needle jumps to 106, when you are east of the airfield the needle jumps to 286. All with the same freq 109.90. No need for a BC button.
Hence, here all is good
And yes , it is Asobo King Air. I do have pms50 gtn750 and the TDS sim GTNxi installed in the comm folder. These are however not used by the kingair.
Can confirm that autopilot FLC climbing and descending is not working anymore after SU8, tested with King Air 350i and with Cessna 208b Caravan.
and i have weird problem with keyboard but it is not so important. Example landing and taxi lights are mapped to “del” and “end” but if i want to turn on landing lights by clikking “del” then nothing happens. You can see from the dashboard that the switch trembles only when you press the key.
I have mapped instrument views to 1-9 and with them is the same problem.
I only had an issue with ascending on the King Air, not descending, and not with any other plane. Though I surely haven’t tested all possible scenarios.
I was browsing the forum and found a thread where someone suggested to delete the fs-base-nav folder in the official one store folder. The sim recreates this folder on the next start. It was a suggestion for someone who had trouble capturing Ils approaches. Maybe worth trying?
Of course at your own risk🙄 (always make backup)
Interesting thing happened right after the SU8 update. I did not have issues with FLC until I remembered that I was using a “engine fix " mod in the King Air. I removed the mod because I realized that it did not have the new updated prop modeling and i wanted to try it out. After this, the updated prop parameters were active and that’s when i noticed the loss of FLC.
After doing some digging i realized that the only main differnce between the engine.cfg file in the old mod and the new engine.cfg file were 20 lines that all started with “Prop_Mod_xxx..” when I reinstalled the old 'Engine fix” mod the FLC worked again but the new prop model dynamics were gone too.
In regards to the keyboard bindings… I had to remapped a lot of buttons and axis’s after the update. Looks like the addition of new “set off” bindings in the update had scrambled some existing mapping in some configurations.
FLS isn’t working for me in the 208B in FLC on both ascent and decent. Descent will immediately pitch down and overspeed unless all throttle is taken out. and it won’t climb in FLC. I have no mods. This was with the standard autopilot in the tasmanian bush trip.
I am not having this issue with the Working Title G1000 NXi installed. I realize the game should work properly without mods, but I am just telling you my experience.
Here’s what I’ve noticed since sim update 8:
FLC isn’t working at all - just pitches down and speeds up
PITCH mode (The mode the autopilot/flight director goes into when you first turn it on, and the mode it will go into if you toggle any other pitch mode off) seems to go into a pitch hold mode, with no way to adjust the pitch.
If you go into VS mode in the clouds, it acts like a PITCH mode - it will hold the pitch , and you can adjust the pitch using the VS trim wheel. The VS bug will also move, but have no effect on the vert speed - it just adjusts the pitch. Once you’re out of the clouds, though, it reverts to normal VS mode operation.
All of that is just climbing, Haven’t had a chance to test it in a descent yet.
On King Air much work must be done, there are so many bugs you cant use the AC:
VOR DME freq. not adjustable, engine power way too much, broken FLC, prop pitch setting, torque adj., feather, etc. etc., AC is just a joke, a total failure. At the same time they corrected 5 bugs they introduce 10 more…Not only the King Air, all ACs have so many bugs, it seems they don´t get a grip on the technical programming tasks.FS2020 still is a sightseeing Xbox game, not a serious simulator…!! Very disappointing. Very sadly software programming flaws affects payware as well. Hopefully there will be a joint venture between xplane and google or similar maybe sometime.
