An update for 2024 compatibility please
-
Custom reg also works perfectly fine for me at this time.
The only thing I currently notice is the CHT of the right hand engine dropping to 0 on takeoff/climb, and coming back alive during cruise. I assume the gauge rises above a certain value which is no longer defined in its range. -
Unfortunately, I ran those engines until they were over 600°C and ready to seize, but I couldn't reproduce your bug. I'll keep my eye out for it. Let me know if you see it again, or can catch it on video.
Are the registrations working for you even after switching liveries in the aircraft configuration menu? It works perfectly for me, so long as you don't preview the aircraft in the configuration menu before loading your flight.
-
FWIW, I’m on Xbox and SU2 beta, and my custom registration does not work. It’s either black or white squares, sometimes flickering, or the lettering is so big, it’s displaying like two characters.
But here’s a fun one. I spawned at Monterrey (KMRY), and as soon as I took off, I was picking up an ATIS from nearby Salinas (KSNS). I thought it must be the COM2, because I had been talking to ATC on COM1. Switched over to standby frequency on COM2, still picking up ATIS. Sometimes ATIS can be a bit bugged, tried switching back and forth a couple times. Changed all four frequencies, standby and active, still picking up ATIS. Tried to turn down the volume, switch off the COMs on audio panel, changed avionics, same problem. The only way to stop the message was to completely shut down avionics, which is… not practical.
I ended the flight, and after a little bit of investigating, I found out, that default planes spawn in, with their radios tuned to 124.850 MHz. Which happens to be the frequency of the KSNS ATIS. Now, the Dukes, of course, remember your frequencies from the previous flight, and therefore don’t spawn with this default 124.850MHz. I’m not super technical, and obviously have no idea how it works, but I wonder if the default frequency somehow still gets loaded “underneath“? Even if it’s not shown to the user? Which could cause the problem?
I tried to recreate the problem in other planes, but I couldn’t. And I couldn’t either in the Duke. I thought it was a one-time fluke. After the recent city update, though, I was flying around San Francisco and when I went to land at KSFO, I started to pick up the Salinas ATIS again. And neither of my frequencies were tuned to 124.850MHz. Just weird.
-
Hello team!
First of all, amazing job! However, please port it to 2024, regardless of the registration issue, because at the moment it is unplayable for me.
Here is the list of issues I am experiencing:
Number one, from the start — when I try to choose the plane of my choice, most or all of them (depending on when I launch the simulator and whether it is in the right mood or not) do not register any mixture movement. Even when the lever is physically moving, it does not respond as it should.
I use a Honeycomb Quadrant and SPADnext, and they work with every other plane. However, with this one — and not always with the same settings, as there are no changes — there is no visible movement of the lever in the cockpit. The physical lever moves, but there is no corresponding visual movement in the cockpit.The second problem I have is that when I follow the cabin pressurisation system and the checklist, the cabin climb does not correspond to what the checklist shows. There is no movement up or down, regardless of the cabin altitude setup or whether I press the test button or not.
Another issue is with the oxygen system. When I finish the flight, the oxygen is always completely depleted, and sometimes it happens just before I land. I follow the tutorials, and it seems like I am doing everything correctly, with the difference between the cabin altitude remaining within the green zone, so I do not know why this is happening. It might be a bug or something I am doing wrong, but so far I have been unable to determine the cause.The third problem is that sometimes not all the textures for the glass gauges are loading. Usually, a quick reset resolves this issue.
The fourth problem is that, not always but sometimes, when I start the autopilot and engage it, it disengages a second later. It is also impossible to perform the run-up checks when testing the autopilot, as it disengages immediately every single time. However, during the flight, it usually stays engaged without changing any settings, so everything that needs to be on is exactly as it was previously.
-
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.
