@Black-Square Wait, do you mean within 2026 or within 1 year from this post? Either way, looking forward to your work, which unlike another recent release, is well worth the price...

Yes. I'm having the same issue with MSFS 2024 on PC. V1.5 installed. Engine display and the PFD aren't working. Things I've tried so far. Removing other add-ons from community folder, reinstalling twice, cold start Vs on the runway, powering on from cold start using ground power Vs APU, deleting JF Avro RJ WASM folder, enabling and disabling state saving and restarting the sim multiple times and switching between the RJ 100/85/75. Will just have to wait for now it seems.

Yes! For some reason or another engine failure was on. Thank you!

Me podría decir de dónde la descargo para donde.

Any one know about this

I found a kind of solution which is not perfect but it is what it is. I have to delete anything tiller related from FSUIPC and only set it in the default msfs settings. it's a little more work if you also fly other airplanes where you set it in FSUIPC, but the only solution so far.

@rinkerbuck That might be the case at sea level, but there is plenty of torque overhead at sea level. The fuel flow will become limiting at higher altitudes, and torque will fail to keep up. ITT increase will also be added with the next update.

Would love it too!

@Zacke said in Some minor observations: The KLN 90B and the MC60 digital localizer work together as the should but passing a flightplan waypoint the KLN 90B keeps alerting to adjust the the track forever. So you have the MSG alert alway on via the announciator and the KLN 90B keeps flashing the desired track and keeps the ADJ NAV IND CRS TO xxx message in the stack. From memory I'm not sure when the KLN 90B does stop this alert after passing a waypoint but I never had that persistant behaviour before. Maybe it has to do with the TRK function of the MC60: The KLN 90B awaits a kind of confirmation from the MC60 that the track was changed. If the KLN 90B acts like the GNS 530, it's probably just reading the simvar for the NAV1 OBS to see if the pilot has set the correct course. It's a link party! https://community.justflight.com/topic/11398/mc60-and-gns-530-interaction-issue

ah... yes. Your report about the KLN 90B MSG annunciator does align with my observations about the GNS 530.

I should add all the orange boxes in the last image say "WASM module crashed...."

@Black-Square Nevermind, a clean install solved it my bad.

Thanks for your quick reply! So I get this right, that the values from the manual represent the real aircraft and are simply not achievable in the sim due to the "thick air" it simulates at low altitudes?

@Black-Square thank you for the quick reply and i really appreciate everything you do for the fs community

Thank you for reporting this. I have just taken a look on my side and confirmed that adding the "Just Flight F70 |" prefix to the Title= entry does indeed fix the missing EFB images. We did make some changes to the package in the v0.1.3 update in order to bring the packages in line with the marketplace versions; however, there were no intentional changes with regard to liveries. I'll forward this on to the rest of the team to investigate further. Apologies for the inconvenience. Mark - Just Flight

I finally found the cause. The TBM 850 integration was working correctly. The issue was caused by a PMS50 GTN750 option. In the integrated cockpit GTN750, System → Setup → Options → VCALC was enabled. This option forces the VCALC page to be displayed instead of the VNAV page. After disabling it, VNAV Profile immediately became available in the cockpit GTN as well. So this was a layer-8 configuration issue, not a problem with the Black Square TBM 850. I sincerely apologize for posting this in the TBM forum. Thank you for your patience and for reading through my overly complicated investigation. Greetings from Berlin! Kai! P. S.: She's a beauty [image: aa312330-8d97-4f61-9beb-c7aeebf90e11.png]