Thrustmaster warthog weird axis issue with A-10C

[whatnot]

Hi,

 

I got my gorgeous warthog HOTAS yesterday and it feels and flies like a dream. However I have a weird issue with A-10C: The buttons work ok, but the axis (Pitch, Roll & Thrust) don't. The weird thing is that they work with DCS P-51D and other titles without any issues, so probably the stick and the drivers are ok and this is probably some simple issue.

 

I've tried around a few things I found from googling around:

 

- Deleted the .lua files for all joysticks and keyboard as referred in http://forums.eagle.ru/showthread.php?t=95236. But when re-starting DCS it doesn't re-create any files. Why?

 

- Downloaded a pre-made config from http://www.digitalcombatsimulator.com/en/files/131072/ and loaded the wathog files but they work ok.

 

- Tried to copy the above files with the same .lua name as the original A-10 lua files were in the input folder, but same behaviour.

 

- Tried to clear up all the axis, exit from the config, then came back and re-assigned them (yes, it detects it when I configure it).

 

But always the same behaviour: My saitek pro combat rudder works ok, TIR5 has no issues, all the buttons work on the HOTAS but none of the axis does. The pitch axis does move however when moving the stick up or down, but it moves only up or down, but doesn't center when I let the stick go.

 

I'm mesmerized but still hoping I could fix it instead of doing re-installs etc.

 

I've got W7 64bit, the controllers mentioned above, 1.2.5 DCS.

 

So close but so far and it's killing me as I decided to wait starting with A-10 untill I get the stick. Now I got but I'm stuck! :helpsmilie:

 

Thanks in advance!

[doright]

Do a quick check that in Options->Controls Tab->A-10C->Axis commands that only Warthog axes are assigned to the appropriate control. You shouldn't have axis from 2 different controllers assigned to the same input.

[whatnot]

Do a quick check that in Options->Controls Tab->A-10C->Axis commands that only Warthog axes are assigned to the appropriate control. You shouldn't have axis from 2 different controllers assigned to the same input.

 

You know what, motivated by your answer I went back to check them even though I had checked them a hundred times. And though I had the configs correct in the A-10C SIM they were messed up with A-10C GAME which then apparently was the one that was selected as type when I took the "Create Fast Mission" to see if controls work.

 

WOHOO! :pilotfly:

 

But two questions in my mind still: what determines if it's 'Game' or 'Sim' configs that are loaded (is it the dificulty easy/med/hard)?

 

I still wonder why the default .lua files were not recreated in the Input folder after I delete them and restart DCS?

 

Anyway, million thanks! I knew this had to be something simple!

[whatnot]

Ok, this is getting all twilight zone on me!

 

So I got it to work for the most parts, but now as I started to walk through the training missions the axis work OK on all of the training chapters I've tried, but in ONE (Engine Startup) has the old behavior described in my original post.

 

I've loaded the profile I downloaded to both SIM and GAME versions of the controls and doublechecked that axis config are correct on both of them.

 

I can work around this by just training the startup on my own using the manual, but it would be very interesting to know why this behavior as it just doesn't make any sense to me!