146 Professional

Could I kindly ask you to raise a support ticket with Just Flight Support at the following link: https://www.justflight.com/support In the ticket, if you are able to provide steps for how our support team can replicate this behaviour, including screenshots/videos if possible, then we will be in the best position to offer assistance with troubleshooting, or we can pass this over to our development team if further investigation is required. Mark - Just Flight

I recall this coming up during the testing of the 146 in XP12. It is expected that the TGT will peak out of limits if the throttles are very quickly advanced from idle to full power; however, I do agree that the TGT peak is quite excessive when this occurs (although there isn't any data out there to confirm/deny that). From the discussions I had with the development team, the high TGT peak in this instance is predominantly a side effect of having the engine simulation accurate throughout their normal range. So if the throttles are advanced at a normal rate, the engines will behave accurately and the TGT won't go out of limits. I'm unsure if the needles should be able to rotate 360 degrees, but again, it's one of those things for which there is no data/reference material available for, as no one wants to be overheating the engines on the real aircraft. I will, however, raise this on our internal bug tracker for the development team to take another look at ahead of a future update to the 146 XP12. Mark - Just Flight

Without knowing which exact annunciator has lit and under what circumstances lead up to it illuminating, it's a tricky one for us to confidently answer. The ANTI SKID FAULT annunciator will light if there is a fault within the system. The ANTI-SKID INOP annunciator will illuminate when the system is inoperative. With the latter, I believe it would only illuminate if the ANTI-SKID switch is set to OFF, or if the system does not have electrical power (Anti-Skid is supplied by DC Bus 2). If that behaviour occurs again, could I kindly ask you to raise a ticket with Just Flight Support via the following link: https://www.justflight.com/support If you could attach some screenshots or videos of the behaviour with the ticket, then our support team will be in the best position to investigate this further and assist with further troubleshooting. Mark - Just Flight

The MSFS version of the 146 Professional does list some 'non-standard' control assignments at the very end of the Operations Manual. The X-Plane versions of the 146 Professional do not list control assignments in the Operations Manual, however, I believe most control assignments in X-Plane are quite well named for their purpose. Please don't hesitate to reach out if there are any specific control assignments that you would like to know. Mark - Just Flight

The v1.0.2 changelog is now available here: https://support.justflight.com/en/support/solutions/articles/17000146695-146-professional-xp12-changelog Apologies for the delay in making that available. Mark - Just Flight

Yes, there were no changes to effect this in the v1.0.1 update. Once a change has been made to fix this, it will be listed in the changelog of the respective update: https://support.justflight.com/en/support/solutions/articles/17000146695-146-professional-xp12-changelog Mark - Just Flight

Thanks for the feedback. I have passed this on to the development team of the 146 Professional (XP12) to consider for a future update. Mark - Just Flight

Thanks for the feedback. I have passed this on to the development team of the 146 Professional (XP12) to consider for a future update. Mark - Just Flight

Thanks for the feedback. I have passed this on to the development team of the 146 Professional (XP12) to consider for a future update. Mark - Just Flight

If I could kindly ask you to raise a ticket with Just Flight Support at the following link, our support team will be able to assist with troubleshooting: https://www.justflight.com/support Mark - Just Flight

Hi all, Thanks for the reports here. The development team spotted an issue with the SkunkCrafts Updater compatibility, and that has now been fixed in the newly released v1.0.1 update: https://support.justflight.com/en/support/solutions/articles/17000146695-146-professional-xp12-changelog To obtain the v1.0.1 update and the SkunkCrafts Updater tool fix, please redownload the product from your account on JustFlight.com. Any future updates will then be available via the SkunkCrafts Updater tool. Mark - Just Flight

Oh, I see. I don't know what the FMC of the 146 supports, but simbrief seems to give you the cruise speed in Mach rather than in form of a cost Index. So you set the cruise speed to mach 0.7. If you need a CI you need to configure the aircraft in simbrief. I am not sure if that's supported for all aircraft.

Cheers! I found a tangential issue with the rollercounters on the autopilot popup window - there's an off-by-one error, the NAV1 and NAV2 COURSE windows display 001 when the value is 000, 090 instead of 100... also I feel they animate too slowly. They're moved directly by the knob between your fingertips so they should move almost immediately with just a couple of frames to show they're moving rather than teleporting between positions. As it is they have a weird floaty feeling to them! [image: 2d2c95c6-8ac6-481b-a2ba-7de6ef7674c5.png]

@rosscogswell Green is the start of the flow; Red is the end. I'll update my post on Infinidim.org shortly to include a copy of the SOP document I wrote for the 146. Ken

"What's important to note is that our/my participation and contributions to this forum are not always a reflection of the work that we are doing on our X-Plane projects or our attitude towards the X-Plane platform and community. Unfortunately the time that I have to contribute to any forum is very limited at the moment, and I'm sure there are members of P3D and MSFS forums that would like me to post more regularly, so this isn't specific to X-Plane. We've spoken about this in other forum threads, our social media channels (Facebook etc), YouTube videos and other articles but let me clear things up here - we remain absolutely committed to the X-Plane market. Where we used to develop for FSX/P3D and X-Plane 11, we are now focused on MSFS and X-Plane 12. The success of MSFS has little bearing on our approach to X-Plane 12 as we continue to partner with the Thranda team for our X-Plane aircraft, and they have no involvement in our MSFS aircraft. X-Plane 12 was released as an early-access product last year. Since then we've been working with Thranda to update our existing aircraft to provide X-Plane 12 compatibility, i.e. the same functionality as in X-Plane 11. Following it's exit from early-access, we've ramped up that work and have been rolling out the updates to our beta testers. We released the C152, DR400 and TB10/TB20 updates yesterday, and the PA28 Archer III, TX/LX and Duchess 76 are next up. The 146 is by far our most complex aircraft so naturally that will take longer and, like we've done with MSFS, we'd like to iron out any issues with the simpler aircraft first. Hopefully that clears things up. Please link to this post if the same concerns are being raised elsewhere, and I'll try to visit here more often in the coming weeks and months. Thanks, Martyn - Just Flight" https://forums.x-plane.org/index.php?/forums/topic/261604-support-for-x-plane-12/&page=3#comments

"What's important to note is that our/my participation and contributions to this forum are not always a reflection of the work that we are doing on our X-Plane projects or our attitude towards the X-Plane platform and community. Unfortunately the time that I have to contribute to any forum is very limited at the moment, and I'm sure there are members of P3D and MSFS forums that would like me to post more regularly, so this isn't specific to X-Plane. We've spoken about this in other forum threads, our social media channels (Facebook etc), YouTube videos and other articles but let me clear things up here - we remain absolutely committed to the X-Plane market. Where we used to develop for FSX/P3D and X-Plane 11, we are now focused on MSFS and X-Plane 12. The success of MSFS has little bearing on our approach to X-Plane 12 as we continue to partner with the Thranda team for our X-Plane aircraft, and they have no involvement in our MSFS aircraft. X-Plane 12 was released as an early-access product last year. Since then we've been working with Thranda to update our existing aircraft to provide X-Plane 12 compatibility, i.e. the same functionality as in X-Plane 11. Following it's exit from early-access, we've ramped up that work and have been rolling out the updates to our beta testers. We released the C152, DR400 and TB10/TB20 updates yesterday, and the PA28 Archer III, TX/LX and Duchess 76 are next up. The 146 is by far our most complex aircraft so naturally that will take longer and, like we've done with MSFS, we'd like to iron out any issues with the simpler aircraft first. Hopefully that clears things up. Please link to this post if the same concerns are being raised elsewhere, and I'll try to visit here more often in the coming weeks and months. Thanks, Martyn - Just Flight" https://forums.x-plane.org/index.php?/forums/topic/261604-support-for-x-plane-12/&page=3#comments

@bulva said in xp12: @derek Of course. You're right. The only thing stopping me from buying it is (I do not hide) the price. If the BAe 146 now cost several dozen $$$ less because it concerns the "old" and falling into oblivion XP11 platform, I would certainly buy it. I'm still using XP11, but we all know that these are the final weeks/months when "everyone" will switch to XP12. PS maybe there are planned New Year's discounts, or other price discounts in the near future ... Good point - limited user base will give us an excuse to hike up prices Ferrari parts vs Beetle parts and all that.

@captjames747 [image: 265ed13b-022b-421d-8705-d377daf3c164.jpg]