The Navigraph survey is out too, put Starship down as a vote there as well. For anticipated releases it was "Anything by Black Square and the PMDG 737-700", I really like the BBJ. https://navigraph.surveysparrow.com/s/navigraph-flightsim-community-survey-2026/tt-DfDJ6

@SadBucket I have like 20 hours in the DA40. Glider with a motor, a bit too slow for a sim model I would be interested in. And the TBM from these guys is too good to consider the FSR. Cheers!

Hi - yes I’m on Xbox. That’s comforting news, thanks. Regards, Mike

@vliah Same thing happened to me recently, I posted it here: https://community.justflight.com/topic/10047/finally-got-an-ils-issue/5. It hasn't reproduced since I uninstalled the kln90B, tho I did not have it loaded into the aircraft and I don't understand why having the unit installed would cause this issue... It is also generally good practice to enter HDG mode before intercepting a localizer.

@Lhotse no problem, happy flying!

Thank you for the detailed feedback. This has been logged on our internal trackers for our development team to review ahead of a future update to the 146 Professional. Mark - Just Flight

Thank you for the detailed feedback. This has been logged on our internal trackers for our development team to review ahead of a future update to the 146 Professional. Mark - Just Flight

The 146 Professional has two types of FMS, with each FMS using a different type of navdata: 'Classic' UNS-1 FMS - Developed by Just Flight and uses a custom Navdata format supplied by Navigraph. It is not currently possible to update the navdata of the UNS-1 on Xbox; however, it is something we have on our feature request tracker to investigate for a future update. 'Modern' ProLine21 FMS - Developed by Working Title and uses the simulator's default Navdata. The navdata used by the ProLine21 is updated every time the simulator's core navdata is updated. The RJ Professional has one type of FMS: GNLU-910A FMS - Developed by Just Flight and uses a custom Navdata format supplied by Navigraph. Like the UNS-1, it's not currently possible to update the navdata of the GNLU-910A on Xbox; however, it is something we have on our feature request tracker to investigate for a future update. Mark - Just Flight

In my case, it was because an old version of the SimConnect client was installed when I installed the Leonardo MD82 Anniversary. This SimConnect version is still from FSX and has repeatedly caused problems in both MSFS 2020 and MSFS 2024. Since I uninstalled it, FSTraffic has been working smoothly again.

@Voice-of-Reason thanks for the update and really looking forward to finding out what Black Square will be releasing in 2026!!!

@Black-Square, so nothing new on the EFB-Tablet-Side?

I would certainly love something different from Garmin, like the Aspen units. However I think the best way would be another dev like TDS for this. I'm still dreaming of a common interface for all addons, so you can change the avionics from a 3rd party provider all to your liking.

@jmarkows said in Mapping BKSQ switches not shown in MSFS2024 to Honeycomb Alpha/Bravo: Things like LVars, HVars, etc. need external programs to map them to controllers, the base sim can't do it. Mobiflight is a free tool that does that and has quite the community sourced library of variables already set up. I've never used it to speak to how easy it is to use. There is also FSUIPC, which I use, but has a rather dated UI and it's very manual. There's also SPAD.Next and Axes and Ohs, all of which are payware and come recommended by their users. Thanks - I really appreciate the response. I did some more digging today and have now downloaded SPAD.Next (14 day trial) and found some good examples online.

@Black-Square said in Copilot and passengers not visible: @qqwertzde When payloads are adjusted via the native payload interface in MSFS 2024, it causes Canard aircraft to flip over backwards. Thanks for the feedback, I really appreciate it. Pity that we can't have pax in the Starship then.

@Avio Can't say I would be jumping for joy over flying above 30C irl

Interesting. I would have thought damage modeling would have allowed it to extend at any speed, and if you're past the extension or retraction speeds then you'd suffer effects. Is there a reason it's set to 190 instead of 200?

@DeeKay Exactly how I always envisioned that would look for my users! I'm glad I was able to give you a quick solution. Enjoy!

@SadBucket I think you can fix that issue by changing a few lines in the right config files within the livery structure. I did this with some F28 and other liveries quite a while back, before the F28 was updated to native. I'm sorry I don't have time to dig through and look for it right now, but I'm pretty sure I found the method in this thread: https://forums.flightsimulator.com/t/unofficial-guide-to-conversion-of-liveries-for-msfs-2024-2020-legacy-aircraft-only/677083/34