146 Professional

Hello Mark,

first of all, I'd like to thank you for your very quick response ! :)
Of course, the large T-tail and the relatively low gross weights are factors to consider. However, the manual states that takeoff is permitted up to a maximum of 30 knots of crosswind. In the simulator, however, i'm unable to keep the aircraft on the centerline in this crosswind... with or without the "RUDDER STEERING AXIS" enabled. Normally i have the axes separated.
Perhaps i'm doing something wrong. If you manage the takeoff and landing at the maximum permitted crosswinds, i'd like to know your settings ;)
My assistance options are all set to "realistic." I'd like to try a takeoff/landing with "medium" options. Perhaps that's an acceptable solution to that problem...

And of course, waiting for the next update... ;)

Thanks again!

Best regards, Volker.

Just a thought here, nothing more, but have you checked to make sure that your .ini is not set to Read Only access? If it is, uncheck it, otherwise it will not save any changes you make to the .ini file

146 Professional v0.2.3 and F28 Professional v0.1.3, and any versions prior to those, aren't compatible with MSFS 2024.

We are currently working on MSFS 2024 compatibility updates for all of our MSFS 2024 products. The status of each of these updates can be viewed at the following link: https://www.justflight.com/articles/just-flight-addons-msfs-2024-compatibility-status

Mark - Just Flight

Missed approach waypoints aren't currently simulated in the UNS-1. However, it is something we have logged as a potential new feature for a future update.

Mark - Just Flight

Entering the Lions den on this one.

The real world UNS-1FW(MMMS) is capable of being approved for BRNAV, PRNAV RNP 0.3 and LPV. Whether the UNS 1 used for JF ‘aircraft’ is modelled sufficiently is another question.

It is still on our radar as something we would like to support, however, it's in the midst of an ever-growing feature request list, so it's difficult to give any clear timeframe for when we may get around to implementing this. If there is an update on this, we will be sure to share it.

Mark - Just Flight

I've run into a situation with this that's locked me out of control on here with the mouse as well, I'm unable to see the cursor, clicking does nothing as does right clicking to mouse look, and there's no way I can tell to cancel the field entry. As far as I can tell all I can do is exit the flight.

There is a significant update to the 146 currently in development that will bring a lot of improvements that were added to the RJ back to the 146. We do have the feedback in this thread logged on our internal trackers, so it will all be revisited again by the development team during their work on the update. Any changes to this default ATC interaction we'll be sure to list in the update's changelog.

Mark - Just Flight

@Moonflower_414 thanks for the reply

That’s unfortunate, although manually inputting is far from a chore to do.

Love the aircraft though !!!

@jmarkows I've experienced that weird issue with pressurisation multiple times in the 146. Never been able to figure out what exactly triggers this condition, so never reported it.

I have been seeing this in the latest build, as well. I had success starting up the radar on ground power after a fresh load, but I turned it back off and was unable to start it under APU or engine generator power.

@Mark Thanks Mark. I've flown the 146 a few times since the 1.2 upgrade, but this is the first time that really jumped out at me.

I don’t use Beyond, but I should have thought of using the TO state from the tablet… Thanks for the advice, I’ll keep it in mind for the future.

After one session where I painstakingly went through the whole procedure at a very slow pace, double checking everything, and still no dice, I became more and more convinced it was either a bug or some compatibility issue (although I use very few addons), rather than an error on my part. So I just uninstalled the plane completely and re-installed anew.

That seems to have done the trick, I’ve already had two flights since and no issues starting - and keeping - the engines.

Thanks for the suggestion, however, t's unlikely for us to change any of the control assignments in the 146/RJ unless absolutely necessary. Any changes to the control assignments would require all users to update the control assignments that they have been using for up to 2 1/2 years, and that could lead to confusion, extra support tickets, etc.

We also try to keep the control assignments as similar as possible between the 146 and RJ, so if we were to use the suggested "Autothrottle Disconnect" for the AP SYNC toggle in the 146, this would then differ from the control assignment used for the AP SYNC toggle in the RJ (as we wouldn't be able to use the Autothrottle Disconnect control assignment as that's already used for the autothrottle).

Mark - Just Flight

@Driver-Airframes

The picture I posted above was a jpeg. The upload seems to be working OK.

Below is a PDF:

sa101.pdf