Jump to content

Recommended Posts

Bought the A10C II a few days ago and installed it today. Found duplicated keybinds and the ones with keyboard assignments do not accept controller assigments.  I'm running Open Beta 2.7. 

 

 

image.png

image.png

 

I'm using a TM Warthog Throttle and Stick and TM Rudder. Also I have other USB controllers connected.

 

I read in another thread that this might happen if there are multiple game controllers, so I disconnected everything, uninstalled the A10C and A10C II modules, did a DCS repair and reinstalled the modules and try with only the TM Warthog throttle connected.... Same issue . (Screen shoots where taken while I had everything connected).

 

Also, I cannot map the HOTAS Boat switch Center or the HOTAS Pinky Switch Center to anything.

 

Any ideas of what is going on and how to fix?


Edited by Draken35
Link to post
Share on other sites

Bind issues are never solved by doing anything to DCS or the module (repairs, reinstalls, whatever). If anything, that just increases the odds of making it worse.

 

This problem arises when there are inconsistencies in your bind files relative to how the same function is defined in the default binds, or when the default binds are inconsistent in and of themselves, often by having specialised pre-made device-specific binds and defaults.

 

The first can be fixed by removing all your custom binds (delete your Saved Games\DCS\Config\Input\A-10CII directory), but obviously, this means you lose all those binds and when you re-make them odds are very high that the issue will be reintroduced. So don't do that.

The latter can only be fixed by the developer making sure that all binds universally  use the same definitions in such a way that overlaps are correctly resolved, and preferably if they stay away from device-specific binds (which would break some things for TM Warthog owners… so they can't really do that).

 

In short. This is just how DCS binding is, and has been since a bind mechanics update a couple of years back. There is nothing to fix, or at least no fix that can be applied that will actually solve anything in any useful way. Just accept and ignore it, because unless the binds are highlighted in red — indicating a bind conflict — these definition screwups don't really affect anything in terms of functionality. It just looks bad.

 

 

e: Oh and…

43 minutes ago, Draken35 said:

Also, I cannot map the HOTAS Boat switch Center or the HOTAS Pinky Switch Center to anything.

This is normal if you're using the TM Warthog, and you'll find it applies to all three-position switches (flaps, autopilot mode, engine switches). The way the binds are defined, you don't actually bind the centre positions — instead, behind the scenes in a way that is not exposed to player binding, DCS detects button releases, so those centre positions are implicitly bound to whenever you move the corresponding switch out of any of the forward or aft positions (i.e. when the game detects a “Boat Switch Fwd button released” signal).

 

You can't bind it because DCS has detected that you own a TM Warthog throttle, and it therefore applies a bind file where that functionality is handled differently than for other devices.

 

This is why the issue can't readily be fixed on the developer side either: because then they would have to forego these kinds of device-specific switch abstractions. Of course, that could in turn be fixed by them actually exposing the full on-press/on-release button detection that the game is fully capable of… but that's not likely to ever happen.


Edited by Tippis
  • Like 1
  • Thanks 1
Link to post
Share on other sites

There is nothing to worry. The TM WH throttle and stick have exactly the right default bindings for the Hog. Where you see duplicated keybinds (in red), one line is for the keyboard only and the other one is for game controllers. Boat switch, Pinky switch and Autopilot switch are 3-position switches of type ON1-OFF-ON2. The software applies simple logic that says "If neither ON1 nor ON2 are active then the switch is in the middle position". Therefore you don't need a keybind for the middle position. That kind of logic cannot work with the keyboard as the key are only depressed shortly.

Nothing wrong, nothing to fix.

 

  • Like 1
  • Thanks 1

LeCuvier

Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5

Link to post
Share on other sites
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...