Warthog Hotas - Mapping problems

[Bilbosmeggins]

Hi all.  I’m having massive problems with mapping input to my Hotas.  In the menus, I map the buttons, switches or axis, ensure there are no conflicts and all is well in the menus, ie the buttons and switches label correctly, and I can see the axis needle moving in the axis configuration setup. However, once I enter the plane, hardly anything works. I cannot map trimming functions, mixture, rpm or anything.  And, to add insult to injury, IL2 has just re-installed after I purchased BoP, so its a clean slate, but is still broken.  Any ideas?  Just for the record, in DCS and X-Plane 11 my HOTAS gives me not a single problem.

Edited May 23, 2020 by Bilbosmeggins
Typo

[OrLoK]

ensure auto management settings are off.

 

or assign a switch to turn on advaned engine management.

 

i have this issue in some aircraft, not sure if by design.

[Bilbosmeggins]

Thanks Orlock. Although I’m afraid that’s not the issue, as I cannot even map “pause” or “reset view” to my HOTAS. In the menus yes, but hardly anything translates back to the game.

[OrLoK]

how many *things* do you have plugged in to your rig?

 

I found if i plug in my TM MFDs my stick no longer works

[Bilbosmeggins]

Hardly anything. Just my Warthog HOTAS, and my Crosswind Rudder pedals, plus my Rift S. I don’t even use my pc for anything apart from a handful of games, as I like to try and keep it pure. Fat lot of good that’s doing me, ?

[FlyingH]

1Is your game in C/program files by any chance? 2Is your game or any of the game tree files set to "read only"? For the first Q, take the game out of there, put it anywhere on your HDD, for the second remove the "read only" tick.

[dburne]

On 5/23/2020 at 9:14 AM, Bilbosmeggins said:

Hi all.  I’m having massive problems with mapping input to my Hotas.  In the menus, I map the buttons, switches or axis, ensure there are no conflicts and all is well in the menus, ie the buttons and switches label correctly, and I can see the axis needle moving in the axis configuration setup. However, once I enter the plane, hardly anything works. I cannot map trimming functions, mixture, rpm or anything.  And, to add insult to injury, IL2 has just re-installed after I purchased BoP, so its a clean slate, but is still broken.  Any ideas?  Just for the record, in DCS and X-Plane 11 my HOTAS gives me not a single problem.

 

I am a little confused.

You give the impression that you have no problem mapping the proper buttons and axis in the controller menu, but then many do not work in the plane, is that right? Which plane?
Also you then state you can not map trimming functions, mixture, rpm, or anything??  But you said no problem mapping the buttons and axis?

You might try deleting the contents of your data/input folder in the game directory and try to re-assign.

 

[Bilbosmeggins]

18 hours ago, FlyingH said:

1Is your game in C/program files by any chance? 2Is your game or any of the game tree files set to "read only"? For the first Q, take the game out of there, put it anywhere on your HDD, for the second remove the "read only" tick.

Sorry for delay, I’ve been away from gaming pc for a while.  I shall check the path and have a play. Thank you for your input. 

 

17 hours ago, dburne said:

 

I am a little confused.

You give the impression that you have no problem mapping the proper buttons and axis in the controller menu, but then many do not work in the plane, is that right? Which plane?
Also you then state you can not map trimming functions, mixture, rpm, or anything??  But you said no problem mapping the buttons and axis?

You might try deleting the contents of your data/input folder in the game directory and try to re-assign.

 

Sorry if my inane ramblings are a tad confusing, lol. Which plane is irrelevant in my case as I have tried several different ones whilst trying to combat the problem. All planes exhibit the same lack of control.

 

Yes, in the menus, everything behaves as it should. Buttons, switches and axis are all recognised as I assign them. And the axis show the sweep moving in the configuration screen.  But, once in game, nothing.  My main flight controls work, ie pitch, yaw, roll and throttle, and the odd button and switch for flaps, gear etc. But most assignments do nothing, apart from in menu.

[Bilbosmeggins]

22 hours ago, dburne said:

 

I am a little confused.

You give the impression that you have no problem mapping the proper buttons and axis in the controller menu, but then many do not work in the plane, is that right? Which plane?
Also you then state you can not map trimming functions, mixture, rpm, or anything??  But you said no problem mapping the buttons and axis?

You might try deleting the contents of your data/input folder in the game directory and try to re-assign.

 

 

@dburne

 

Just had a peep at the input folder, and the contents are as follows:

 

current.actions - ACTIONS File

current.devices - DEVICES File

current.map - MAP File

current.responses - RESPONSES File

devices - Text Document

joys.ffp - FFP File

joysffmap - CFG File

 

Am I okay to just clear these out? Presumably, the game will repopulate the folder with what it deems necessary. At least, I hope so.

 

Cheers

Andy

[dburne]

Yes I think so, leave them in your recycle bin though so you can restore them back just in case.

[Bilbosmeggins]

Good thinking. My party piece is to just bulldozer everything and regret it later.  I’ll give it a blast tomorrow when I’m a bit more awake.  Much appreciated

[Bilbosmeggins]

Quick update.....

 

Tried the above, and cleared out the input folder. Back into the menus, set up the basics, and all looked good. Then in to the game itself and still barfed. Certain features it just won’t let me have.  I’m in full realism mode, so should be in control of everything.  If I cannot even  trim the aircraft, which I can’t, then it makes the whole thing a bit redundant. 
 

If I didn’t fly VR, then I could reluctantly use the stock keyboard mappings. But, that isn’t really an option, unless I want to keep peeling the headset off to break the immersion, and have a peek at the keyboard.  Also impossible once things get hectic.  Plus, that would be no fun whatsoever. 
 

Verdict:  As much as I love IL2, and the whole WWII thing, I need my flying fix. Each time I fire up IL2, I spend 95% of my time pissing about in the menus, and the remaining 5% of the time testing the disappointing results. So, I’m off to DCS, where I can at least map my HOTAS.  I shall return to IL2 when I next upgrade the PC, to see if the new rig is interested in playing it.
 

Thanks for the suggestions. Much appreciated ?

[dburne]

13 minutes ago, Bilbosmeggins said:

Quick update.....

 

Tried the above, and cleared out the input folder. Back into the menus, set up the basics, and all looked good. Then in to the game itself and still barfed. Certain features it just won’t let me have.  I’m in full realism mode, so should be in control of everything.  If I cannot even  trim the aircraft, which I can’t, then it makes the whole thing a bit redundant. 
 

If I didn’t fly VR, then I could reluctantly use the stock keyboard mappings. But, that isn’t really an option, unless I want to keep peeling the headset off to break the immersion, and have a peek at the keyboard.  Also impossible once things get hectic.  Plus, that would be no fun whatsoever. 
 

Verdict:  As much as I love IL2, and the whole WWII thing, I need my flying fix. Each time I fire up IL2, I spend 95% of my time pissing about in the menus, and the remaining 5% of the time testing the disappointing results. So, I’m off to DCS, where I can at least map my HOTAS.  I shall return to IL2 when I next upgrade the PC, to see if the new rig is interested in playing it.
 

Thanks for the suggestions. Much appreciated ?

 

There is something being missed, as the Warthog should work just fine with IL-2. Mine certainly did when I was using it.

Sorry it did not help.

[AtomicP]

25 minutes ago, Bilbosmeggins said:

Quick update.....

 

Tried the above, and cleared out the input folder. Back into the menus, set up the basics, and all looked good. Then in to the game itself and still barfed. Certain features it just won’t let me have.  I’m in full realism mode, so should be in control of everything.  If I cannot even  trim the aircraft, which I can’t, then it makes the whole thing a bit redundant. 
 

If I didn’t fly VR, then I could reluctantly use the stock keyboard mappings. But, that isn’t really an option, unless I want to keep peeling the headset off to break the immersion, and have a peek at the keyboard.  Also impossible once things get hectic.  Plus, that would be no fun whatsoever. 
 

Verdict:  As much as I love IL2, and the whole WWII thing, I need my flying fix. Each time I fire up IL2, I spend 95% of my time pissing about in the menus, and the remaining 5% of the time testing the disappointing results. So, I’m off to DCS, where I can at least map my HOTAS.  I shall return to IL2 when I next upgrade the PC, to see if the new rig is interested in playing it.
 

Thanks for the suggestions. Much appreciated ?

 

With trim, some aircraft are a bit finicky and the trimming process can take a few seconds (i.e. a long button press). Also, if I recall correctly the 109 and 190 have a different trimming setup (the adjustable stablizer) so you may want to check you have that mapped. The whole control mapping in BoX needs a bit of work though. I wish the developers would group similar controls together, like the trimmers and different radiators. Also having a feature like DCS where by pressing a button you get a highlight of what it is mapped to would be really useful especially when you've been away from the sim for a while. 

[Bilbosmeggins]

17 minutes ago, AtomicP said:

 

With trim, some aircraft are a bit finicky and the trimming process can take a few seconds (i.e. a long button press). Also, if I recall correctly the 109 and 190 have a different trimming setup (the adjustable stablizer) so you may want to check you have that mapped. The whole control mapping in BoX needs a bit of work though. I wish the developers would group similar controls together, like the trimmers and different radiators. Also having a feature like DCS where by pressing a button you get a highlight of what it is mapped to would be really useful especially when you've been away from the sim for a while. 

I get what you are saying, but it’s not that. It’s just not working. If I press the trim button, the eight-way hat switch on top of the joystick, nothing happens to the plane’s attitude, and if I look down inside the cockpit the trim controls aren’t budging an inch either. Long press, or short press, just no response.  But the trim is just an example, most of what I try to map fails to work, apart from in the menus.

 

Fully agree with the DCS feature, showing you what is mapped by instantly jumping to the command and highlighting it.  X-Plane does it even better by showing you a graphic of the HOTAS, and what is being pressed, and what it’s currently mapped to. Although I can’t fly X-Plane either atm because their latest update broke vr. Luckily though, it’s well documented on the forums, so I don’t need to go troubleshooting like it’s just my problem.

41 minutes ago, dburne said:

 

There is something being missed, as the Warthog should work just fine with IL-2. Mine certainly did when I was using it.

Sorry it did not help.

No worries @dburne. I appreciate you trying. You’ve helped me out many moons ago, and you are always one of the first to step up to offer assistance. 

[dburne]

What else do you have plugged in to your USB Ports ?

Are you running it through a USB 2 port or USB 3 port?

[Bilbosmeggins]

Hardly anything. Rift S on a 3.0, k/board mouse on 2.0, Crosswind rudder 2.0. Throttle and joystick plugged into the front of the pc for convenience, joystick on a 3.0, throttle on a 2.0. But, as I said before, this setup works flawlessly in DCS, X-Plane 11, oh and Elite Dangerous.

[FlyingH]

Those settings that don´t respond, are they with a modifier ie CCTl_, SHIFT_ or ALT_? If so you´ll need to make aCHAIN(DOWN+,D(32),DOWN+,D(32),UP+,D(32),UP+)  string Where the D(32) is the delay time for the game to execute the command.

Edited May 26, 2020 by FlyingH

[Bilbosmeggins]

Certainly not using a modifier on the HOTAS, but not sure if the original keyboard mappings are using modifiers.  I’ll have a check later. I’m not using TARGET by the way.

[dburne]

4 hours ago, Bilbosmeggins said:

Hardly anything. Rift S on a 3.0, k/board mouse on 2.0, Crosswind rudder 2.0. Throttle and joystick plugged into the front of the pc for convenience, joystick on a 3.0, throttle on a 2.0. But, as I said before, this setup works flawlessly in DCS, X-Plane 11, oh and Elite Dangerous.

 

Can you try the joystick on a 2.0 port just to see?

[Bilbosmeggins]

6 minutes ago, dburne said:

 

Can you try the joystick on a 2.0 port just to see?

To be honest it won’t make any difference because I’m getting zero input responses from both joystick AND throttle. If the problem was exclusive to one or the other then it would be worth pursuing. And the fact that they both work perfectly in the menu is perplexing.

Anyway, I sincerely appreciate your efforts, but I am going to sink all of my energy into DCS for a while. I’ve been buggering about, trying to get IL2 working for the best part of a week, and I shall end up putting my foot under the pc if I continue, lol. It has mentally drained me.

[dburne]

5 minutes ago, Bilbosmeggins said:

To be honest it won’t make any difference because I’m getting zero input responses from both joystick AND throttle. If the problem was exclusive to one or the other then it would be worth pursuing. And the fact that they both work perfectly in the menu is perplexing.

 

You have something really, really odd going on there.

It should work just fine in IL-2 GB.

Some axis can be a little tricky to set up, like toe brakes for instance.

But for all axis and buttons? 

So you see it all work properly in Windows Controller menu?

Everything assigns properly in the game controller setup menu?

Then you click on Accept, go into the plane, and nothing works? Elevator, Ailerons, Rudder, trigger, etc?

I will tell you, that is almost inconceivable.

Edited May 26, 2020 by dburne

[Bilbosmeggins]

9 minutes ago, dburne said:

 

You have something really, really odd going on there.

It should work just fine in IL-2 GB.

Some axis can be a little tricky to set up, like toe brakes for instance.

But for all axis and buttons? 

So you see it all work properly in Windows Controller menu?

Everything assigns properly in the game controller setup menu?

Then you click on Accept, go into the plane, and nothing works? Elevator, Ailerons, Rudder, trigger, etc?

I will tell you, that is almost inconceivable.

 

10 minutes ago, dburne said:

 

You have something really, really odd going on there.

It should work just fine in IL-2 GB.

Some axis can be a little tricky to set up, like toe brakes for instance.

But for all axis and buttons? 

So you see it all work properly in Windows Controller menu?

Everything assigns properly in the game controller setup menu?

Then you click on Accept, go into the plane, and nothing works? Elevator, Ailerons, Rudder, trigger, etc?

I will tell you, that is almost inconceivable.

 

More or less, but it’s not all axis and buttons. It allows me to map pitch, roll, rudder, and throttle, so I have the bare essentials to get airborne. It’s just certain functions that it will absolutely NOT let me use in the game. Trim being one of many.  The game fresh installed the other day too, but still wouldn’t work.  But, as I said, I’ve put it behind me now, for the sake of my sanity.

[dburne]

1 hour ago, Bilbosmeggins said:

 

 

More or less, but it’s not all axis and buttons. It allows me to map pitch, roll, rudder, and throttle, so I have the bare essentials to get airborne. It’s just certain functions that it will absolutely NOT let me use in the game. Trim being one of many.  The game fresh installed the other day too, but still wouldn’t work.  But, as I said, I’ve put it behind me now, for the sake of my sanity.

 

Well should you want to try again, I would try plugging that joystick in a USB 2 port instead of the USB 3 port.

Something in the back of my mind is hinting that TM and USB3 ports do not necessarily get along all that well.

But then again my memory ain't what is used to be.

 

Best of luck,

[Bilbosmeggins]

 Cheers for the suggestion.  However, seeing as it works perfectly in the other titles that I play, I am going to leave well alone. Years ago, I was forever unplugging usb cables, and sticking different peripherals in and out of my pc. Then, when I would plug the old stuff back in, I would often end up sticking things back in a different order. Not mixing up 2.0 and 3.0, or whatever it was back in the day. Just not necessarily back into the same sockets.  I had so much trouble that I changed my ways.

 

When my current pc was built, specifically for flight simming in vr, I made a concerted effort to label up each socket, and each peripheral. So that I could get some consistency, and the registry wouldn’t get so screwed up over time.  And it has worked flawlessly until now. Still does, apart from IL2. 
 

I believe the way computers are, that it is not necessarily an IL2 problem. Just some deep-rooted coding somewhere that has somehow gone awry.  I just think that, short of a complete formatting of my pc, I am stuck with it. I’m currently waiting for the new crop of GPUs and CPUs to land, then I shall be buying a new system. I shall most likely come back to IL2 then and see how I fare.

[unreasonable]

58 minutes ago, Bilbosmeggins said:

 Cheers for the suggestion.  However, seeing as it works perfectly in the other titles that I play, I am going to leave well alone.

 

Understandable. You are not the only one having mapping problems where there were none before.  

[Bilbosmeggins]

Yeah, it’s a bit mad, but beyond me.  No biggie though, as I’m enjoying DCS far more than I ever thought I could. So I’m occupied for the foreseeable future anyhow. Every cloud.... ?

[DirtyBri]

A bit late the table with this problem, 

But I am having exactly the same problems with my Warthog, Inputs all map and test correctly in the key mapping pages, but in game, only the basic axis (pitch, roll, throttle) work! but nothing else e.g proppler rpm, superboost etc..... I have tried all the above suggestions 

Idont use thrustmaster GUI as its to complicated

 

ANY HELP WITH THIS PLEASE

[dehowie]

Add anther Warthog user to the list of those that cant assign buttons on the stick or throttle.

Basic axis works but any assignments like trim up or down are not recognized. Neither is the Prop axis on the throttle.

 

 

 

[Hoss]

On 5/26/2020 at 3:39 PM, dburne said:

 

Well should you want to try again, I would try plugging that joystick in a USB 2 port instead of the USB 3 port.

Something in the back of my mind is hinting that TM and USB3 ports do not necessarily get along all that well.

But then again my memory ain't what is used to be.

 

Best of luck,

3.0 works fine on my set-up. Is TARGET being used to program your keystrokes? If DX inputs are being used it's fine, you just need to find the conflicts of joy1 or joy0-button1, 2, 3, etc. IL2 is much easier to program than DCS, I use TARGET SCRIPT in DCS and its all dx inputs, where I use TARGET GUI for IL2. RCTL + A type Keystrokes. If you use TARGET Script, or TARGET GUI, you should never start the game without starting TARGET first, or it will hose all the work you have done, by changing the input folder set-up and nothing will work right. I use the 128 button dx TARGET script I found on DCS forums. I usually have to clear all the dx inputs out of the "Stick/Throttle columns, because TARGET makes a new column (TARGET Combined) where I put all of my commands. Otherwise nothing works, you will only see combined when you start TARGET in IL2. Don't know if that's any help, I can only guess since I can't see what you are doing. Keep on trying and let us know if you get it sorted. One more thing, my TMWH does not like being plugged into a powered USB hub of any kind.

 

Hoss

On 10/5/2021 at 8:12 AM, DirtyBri said:

A bit late the table with this problem, 

But I am having exactly the same problems with my Warthog, Inputs all map and test correctly in the key mapping pages, but in game, only the basic axis (pitch, roll, throttle) work! but nothing else e.g proppler rpm, superboost etc..... I have tried all the above suggestions 

Idont use thrustmaster GUI as its to complicated

 

ANY HELP WITH THIS PLEASE

You know RPM, MP, Flaps, all trim commands have to be a "Hold" command, by default all presses are "PULSE" which won't work for commands that need to be held down to work. Try the P-51 flaps, they are incremental and should work with pulse. 

 

Hoss