Starship

I would if I could, but that would be creating my own simulator to get around some of these issues, I'm afraid. I have changed nothing about how payload and fuel saving works in any of my aircraft for years. They all work on my end, and every computer I have tested on physically. Yet, it just doesn't seem to work for some people. I have spent a huge amount of time trying to find the cause in the past, with no luck. The differences that arise between installations when everything runs on Windows, and all supposedly on the same simulator versions, are really surprising.

Good questions. Performance is only degraded below ~20% engine condition, getting progressively worse until failure. Failing to disengage the starters (in a turbine aircraft) should cause any engine damage by itself. Here are all the items that can degrade engine health: Over-Torque, Prop RPM Exceedance, Ng Exceedance, Oil Temperature Exceedance, Engine Fire, and FOD Ingestion. They will not degrade below 100% if you do everything perfectly, leaving the MTBF to be the reason your engine fails (at 100% health). I consider this to be substantially more realistic than other forms of engine damage simulation that I have seen, since components often fail hours after they leave the factory, which is called "infant mortality".

I'm on the original setup as well. I have nearly finished my ferry from Wichita to Europe via the northern route, and have deselected the 430 from day one, as well as the GPS augmentation on the original system. VATSIM is a bad excuse in my opinion. While I fly on IVAO, I have never ever had any issues flying classic aircraft with classic navigation methods online. I have flown over the pond with the A2A Stratocruiser navigating by stars and weatherships, flown the 707 with INS and radio navigation, and was never turned down by ATC. Sure working an aircraft which is unable for certain procedures increases workload on both sides (hold over...), but also the fun factor. Because it's different and not the same as other aircraft, packed in a different shell. On the Dukes I'm simulating a personal aircraft that has been updated to the latest avionics (and would love to get rid of this RNAV receiver). For the Starship the original equipment is fantastic. Simbrief route import via floppy would be nice, but that's all. Of course, only my personal opinion.

Well, I've fixed it (it was actually one missing material node), but unfortunately, I was unable to improve upon the King Air, since MSFS does not provide a variable to access the amount of windshield icing. This means you will get some mildly strange behavior if you run the windshield wipers while the glass is iced over. No different than the King Air, though. As usual, I did find something to improve, though. Here is a preview from the changelog: Windshield wipers now flutter when deployed at high indicated airspeeds, and also become jammed when airframe icing is moderate. When the wipers are deployed at high airspeed, the apparent wind will affect the resistance on the motor, slowing down the downward sweep. At high enough wind speeds, the wipers will not return to their parked position at lower wiper speeds. This was a particularly fun effect to program, so I hope you enjoy it!

It’s absolutely fixed now @Marionettework !

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.