Piston & Turbine Dukes

@SMN204 I'm using K:AVIONICS_MASTER_1_ON and K:AVIONICS_MASTER_1_OFF events. You should be able to find those among in the list of events in FSUIPC, no need to define your own for them.

Thanks brennan. Could you please elaborate what you meant by entering Beta range ? Found the Beta range in the manual.
Checked and it is the cause.
Thanks

It is easy made with the MSFS controls. With Honeycomb Alpha in my case, but also can be made with other hardware. Magneto-Srarter knob.jpg

Hope this help.

As always, a problem with the Community Folder. Wrong gtn750 folder. subfolder gtn750 👍🏻

Thanks for the explanation.

@ExcessionOCP I can confirm that this mapping works for me too (and is not flaky at all), provided the new v1.1 tablet option “Control AP Pitch with Hardware Events” is enabled. Thanks for the tip! I also can't quite remember what the MSFS binding is called. It isn't quite what you wrote you above, but there are not many to choose from along those lines.

I mapped it to the IAS button on my Honeycomb Bravo. Press and hold while adjusting pitch, then let go to keep that pitch. I presume this isn't a realistic option for the Century IV (the manual doesn't say either way) but it is convenient!

I thought I'd tag in @flying_drunkard in case this was still an unsolved point.

N1930G. It doesn't take it at all no matter how much I try. My best guess is that whatever aggressive censorship algorithm Microsoft has implemented thinks that N193 looks like the first few letters in a certain word that they don't want to allow, but just a wild guess. It accepts N1903G.

Your workaround worked though! Thanks.

@hangar_101 said in Event for "green course bug" HSI ?:

I have not tested it but I believe the events HEADING_BUG_DEC & HEADING_BUG_INC might do the same job as well.

This is work in FSUIPC!!
(>K:HEADING_BUG_DEC)
(>K:HEADING_BUG_INC)

Thanks!

Many thanks !!!

@hangar_101 yes, not all the breakers are shown on the diagram, only some main busses - those which affect multiple circuits, not individual circuit breakers which should be obvious in what they connect.

Figured it out. It was an engine failures bug. Turned off failures and all worked as it should. Thanks for all the suggestions!

@Black-Square So you changed the time displayed as HOBBS time with the engine time with this update?

I stumbled across, because I set the Hobbs hours in the state.cfg of the Grand Duke to match the hours of my Duke in FSEconomy, right after my first installation after release.
But after the update it shows the engine time (the numbers don't match on the screenshots of the CFG and the hobbs meter, because I did one flight in between. But instead of the saved "57x.." hobbs time, it shows the "47x.." engine time.)

Bild Text
Bild Text

It's no problem, but I'm just curious to know if it's on purpose. Perhaps I edit the engine time in the cfg, to match my FSE Duke hobbs hours again. :)

I would have imagined everything as normal, but pressure left at SL which will cover heights to 10000. I await more learned info on this one!

Thanks. It's working, but it needs a lot of abuse to get damaged. Talking specificaly of the engine damage. So at least the engines are taken from a tank.

That's how it is in the real aircraft. I suspect the extra fuel is in the form of a header tank in the left engine nacelle where there is a centralized fuel filler nozzle that gravity feeds to all the other tanks, though I have been unable to confirm this.

@Creech23 said in Turbine Duke Range:

MAJOR ISSUE. UNFLYABLE.

When I am in the duke throttle levers work yet I don't gain any RPM. From idle to full is just 1200 RPM.

I have my throttles set up so that full travel is normally from 0 to 100, in this case full beta to max power, and when I want to slow down after landing I have a hardware switch that toggles the reversers on and full travel becomes 0 to -100.

When what you've described happens to me it's invariably because I've knocked the physical switch and the plane is trying to go backwards. Try toggling your reversers.