Piston & Turbine Dukes

Sorry that's happening to you. Nothing is more infuriating than a CTD at the end of a flight. Luckily, I can't recall a single reported case of CTD's with the Dukes that wasn't a one-time thing, or wasn't eventually attributed to something else. The method that I have chosen for programming my aircraft makes them delightfully resistant to CTD's, unlike aircraft that use a lot of WASM instruments.

From what I've seen in my own coding, I always suspect the GPS unit in the case of CTD's, because the simulator's native flight planning system seems to be one of its least stable aspects. For the sake of testing, I would recommend using another GPS unit on a couple flights to see if the CTD can be attributed to the GTN 750/650.

Feel free to report back here, but I might also recommend contacting Just Flight support. They have a knowledgebase for general simulator issues, while I specialize in the aircraft specific knowledge. They will also have access to an XBOX for testing, if that's needed. Please let me know what you discover!

I was recharging it from the tablet.

I like Elizabethton and Roanoak, cheers

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 ;)

@Black-Square Thank you!

Just experienced this myself. I was definitely not parked on a parking spot. I agree with @seipp that the restriction should only be chocks or brakes, to accommodate airports with crap parking design.

That would be excellent, thank you!

Really appreciate these amazing planes.

@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.

Thanks! @Black-Square :)

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.

I recently turned on the headphones simulation in 2020 through the menus, but I actually didn't like it (certainly in comparison with the Comanche's custom implementation). So while I am excited for the next Duke update, I'm cautiously interested to see whether the variable noise cancellation (great idea!) works quite as well or if I'll prefer it switched off.

I think I have become accustomed to the volume of the Duke in cruise now. It's when switching to the external view for screenshots that my ear drums are assaulted! :D I know it's realistic, but it would nice if the internal/external volume could be better balanced for my own sake, and that of anyone in earshot! Not sure if it could be handled via the tablet, or if it's baked into the simulation (perhaps a .cfg file edit). Maybe another idea for the list.

I know the 2020 Duke update won't launch before the 2024 update is ready, as that might cause chaos and frustration, but at this point I'm cursing 2024 for dragging general progress down for 2020 products ;)

@Black-Square It's solved now. Thanks for responding and helping.

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! :D

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.