Piston & Turbine Dukes

@Randolf thanks for the hint - I will take a look to your AP-Template.

and thanks again for your savestate solution :-)

@Black-Square Great! That will do for sure! It will be Punta Cana to Dubai. I want to challenge myself to always keep the engines at 100% health.

Hopefully this patch will drop soon? ;)

I see that you found a way to send the message. Thanks for sharing his contact information. I just sent him an email, so hopefully we will hear back soon.

Thanks for all the notes! It's always my power users who discover the most obscure bugs. The RNAV localizer 360° wrap-around was already reported on this forum, and the fix is ready for the next update. As for the needle positions, it may be due to the fact that the wraparound allowed for inadvertent selection of OBS courses beyond 360°. The update should fix all that shortly.

Indeed you found something from the Piston Duke that accidentally made its way into the Turbine Duke! The fuel flow failure triggered the loss of a circuit that does not exist in the Turbine Duke. I've fixed that as well. Thank you for letting me know!

@Piper201 said in If you have engine problem - check your bindings (Honeycomb Bravo):

SimHanger Flight Simulation

Yes they do. I set up my Honeycomb Bravo using their tutorial back in 2020, but a lot of thing changed since than LOL

Good question. Yes, you should be able to use the control assignment "Flight Director Pitch Sync" in the simulator's control options. You just have to make sure "Control AP Pitch with Hardware Events" is selected on the tablet in the aircraft.

@Randolf I just think, since it's already been made, it would be a nice customisation addon. I'd like to be able to remove the ADF and KNS-81 personally anyway (like I said, dual GTN750s would be awesome).

I was just doing a test with night flying and saw it come on very briefly (perhaps the 2 seconds that the audio should play?). Tested a bit more and it stays illuminated longer the less VS you pass it with, so it is just connected to distance below DH selected.
The lamp is however supposed to stay illuminated untill you reach 20 feet AGL so it should have stayed on for my screenshot.
alt text

@Mustang For what it is worth I decided to to change the "Yoke" set up for the DC-6's.
4 mags and one switch, I removed the L,R,Both and Start...Then...I got really feisty and cleared out "All" electrical bindings...on both Wheel and Throttle. There are times I can't get my fingers behind the engine controls...like right after Take Off. So it may be a little "Old School", I just use the Mouse". And also the Lear 35 (PWS) just got an update and I noticed the landing lights would not go out at all, and that is with the above "No switches" set-up, SU-15 issue adding fuel to problem?

@Nicotine70 This is a Life Saver Thank You so much been pulling out my hair to try to figure out why all of a suddon it didn't work but with advice it works for me again Thank You

Quite to the contrary, I am shocked and disturbed that none of my beta testers caught this, nor did I. It looks like the scaling from the TBM snuck into the Duke at some point, and I never fixed it. Thanks for pointing this out!

I'd prefer one for Photoshop, or a combination.

And at -40 the two scales meet. Perplexing :-)

@Randolf said in Oxygen Leak and Alt Static Air:

@Kilstorm If you're using AAO and want to control it with axis, what you could do, is set the axis range to be from 0 to 1 and enable the integer checkbox, that way AAO will only send values 0 and 1 if the axis is below or above half point (assuming the variable for the oxygen knob takes values 0 and 1, didn't check).

Thanks. I will give that a try. The value is Boolean so I dont know what that means but do understand what you are saying so Ill try that and reply back.

@Randolf there it is. I knew i was missing something, Thank you very much

Super easy! It will be (L:var_PulseOxyPercent, number) in the next update. Thanks for the suggestion!

@Marionettework Rob has all of his resources publicly available online for all to see and use. However I do hope he’s participated for hands on reference for the aircraft and sound recording. As for the RNAV and VNAV, I think the aircraft only has advisory VNAV, but it is fully RNAV capable. It has also been retrofitted with GPS and will almost certainly be present. I’ve seen Rob’s plane equipped with a GNS430 in the lower pedestal beneath the autopilot, but in the walkaround of one of Raj Narayanan’s Starships, there appears to be something completely different down in that slot. I’m not sure exactly what goes there as in the manuals I’ve read it just shows a blank plate, so it might be something that can be customized. That said, I’m sure Nick has been in contact with both of them and I don’t doubt they’ve been happy to share all the bountiful info they have, so let’s hope he can get all those things done accurately.

Sorry for the late follow-up. The modelled cowl flaps were always open, they didn't budge at all, and they were matching what's visible on the tablet -> control issue.

While the audio cues for the electric motor gave me a false sense of working controls, FSUIPC interfered for SOME reason. I didn't have cowl flaps assigned to any hardware controls, but FSUIPC inherited the calibration settings for cowl flaps axes from another profile. When I turned that off (ie. when I reset the calibration settings for the unassigned axes), the cowl flaps started working.

Thank you, Nicotine, for pointing me in the right direction with the images of the open and closed cowl flaps. I never checked their state, for some reason I had this idea that the cowl flaps were internal and I hardly pay much attention to the outside of my planes unless the dev forces me to do a walkaround. I learned that I can actually observe the left-side cowl flap from the pilot seat.

@Maverick85 I have this exact same issue, sometimes it recovers and sometime it doesn’t. Completely locks up the sim and it’s super annoying. Have tried everything to work out what is causing it but still not found it.

@Randolf Definitely. It requires .cs file fromat, I suspected it won't be as easy as saving the script in text editor then renaming it to FILENAME.cs.

Currently browsing the forums to how to even create a script.... I never did such thing, used to modify existing ones back in the days for FSX and GTA:SA, but those were different times.

Anyways, thanks for your help, I will figure this out from this point.