LKPR Prague to LOWS Salzburg in the wonderful Starship... [image: 61f635e8-23c6-4ae8-9cbe-c302155776ea.png] [image: 00a826fa-b2f5-4431-978d-86d90e2eef2a.png]

For me, enabling C-State was like Gandalf tapping my PC with his cane. AB SO LUTE night and day. Thank you for this suggestion. I was going crazy with the cruise stutters with all hardware loads under 70%.

@SaabFAN86 I have no idea what format that text and color information is supposed to be presented in, nor how to get it to you. Can you give me an idea of how these other units work? I suspect this is not something that's possible from the JavaScript context, but I will do it if it's remotely possible, or send you a custom solution if it's not something I want to include for all users.

Even with the avionics powered?

Absolutely, I really appreciate the amount of work that has gone into this.

@Andydigital and that’s why telling me what I can and cannot do? Oh the hypocrisy. I have a different option than you. Deal with it.

@piosto It doesn't make any significant difference in ITT if starting feathered vs. full forward. On the actual aircraft, the peak ITT is usually achieved well before the propeller RPM has reached a hundred or so. Battery and hot section condition are the primary determinants in the health of your starts. The only reason you maybe keep things feathered with an external power start, is simply for noise and comfort of the ground crew. They have to remove the GPU plug from the L/H wing. Less air being drawn and sucked across the wing. Reduces risk of a hat or something being drawn into the spinning propeller. It's less an issue though with Starship's "backward" PT6 installation. Patrick

@ProfCrash said in RPM goes up and up in reverse: next

Trust me, I would if I could on this one. To the best I can tell (and have reported on the developer forums), they actually hard-coded their own registration "instruments" to work during the aircraft preview screens, while all other "instruments" are disabled. This is why bypassing the aircraft preview, and loading the session without changing the aircraft, allows the registration to still work in 2024.

@Black-Square Spot on Nick, still amazed how quick you come up with workarounds for this platform I'm on an xbox (PC) gamepass install for 2024 (SU2) if it makes any difference? Also with a custom drive install (E: not C:) Cheers James

Ah Sweet! Absolutely excited for 1.2

Is that why the bar light isn't modeled? I actually have no idea where it is; I went aft and poked around a bit, and the lights above the bar do work with the attached push button, so I'm assuming something would fold out and that contains the bar light? I did think it was odd that an aircraft released after the Dukes and their lovely interactive cabin didn't go as far. The explanation makes sense, and I am a cockpit flier only, so I would have gone through the cabin once to click everything and marvel at it and then probably never touched it again, so I'm not terribly crestfallen over it. I would love to see it in a future update, but I understand that time and effort don't grow on trees, and that such an ask would fall pretty much to the bottom of any totem pole.

@Halivan said in Duke in 2024?: Just made an account to help the OP here as I only have 2024 installed on my new PC. I decided not to bother with 2020 anymore. Just google “Contrails how to fake MSFS 2020 install”you will find the steps to create a blank folder in Windows to trick 2020 installers into installing sceneries, airplanes… into that blank folder. You can also change the destination of the “2020 community” folder. Afterwards, just use Addon Linker to link it to 2024’s community folder. Finally, scroll a few posts down from this one and someone explains how to get rid of the patchy liveries. I appreciate that, thank you!

Appreciate it A lot! Happy flying and sunny days to you! David, Sweden.

Loads of uses, I do all these and set as MSA on co pilot side during approaches while setting DH/MDA on pilot side

I saw in the manual that "If the opposite engine’s power is reduced below ~17% torque, both propellers will unfeather, and the autofeather system will be completely disabled". Maybe I ended up going below 16% torque on my left engine during descent, which caused the issue. But then, does that mean that in the event dual engine failure this plane cannot feather at all? I'm more familiar with piston engines that (I seem to recall) can be feathered in the event of engine failure. @Marionettework That governor failure happened with my engine at 100% health, so I guess the risk is slim but not zero!

Ah, IAPS. Which, if you were curious is still a component (and abbreviation) used in all the modern Collins stuff right up to Proline 21 Advanced.

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!

Thank you. Perhaps it is a problem if the aircraft's injected by Beyond ATC. I will test it again.

Mystery solved (I think). I recorded a flight where the creak happened but it wasn't in the recording, suggesting the sound was not coming from MSFS. I'm reading posts in OnAir discord that fragile cargo will creak during flight so that's almost certainly what's going on.