Starship

@dadgametime said in VNAV super helpful!: I’m still struggling with GS in 2024, but ILS is no problem in 2020. I think that may be a 2024 bug though. I’m still not sure about a few things under the skin like, am I navigating with VLF if I use the flight plan in the CDU but don’t use GPS? (I have the 430 turned off completely to prevent any possible conflicts). Whether or not the 430 is in the cockpit means nothing as far as position updates go, you just lose it as an option to drive the FD/AP. On the System Control page, one of the bottom right options allows you to tell what systems it can use to integrate its position. EDIT: found it, Sensors button. I have no GNS in my cockpit, but still had to select GNSS/WAAS off on this screen (there's a GPS unit in the nose avionics bay). Somewhere between the CDU and the MFD you can dig around enough and it will tell you what system it is using; it might be in the FMS page on the MFD, but it's not something I can directly point to without being at my computer to load the aircraft and look at. As far as the ILS goes, if you're trying to intercept with a heading, it seems APPR does not arm a lateral mode like it reportedly does in 2020, so you have to hit Nav as you get to the localizer and then APPR. Otherwise you will grab the GS but blow through the localizer.

@slipperfruit Look at the tablet; the cockpit air also gets piped directly into the instrument bay as well as the pilot/copilot air vents. Cabin temp gets piped into the cabin, but can also be blown into the instrument bay with the aux blower. In practice, I'm sure the cabin/cockpit differential works about as well as modern cars where the passenger tries to set a different temp from the driver but the important part is the cockpit air temp gets blown right into the bay with the displays.

The funny thing is that TOGA was in the original Asobo GNS units, and when WT took them over is when it stopped working! I went through a long back and forth with FSW in their 414 because it had stopped working for me, and eventually they told me the new, mandatory WT GNS units did not support the TOGA Kvar and as they used the avionics AP instead of coding their own, there was nothing they could do about it until WT put it back in. I was pleasantly surprised to find it working in the Starship, where I have the GNS disabled, as Nick has also traditionally relied on the AP of the underlying avionics (I think). For me, that has meant the WT GNS units, as I am not interested in using the various flavors of giant touchscreens, so for most things I've given up having TOGA work at all. However, it seems like this latest batch of nonsense has him just doing the whole thing himself, which I imagine will eventually work its way back from Starship to the Dukes, TBM, and Professional series.

Last few landings were successful on my side. Even with the "Unrestricted Beta" off, adjusting power to maintain a steady speed in slow flight is still kind of tricky. But it feels realistic (I always found slow flight too easy compared to real life in Flight Simulator). I suppose doing a bit of slow flight training would be super useful.

I had a similar issue with the CWS button in the Duke, and for my hardware the solution was to use the _IsDown variable. Try PropGovTestSwitch_IsDown instead maybe? Send it once and then zero it on release.

Just a typo. Fixed. Thanks for letting me know.

Thank you both!

And here not limited to the AP (though I suppose the root cause is the same)

It's both by design, but also because there's not much I can do about it. I can't control what's happening inside the GNS, so it just switches back by way of overriding it. I suppose I could make the CDI button inop on the GNS... I don't think it's used to anything else. Thanks for leaving the note, though. I'm sure there will be someone else with the same question.

I think I found where I added a piece of code within a few days before release that probably caused this. I'm giving Direct-To a major overhaul anyway, so this should be fixed in the process. Thanks for telling me so I knew what I was looking at in my code.

I forget how that lovely gentleman implemented it after some of our conversations, but I can always ask. I will take a look in his code too for ideas. That's actually an excellent suggestion.

There is always a small chance, but it's very low on my list, as you might imagine. It would be relatively easy for me to add the functionality of the EDM, as you suggested; however, I figured that anyone who wanted the MX screen would also want the data to be logged and saved between flights. That's where the real work begins. I'm so glad you're enjoying it, though

I'm glad it was a quick win. If only they were all that easy! Thank you!

It's just gonna take a few more months. I mean look at all the logged items that are broken in 2024, lol. It's a long list. I live in Phoenix, AZ and I can't get the buildings or terrain to look anything like the real thing. 2020 looks way more accurate for me in PHX, but I swear I've seen V1 fly on his streams and PHX looked great. It's very strange. The problem I think a lot of us have is the way MS/Asobo are creating a sim, updating it, then abandoning it for a newer version. The atmosphere, sky coloring, ground textures are so much better in 24, as is the FDE and other features like the tablet with charts and a good little planner. However, it'll be several months before we can positively say it's "stable". Heck, even AI traffic in 2020 with FSLTL is still goofy at times. In a way it's always been this way, FS2002, FS9, FSX all had relatively minor updates every 4 years, but they did break older add-ons. It's just that you had 4 solid years of code that didn't change. Now it's much like P3D where frequent updates require developers to go tweak things to continue to work. I don't envy developers in this regard, but make no mistake, the work you guys do is very much appreciated and I really enjoy some of the art we get.

That's correct. That section of the manual is always chronically neglected by me for some reason... I've fixed it.

I just think anything dynamic like that would be too resource heavy and not an effective use of code. I do think it would be cool to hear prerecorded aviation SELCAL tones and reports, but they would have to be long enough to play without just repeating. Say one recording, as you dial 8864, plays a couple aircraft reporting positions and confirming SELCALs, but reverts to noise and doesn't play again unless you tune off the frequency several KCs or something.

@jmarkows if you watch the tablet for the engines, you can see the various type of FOD being ingested, dirt, rocks, snow, rain, sand etc. when you fly through clouds at altitude, you’ll see a snowflake so ice is a risk to do damage and you’ll see a snowflake ️ in the FOD area. Wouldn’t it be nice if real planes told you that, but I guess that’s why we have checklists and rules.

While you don't have to feel bad for me, it's actually almost impossible to predict what will make a programmer upset in this respect. There's a good image I've seen to explain this. It says... Programming is chaotic magic. There are no rules. You ask a game dev "Can the player summon a giant demon that bursts from the ground in an explosion of lava?" and they'll say "sure, that's easy!". Then you'll ask "can the player wear a scarf?" and they'll go "oof." I'm always glad that people point out these little things to me, by the way. Never hesitate!