I have no idea about that, all I know is it works for me. Maybe it’s the GNS530 mod kicking in. I could select V/S after entering target altitude (and ‘arming’ it), and change it’s value on the screen and the V/S analog gauge went to -1k ft/min and then it bleeps when you approach target altitude. I really don’t know any more than that. It works very like the AP on the EMB-110 except you can use the GTN750 on that aircraft.
Nice eye-candy and thats about as far as it go’s. When you can run the engines on red for an extended period of time without any consequences then it really is little more than a 30$ game expansion pack.
8 Likes
I mean it has literally done this as I type.
12500ft selected, it has now climbed to 13500ft and still climbing even though ALT mode engaged automatically just before the selected altitude of 12500ft.
Now I am in vs with -1000fpm and it is still climbing.
Please somebody from Aerosoft explain what is going on.
2 Likes
I for one appreciate those of you who are providing your opinions, unbiased. Thank you! I will not be purchasing this until it’s fully ironed out.
5 Likes
In believe the official response is that is all MSFS’s fault and had to be fixed by Asobo in the default KAP140.
I’m unimpressed.
1 Like
Yes and it is not the case, it works fine in other aircraft.
1 Like
You know, perhaps I could have learned my lesson a long time ago. When I first got the CRJ, I was having a problem with the Logitech Multifunction Panel with the stock Logitech drivers (haven’t moved to SPAD yet). Most of the AP functionality worked, but I couldn’t set the altitude with the panel. It was perpetually locked at 10000ft. You could change it momentarily, but it would just snap back to 10000ft. So I brought this to their attention.
Mathijs kinda snapped at me that I should be talking to Logitech, and made it out like questioning the CRJ, which was my first payware aircraft, was beyond the pale. It was the ■■■■■■ Logitech drivers that were to blame, not the CRJ. I was new enough to the flight sim world that I didn’t question it, and after pushing for a few posts that it looked like it was changing it, but something was snapping it back, I gave up because I was tired of being hassled by other forum users over the suggestion.
I learned, from that as well as elsewhere, that with the stock drivers it works best with stock aircraft, and add-on aircraft to varying degrees, but I haven’t forgot the attitude I was greeted with as a new customer, thinking he had found a bug.
6 Likes
Yes, you can just use vs after selecting the altitude. However by engaging IAS, you then can control your pitch with throttle to decend or asacend, while your speed is held where you selected IAS. All the other buttons light up when active IAS does not light up or engage. I am familiar with this because I flew the rw design in xplane. Simply, the IAS needs attention.
BW
1 Like
He’s telling you IAS is not modeled in the aircraft.
Thanks. Since it is not modeled, I will use vs.
BW
IAS is non functional, Aerosoft have said.
And for me when in VS it just shoots through the selected altitude every time, despite ALT mode engaging.
Then there is the extra problem of when you engage the AP the VS sets to 0fpm, so if you are climbing when you engage, as you normally would be, the aircraft pitches down to level.
When i think about what happened when I selected IAS and then climed or ascended by using the throttle that the altitude did engage when it reached the selected altitude. Nevertheless, I think using vs is the best way to go.,
It should be yes!
Review flight from a great YouTube who knows what he’s talking about. Mentions the autopilot issues basically as soon has he’s talked very briefly about the look of the plane and an overview of the flights. You can tell he knows what he’s talking about as soon as he goes through the departure.
1 Like
IAS actually is functional - like in many other implementations of the default AP, the IAS/FLC commands are still enabled in the AP they just aren’t hooked up to any cockpit controls, so if you manually map controls to the FLC mode commands you can use it.
Correct. And you can follow this by looking at the variables. The very moment you change the altitude VS mode is engaged. You just do not notice it, as it sits with 0 fpm thus holding current altitude.
You notice it if you are in climb when you engage and the aircraft pitches down massively instead of holding pitch as it should
Yep, that might also be a source of the faceplants with ils. Glideslope not yet captured and for whatever reason VS becomes more than 0. Less in that case. Into the mud you go. Without any visual feedback why that may be the case 
check out my showcase Microsoft Flight simulator 2020 Featuring: the DHC-6 Twin Otter by Aerosoft - YouTube
Why would you do such a thing in first place? If you follow procedures it’s not even an issue…
If you fly a real plane, would you attempt things that would risk the plane on purpose?