Whiskey1968 Posted Monday at 05:35 AM Posted Monday at 05:35 AM As stated in the title. I go through all the start up procedure for the pilot, set the MFD's up as if I was to fly it, throttle up to flight power then jump into the CPG seat and start setting up things back there. Call for rearm and refuel and comms work fine for the time being. Set the MFD's, and go to set the TEDAC up and when I try the key bind for TADS on my Apache grip (Virpil Collective base without twist throttle) its a no go for TADS. Try using the switch in game by clicking it with my mouse and still a no go. Link, HMD and FCR work fine. Also, noticed the keyboard command and the key bind on my stick for communication menu doesn't work coinciding with the TADS switch failure. Tried calling ATC for a Hover check to find out the binds don't work. At this point, I was getting tired of trying (4 previous tries of going through the full start up and mission set up only to be grounded by key bind failures). I looked to make sure now dual key binds are assigned, checked my controls connection to the pc, checked the joysticks, throttle quadrant and collective buttons and axis in their individual software (VKB and Virpil) and all works fine. Everything worked fine in any other game or program i used. I read some earlier posts regarding this problem and haven't found a solution. Any ideas, suggestions or solutions would be greatly appreciated. Regards, Whiskey
LorenLuke Posted Monday at 07:27 AM Posted Monday at 07:27 AM 1 hour ago, Whiskey1968 said: As stated in the title. I go through all the start up procedure for the pilot, set the MFD's up as if I was to fly it, throttle up to flight power then jump into the CPG seat and start setting up things back there. Call for rearm and refuel and comms work fine for the time being. Set the MFD's, and go to set the TEDAC up and when I try the key bind for TADS on my Apache grip (Virpil Collective base without twist throttle) its a no go for TADS. Try using the switch in game by clicking it with my mouse and still a no go. Link, HMD and FCR work fine. Also, noticed the keyboard command and the key bind on my stick for communication menu doesn't work coinciding with the TADS switch failure. Tried calling ATC for a Hover check to find out the binds don't work. At this point, I was getting tired of trying (4 previous tries of going through the full start up and mission set up only to be grounded by key bind failures). I looked to make sure now dual key binds are assigned, checked my controls connection to the pc, checked the joysticks, throttle quadrant and collective buttons and axis in their individual software (VKB and Virpil) and all works fine. Everything worked fine in any other game or program i used. I read some earlier posts regarding this problem and haven't found a solution. Any ideas, suggestions or solutions would be greatly appreciated. Regards, Whiskey Re: Comms menu- Sometimes certain servers disable easy comms. This means the regular comms menu will not work by default when not on the ground. Check out bindings specifically for the radio and test those. Those should always bring up the menu. Re: TADS- Just to be clear, you do not have the PNVS on? Depending on the position of certain switches, the PNVS switch from the backseat can actually take control of the TADS instead of the PNVS and render it unusable to the front-seater for the duration of its usage. It's possible that this could be a reason that I could think of a to why the TADS could be unusable from the front seat.
admiki Posted Monday at 10:40 AM Posted Monday at 10:40 AM I had similar instances in front seat of the Mi-24, where DCS would respond to some, but not other inputs from my controler. Checking in controls menu show everything working as it should, every input instantly recognized, but in cockpit about half the stuff would not work. Then pressing all the switches, buttons and axes would somehow unstuck it and it would work fine from then on. Could not figure what combination would get it to work.
ShuRugal Posted Monday at 01:03 PM Posted Monday at 01:03 PM Check your "modifiers" menu in the control bindings. if you have any modifiers set as "switches", this is your culprit. A modifier button set as a "Switch" emulates a toggle and behaves like click-retract pen: push the button ones and it turns on and STAYS on, push again to turn it off. for 99% of usage cases, you should never have anything in the "switches" category of your modifiers page. This category exists to allow you to set up alternate bindings you can swap to with a single press-and-release if you have no physical toggle switches to use as a normal modifier.
Solution Whiskey1968 Posted Monday at 06:53 PM Author Solution Posted Monday at 06:53 PM 11 hours ago, LorenLuke said: Re: Comms menu- Sometimes certain servers disable easy comms. This means the regular comms menu will not work by default when not on the ground. Check out bindings specifically for the radio and test those. Those should always bring up the menu. Re: TADS- Just to be clear, you do not have the PNVS on? Depending on the position of certain switches, the PNVS switch from the backseat can actually take control of the TADS instead of the PNVS and render it unusable to the front-seater for the duration of its usage. It's possible that this could be a reason that I could think of a to why the TADS could be unusable from the front seat. I have not flown in almost a year. Never knew that about the servers disabling easy comms. I will change some binding to check that out. Thank you . As for the TADS, I did turn PNVS on initially, but put the switch in the off position after. Could that have somehow interrupted the key bind? I will test without PNVS today when I get home and see if that was the culprit. Thank you!!! 5 hours ago, ShuRugal said: Check your "modifiers" menu in the control bindings. if you have any modifiers set as "switches", this is your culprit. A modifier button set as a "Switch" emulates a toggle and behaves like click-retract pen: push the button ones and it turns on and STAYS on, push again to turn it off. for 99% of usage cases, you should never have anything in the "switches" category of your modifiers page. This category exists to allow you to set up alternate bindings you can swap to with a single press-and-release if you have no physical toggle switches to use as a normal modifier. Ah ok, so a modifier is like CNTRL, ALT, Shift and separated by left or right as well? I will check this as well. Thank you
Whiskey1968 Posted yesterday at 01:24 AM Author Posted yesterday at 01:24 AM It was a key bind set to a modifier. Not sure how that happened but it was the issue. Thanks for the info my friend, greatly appreciated.
ShuRugal Posted 18 hours ago Posted 18 hours ago 11 hours ago, Whiskey1968 said: It was a key bind set to a modifier. Not sure how that happened but it was the issue. Thanks for the info my friend, greatly appreciated. glad i could help. i manage to screw that one up about every other time i have to do keybinds. always manage to accidentally assign one of my HOTAS buttons as a switch modifier instead of a momentary.
Whiskey1968 Posted 8 hours ago Author Posted 8 hours ago 10 hours ago, ShuRugal said: glad i could help. i manage to screw that one up about every other time i have to do keybinds. always manage to accidentally assign one of my HOTAS buttons as a switch modifier instead of a momentary. Yeah, never knew I even done it lol. Oh well, crisis averted. Thanks again.
Recommended Posts