Piston & Turbine Dukes

I'm mainly looking forward to the 2020 update, as I haven't moved over to 2024 for any 'formal' flying. I think the 2020 update has been baked and out of the oven a while but is held up by the turbulent 2024 situation. Main areas I'm excited about: Headphone simulation Rain sounds Better click-spots for cowl flaps (hopefully) and maybe the wing anti-ice switch (fiddly to flick it down) Fuel levels saving correctly (not sure if that fix is in), maybe a few other persistency elements Some other stuff I likely read about and have since forgotten! The update might also see me switch to 2024 at last, since the Duke is the main aircraft I'm flying these days (I tend to spend months with one aircraft at a time, as if I own it).

@Black-Square said in Love the sound, but need headphones shortcut!: @Orlaam I agree that all aircraft I have experienced feel noticeably worse in 2024. I find them much less satisfying to fly in my pursuits as a real pilot. I have been hesitant to make adjustments, because there were no advertised differences to existing flight models in 2024, and I think the difference might lie only in control input responsiveness. I have decreased the sensitivities of my controls substantially compared to 2020, and that has helped. Although I don't like making changes at the last moment, I may find the safest variable to tweak on my 2024 updates in an attempt to alleviate this. I actually think the 2024 flight model is more enjoyable than 2020 overall. I am not a real pilot, but when I watch videos of landings, the 7-10 knot winds aren't blowing planes all over the place and pushing them off the runway, which is how I feel 2020 and previous versions of MSFS do. The iFly 737 MAX is great in both 2020 and 2024, but when you touchdown in 2024, the MAX doesn't try and run off the runway. The controller input for crosswind input is less extreme, thus to me it's better. The Starship handles great in both sims as well. The differences between aircraft can be very vast though, and I assume it's how they tweaked the FDE. It seems one can overcome the minutia of oddities in MSFS if done right. The Starship certainly seems to overcome some problems MSFS inherently has, albeit accounting for the drag of the props or canard wing.

Right! Got it sorted. 4 for the 'On' + Repeat when held. Starter has a little dig but I'll live with that. Can't do a mag check though but I'll live with that as well. Thanks again for replying, I appreciate it. No need to look for another twin now.

Got it. I see the section in the manual. Thanks.

It sounds like the throttle is full forward and the engine overtorques

@Buzz you may well be right. Given that the majority of the time the aircraft is loaded in the sim, it will be in a running state, that approach won't make much of a meaningful difference vs a failure timer that only runs when engines are running. Nick said there's a reason for real inspections being "based on calendar months", which I took to mean that all the elapsed time between flights would be considered for failure generation when you next load the Duke in the sim, but I may have read too much into it. I suppose one way to test might be to set my computer clock to 1995 (furthest back Win10 will go), reinitialise the Duke by deleting any saved/state files, then load it in the present day and see if any failures had appeared. But I'll just wait and see if Nick clarifies first. If your idea is right, then maybe my idea can go on the wishlist instead - perhaps as a toggle option

I almost thought this was a duplicate, because we just had a nearly identical post a day or two ago. Here was my response: "Every time I have seen a similar complaint, the cause has been destroyed engines (usually due to improper starting procedure). Check the engine health bars on the upper right of each engine visualizer page. If they are at 100%, then we can troubleshoot further. A video or screenshots might help at that stage." If that's not the problem, let me know and we will troubleshoot together.

Every time I have seen a similar complaint, the cause has been destroyed engines (usually due to improper starting procedure). Check the engine health bars on the upper right of each engine visualizer page. If they are at 100%, then we can troubleshoot further. A video or screenshots might help at that stage.

Fixed, luckily another user had the same problem and he posted this solution and it worked for me Create directory "Microsoft Flight Simulator" inside directory "C:\Users%USERNAME%|AppData|Roaming" Copy file "UserCfg.opt" from "C:\Users%USERNAME%\AppData\Local|Packages\Microsoft.Limitless_8 wekyb3d8bbwelLocalCache" into newly created directory above (1.) That's it - then you can run installer and after install you can remove

@Gilandred Well, it doesn't seem to have been the case. I made it very clear that I didn't want price protection, especially not a year later, but only that I wanted the option to pay the difference between the Piston and the Bundle at the official price. Nothing else. The rest is just something you made up.

Awesome. Thank you. I will look.

The KX-155's are not GPS units, therefore they represent the "No-GPS" option. There is currently no way to load a sequence of RNAV waypoints into the KNS-80 or KNS-81. I haven't looked into it, but I suspect this would not really be possible, given how the flight planning system works in MSFS, as the waypoints are not defined by radial/distance pairs. In theory, I could create a system that selects appropriate radial/distance pairs based on injected GPS waypoints, but I don't think this would satisfy most users who want to follow realistic RNAV procedures, or actual history charts, as much as possible. Let me know if you have any more questions!

I found a solution to make the installer from Just Flight work with MSFS 2024: Create a folder on your PC Called Microsoft Flight Simulator In the following location C:\users<YourName>\AppData\Roaming\Microsoft Flight Simulator Then copy from your 2024 folder the UserOpt.config into it. That’s all you need to do. Any installer e.g. Just flight will now work and install the planes into your 2024 folder and the DRM will work.

I encountered the same problem during multiple flights. When I start cold and dark on a parking spot fuel flow is showing 0.0 although everything is working fine. If I start on the runway with the engine running fuel flow is displayed without any issues. I investigated a little bit further and found that in cold and dark start the fuel flow is 0.0 when I move the condition levers each on its own with the mouse to start the engine. If I start both engines at the same time with both condition levers bound to my VKB STECS axis I normally use for leaning engine in single engine planes like the DA40 engine starts and fuel flow is showing with correct numbers throughout the rest of the flight. Unfortunately I don't have the option to use two separate axis for each condition lever and it feels a little bit unnatural to do a double turbine start at the same time in parallel.I hope this information helps you to fix this problem for MSFS2024 update. Anything I can do in the meantime to enjoy the turbine with fuel flow information in MSFS 2024 in a normal startup procedure? I love my Turbine Duke in MSFS 2024. Currently I am crossing the Atlantic from Wichita factory to my home field Nuremberg in a realistic transfer. Can't wait for an officialy supported version.

Glad you found the solution! Indeed, that addon has caused us a lot of headaches, but I haven't seen it come up in a while, so I didn't immediately think to recommend looking for it. Let me know if you have any more questions!

@Black-Square All sorted Nick. I dropped my wallet on SPAD and learned how to use it. Took a few days but the clues on these forums and some youtubes later - I have solved all my annoying issues with all of your products and some other 3rd party AC. Should have bought SPAD a long time ago I guess. The answer for this was to add LVAR:bksq_TabletVisible 0 or 1 to display and dismiss it.