Jump to content

[CHK] Rudder Axis Command


KEULE

Recommended Posts

Dear Deka team,

 

the problem I have is that for some reason JF-17 Axis assign doesnt work for the rudder. The line is red and for that reason rudder input doesnt work. Keyboard input is fine.

 

Is there anything I can do to make it work? My rudders are not bound to anything else. On all other modules they are working like supposed to.

 

Thank a lot for your help!

 

Kind regards.

876137570_JF-17RudderConfig.thumb.PNG.3c62a4207c97ff14ea389707f2d9d738.PNG


Edited by uboats

If I would like to fly SFM I could get it for free at World of Warplanes.

 

You only need 2 of the following 3: Altitude - Speed - Skill

Link to comment
Share on other sites

+1

 

I was able to bind my pedals to the rudder axis when first installing the module and it worked for about a day, then it exhibited the same issue.

 

I was able to fix it by removing the input folder for the module but the issue came back after another day or so!

Link to comment
Share on other sites

i had the same issue with throttle using Warthog throttle when I first installed. Game restart and rebind fixed the issue

Owned Modules: F-18, F-16, F-14, AV-8B, A-10c, Huey, Hip, KA-50, Gazelle, Mig 15, Mig 19, Mig 21, FC3, P-51, BF-109, C-101, L-39, F-5, YAK-52

 

PC Specs- 8700k at 5.1GHz on Asrock z370 Fata1ity k6, EVGA 1080ti SSC2, 32 GB G.Skill TridentZ, 1TB NVMe m.2 Drive for DCS with a 500gb NVMe M.2 boot drive, Oculus Rift S

Link to comment
Share on other sites

I'm having the same issue except mine is showing it bind the same axis on the same device twice.

 

The only current work around I've found is to click on that box and hit "Default" which allows it to work again until DCS is restarted. See attached image. I've tried uninstalling and reinstalling the module to no avail.

jf17rudderissue.thumb.JPG.463b0f8daf3c6ee4c98bc77173510985.JPG

Flying the DCS: F-14B from Heatblur Simulations with Carrier Strike Group 2 and the VF-154 Black Knights!

 

I also own: Ka-50 2, A-10C, P-51D, UH-1H, Mi-8MTV2, FC3, F-86F, CA, Mig-15bis, Mig-21bis, F/A-18C, L-39, F-5E, AV-8B, AJS-37, F-16C, Mig-19P, JF-17, C-101, and CEII

Link to comment
Share on other sites

Upon looking into my VKB rudder input lua, this block appears whenever my rudder stops working.

 

I have never assigned the T6 axis in game, and the game itself reports that it is unbound on my pedals.

 

If I delete this block of code then the game reports starts reporting my RX axis as being assigned to both Rudder and T6 Antenna Elevation. I delete the T6 binding and my rudders start responding in sim again.

 

Unfortunately the problem re-creates itself next time I restart the sim.

1Bjz34D.png.2766a1809d09ba2b7b13feff3cd241e7.png

Link to comment
Share on other sites

I'm having the a similar issue with the tfrp rudders. I can bind the axis and I see them moving in controls but they don't respond in the sim when I try to go left or right. Toe brakes work fine.

Asus ROG Strix Z790-E | Core i9 13900K-NZXT Kraken X73 AIO | 32GB DDR5 G Skill Neo 6600mhz | 2TB Sk Hynix P41 Platinum nvme |1TB Evo 970 Plus nvme | OCZ Trion 150 960GB | 256GB Samsung 830 | 1TB Samsung 850 EVO | Gigabyte OC 4090  | Phanteks P600S | 1000W MSI  MPG A1000G | LG C2 42 Evo 3840x2160 @ 120hz

Link to comment
Share on other sites

  • 4 months later...
  • 2 months later...
  • Recently Browsing   0 members

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