@CdnCptMoustache I just looked into this, and that variable is only set to zero in the Turbine Duke, and Starship. There's a high probability it was a mistake, and I copied it over to Starship, but I will test things out and see if that's the proper solution before the next update. Thanks for pointing it out. This problem was on my list, but I haven't thought about it in a while.

I have raised a support ticket for this as it seems broken and also same on the Arrow III / Warrior II and Tomahawk as I have just tested. Can not be sure but perhaps this issue arrived with the new Configuration option on the EFB for Fuel and Payload? Hopefully the save state across these aircraft can be checked and fixed where needed as it is always nice to get into an aircraft in the state it was left. Cheers Matt

@NixonRedgrave Glad you figured out the sound. Sorry for the delay. The temperature regulation problems have more to do with the lack of mass air movement through large forward-facing inlets, but rather just those two NACA ducts on the top of the aircraft. This is a typical problem with pusher aircraft, including the Skymaster. Let me know if there is anything else I can do for you! Always happy to help!

Hi Mark, It works! Thank you so much for replying with the missing pieces🥳 With kind regards, Melvin

Yes. I realized the Ascend & Descend notification to the left of the VS knob is in fact the upward & downward pointed triangle, which I can now get, so its sorted. Thank you

@alanfernandes Yes you are correct but a lot of 3rd party devs have added in other features that aren’t included with the base working title avionics. Like for the G3000/G5000 Skyward developed a whole Datalink functionality with it and it has some protections built in. Especially now that we know that the King Airs are gonna be the 300 and the 1900D both of them could get garmins. The 1900D has a slightly specialized one called the G950nxi and the 300 has the regular G1000nxi.

Thanks, that makes sense. I'd only seen the default Caravan at 65 and assumed a sim update had changed it. Appreciate the explanation.

Cool, thanks!

I had a feeling it was North America but I never would have guesses it's Not! Thank you - I'll let you get back to the Twin Commanders... which in case no-one has mentioned, are looking incredible!

Thanks. Good thought on the high zoom level - lens effects was the issue I was running into trying to grab screen shots. I got close with pics off search engines but I think I can still do better. This is my first foray into air manager . . . . got all the avionics displays working except the KFC 150 (Glass Out isn't finding the KFC) - still have to get the buttons working on the KNS 81, KFC 150, KR87 and the radar but I'll get there. This will be on a 24" touch panel to the right of an altimeter motives Baron panel that's on the way [image: 4aaa50d0-6516-4b7b-8fdf-d83f1cf6d5cb.jpg] .

Then i will do the same, thank you!

I don't see an issue with the placement of the LIM waypoint here, as @JabbyJabara says those are all 6000+ restrictions so you wouldn't expect to be at 6000ft until WW974. What was your cruise altitude for the flight? As for whether the LIM point would reflect an earlier speed restriction, we had quite a bit of debate over this internally but found evidence amongst the documentation that it always will display the standard 250/10,000ft but the aircraft will stick to the procedure speed restriction.

It sounds like you are reporting different issues. In terms of manual trimming, I'm not aware of any changes that we've made that would affect that. There is currently an issue which prevents the stab trim wheel from being clicked and dragged but that has no impact on the elevator trim assignments. We've flown a lot of flights here without any trim issues. Regarding being out of trim when disconnecting the AP, we reworked the autotrim logic in v1.2, and all of our testing here results in the aircraft being perfectly in trim when disconnecting the AP. That's a significant improvement on the previous behaviour. I'd recommend that you both submit support tickets so that we can get some more information, including hardware and control assignments.

Thank you for the very quick response Nick

Please excuse my ignorance.

Thanks, you are right!

OK - so contrary to what I read about updating and just installing over, I uninstalled the plane and then did a re-install and now all's well. Thanks .

Hey, there! What a wonderful project! I might recall your suggestion a while back. I'm sure there were a few with that idea, because it's a good one. It's really interesting to see what can be done with AI now too, and always amusing to see that someone has been earning my code, just as I've learned from others my whole life too. Excellent work! I hope you don't misinterpret my delay in responding to mean anything other than that I've been busy. In reality, I've been trying to think of how to respond most appropriately. It's quite difficult as a developer when something this good comes up, because it seems like a poor choice not to add it for everyone who would enjoy it; however, it also might be a little daunting for less than the top ~1% most experienced users. Of course, then there is also the technical challenges of adapting it to all my aircraft, documenting, and maintaining it. Ideally, I would love to offer something like this as a free download for those who are interested, because it would allow me to maintain it separately from the aircraft (every aircraft updated is several days of work for me and the Just Flight team, adding up to about two weeks of work to update my entire fleet), and also because I think it would allow others to treat it as an "experimental" feature, whereas anything included with the aircraft is expected to approach perfection, at least in my eyes. Would you have any interest in creating this as a mod that could be added to the aircraft? Clearly, it would be best if it was modular, since updating the entire tablet every time the aircraft is updated is a recipe for support tickets. Ideally, it would be a new set of files that are dropped in the same place in the virtual file system, and then probably a modification to the main HTML to add the JS, which is okay, because the HTML shouldn't really change after an aircraft is released. I know that would be a lot of work, but it would be a lot less work than it would be for me to maintain with official support, which is why I recommend it. If I don't have the bandwidth to support this feature, it might never happen, but it would be sad to never see it happen because of it! I hope you understand and that this doesn't sound like a dismissal! I'm very impressed, and would love to see what we could do together, on this, or any other part of my aircraft you take an interest in! I'm just doing my very best to manage expectations.

Hi all! I had huge problems flying the f100/f70 in real weather. Approach speeds fluctuating wildly and incontrollable aircraft. But, I found a solution in the internet which seems to work on my pc. It’s a windows problem (!). The OS clock synchronization, didn’t work well (but check also DNS and IPv6). It caused MSFS2024 to mess up winds, particularly during last 500 feet AGL of the approach. The link is here: https://forums.flightsimulator.com/t/extreme-crosswinds-and-wind-swings-close-to-the-ground-on-final/728054 Many thanks to paulofranca89!

Thank you 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