[image: 51155bd3-7f44-41a4-928c-3e2835fae92c.png] iceland always special

Great, now I have a pitch meeting for Starship stuck in my head. Manager: So, you have a replacement for the King Air for me. Engineer: Yes sir, I do. We've been thinking about these things called composites. Lighter and stronger than traditional aluminum. We can make this airplane lighter and faster while still putting all the latest whiz-bang features into it. Manager: Sure, but how will we get the FAA to certify it? Engineer: Super simple, barely an inconvenience. Manager: What are we gonna call it? Engineer: This is the 80s! We're packing it with all of the latest in space-age materials and electronics, we should call it a Starship. Manager: I like it, with a name like that it'll be an instant hit!

In VR, the GTN would be a lot more user friendly. I don’t even need it to drive the AP, just having it for frequencies, traffic alerts, charts, etc. would be good enough for me. Understand if you want to wait for full functionality however.

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.

Interesting thread, I've had the same thing when using heading mode, I can see the GS and LOC on my display but APP didn't trigger so ignored the FD and flew down using the LOC and GS indicators. This happened after Vectors to ILS from Beyond ATC, when flying in a STAR and using Nav then wasn't an issue, APP worked as expected. Glad to see the issue wasn't between the keyboard and chair

Yeah, that adds up, I also have the feeling that the legs must be far enough apart to cause it. Thanks a lot Correction: I also see it closer to a fix.

@jmarkows I thought both were updated much more regularly? Might be wrong though. Strange it's ok in 2024. Something similar happened recently with EDDL or EDDK I think where the numbers were off for ages, people posted about it in the MSFS forums IIRC

Honestly, you could probably "spoof it" in the gauge programming I suppose (I have no knowledge of actually coding these things though), and reality is 99% of people would probably be satisfied with it. Unfortunately, only way to really model it correctly (as highlighted in an another thread) is to wholly develop a different engine model - and I don't think that's fair to put on you and this project at the moment. So is what it is. You already got a Garrett you're going to have to somehow model in MSFS with the Turbo Commander so I think your hands are gonna be full haha. Patrick

@plhought Hey Thanks for the video! Here is the AFX text for the 350 that shows the same behavior Video rewind to watch the prop governor test as well but the feather really shows the torque spike

@Black-Square Sure, you are welcome. John Hodgson or Mark Allison should have my contact details.

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

You're the best!

I stand corrected!

I am enjoying these and hope you continue with the rest of the flights.

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.

It’s absolutely fixed now @Marionettework !

Metroliner.. ^^

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

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.

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.