Piston & Turbine Dukes

Oh, I was going to send you a link to another thread where I explained how I fixed this, but I see that you were the one who started that thread. Yes, this is already done for all my aircraft, and will be included in the next update for the Dukes. Enjoy

yup, it was....I'm stupid...thanks ^^"

The camera's bounding box is baked into the model, so it would not be something you can adjust on your end, unfortunately. You could set a camera preset for this location, or use the native "toggle landing view" control in MSFS, both of which should ignore the bounding box. I try to create the bounding box to give as much vertical height as possible, so I suspect that there isn't much I can do in that respect without the camera beginning to clip through the geometry. I hope that answers your question. You know where to find me if you have any more!

What I've started to do with the turbine duke is just adjust the throttle to match the fuel flow figures in the manual. The speed is off slightly but that way I won't run out of fuel.

That is a purposeful choice that myself and some other developers have taken. The way the MSFS rendering engine works, objects spinning at high speed will develop a fuzzy and jittering halo around them. To me, this is infinitely more distracting to a real world pilot than the static spinner with a blurred material. I appreciate the feedback, and if the majority of the community says they prefer the way it is in the default aircraft, then I will reconsider my opinion, as I always want as many of my users to be happy as possible.

@rockywaves See reply in your other thread.

Brilliant! I had pressed the Repair Engine many times thinking that was a "cure all" for anything wrong. After cleaning plugs and clearing cylinders the best plane in FS2024 is running at 100% for me again. Thanks so much for the help and all you do for our hobby!

Similarly, while programming SPAD as well, I've been trying to understand the CWS/ATT mode further myself and have confused myself with the manual. Should pushing ATT sync the pitch knob/FD to the current pitch of the aircraft? Or should I be pushing CWS first to achieve that? (I suppose that's really an "order of operations" type question perhaps) Thanks!

I'm having trouble with shutdown using this exact configuration (GTN750); I'll test it with a different configuration.

Hmmm, time to find that breaker...

@Tailhook said in Duke (Piston + Turbine) LVAR for MobiFlight: "starterInUseSeconds" Lvar compared to the Baron XML, but that might be a leftover dead-code now That's correct. It's from before I simulated battery temperature more accurately. Let me know if you find the issue, or have any more suggestions! Everything seems to have gone well in this respect with the last update, so I am now less afraid of making changes in this area

I have the premium version on Xbox and everything words fine with the Duke

Okay that makes sense, I will do some more flights with another GPS to see if its the 750 then. I appreciate the info, thank you!

That's great news, thanks! It was obviously not a huge issue but irritating every time you see it nontheless.

I just wanted to let you guys know that I implemented a workaround for this issue, which will be released in the next update when SU4 is released. You can read about it further in this post, if you would like. Thanks again!

@GunStrauss It will not be 2024 exclusive, but that does not limit my ability to use any 2024 features. With reference to the fuel flow issue, the solution is not 2024 exclusive, and it will be implemented for the Commander 114, and hopefully back-ported to all my previous aircraft.

@Black-Square Oh ok thx for the reply. I'm looking forward at the Bonanza and Baron Professional. One question still, when you have time, will you try to give the beacon lights for the Dukes a bit more juice in daylight ? I'm not talking about strobes, nav's or landing lights, they are fine, I would love to see the beacon flashing during daytime. Like the one on the Aerostar.

@Black-Square Have you noted that for the next update?

@Black-Square nah I think SU4's borked something, the latest beta's had all sorts of regressions in it

Thanks - will give that a try this weekend.