Thanks for sharing your experience. This is not the first time that I have heard of the native weather radar causing performance issues after a long flight. It seems this only affects a small number of users, and we haven't been able to determine the cause, except that it has something to do with the native weather radar display. Troubleshooting has been slow going, since I've never been able to reproduce this on a computer that I have access to. We found some BIOS settings or graphics driver changes that may have made a difference in the past, but nothing was definitive. Unfortunately, without anything definitive, it's difficult for me to approach Asobo with something for them to look into. If you feel like you're seeing this very consistently, and you're willing to help, I might be able to devise some tests for you to run (editing the weather radar code), but I will warn you that a lot of good men have lost a lot of hours trying to track this one down. Thanks again, and I hope you are otherwise enjoying the aircraft! Let me know if there is ever anything I can do for you.

@joncoughlin Just curious, did you ever figure this out? I'm currently working on the same issue, using Axis and Ohs. I tried to use chatgpt to write an RPN script for the purpose, but probably because I'm not experienced with LLM prompts, I gave up after about a dozen non-working scripts. EDIT: Just to clarify, I'm able to control them with button presses, but I dropped some money on the ProDeskSim F28 levers, which includes the fuel valve levers, so I'd prefer to find a way to bind them to axes. So I can set the LVar to 2/off with the button at the bottom of the axis, and I can set it to 1 when that button is released, but I have no elegant way to then set it to 0. Too bad the Bravo doesn't have detents you can set as buttons, like the Thurstmaster Airbus quadrant.

@djw4250 I'm glad it worked. I've probably spent hours in these sections of the BS manuals. I still feel lost half the time lol

I Used The Pro series of Bonanza, Baron and Caravan and the Analog King Air for the tests. In those tests I used The GTN750 with the KX-155 as well. I also used the GNS430 with the Bonanza. I did not use the GNS430 for the Starship earlier BUT after your post here i just tried to switch over to having the FMS1 by the 430. The flights with the 430 were all OK. So to be clear: There is nothing wrong with how the STARSHIP works, It was me expecting a function it probably should not even have. And it flies so nice & really can keep one busy if one wants! Thanks for taking time Nick. Dave.

@Black-Square Ya know Nick, that unreleased update with the interactable control surfaces sounds like a perfect time to add the cockpit window sun shields and "brakes off" sign in the window we chatted about ages ago Also, taking delivery of our IRL Commander in the next 4-6 weeks. I sent a justflight message with my email ages ago, but haven't heard from you. If you want to connect on Commander stuff, feel free to reach out!

@djw4250 That space usage is kind of a reality check for me lol... but what a cool base to build a simpit around.

Hey, just wanted to bring this up- as you said it looks good so far on the Commander.. have you already worked on a solution?

@Chotter Thanks for this but I am not a mobi expert and am rather lost on what to put where. I have used Mobi, but only with things from the HUB. Your code makes sense to me with what you are doing though. With that said: I think that first I create a new project: Create a new "Add Input Config": Choose Input: In the module, be lazy and scan for input, move a blue prop lever: After that I am at a loss where to go to input the actions you have mentioned. Hope you can drop a little more help.

@jmarkows Thanks so much, wasn't 100% sure that's what was meant... so I tried it last night, but didn't reload a flight to check. Appreciate your help.

@Mark Are you still in discussions with Asobo on this issue? I see it's still not resolved in SU5

Could I kindly ask you to open a support ticket via the following link: https://www.justflight.com/support In the ticket, if you could provide the same information you have in your forum post for how we can reproduce the crash (departure airport, SID, etc.), then our support team will be in the best position to be able to look into this further. Mark - Just Flight

Thank you for your interest, and it was great to meet so many passionate community members at FS Weekend! We have been posting a few updates on our social media channels over the last few weeks, highlighting the latest progress. Our latest in-development article (and an updated Detailed Description) can be found here: https://www.justflight.com/in-development/f70-f100-professional-bundle The finish line is in sight now, and we can't wait for everyone to experience the F70 and F100 in their simulators. Mark - Just Flight

Thanks for the interest. The F70 Professional and F100 Professional will support the MSFS 2024 Walkaround mode with interactable doors and ground equipment. The full feature set can be found on the in-development page: https://www.justflight.com/in-development/f70-f100-professional-bundle Mark - Just Flight

Thanks for the interest! The information in the 'Detailed Description' section of the in-development page will be the feature set of the release build: https://www.justflight.com/in-development/f70-f100-professional-bundle As with our other products, we will support the F70 and F100 for many years after the initial release, and during that time, we will undoubtedly add new features and improvements. We're not ready to commit to what those may be at this stage, but a big part of it will be driven by community feedback. Mark - Just Flight

Before agreeing, is the HOBBS unique to livery, if it is not I have see the same. back to 0.

Thank you all. You both nailed it. Changed fuel type to Jet-A (external TDS interface) [image: e424cccc-c1e2-4602-a7fa-eafbedf9a39b.png] Issue fixed [image: 5ccdc9ea-7cf9-4daf-9600-a042aece7912.png]

Finally problem solved, I contacted JustFlight support directly and the correct file was made available. They claimed that they sent the correct files to simMarket, in short it was a problem with the store's support, and only today (8) did they correct the problem by making the correct aircraft file available.