Warthog throttle not recognized

[franx]

BoS recognizes my Thrustmaster Warthog joystick and also the switches on the throttle unit.  But the the throttle itself, it won't recognize.  Any ideas why?

[Sokol1]

Open the box to assign control for throttle in game settings and move the throttle lever back and forth several times.

Sometimes the axis is not recognized in the the expected way (minimum to maximum) but inverted, if are the case

click on orange box "invert".

[SYN_Blackrat]

Do you have both throttles locked together with the sliding pin? If so unlock and just move one throttle?

 

 

.and the obvious, does the throttle show in the windows controller window as working on an axis?

Edited December 31, 2014 by SYN_Blackrat

[Allegra]

Hmm - I'm having exactly the same issues as the OP. I have a Warthog set up - and the JS works perfectly.

 

All the switches / buttons on the base of the throttle unit work, as do the buttons on the throttle itself. I have locked the two throttles together - doesn't work. I have moved them independently - doesn't work. I have moved them both independently and together for a full three minutes in each configeration. The grey 'increase / decrease' lever on the right hand side of the throttle unit is behaving in exactly the same manner.

 

When I go into the windows controller the upper reach of the throttle (Max) is not registering, but the lower end of the reach (Idle) does.  

 

I tried inverting the response in the vain hope that something may work - nope.

 

Bit of a loss to know what is occurring.

 

Any and all suggestions greatfully received.

 

Cheers

[dburne]

What does your axis response for the throttle show in the TARGET device analyzer?

[SYN_Blackrat]

Interesting, I use a CH quad throttle for BOS, but just tried my WH throttle and all recognised, locked, unlocked, both throttles and the Grey zoom lever, I do not use Target, it is not even installed, just the WH drivers.

 

Have you tried another USB port.?

Edited January 1, 2015 by SYN_Blackrat

[Allegra]

Thanks for the replies - lol Black...yes - but I'll try another couple and see if anything happens.

 

I've spent about 4 hours trying to fix it even resorting to an X65F throttle that I have.

 

Interesting thing is that again the buttons work - but no luck on the throttle itself.

 

And dburne, the TARGET analyzer is not registering for this game either!

 

However, the Warthog works in both RoF and CloD...

 

I'll switch ports and see what happens.

 

Cheers lads.

[dburne]

 

 

And dburne, the TARGET analyzer is not registering for this game either!

 

However, the Warthog works in both RoF and CloD...

 

I'll switch ports and see what happens.

 

 

 

The fact it works in ROF and CLoD would seem to suggest the problem lies not in the Warthog device or it's software, but from within BOS.

Sounds like something has gotten corrupt in the joystick files for BOS  to me, might want to consider deleting the contents of the input file folder within BOS, or a re-install...

 

Btw, do you use a TARGET profile for BOS, or just assign controls within the game?

Edited January 1, 2015 by dburne

[Allegra]

Hi Don and Black

 

The changing of ports again didn't work.

 

Don, I was beginning to think it was probably a corrupted file somewhere, but really hoped that it wasn't - took ages to download.

 

TBH I have only used the TARGET analyzer just since this occurred. I have to say - intuitive it is NOT!

 

I assign my own buttons / controls, etc. - makes it a lot easier for the games I play.

 

Ah well - back to the ol' download again...<grumble, freaking, grumble>

 

Thanks for the input.

 

Cheers

Al

[dburne]

Hi Don and Black

 

The changing of ports again didn't work.

 

Don, I was beginning to think it was probably a corrupted file somewhere, but really hoped that it wasn't - took ages to download.

 

TBH I have only used the TARGET analyzer just since this occurred. I have to say - intuitive it is NOT!

 

I assign my own buttons / controls, etc. - makes it a lot easier for the games I play.

 

Ah well - back to the ol' download again...<grumble, freaking, grumble>

 

Thanks for the input.

 

Cheers

Al

 

Best of luck , let us know how you make out.

[SYN_Blackrat]

Rather than redownload, might as well try deleting a few things in th einput folder

 

C:\Games\IL-2 Sturmovik Battle of Stalingrad\data\input

 

Nothing to lose.

 

any current.* file for a starter and see if that gets renewed?

[SCGSalty64]

I use a Warthog too. Check to make sure that your throttle is calibrated. First calibrate it as a stand-alone device and then run the Target software for some profile you have (any game will do) and this sets it up as a combined single virtual device. Leave the Target software running and go into your calibration mode and calibrate the whole device. Once you have calibrated using both methods go back into BOS and see if it recognizes the throttle axis. I have mine assigned directly as a stand-alone device but I plan on creating a profile to see if I can get more functionality. I hope this works for you.

[I./JG62_froNt]

Having the exact same problem right now  . Did you solved yours?

 

Joystick throttle axis works fine and is calibrated. But it still does not recognize it 

 

tried deleting the input files but that ends with my mouse not working anymore in the menu. also the files wont get replaced. 

 

-----------

edit

 

should've tried it with pulling out the throttle   

Edited May 23, 2016 by uRpark

[Dallas88B]

I have had your problem, this is how i fixed it. (I know this thread is old.... but just in case for someone else with this problem)

 

Try just deleting the file devices.txt (move it from the input folder to say the desktop).... its contained in your drive at IL-2 Sturmovik Battle of Stalingrad\data\input. Restart the game. The game will recreate the file itself and should then recognise the Thrustmaster Warthog components and the rudder (if your using a rudder).

 

You can see what the file says now (but use Notepad++ rather than Notepad if your going to edit and save the file... but I suggest you dont try to edit the file ... however taking a look you will probably see that the line about the throttle is missing)

 

When its correct it should include lines for the rudder (if your using a rudder), joystick and throttle like:

1,%223a590c40-8119-11e8-0000545345440180%22,T-Rudder|
3,%222934f790-ab84-11e8-0000545345440180%22,Joystick%20-%20HOTAS%20Warthog|
2,%2229351ea0-ab84-11e8-0000545345440280%22,Throttle%20-%20HOTAS%20Warthog

[MAS42]

So, I know this is a really old thread but after a bit of faffing around I fixed my Warthog throttle issue quite easily.  The warthog throttle has a pysical idle detent.  To set minimum power you need to physically lift the throttles and move them back.   If you do this while you are calibrating the mapping so you are using the full forward/backward movement it should recognise the throttle axis.