Piston & Turbine Dukes

@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.) [image: Microsoft-Flight-Simulator-18-06-2024-12-23-18.png] [image: Hobbs.png] 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.

Negatory. Also, I disabled wind in the video.

@Harry_W Thx. But what about the InitialXyz in the corresponding camare adefinition ? You may change this also f.e.: [CAMERADEFINITION.37] Title ="PilotVR" ... ;InitialXyz = -0.337585,0.094898,-0.248452 InitialXyz = -0.30,0.088,-0.05

@fdrake On the piston Duke, the A/C compressor runs off the right engine, and it doesn’t kick in unless you have that engine running at least a bit above idle (which I’m told is true to life). I don’t know if the turbine Duke is the same way, but you might try it and see if it helps.

@alehead said in Virtualfly TQ6+ Throttle quadrant and Axis and Ohs in the piston and turbine Dukes: I am really having problems setting up the hardware levers of my TQ6+ to work properly in the Dukes. The problem is worst with the mixture levers. I get no smooth transition from full rich to cut of For the Turbine Duke this is normal. The mixture lever (actually condition lever) has only to options: Full rich and Cut Off. The Piston Duke should however have a smooth range, though since the engines are turbocharged you can keep the mixture full until the rpm's start to drop at high altitude.

@mysticfm ofc, these should work in FSUIPC. You need to replace the expression after the # sign with the following (before # is name of the macro). press: 1 (>L:var_PilotCws_IsDown, Bool) release: 0 (>L:var_PilotCws_IsDown, Bool) But with the newly implemented HW events support, you could try using the newly supported event K:SYNC_FLIGHT_DIRECTOR_PITCH together with the HW events option on the tablet. Then you wouldn't need to define macros in the events file. Though I haven't tried it and not sure how to use it, if you need to give it parameter 1 and 0 for press and release?  ¯\_(ツ)_/¯

@Rhinozherous thx yep it did