Starship

It works, thanks!

@jmarkows Yes, it was the wind, nothing to do with engine starts (as I thought previously). It seems you are right and if the wind is from the tail and like around 10kt the plane will not move. I am not sure if this is how the real plane would work, but it would be nice to allow reversers to move the plane up until like 20kt tailwind.

After diving down this rabbit hole, I have to take back my jab at Collins, they actually documented it correctly. [image: 2ba52de6-7360-4a4b-9ae2-c7b3436c0410.png]

To clarify, FD vertical GS guidance

Thanks for the video. I can see that being quite useful for anyone who enjoys FS2Crew in the airliners. Let me know what I can do to make it possible when the time is right. You would think it wouldn't be terribly difficult with my checklists already formatted in XML for the simulator's interface.

@Sunake Yes, I found this odd. But more power to Black Square to properly replicate this "quirk" then

Metroliner.. ^^

@CoolGunS said in Localiser Tracking: TIP: Ensure you know the exact Final Apch Crs from the ILS approach chart and set your VOR1 needled precisely to it so that it does track the right heading to the threshold. What Nick said, it is retro tech and yes it does act a lot like a police dog following the scent from the pair of gloves. Or if you’re lazy or you forgot or don’t have the chart, you can fly using FMS until the last turn and then click CRS 1 to set the current course.

@CoolGunS You're not alone

I wouldnt know. I'm pretty sure at altitude you'd be below the gear speed till 12-13k anyways. Patrick

The very last message I just posted in that other topic explains that hopefully you will be able to do both with my current implementation. I'm still frantically writing code, but I think I will be able to overwrite any weirdness that comes from the native flight planner, leaving the airplane with the good route interpreted for Starship, and the ATC with the route to provide air traffic control.

I would be more interested to know if you have a stuck safety valve, since the cabin is still pressurizing beyond the differential limit. This would appear in your list of failures, and as a red valve on the cabin visualizer. There is some hysteresis in the valve, so it's possible that you caught it between actuations somewhere between 8.5-9.0 PSI.

Instead of just displaying the table, would it be possible to interpolate the data for altitude / temperature / weight for max cruise and best economy, and present us the interpolated book values for the current flight condition?

Make a recheck! Maybe my mistake.

@whitesnuf said in Nav-Mode not selectable: Hello, Sorry for a maybe stupid question. After my first flights with GBS as source I cannot select the nav-mode in the autopilot anymore. In the GNS I select a direct to path and want to follow it with the Nav-Mode, but I doesn't engage. It deactivated heading mode and itself stay also deactivated. I have selected the GNS as nav source. What am I missing? If you happen to be using the Haida livery for Starship, download the 1.1 update of the 2024 livery.

No worries! I hope all your problems in life can be so easy

I had someone ask a little while ago how I test my aircraft for performance, and I said that I rarely do, unless there is something very specific that I'm looking for. Instead, I just program the only way I know how, which is to conserve resources like it's maybe 2010. As for the numbers, the impact is small, but they all add up with everything else. The blinking is an addition test that must be performed on every loop, regardless of the blink state, for every single indicator that would blink. If it's supposed to only blink for ~10 seconds before coming steady, that's another counter that has to be incremented for every single indicator on every loop, and another test to see if it's supposed to become steady. When it's blinking, writing to the screen is the most resource consuming of all.

Smoke