146 Professional

I just entered the MFS2020 content manager and... THE UPDATE IS READY. Let's enjoy.

We are aware of the autopilot not holding the glideslope perfectly, this we believe came about after a recent sim update that changed the atmosphere/weather in the simulator. It is something we are looking into and once we have a fix it will be included in an update to the 146.

Mark - Just Flight

We spotted a small controller issue with the Xbox version of the 146 that prevented us from releasing the Xbox version this week. A new Xbox build has been resubmitted and should be released next Thursday.

Mark - Just Flight

I apologize, I have repeated this message by mistake.

Okay, will be running tests on my side aswell. Thank you

@BAEflyer , we will see. I am going to keep random failures on mid or high and observe how it goes with other event types.

Thank you for your suggestion. I have logged this on our internal bugs/feature request tracker and we will consider this for a future update.

Mark - Just Flight

This is a known issue and we can confirm it has been logged on our internal bug tracker.

Mark - Just Flight

Mobiflight has presets for mapping the TMS. Just select the "BAE146" and the "Autothrust System", and the code is there when you select one.

https://hubhop.mobiflight.com/presets/

I've also noticed it is very easy for the AP to (correctly) disconnect if you fly too slowly.

Engine management and use of flaps takes practice and experimentation on approach.

Depending on weight etc., I'm having to drop a notch of flaps close to 200 kias,and further flap extensions causes massive drag... as does the airbrake. As such it is very easy to drop below the yellow bug -- which of course I keep forgetting to set by clicking on the placard.

It's challenging- but good fun - to fly.

Yes. Quite normal.

I find the stock trim when using a pulse encoder wheel, a little too sensitive. But you can go into the system.cfg file, and reduce elevator trim sensitivity from 1.0 to 0.75.

I have just encountered the same issue.
I flew to EINN via the TIPUR 2D arrival. I manually set the VNAV to waypoint to GILOG. However, the distance calculation was still to TIPUR and the altitude calculation was to 6000ft:
before TIPUR
Passing TIPUR, the calculations were now correct to GILOG:
after TIPUR

Oh and BTW... the new FMS is awesome. 👍

Thank you Mark!

@Mark I will check again in which direction the switch moves exactly, but I always selected "Start" (Up). The problem is that the whole start sequence is not beginning, when it happens.

I wil check again abd report here, and maybe I can catch it on video.

Thank you

I am also having this issue, often finding it difficult to taxi in a straight line and makes taking off a little more fun.

I can't recall if I had it before.