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.

@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.

Bizarre! Thanks for sharing!

@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.)

@Torcsen said in External power startup - FMS-checklist items order: However, it seems the flight plan and alignment were stored in memory, because everything came right back when I switched to generator power. If you use the Fuel Mgmt page on the CDU to enter your starting fuel, be aware that the value is zeroed if you cycle power on the CDU.

@Mad_X Check out item 3 of a write up I've made a few months back. One Request, One Observation It's almost identical I believe as yours. But the funny thing is, my fuel used did agree with the tables. Just not the indication. Have a look at item 3 of my post and try to do the same. Doesn't need to be as complex. You can take remaining fuel at the start, then (leaving power constant) take another reading 15 minutes later. That difference in fuel remaining, multiply it by 4 to get your 2-engine fuel burn in pounds/hour. Divide that by 2, and you get the average engine fuel flow. That value should match the fuel flow indicator (and also your tables). For me, it matched the tables, but not the indicator. As you can see from my post, I didn't hear anything back other than that it should work normally.

Yes, funny

@AlphaEcho this is a beta SU4 issue I think. Ive been flying the starship alot recently and had no issues with lighting before latest SU4 BETA..

@Torcsen I used to put the version in the file name, but I was politely asked to stop doing this because it didn't play nice with the installer/updater for some reason. Looking at the end of the contents for the changelog, or the changelog itself, should tell you if it's up to date. It appears that Starship's manual has never been updated on the website. I was under the impression that this would be done at the same time as release. My apologies. I'll see that everything is updated soon. In the meantime, you can always find the latest manuals packaged with your aircraft, assuming you have a non-marketplace version of the aircraft.

@Black-Square Ah - that sounds good. Could even be that I had instinctively been using enter in the past, as a carryover of my operation of the KLN-90B. There, pressing enter is bound to the physical ENT key, so fx route entry can be handled entirely on the keyboard. But of course that is also a system with a different philosophy, with dedicated keys instead of LSKs, so a bit more logical to make a full on keyboard operation mode for it.

@Dingle The MSFS mod won't work in FS2024. If you still want to disable blue highlights do what I did. link to MSFS forum. It won't work for all planes but works for Aerostar and many other planes that use default Asobo templates for mouse interactions.

Just installed TBM and DUKE in 2024, and now with the new b-event system playing in all the default aircraft, it's a bit sad to be back in a cockpit with static knobs and buttons

@MikeyFlyz Why would you not be able to share it?