An update for 2024 compatibility please
-
While I'm working hard on getting all my aircraft in MSFS 2024 regardless of the simulator's bugs, none of these issues (with the possible exception of the gauge glass) sound like MSFS 2024 issues to me. Have you been flying the Dukes in MSFS 2020?
I have seen reports of the mixture not working with the native bindings, but here is some advice from the FAQ at the end of the manual:
Microsoft Flight Simulator’s turbocharger simulation has been significantly flawed for several
generations. This aircraft has a custom turbocharger that fixes nearly all of these issues, and is
much more realistic, as a result. To make these changes, the new “Input Event” system is used
to intercept hardware and key-bindings for the mixture control axis. Please make sure that your
hardware bindings are using the Key Events, such as “K:MIXTURE1_DECR_SMALL”, or
“K:MIXTURE1_SET” to set the mixture, and NOT setting either “A:GENERAL ENG MIXTURE
LEVER POSITION:1”, or “B:FUEL_Mixture_1_Set”. Alternatively, setting
“L:BKSQ_MixtureLeverPosition_1” from 0-100 will also work to set the mixture axis.You might have to provide a video or screenshots for me to help you troubleshoot the pressurization system. It's relatively unlikely that it is not working, as I haven't received any other reports to that effect, and the same fundamental system is currently used in all of my aircraft. Happy to help, though. You just have to give me a little more to go on. For instance, when you check the pressurization system with the push button in the ground, are the engines at idle? The turbochargers can only pressurize the cabin if the engines are brought up to ~2,000 RPM. Also, make sure all the doors and windows are closed, and the "Cabin Door Latching Failure" is not triggered.
In the Duke, the only way for the oxygen to become depleted is if you have activated it with the knob (green band showing), or if the "Oxygen Leak" failure is triggered.
If you're using Honeycomb products, I suspect your autopilot problems might be related to control bindings, or at least that might be masking the problem. For instance, have you activated the "Pitch Trim" toggle switch on the pilot's right subpanel? Without that switch on to provide power to the trim motors, the autopilot will not engage. If you're activating the autopilot from external hardware, this could cause it to activate momentarily before being deactivated.
I'm always happy to help troubleshoot if you have any screenshots you want me to take a look at!
-
Hello team,
Thank you very much for your response. I feel foolish regarding the mixture, as I should have read your manual properly, but it’s so comprehensive and long that I actually missed that very important part. Thank you very much for reminding me ;)
Regarding the pressurisation system, I will definitely record a video for you and post the link. That will be the best option to describe it. You might find something obvious too.
The oxygen issue is actually something I’ve seen not only with myself but also in another video. I’m also going to record my next flight and see if it comes up again.
Regarding the autopilot, this time I’m actually confident I’m doing everything right. As stated previously, I will post a video showing the issue. It is bound to my Stream Deck, and I have also clicked it manually with the mouse in the cockpit. Every single time, the result is the same. So, I’m basically hoping that I’m doing something wrong, but it doesn’t feel like it.
Would you be able to tell us when you expect to port the Duke Piston and Turbine versions to Microsoft Flight Simulator 2024?
And to answer your question, I never actually tried it on Microsoft Flight Simulator 2020, because at the time I decided to wait before purchasing your plane.Thanks very much, and I can’t wait for that to happen, as well as for the other fantastic planes you have – including the new one, which I hope will go straight to 2024 as well.
-
I feel like I have to correct myself. The Dukes do, in fact, not remember the previous radio frequencies, and always spawn with the same frequencies set. Only what’s being programmed into the KNS-81 is remembered between sessions. In the stock Duke and the turbine Duke, the COM2 standby frequency is always 124.85, when I spawn, but that still doesn’t explain the behavior. I feel like the problem might be with the bundled PMS GTN. It’s not every time though, and I can’t reliably reproduce the issue.
-
@Black-Square it really happens everytime. Copied the folder over from the 2020 community folder, where this did not happen. I'll try a fresh reinstall, and will also check if this might be livery dependend. I'll report back if I have any news.
-
@Black-Square News on this! I reinstalled and then had the issue on both engines everytime. However, it always happened that the temperatures came back from zero (also according to the EDM) to normal operating temps. So I asked myself what happens when transitioning to cruise. Answer: Adjusting the cowl flaps.
I found out that when I move the cowl flaps before engine start (or possibly at any time), I am getting normal readings again.
When loading the sim up, the state of the cowl flaps is fully open. I imagine that in FS24 an unreasonably high value is set as standard. When moving the flaps, it is then overwritten by the correct value, which translates in correct CHT temps. When not moving the cowl flaps, the engine is cooled at such a high rate, that it never warms up even at takeoff power.
This is my suspicion.. I found it to be reproducable now. -
Thank you for looking into this! You are actually more correct, and your answer more accurate, than any non-developer has any right to be! I think I fixed this on my end a long time ago, so I never even saw it manifest the way you're describing. If you look at the engine visualizer on the tablet display, I think you will see that the cowl flap position indicator is clipping though the rest of the engine symbol. Yes, these are the joys of MSFS 2024. While you're looking at completely baffling bugs and errors that render your aircraft unflyable, there are also lots of little things, like the cowl flap position loaded from the *.flt files suddenly being multiplied by 100 when compared to MSFS 2020. This yielded a 10,000% starting cowl flap position, if I recall correctly. Thanks again!
-
No worries, all fixes will be rendered useless after the next SP anyways, with 10 more issues appearing out of nowhere. :P
Custom registrations for example. After switching from another aircraft and registration, they are drawn onto the aircraft correctly on the preflight screen, but messed up (like in your screenshot from a month ago) after loading in the sim. If I start the sim with the last setup (aircraft and reg) and don't change anything, the plane loads up fine in the sim as well..
I spent some years in the MilViz Beta team, so finding bugs and the cause is something I know quite well about ;) -
Hello again,
The issues I mentioned earlier are no longer a problem, but unfortunately I still can’t save the aircraft’s state — every time I load in, it’s like a brand new plane. I’m flying around the globe, starting from Poland and now in Gran Canaria, always having 100% health engine power before, during, and after each flight.
Could you please help? Thanks!PS this is my understanding of the manual, window was open, some never tested
What is saved automatically:
• Radio configuration, including:
• Preset frequencies - not
• Distances/radials/etc. in radio memory - not
• Many radio and switch settings - not
• Cabin environment and aesthetics, such as:
• Sun visors
• Armrests
• Windows
• Temperature controls -not
• Engine health -not
• Oxygen pressure
• Fuel tank levels, only if you load the aircraft with default fuel values - not
• Covers/chocks status — if “Load with Covers & Chocks Deployed” is selected in the tablet⸻
What is not saved:
• Switches affecting primary aircraft systems, like:
• Battery switches
• De-icing
• Payload and passenger weights (MSFS limitation, though internal code supports it)
• Any changes made if you exit the simulator improperly
• Must quit via “Quit to Desktop” in MSFS main menu to save properly -
@amadi8 I would assume, that having 100% health, means you’ve taken proper care of the engines. The left engine on my Turbine Duke is at 85% health, while the right engine is still at 100%. What happened to the left engine, I don’t know, I haven’t had any hot starts or anything. Possibly, there’s some debris that has entered, at some point, and caused the damage.
-
@ploodovic Thanks very much for your comment. So, I’m already on my trip—I’ve flown 16 real hours, and I assume that would show some wear and tear on the components, but everything seems to stay at 100% all the time. The longest flight was just over 3 hours, and again, when I landed, everything was still at 100%.
I’m not sure how this works with this plane, but when I fly A2A aircraft, wear and tear happens constantly—even after just a few hours, there’s already some deterioration. So yeah, I hope they’ll optimise this for 2024 and update it like they’ve done with other planes for example recently what is done by Just Flight.
-
@amadi8 I don’t think there’s anything wrong with your situation, I think it’s working as intended. You can adjust the rate at which failures happen, the MTBF, but that isn’t exclusive to the engines, that’s everything in the plane. If you want a higher degree of wear, try increasing that from the tablet.
-
@ploodovic My understanding is that failure is something different from wear and tear on the plane. It's related, but not exactly the same—because we have to make sure the plane is in running condition, not necessarily by increasing the rate at which failures occur. I’d really like to hear the developer’s opinion on this. If someone could join in, I’d really appreciate it.
-
I have not observed any differences between MSFS 2020 and 2024 regarding engine degradation or state saving. Engine condition is entirely dependent on your operation of the engines, so they will not necessarily degrade with only time in service. All "wear" is baked into the MTBF. If you fly enough, you will encounter failures eventually, and you can increase their likelihood with the global failure rate slider. I find that 10x and 25x produce failures often enough to be interesting for home simulation, since you can fly a real aircraft for hundreds of hours without a single incident.
I chose this combination of methods, as I considered it to be the more realistic way to depict failures than the performance-only methods used in some other aircraft, at least for the failures I was trying to depict. For instance, a hard landing should not really have an impact on your navigation lights circuit, nor is a factory new airplane guaranteed not to suffer infant mortality of its engine in the first five hours, not matter how well you treat it.
As for the delays with my updates, I am quick to admit that I have a curse, which makes me uncomfortable with releasing unfinished or knowingly subpar software. Unfortunately, MSFS 2024 has been my worst nightmare in that respect, because important things (like lighting) are still changing frequently on the SU2 Beta. There are also still bugs in MSFS 2024 that have a detrimental impact on my aircraft that are still not fixed, despite the simulator being released six months ago. I'm very sorry to keep you waiting, but every time I think my aircraft are ready for their official MSFS 2024 debut, something new presents itself. I have considered workarounds for these issues, in addition to the many I have already implemented, but I have left the most difficult and time consuming for last, hoping I wouldn't be forced to implement them just to overcome bugs in the core simulator. I will be releasing Starship in MSFS 2020 and 2024 regardless, so that will be the catalyst for all the other updates if the simulator's bugs are not fixed by then. I hope you understand, and thank you for being patient with me.
