Starship

The beep is from the computers in the cabinet behind the copilot's seat, which get powered up for either avionics switch, so that makes sense. The ground com will always make its beep separately.

Why do you think I said I understand if you don't want to implement it And I fully agree, we prefer more aircraft

@SebAvi I've made a note in my email today for them to look into this, or at least get an explanation of why this still persists. Hopefully there is something we can do about it.

@MiRexer Thank you ! I am using the desktop icon or launching from the Steam library. I don't use task bar icons @Black-Square Thank you Nick. I always wondered why I never had state saving issues with the JF planes, but I see that those use WASM code.

Bizarre! Thanks for sharing!

I figured it would be something that would get re-used in multiple aircraft. I would add though, the built-in ATC is most likely to be used by more casual people who will pick up this plane in Marketplace, and they won't know to ask about this issue on the Justflight forums, they might just drop their rating a bit, call it "buggy", or whine about it on Facebook, and move on. I've already seen other people ask about it on other forums. The hard core people who come here tend to scoff at the built-in ATC.

Your stories of flying with your father warm my heart! You describe Starship in exactly the same way that I feel about it. What an absolutely remarkable aircraft. So glad you're enjoying it. Short answers... The sun visors are like that in all my aircraft, because I remove all glass elements in the first LOD model. Otherwise, they seem to cause graphical issues like flashing with some export settings. I've been meaning to revisit this for a long time to see if anything has improved over the years. I have taken note of your career mode request. I have had relatively few requests for career mode compatibility for all my aircraft since MSFS 2024 released, which I was quite thankful for, if I'm being honest. The requirements for career mode approval from Asobo are extremely onerous and arbitrary for aircraft developers, so it would represent an investment of many weeks for my entire fleet. Nonetheless, if I get enough requests, then it shall be done! Thanks again for your stories, and please let me know if there is anything I can ever do to improve your flying experience for you and your father!

My old CPU has died. I upgraded my PC to Ryzen 9 99503D. I will be testing again to see if performance issue still persists

@x4569 Where in that picture is the aftermarket TCAS?

@Black-Square said in Bindings for copilot instruments & standbys: To increment and decrement the glass panel barometers, it should be as easy as the HTML events: K:ALT_BaroAdjust_Inc_1 and K:ALT_BaroAdjust_Dec_1 (_2 for the right side). For the standby altimeter, you can use the native events: K:KOHLSMAN_INC and K:KOHLSMAN_DEC. K events like that are normally able to be bound with MSFS default bindings, yes?

In general I would love to see more mapping to standard key commands by 3rd party developers - I’m on Xbox so strictly limited to 2024 in-game commands. The stock 172 and Caravan, for example, offer extremely generous control mappings (every button on the GPS unit, rotary light dials etc).

Yeah, I wasn't sure. I'm creating my SPAD.next profile. Thanks !

Thanks Nick for the answers!

Oh yeah there was also a co2 detector failure that I missed - saw it when I was resetting the oxygen leak. I didn't notice the oxygen leak until I'd lost almost half of it

(I just attempted a post here that appears to have failed so I apologise if it subsequently appears as a duplicate) I tried both methods you asked about with no success I'm afraid. If it helps at all, this is the flightplan text string out of Simbrief. KSEZ/21 N0273F080 DCT 360530N1112259W DCT KLIFF DCT 364809N1113625W DCT KPGA DCT 365159N1113524W 364902N1113752W 363745N1114550W 363029N1115113W 362703N1115018W 362537N1115219W 362343N1115255W 362328N1115058W 362218N1115329W 361140N1114758W 360608N1114949W 360245N1115423W 360607N1120522W 360339N1120629W 355749N1120757W 353031N1121024W 351832N1121035W 351601N1120946W 350435N1115659W 350004N1115815W 345807N1120128W 345541N1115943W KSEZ/03. I also have the PLN file I could send along for analysis if that's helpful. (In case anyone is wondering about the craziness of this plan, it was intended to give me a rough guide to a closed circuit for a high speed low level run through the marble canyon and grand canyon areas.)

I realized today that I hadn't taken Starship on a trip around the Mach Loop yet. [image: 2d68de7d-d982-40e0-848d-3e7ff1fccd86.png]