WiCK3D Posted January 2, 2022 Posted January 2, 2022 Hey guys. So out of the blue, my aircraft rudders hard right on taxi and hard roll in flight. No idea why. not a trim issue. My deadzone on HOTAS is 3 never had any issues. Is it because i had Cat 1 with GBU 10 and 12? Should be cat 3? Any ideas? thanks
Falconeer Posted January 2, 2022 Posted January 2, 2022 (edited) Any A-G weapon or wingtank on the jet should be Cat. III config, but i dont think that's your problem. Does it happen when you enter a mission? I had the same problem with some modules and i *fixed* it by deselecting synchronize cockpit controls in the options menu. Sounds like some sort of potentiometer spike in one of your controllers Edited January 2, 2022 by Falconeer Planes: Choppers: Maps: Flaming Cliffs 3 Black Shark 2 Syria A-10C Tank killer 2 Black Shark 3 Persian Gulf F/A18C Hornet AH-64 Apache Mariana's F-16C Viper Afghanistan F-15E Strike Eagle Kola Peninsula Mirage 2000C AJS-37 Viggen JF-17 Thunder F-14 Tomcat F-4E Phantom
WiCK3D Posted January 2, 2022 Author Posted January 2, 2022 23 minutes ago, Falconeer said: Any A-G weapon or wingtank on the jet should be Cat. III config, but i dont think that's your problem. Does it happen when you enter a mission? I had the same problem with some modules and i *fixed* it by deselecting synchronize cockpit controls in the options menu. Sounds like some sort of potentiometer spike in one of your controllers That was exactly the issue. Spot on mate. Solved. Cheers
Cepheus76 Posted January 2, 2022 Posted January 2, 2022 (edited) Edit: Deleted the post, since it became irrelevant. Edited January 2, 2022 by Cepheus76
Falconeer Posted January 2, 2022 Posted January 2, 2022 No worries Planes: Choppers: Maps: Flaming Cliffs 3 Black Shark 2 Syria A-10C Tank killer 2 Black Shark 3 Persian Gulf F/A18C Hornet AH-64 Apache Mariana's F-16C Viper Afghanistan F-15E Strike Eagle Kola Peninsula Mirage 2000C AJS-37 Viggen JF-17 Thunder F-14 Tomcat F-4E Phantom
Dannyvandelft Posted January 2, 2022 Posted January 2, 2022 Any A-G weapon or wingtank on the jet should be Cat. III config, but i dont think that's your problem. Does it happen when you enter a mission? I had the same problem with some modules and i *fixed* it by deselecting synchronize cockpit controls in the options menu. Sounds like some sort of potentiometer spike in one of your controllersIf that fixed it, it means you have a double bind somewhere. Sent from my SM-G960U using Tapatalk
Falconeer Posted January 2, 2022 Posted January 2, 2022 No, i checked it multiple times and there where no double binds Planes: Choppers: Maps: Flaming Cliffs 3 Black Shark 2 Syria A-10C Tank killer 2 Black Shark 3 Persian Gulf F/A18C Hornet AH-64 Apache Mariana's F-16C Viper Afghanistan F-15E Strike Eagle Kola Peninsula Mirage 2000C AJS-37 Viggen JF-17 Thunder F-14 Tomcat F-4E Phantom
MAXsenna Posted January 2, 2022 Posted January 2, 2022 4 hours ago, Dannyvandelft said: If that fixed it, it means you have a double bind somewhere. Sent from my SM-G960U using Tapatalk It actually doesn't, or it is a "ghost bind". I have this behaviour in a lot of modules, and I don't want to sacrifice the "sync with HOTAS". So whenever I have this issue, I will clean out the axis settings on all unused peripherals, even my TM Cougars. And there are NO conflicts ever. But this procedure actually solves it. It's tedious, and it often reappears, so I only do this for the module that currently has my attention. This issue was introduced for me when the Hind arrived. And it seems I have narrowed it down to the Cougars. Pinging @Flappieand @BIGNEWY I might be able to provide tracks next weekend, haven't seen my computer for the past two weeks.
Dannyvandelft Posted January 2, 2022 Posted January 2, 2022 It actually doesn't, or it is a "ghost bind". I have this behaviour in a lot of modules, and I don't want to sacrifice the "sync with HOTAS". So whenever I have this issue, I will clean out the axis settings on all unused peripherals, even my TM Cougars. And there are NO conflicts ever. But this procedure actually solves it. It's tedious, and it often reappears, so I only do this for the module that currently has my attention. This issue was introduced for me when the Hind arrived. And it seems I have narrowed it down to the Cougars. Pinging @Flappieand @BIGNEWY I might be able to provide tracks next weekend, haven't seen my computer for the past two weeks. Yeah, I had it on the Hind and Harrier too. And it was double binds lol. Sent from my SM-G960U using Tapatalk
MAXsenna Posted January 2, 2022 Posted January 2, 2022 18 minutes ago, Dannyvandelft said: Yeah, I had it on the Hind and Harrier too. And it was double binds lol. Sent from my SM-G960U using Tapatalk Well, I of course meant "it doesn't necessarily mean you have a double bind". Like I wrote I get this "spiking controls to limits" a lot IF I have the "sync with HOTAS" checked. And I NEVER have any axis conflicts. It's always the first thing I check. No, this is a bug, and it was introduced with the Hind. It can be solved by going into controls settings, clearing every axis even if there ain't no conflicts. 1
macedk Posted January 3, 2022 Posted January 3, 2022 I had it in the Hornet, was double bind for me. Remember to scroll right on the controls list. The list is mighty long: Joystick, Throttle, Rudder pedals, Mfd1, Mdf2, keyboard, Mouse and Trackir. (for me) OS: Win10 home 64bit*MB: Asus Strix Z270F/ CPU: Intel I7 7700k /Ram:32gb_ddr4 GFX: Nvidia Asus 1080 8Gb Mon: Asus vg2448qe 24" Disk: SSD Stick: TM Warthog #1400/Saitek pro pedals/TIR5/TM MFDs [sIGPIC][/sIGPIC]
Flappie Posted January 6, 2022 Posted January 6, 2022 On 1/2/2022 at 7:43 PM, MAXsenna said: It actually doesn't, or it is a "ghost bind". I have this behaviour in a lot of modules, and I don't want to sacrifice the "sync with HOTAS". So whenever I have this issue, I will clean out the axis settings on all unused peripherals, even my TM Cougars. And there are NO conflicts ever. But this procedure actually solves it. It's tedious, and it often reappears, so I only do this for the module that currently has my attention. This issue was introduced for me when the Hind arrived. And it seems I have narrowed it down to the Cougars. Pinging @Flappieand @BIGNEWY I might be able to provide tracks next weekend, haven't seen my computer for the past two weeks. If the issue is what you're describing, then it might be even more interesing to attach your aircraft custom inputs (as a zip) as soon as the issue happens, but also right after you fix them. This way, we could compare .lua.diff files and see what's happening. ---
MAXsenna Posted January 6, 2022 Posted January 6, 2022 1 hour ago, Flappie said: If the issue is what you're describing, then it might be even more interesing to attach your aircraft custom inputs (as a zip) as soon as the issue happens, but also right after you fix them. This way, we could compare .lua.diff files and see what's happening. Good idea! Will do!
Recommended Posts