Never mind. Avionics is configured through the EFB. Problem solved.

I'd gladly pay for the tbm to be at the other BS aircraft level

I experienced this for the first time. I was flying in the Caravan without cargo pod, with no GPS, VOR to VOR. [image: 5b593bd9-5172-4279-846a-ba4bf391b734.png] At #1, it switched to ROL for the first time. It took me a while to realize what was wrong, but I was eventually headed in the right direction. Then it switched to ROL again, by #2. Back on track, and no further problems. As I flew over the VOR (#3), it switched to ROL, but this is, as I understand it, the correct behavior, when briefly losing the signal. As I was slightly adjusting the heading away from the VOR, I had an idea. The first two times it switched to ROL, the heading bug was still pointing north, as thas was my takeoff heading. After the second disconnect, I finally centered the heading bug, and had no problems after that. So I now set the heading bug 90° to the right, just to test. It again switched to ROL at #4. I, yet again centered the heading bug, and I reached my destination without any more disconnects. Anecdotal, of course, and it might be purely coincidental, but for all my unexpected switches to ROL mode, the heading bug was not centered, and while it was centered, I had no switches. Further testing needed.

thank you.

+1, but I don't think it will make a big difference as air conditioning units in the real world are typically quite weak! I think it would be more interesting to have for the airports that like to cut down on APU usage for noise reasons.

Thanks Mark! Glad they could get it sorted out

There are a few online with no readme or such that explains the process of "regenerating a json file." Is that something done with a text editor?

Any update on this?

This is weird. If i click on the flipchart nothing happen and i even can hear the soundanimation with rotating paper but the value stays fixed. A fast select and deselect of the option and all is well. I mean i have no alien installation and so far nobody else have this. My steps are -deselect the the option " FLIPCHART WT SYNC" in the efb -shutdown msfs 2024 -start msfs 2024 -freeflight select F100/F70/F28 -try to flip wt on the paperchart and i get soundanimation but no change in value -quick jump in the efb, select/deselect the option and all is fine Iam no ticket fan becaus i have to much of it on my workplace. So this report is the best i can do. But if realy no one else can confirm this behavior...well so i still have the alien theory

@Black-Square Is there any chance this issue could be addressed in the next wave of updates for all your aircraft? I’ve noticed it particularly on the Caravan recently.

@Martyn Thanks for the reply! Really looking forward to flying it. I guess I'll just have to wait patiently!

I tested closing the cabin door after deboarding to cool down the cabin a bit, which works quite nicely. Cabin can then be maintained in the lower to mid 20s.

@Black-Square thank you for your reply… Waiting for the fix

Disregard, I found them, sorry!

I suspect there might be some differences in the way lighting is handled in MSFS 2024 Native (Modular) and MSFS 2024 Native (Non-Modular) packages that could improve this, but I couldn't say for certain as we have no experience with the former at the moment. We do have this logged to take another look at some point, but we wouldn't be able to promise any improvements until we've looked into it further. Mark - Just Flight

Thank you all for the feedback. For any AFCAS/ATS related feedback, could I kindly ask you to raise a support ticket with Just Flight Support at the following link: https://www.justflight.com/support The F70 & F100 Professional are complex products, so in order to give our support team the best chance at offering speedy assistance, and for any potential bugs to get properly logged and addressed, could you please include any screenshots/videos of the behaviour with your ticket, as well as attaching the log file generated by the product. Instructions for locating the log file can be found here: https://support.justflight.com/en/support/solutions/articles/17000152594-where-to-find-the-log-file-s- Mark - Just Flight

Thank you Mark! I just corrected the title= entry to make it consistent with the house liveries.

The takeoff/landing performance data that we have access to for the F70/F100 is from an airline that didn't operate at high-altitude airfields, so the performance data only covers airfield elevations from 0ft to 8,000ft. This, I believe, was the standard takeoff/landing performance data that all airlines received, regardless of the airfield altitudes they were operating at. We did recently receive some performance data for an airline that used to operate at high-altitude airfields, and it appears that they had specific performance data for every high-altitude airport they operated at. I.e. there isn't a single graph that covers all airfield elevations from 0ft to 12,000ft, they instead used the 0ft to 8,000ft graph to calculate performance in that range, and then had flap 0 (dry), flaps 0 (wet), etc. performance tables for every airport they operated at above 8,000ft. With the performance data being airport-specific (based on runway length, slope, elevation, surrounding terrain, etc), that makes it tricky to implement the data into the performance calculator without extensively extrapolating the data (which would come at the cost of accuracy). We do plan on looking into this further once we implement the more powerful Tay 650 engines, which have different performance data. Mark - Just Flight