Starship

Any news about this? Having lights visible from a distance in the LOD would really help. Thanks.

@FlightEngineer1 yes, I'm aware of ai.cfg. I have used this to enable and tune (to an extent) autopilots in planes that don't have them natively, with mixed success but usually well enough to pass muster. This often also entails adding an autopilot electrical circuit to systems.cfg, and checking engines.cfg (why there?) to make sure that the param DisableAutopilotControls=0; sometimes a dev will explicitly set it to 1 and then no autopilot. Maybe I'm just old and slightly bitter at this point, but I have no faith that Asobo will ever address this, are aware of it, or even know what they're doing in this regard. There are core algorithm parameters that were REQUIRED when I was doing industrial process control PIDs, which are utterly absent here. Which brings into question the form of the equation they are using. They're never going to expose the maths, and I have better things to do.

One of the most inviting views in the sim [image: 727f8029-985e-4c16-b387-4fa9ec21a16d.png]

Brilliant, thanks Mark!

@Tadeus72 said in Your favorite medium-long range cruise altitude: Thank you, often when crossing the States I actually look for a scenic route, this might be a great inspiration, will check it out. If you fly it, please let me know how you like it. I think there's one small "error" in it near the Grand Canyon, one airfield you can get into but the runway might be too short to get out of again. Of course, if you're not flying it for the VA you can skip it no problem. I've yet to fly it myself.

That may be true. I just completed a flight using VORs only, and the FD/AP behaved the same way. Hunting for center. More of a concern though, was the AP dropping out of NAV mode to ROLL several times throughout the flight, even when close (20nm) from the VOR. And once from APP mode within 10nm of approach it dropped back into ROLL again.

H:ALT_AltitudeSelectKnob_Dec_1 and H:ALT_AltitudeSelectKnob_Inc_1 are the events for the reference altitude.

@Black-Square No problem! My friend owns the Caravan and he also confirmed that this is happening, so this is probably affecting all Black Square products.

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

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