Jump to content

Power Levers


Recommended Posts

Since update too 285 40170 my power lever are not working properly. I had the ( both ) assignment  to the left W/H throttle on RZ axis now when I move the throttle the levers jump to lockout position and engine overspeed, and when pulled back the levers stops halfway between idle and fly. Pryor to the update I could move the left throttle to assign the axis but now it is not recognized, and if have to select RZ but not woking.

Any ideas, anyone else experiencing this.

I have tried reassigning and repair checking all files. Nothing.

Left lever works fine in other modules.

Intel core I9 10900K 3.7 ghz

Asrock Z490 Extreme4

G-SKill Ripjaws V 32GB

Cooler Master 120m

GTX 980 Superclocked

Corsair AX850w psu

Samsung 1 T M.2 2 X 850 ssd's

Sony 48 in HD TV

Trackir 5

Hotas Warthog F/A-18C Hornet Grip

Logitech Pro Peddles

Windows 10 64

Link to comment
Share on other sites

Since update too 285 40170 my power lever are not working properly. I had the ( both ) assignment  to the left W/H throttle on RZ axis now when I move the throttle the levers jump to lockout position and engine overspeed, and when pulled back the levers stops halfway between idle and fly. Pryor to the update I could move the left throttle to assign the axis but now it is not recognized, and if have to select RZ but not woking.
Any ideas, anyone else experiencing this.
I have tried reassigning and repair checking all files. Nothing.
Left lever works fine in other modules.
Have you configured the axis as sliders?

Sent from my MAR-LX1A using Tapatalk

Link to comment
Share on other sites

I have tried it on the slider and it does the same thing, jump's to lockout and rpm to high.

I have in my stable install the power lever inc/dec smoothly on a two way momentary switch and it works fine. I tried the same thing in the O/B install and when it move the power lever forward the will go all the way to the lockout position, but in the stable install the levers will stop at the ( fly ) position. So something is wrong with the beta, and that is the only issue with it.


Edited by FOXFIRE TWOONE
  • Like 1

Intel core I9 10900K 3.7 ghz

Asrock Z490 Extreme4

G-SKill Ripjaws V 32GB

Cooler Master 120m

GTX 980 Superclocked

Corsair AX850w psu

Samsung 1 T M.2 2 X 850 ssd's

Sony 48 in HD TV

Trackir 5

Hotas Warthog F/A-18C Hornet Grip

Logitech Pro Peddles

Windows 10 64

Link to comment
Share on other sites

Have you changed your setting in DCS menu AH-64D spezial tab for Detend in Lockout position? Maybe accidently by the Patch installed?

 

  • Like 1

DCS MT 2.9.4.53707
Modules: UH-1H - SA342 - KA-50 BS3 - MI-24P - MI-8MTV2 - AH-64D - CH-47F(Preorder) - UH-60L(Mod) - A-10CII - F-16C - F/A-18C - FC3 -Combined Arms
 - Supercarrier - NTTR - Normandy2.0 - Persian Gulf - Syria - SA - Sinai - Afghanistan(Preorder) — Waiting for: OH-58D - BO-105 - AH-1G/F(Mod) - OH-6(Mod) - Kola  - Australia - Iraq

DCS-Client: 10900K, 64GB 3600, RTX3090, 500GB M2 NVMe(win10), 2TB M2 NVMe(DCS), VR VivePro2, PointCTRL, VaicomPro, Wacom Intuos S with VRK v2Beta

DCS-DServer: 11600KF, 32GB 3600, GTX1080, 1TB M2 NVMe(win10), 2TB M2 NVMe(DCSDServer), DCS Olympus

Simpit: NLR Flightsim Pro, TM Warthog Grip with 30cm Extension + Throttle, VPforce Rhino FFB, Komodo Pedals with Dampers, VPC Rotorplus+CBkit+AH-64D Grip, NLR HF8, Buttkicker (3*MiniConcert), TotalControls AH64D MPD‘s, TM 2*MFD‘s, Streamdecks (1*32,3*15,1*6), VPC CP#1

Link to comment
Share on other sites

8 hours ago, corbu1 said:

Have you changed your setting in DCS menu AH-64D special tab for Detent in Lockout position? Maybe accidently by the Patch installed?

 

Thanks Corbu1 the lockout had been changed in special to auto. Switched it to finger lifts and now levers stop at fly.

Still have a problem though, my W/H left throttle is not being recognized in controls setup and that is what I had the lever's assigned to from the beginning. Wondering if the patch broke something in sim.

All is well again. 

I decided to do a sys scan for corrupt files and their were some. Then went to control panel and reset W/H throttle to default, and recalibrated it, that fixed it. Now back to normal. 🙂


Edited by FOXFIRE TWOONE
  • Like 1

Intel core I9 10900K 3.7 ghz

Asrock Z490 Extreme4

G-SKill Ripjaws V 32GB

Cooler Master 120m

GTX 980 Superclocked

Corsair AX850w psu

Samsung 1 T M.2 2 X 850 ssd's

Sony 48 in HD TV

Trackir 5

Hotas Warthog F/A-18C Hornet Grip

Logitech Pro Peddles

Windows 10 64

Link to comment
Share on other sites

Great all is fine for you again👍

DCS MT 2.9.4.53707
Modules: UH-1H - SA342 - KA-50 BS3 - MI-24P - MI-8MTV2 - AH-64D - CH-47F(Preorder) - UH-60L(Mod) - A-10CII - F-16C - F/A-18C - FC3 -Combined Arms
 - Supercarrier - NTTR - Normandy2.0 - Persian Gulf - Syria - SA - Sinai - Afghanistan(Preorder) — Waiting for: OH-58D - BO-105 - AH-1G/F(Mod) - OH-6(Mod) - Kola  - Australia - Iraq

DCS-Client: 10900K, 64GB 3600, RTX3090, 500GB M2 NVMe(win10), 2TB M2 NVMe(DCS), VR VivePro2, PointCTRL, VaicomPro, Wacom Intuos S with VRK v2Beta

DCS-DServer: 11600KF, 32GB 3600, GTX1080, 1TB M2 NVMe(win10), 2TB M2 NVMe(DCSDServer), DCS Olympus

Simpit: NLR Flightsim Pro, TM Warthog Grip with 30cm Extension + Throttle, VPforce Rhino FFB, Komodo Pedals with Dampers, VPC Rotorplus+CBkit+AH-64D Grip, NLR HF8, Buttkicker (3*MiniConcert), TotalControls AH64D MPD‘s, TM 2*MFD‘s, Streamdecks (1*32,3*15,1*6), VPC CP#1

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...