Just my 2cents on this. I know some other developers have done this like FlightFX with the HondaJet and the VisionJet. The Piper Turbo Arrow also have Navigraph and Simbreif in the tablet which was suprising. I know other do as well in smaller GA aircraft and as someone who is on Xbox this is amazing as we do not have the add ons that PC users to do allow for a pop out or things like that. The other thing to consider would be developing a stand alone pop-out for Navigraph/Simbreif for the marketplace. Similar to what PMS50 just did with the GTN750. Xbox users can now use a pop-out GTN750 like the PC users do. One of the reasons I love this so much is that it now, for the most part, allows every aircraft to have Navigraph and Simbrief intigration through the pop-out unit. Just food for thought.

Need B1900 for irl training. maybe one day we'll see that along side a B200 and 350 professional.

I did so, and so far there has been no this problem.

@Black-Square I tested on brand new PC. So there can't be coincidence. I've been flying Baron Pro for few weeks. I fly mostly two hours hauls or 3-4 hours long hauls. Baron run smooth without any issues. I know some code is being reuse that originally pioneered in Duke and Starship to bring Baron and Bonanza up to pro. I'm guessing it something unique to Starship that causing it. I'm guessing navigation system or radar. Here are some data that may help: My PC: Ryzen 9 9950X3D, 64G RAM, RTX 5090 My last Starship route: KHQM/06 N0256F170 DCT HQM V112 ILWAC T257 ONP V452 FMG T274 LIDAT/N0285F370 DCT BASIC DCT KLAS/26L MSFS 2024 settings: [image: image.png?ex=69134c78&is=6911faf8&hm=d23be429b872f763ee3be244ba2e9eb4cb62fb81b1ac0b6375cd110200bf4944&=&format=webp&quality=lossless&width=1724&height=1114]   

I was wondering if you're finding any issues with state saving... right now, I think I was messing it up for myself because I had an N-number written in the identification field on the config menu before starting a flight. When I deleted and made everything blank, N786BP reappeared and I could have it shown on the side once again. During this- flight hours was never increasing, and fuel state wasn't saving. I realize as well FS2024 really messed things up with respect to that, the way it loads aircraft.

tc is turbo charged:)

Okay, thank you for the info, it is useful to know it's probably not intended, I will try again on SU3, and SU4 when it is out before coming back! Thanks

I have just tested this on my side, and the state saving is working as intended. I'll list a few things below that may be worth checking: "State Saving" must be enabled on the EFB prior to exiting a flight (the State Saving box will be light grey on the EFB when enabled). With State Saving enabled, the aircraft's state at the time of exiting the flight will be saved, and then reloaded the next time a flight is started in the aircraft. The State Saving should cover all controls in the cockpit, as well as external equipment such as the Chocks, Tie-downs, and Towbar. Ensure the simulator is closed down correctly via the Main Menu, rather than using Alt+F4 or Task Manager to force it to close. We don't officially support any of our products on the MSFS Sim Update Betas. Although you mentioned it in your post, I thought I would bring this up just on the off chance that you were using the SU4 Beta. The Sim Update betas are beta releases, so bugs are expected, and we have seen some odd behaviours like this in previous betas. Mark - Just Flight

We do have this logged on our internal bug tracker, and we will look into it again ahead of the next update to the F28. We did intend to look into this ahead of the recent update to the F28 Professional; however, on this occasion, our systems developer wasn't available due to commitments with other products. Mark - Just Flight

The best thing to do here will be to raise a ticket with Just Flight Support at the following link: https://www.justflight.com/support In the ticket, please attach that video and include any additional information that may help our support team replicate this behaviour (flight plan, arrival airport/runway, default/third-party airport, weather conditions, etc.). Our support team will then be best positioned to attempt to replicate this and pass it on to the development team if required. Mark - Just Flight

If you search for MFD.js, the checklists start at this.normalProcedures = [. If you want to edit the "crew notes" page, search within the file for drawCrewNotesScreen(){.

@C-FJDH Yeah not fully clear to me..@Black-Square, Nick can you enlighten us when (if) you get 5 mins?

Wonderful!! Glad you figured it out. Let me know if you ever need anything else!

Just updated this to V1.0 (haven't heard any complaints yet). Added Abbreviated Normal Checklists by me - based off the Black Square checklists. These are for people already VERY familiar with the aircraft and the full Black Square checklists. It strips items down to a more usable format on the screen. Engine start is down to just one line item "Left & Right Engine Start" - you can go to the full checklists for the details.

@Iconography said in Fuel Gauge Calibration Issue: @tttocs that’s expected - if you review the manual you’ll see that the extended tanks allow for more fuel but the gauges are still standard equipment and don’t reflect the additional fuel. Edit: found the section - Each fuel tank has a capacity of 86 U.S. Gallons, with 83 gal usable in the normally aspirated aircraft, and 101 U.S. Gallons, with 98 gal usable in the turbocharged aircraft. The extra 15 gallons of fuel stored in each wingtip cell of the turbocharged variants is not reflected on these instruments. Doh...So I'm guessing this is why I just saw 78 Gal. in the EFB and full on the gauges. RTFM is so many big words...Thank you.

Thanks I think that's got it! Reverse from SPAD.next [image: 5021399c-92b3-4400-874b-57d5622f13bf.png]

I think you could do something like this with FSUIPC and WideFS (from the same guy). As I understand it, WideFS is a remote client for FSUIPC, though I haven't played with it at all, myself.

Just thought I'd chime in here that I experienced the same thing this morning on 2020. Started from a cold and dark state on a fresh computer restart. Not really sure what I did differently this time around, but wasn't able to get AT (it would just snap off) or AP to function; FD switches turned on but no FD displayed.

Got it. Would be nice if the TDS service could house clean those services based on the simulator status, but glad to have found a solution (and that you have experienced it as well). Placed here in case users come looking for issues. There is certainly nothing wrong with the Baron at all that contributes to this issue.