Starship

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.

@DrZGard the only things I have working in modded files right now are the transponder presets and changing the fuel increment from 10 to 5. I have tried the others in modded files, and I think they should work but they don't, either as a separate mod or modding the files directly in the aircraft folder (which I hate doing). I should mention this is in 2024 SU3.

@Black-Square I also have reversed trim, it's an aircraft issue as very few other planes has this reversed. Also I'm in MSFS2020, so it's not connected to sim version. This comes up with only a few planes, and only if the trim is on an axis like my controls or the Turtle Beach controllers; it's been like this since the release of the Starship. You can reproduce it with any hardware axis (eg throttle) bound to the trim axis, just compare Starship to other planes eg. the default 172.

@OrangeAnon Thanks so much, this has fixed my issue! I might give in and use something like mobiflight in the future. For now I'll just accept the quirks of the native MSFS way.

[image: 0f68280a-aa93-4bdf-9527-e502c8fab584.jpeg] I had to take a screenshot from a video I took at USNA while visiting my son there. Across the water from the years, you can see the three remaining VLF towers. Sorry. It was a drizzly day.

You mean the last SU4 beta update I assume? Did it cause a co-pilot to appear in the Starship?

I've had another AP coupled VOR approach fail. This approach had a standard teardrop intercept, so I set NAV2 on the outbound radial and NAV1 to the inbound radial. As I approached the IAF I activated NAV2 as the source and pressed NAV. She coupled to the outbound radial and flew it beautifully, Using HDG mode at the completion of the outbound I set up a standard 30-degree intercept to the inbound radial, changed the Nav source to VOR1 and pressed NAV. It flew right through the radial without intercepting, so I finished the approach manually.

@jmarkows LNAV approach. Achieves the same thing as a non-ILS VOR or NDB approach with similar minimums except the GPS is providing the lateral guidance.

The whole bundle, it's cheaper than buying them separately

Unfortunately I still has this issue randomly coming up even after 1.2 . It only happens to Starship and I believe it has to something with custom avionics. Recently I upgraded to RTX5090 thinking may be related video memory issue obviously its not . I tried several long hauls routes without any issue. Then intermittent stutter came back - every second micro stutter. It usually happens enroute and all the way to the landing. I program FMS manually typing each waypoint using keyboard. The only thing come to my mind is something to do with waypoint programing.

@piosto All good

Yes, it’s as simple as replacing a single file. It has the words “gauge glass” in the name. Sorry, I’m not at my desk right now. If you can create a blank or modified .dds (2020) or .kxt2 (2024) file, you could just drop the file in the aircraft’s texture folder for yourself. The more “correct” way to do this in MSFS is to create a mod, which is loaded in your community folder. If you’ve never done this before, it can be a little tedious to set up, but for anyone familiar with the process, it will only take a couple minutes.

Thanks for the quick response! I shut the sim down and restarted it, the issue disappeared and systems now operate normally and the Hobbs meter works now. Go figure. Thanks for the great aircraft!!!

Thanks for the screenshots! That always makes troubleshooting so much easier. I’m glad to hear you’re enjoying Starship. She will always be my favorite. Everything looks like it’s configured correctly. This might sound like a silly question, but what weather are you looking for on the horizon? I’ve seen many users who are not aware that weather radar only detects precipitation, and not clouds.

Anyone know if this question has already been answered somewhere? If so, please link…

@Black-Square the distance is absolutely fixed i can see the starship from miles away in the daytime, but you might have only rigged the lights to the highest level of LoD? Cheers

@Kaaplink Thanks, my idiot self had not updated to V1.2. Once I did that and turned on the setting, it worked perfectly! Thanks a million!