Starship

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

I think I've talked myself into this working as designed. The progress page reports the distance from your aircraft to the first waypoint, and the distances between subsequent waypoints. If you are flying away from the first waypoint, all of the distances will increase, which is what I saw the other day. In that case though, I was flying away from the first waypoint and towards the second, which caused a little cognitive dissonance (why is the distance to the waypoint I'm flying towards increasing, not realizing until later that the distance is not the distance to the next waypoint, it's the distance from your aircraft to the first waypoint and then the second).

I figured it out, system control -> GNS -> Nav source -> FMS1

**Typo above ^ I meant to say RNAV 0.3 for the AMS-850 but LNAV only and definitely not RF capable. My b.

Tips I've found if you want to keep your avionics bays as cool as possible. Turn on the ALTN and leave it on. As soon as you have the engines lit: Bleed air valves to Both Temp mode to Auto CKPT and CABIN Blowers all the way up Turn the CKPT temp all the way down (the inner knob) Set the Cabin temp so that the Temp Mode Target on the Cabin page on the tablet shows 70 degrees or whatever you want the cabin temp to be. turn on the lights master and turn down the displays (less heat) You can have those bays in the green most of the time doing those things. If your cabin temp won't stay with the set temp (Temp mode target on the Cabin page on the tablet will turn red) then turn the bleed air valves up to High Flow.

@CapVideo They seem quite random, but are fairly frequent with ILS still... Haven't gotten a chance the last bit but hoping to do more testing on it to find any common scenarios at least. Thanks!

Just noticed this today - fuel burn goes way down at higher sim rates. I'm at 36k feet right now with my fuel flow showing at 250 pph per side at 1x sim rate. If I turn it up to 4x it goes down to 226 pph and 8x goes down to 160 pph. I do use sim rate quite a lot for long cruises - I'm flying the Starship around the world right now.

Maybe I have seen a similar issue (but on SU4 beta, don't know if that plays probably a role) I was on a course which had sth like a wide rectangle path. [image: 87f4610b-0448-436f-81e3-df107cac48df.png] Original active leg was from the left position to 1 (note: its just for illustration. "1" was not the first WPT on the plan) Then I set a direct-to to 3. What happened then was, that the leg from 2 to 3 got magenta. And the Starship was flying a course like the direction from 2 to 3. But not heading to the leg or to 3. What I would have been expecting was, that it steers at this point directly to 3, maybe "illustrated by a magenta line from PPOS to 3?! But no line was drawn, just the active magenta leg from 2 to 3. I then made a direct to to 4, leg 3 to 4 got active and Starship was flying to that leg. Mysterious ...

Oh okay. Maybe it's a case where my references are too old and the starships you modeled this after behave differently? But yeah the other stuff I mention was fixed so thank you for that and sorry, it's just the manual boot tests are not displaying and extinguishing the various messages.