Starship

Found a way to avoid the second point. I was always selecting an arrival airport before starting the flight and this triggered the auto-import later in the Starship. No arrival airport, no automatic import, good enough for me

I never thought to check that. It happens on a regular flight plan route, so that distance could be 5NM to 150NM. Seems to hunt for center for a while before settling in. On my flight last night, I did note that the FD/AP was very solid when tracking large changes using the heading bug. So it's related to NAV mode. Is it possible that the CDI sensitivity is too high for enroute navigation? I know some units have different settings for enroute vs approach.

I've noticed this too on the Xbox series X. After flying the P180, many sounds are missing when going back to the Starship. This is also for the Baron and Bonanza. Restarting the sim is the only thing I can do on Xbox to fix this. No big deal for me, just information to share.

@SadBucket Great! Tks!

I have started to notice it in other planes as well now. Thanks for your effort but this seems something that Asobo needs to address. In comparison, the Starship isn't the worst affected.

Not sure you read the thread (particularly Nick's responses rather than my drivel), but those vars aren't (or weren't) being exposed, they're only internal. So AAO/SPAD/Mobiflight can't see them, at least not until you make the changes to expose them that Nick and I talk though up above. All sorted now though!

@SadBucket I do fly predominantly without the 430, however if I am flying a rnav departure or arrival, it comes in handy. Especially an intercept of a radial of a waypoint.

I'm mainly flying the Baron Pro, but have had the same problems, especially on short final and if the wind speed is 10kts+. I actually found the plane uncontrollable and nothing could stop it rolling over and crashing inverted. This happened with some other aircraft, but not all. I tried to use the MSFS2024 turbulence settings to fix it, but I found that setting it to Low or Medium resulted in no turbulence at all, so quite boring. Then I discovered and installed ActiveSky. I have set the Turbulence Effect Scale to 50% (the default) and then reduced overall wind turbulence from 100% to 50%. This results in there still being turbulence on the plane in the air, and some more turbulence on short final still, but now it's manageable. And what a great weather synthesis! Much more realistic looking skies, and more closely aligned to Windy.com's winds. Give it a go!

It was hot starting as if the engine covers were still in place despite not visably being in place. I did a restart of the sim, un install, re install of SU5 beta and it seems to work correctly now. Shhhhhh dont wake the copilot troll :p

@Black-Square said in Starship 2024: I always publish changelogs with each of my updates, but since Starship was released for MSFS 2024 on day-one, there aren't any specific changelog items for the MSFS 2024 features. The walkaround features include the external power, pitot and static covers, engine covers, gear downlock pins, and chocks. I have some updates for Starship that are yet to be released, which will include interactable control surfaces, and sounds for all the walkaround actions. I hope that answers your questions! Always let me know if you have any more. thank you for your response

The Navigraph survey is out too, put Starship down as a vote there as well. For anticipated releases it was "Anything by Black Square and the PMDG 737-700", I really like the BBJ. https://navigraph.surveysparrow.com/s/navigraph-flightsim-community-survey-2026/tt-DfDJ6

@Black-Square said in Copilot and passengers not visible: @qqwertzde When payloads are adjusted via the native payload interface in MSFS 2024, it causes Canard aircraft to flip over backwards. Thanks for the feedback, I really appreciate it. Pity that we can't have pax in the Starship then.

Interesting. I would have thought damage modeling would have allowed it to extend at any speed, and if you're past the extension or retraction speeds then you'd suffer effects. Is there a reason it's set to 190 instead of 200?

oh i have 0.1.0 but latest is 0.1.2 u think that could be the cause? EDIT : i've read the change log and there is something about it indeed so its on me thanks anyways!

@MD82 Feel free to use it a lot and let me know if you find any issues or inconsistencies. I moved away from the landing page look to give it more of a 'calculator' feel.