Thrustmaster TARGET axis mapping issue - RESOLVED

[Japsai]

IL-2 BoS doesn't recognise Virtual Controller axes when running TARGET configuration (for T.16000M and TWCS) although it does recognise the Virtual Keyboard strokes. When flying or if trying to map them within game. Can only get it working if I turn TARGET off and map the joystick and throttle axes and buttons separately.  Slightly annoying as I wanted to use a virtual controller and all the functionality of TARGET. Must be a solution but I haven't found it on forums. Any help appreciated (PS. I launch through Steam if this is significant).

Edited June 20, 2019 by biffa66
Resolved

[Velxra]

Best option is to not use target at all for iL-2. But if someone can walk you through the headache I'm sure it is possible to use it.

[FlyingH]

Are your axes configured in your TARGET script?

 

[Japsai]

I think so. Went through the normal Target GUI configuration wizard and selected different DirectX (DX) axes for the different controller axes (making sure there were no conflicts between controllers) before moving on to the button/key configurations (virtual keyboard).  Then run the configuration.  The buttons work but the axes don't.

Edited June 16, 2019 by biffa66

[Sokol1]

Try renaming the file "devices.txt" in folder "Input" (e.g. for  _devices.txt) and start game again.

Edited June 18, 2019 by Sokol1

[Japsai]

 

On 6/18/2019 at 3:48 PM, Sokol1 said:

Try renaming the file "devices.txt" in folder "Input" (e.g. for  _devices.txt) and start game again.

Many thanks Sokol1 this worked perfectly.