Piston & Turbine Dukes

Just resurrecting this old post. As far as I can see there's still no paintkit - is that correct? Any chance Black Square could release one please? I can make do with the plain white aircraft but a paintkit would be easier, to separate out dirt layers and other details (if one exists!)

That’s great, thanks very much.

I was recharging it from the tablet.

I like Elizabethton and Roanoak, cheers

@Black-Square Thank you!

@Noob21 My father purchased the second Piper Navajo Chieftain off the production line (saved from the Lock Haven flood by being in the paint shop). In its first year had de ice boots, radar, and King KN74 RNAV installed. This was 1973. I remember watching the numbers roll up or down when he would change waypoints.

I suspected it was one of your personal touches, I appreciate it. So in this case I should ignore the ETM and keep the engines syncronised based on the engine instruments directly, correct?

@John-S Thanks for the kind words, I'm glad to hear that you are having fun. Logs are a bit difficult, since I cannot write to the file system with JS avionics. Best would be if you could find a reproducible case. Like a sequence of actions and a specific approach that always results in the problems you see. If I can then reproduce the issue on my machine, I can use the debugging tools to see what is going and then it is usually easy to find and fix the issue. The most difficult part is usually to reproduce the issue. A video also helps a lot to see what steps you are taking.

Both engines were at 100%. I've only had the Duke package about a week. I can't thing of any other cause, nothing in my Com Folder but scenery and other aircraft. No performance stuff. It's probably not noticeable in most cases, I only noticed in long cruises when in economy mode. It's by no means a "show stopper" just something I noticed and wanted to see if it was a bug or something I'm doing wrong.

That would be a fun feature (and one that would be both fascinating and horrifying in the real world). Unfortunately, Asobo has not made it possible to save any kind of file from the Javascript context, presumably for security reasons. This means that I am limited in the size and formats that I can choose for stored data within the simulator's own state saving, which I have found not to be terribly reliable. I have brainstormed many amazing features that I would add with better or more stable state saving, but that would either require me to build my own internal networking protocol between JS and WASM (I've done that once already for JS to/from RPN), or for something to change on Asobo's side of things. Trust me, I have lots of ideas, and I will add yours to the list! I would enjoy asymmetric flap extension in aircraft where that is possible. For the Starship in particular, it's theoretically possible for the flaps to become asymmetric, as well as out of sync with the forward wing, which could produce some interesting results. Almost anything is possible in MSFS if you want it badly enough, but the native aerodynamics simulation does not provide any way of achieving this without the kind of creative solutions that I have created for most features in my aircraft.

Fantastic stuff, thanks for the reply and the extra detail. It seems almost counter-intuitive to use a dedicated heater at all times, when the engines are capable of providing plenty of hot air to the cabin once airborne, but given the age of the aircraft, it was likely a design choice based on cost or complexity or availability of suitable equipment to regulate the temperature. Not sure, but the fact we are asking such questions to understand your aircraft in such depth is a testament to the incredible simulation you've built!

Wonderful. I'm so glad I thought of that. Happy flying! There will be a compatibility update for the Dukes soon, so you can look forward to improved visuals and some new walkaround features.

Hello, any news about this issue fix ? maybe in 2024 release please? Thanks !

Hey @Randolf thank you, that's very kind of you. This is exactly what I was trying to do; however, I was trying to follow the manual's instructions for using the sliding arrows, etc from the main configuration window. I wasn't able to enter negative values there (via the RAW button), but via the Developer mode Behaviors I deduced that a negative value was what I needed, so I was very confused. But somehow I didn't notice the min/max boxes in the Assignment window -- I guess I was too focused on the other section. Thanks again! Derek

Yes, that's exactly what I need!

The speed at which you might be able to increment/decrement that variable would be up to the hardware binding software that you're using, but this very simple code will just increment/decrement the variable every time the code is run. (L:XMLVAR_Cabin_Heat_1_Position, number) ++ 100 min (>L:XMLVAR_Cabin_Heat_1_Position, number) (L:XMLVAR_Cabin_Heat_1_Position, number) -- 0 max (>L:XMLVAR_Cabin_Heat_1_Position, number)

I'm not sure about the earlier posts in this topic, but the Turbine Duke has different fuel capacities in each wing. Since the MSFS payload interface sliders load the aircraft to a given percentage of fuel, I would expect this difference to show up if you load the aircraft with the sliders. The left fuel system has a capacity of 138.4 gallons and the right has 132.5, which would account for your 6 gallon difference if the sliders were set to 100% for both tanks.

It's working fine! P.S Flight Sim Awards 2025 - You Are The Winners !!! Congratulations !