Wrong Joystick ID assignment Warthog HOTAS

[216th_Jordan]

Hey Dev Team,

 

since the patch 2.004 it seems that Il-2 is assigning different controller numbers to the joysticks. When I launch my combined Hotas profile in the T.A.R.G.E.T. software it always showed

 

"joy0_xxx" ingame. (pre-patch)

 

 

Now (after the patch) it changed input settings to

 

"joy3_xxx" - which I cannot control. (see cursor in picture below)

 

 

 

 

 

but when I press reassign it shows me "joy0_xxx" as before! (see picture below) So it gets a wrong ID assignment for no obvious reason.

 

 

Please let me know if you need any additional info.

 

Thank you,

Jordan

 

EDIT: Fixed missing Links

Edited October 21, 2016 by 216th_Jordan

[216th_Jordan]

UPDATE

 

To avoid reassignment ingame I edited the 'current.map' file and replaced all 'joy3' with 'joy0'.

When I launched the game again the 'current.map' file was back to joy3 alltogether. I had to make the 'current.map' file 'read-only' to have any chance of playing without needing to reassign on every game-launch.

 

[JG5_Schuck]

Same here Jordan,

My Simpeds and CH throttle swapped around (joystick1  to joystick2 and visa versa), and now every time i launch the game i have to also reassign the buttons

on the throttle...... all 24 of them or they don't work!!

Edited October 21, 2016 by JG5_Schuck

[216th_Jordan]

Same here Jordan,

My Simpeds and CH throttle swapped around (joystick1  to joystick2 and visa versa), and now every time i launch the game i have to also reassign the buttons

on the throttle...... all 24 of them or they don't work!!

 

Hey Schuck,

 

do what I did, edit the current.map file and mark it read only when everything works. You will not be able to change the buttons ingame any more but the game will not be able to change it back. (I also always keep a backup copy of my working current.map file)

Edited October 21, 2016 by 216th_Jordan

[Moggy]

Hi Jordan, just to let you know I've had exactly the same issue with my Thrustmaster T.16000M joystick whilst using the TARGET software and the new patch. I had already made a backup of the current.map file so it was quite easy just to make it read only. When I go into the settings I can still see the game trying to alter the settings back to joy3 to no avail.

[Chief_Mouser]

Same problem with my Thrustmaster Warthog HOTAS. The two throttles, the Y and X axes (pitch and roll) and the rotary I use for Mixture are always being reset to joy6 instead of joy0 and joy1. Only the axes; all of the buttons assigned by the TARGET software are fine. Will try Jordan's solution as a workaround.

Cheers.

Edited October 24, 2016 by 216th_Cat

[darthdooboss]

Same problem with Saitek x55....

I lost a lot of time reeditng all key and axis asigantions

[Chief_Mouser]

Will try Jordan's solution as a workaround.

Cheers.

Didn't work for me. I still have to re-assign the axes every time I fire up the game  .

Cheers.

[216th_Jordan]

Didn't work for me. I still have to re-assign the axes every time I fire up the game  .

Cheers.

 

So, when you reassign them, do they also show different numbers to the same controller than before? (Like first assignment: joy0, seconds assignment: joy2 )

Because when its read only it really  seems that your controller ID numbers get messed up by something, maybe ontop of the T.A.R.G.E.T profile issue (which doesn't happen in my case).

Edited October 23, 2016 by 216th_Jordan

[JG5_Schuck]

Yep, mine keep swapping controller assignments,

ie Joystick1 changes to Joystick2...... and visa versa.

i also have to re-assign all the buttons and axis, as nothing works after. (six axis and 12 buttons!)

 

So ive made a copy of the file on the desktop and copy/paste over the original every time before i start the game.

Its a ball ache, but hopefully only a temporary fix as i'm sure someone is looking into it!!

[Nebsky]

I also have this problem! A few days ago...there have been changes of Joy Axis 3 on Joy Axis 1.Why is this happening? i have 2 profiles and do it save on the old.

[Chief_Mouser]

Weird. Now my control assignments have gone back to working normally. No resetting on game launch. Nothing I've done; they just decided to behave themselves

Cheers.

[310_cibule]

Same issue with Saitek Quadrant here since 2.004. This peripheral has ID 4 but it always changes to ID 0 (which is assigned to CH Throttle) whenever the game is relaunched.  

 

I'll try Jordan's "read only" solution as soon as getting home tonight. What text editor did you use?

 

The game also freezes pretty often while key mapping.     

Edited November 2, 2016 by 310_cibule

[zanzark]

Same here with Saitek quadrant, logitech 3d pro and driving force gt

[216th_Jordan]

Same issue with Saitek Quadrant here since 2.004. This peripheral has ID 4 but it always changes to ID 0 (which is assigned to CH Throttle) whenever the game is relaunched.

 

I'll try Jordan's "read only" solution as soon as getting home tonight. What text editor did you use?

 

The game also freezes pretty often while key mapping.

I use Notepad as it is so basic and set read only under file properties. (all you really need then is CTRL+f and then find and replace all wrong joyX) I caught myself today tring to save some inputs inflight and wondered why it would not work

 

 

Say: did it work for you?

Edited November 4, 2016 by 216th_Jordan

[310_cibule]

Yes,Jordan, it did. Thanks a lot for sharing the solution you found out.

[Han]

Please try to delete

\data\swf\il2\storage\saveddevicesidentifiers.txt

and try it again (without readonly)

[KoN_]

Same here for me I cant use target at all for some reason it assigns a different joyID. When with in game . 

I would love to use TARGET as it gives me my curves i want to use .

 

I have lost count how many times i have resigned my joystick key binds here .

 

 

on a side note , I wish we had a DCS work round for curves and key binds  ` were we can keep the joystick settings as a file .

 

Even unplugging from USB port will change the joyID . in windows  .

 

How ever this is not effected with DCS . 

Edited November 10, 2016 by II./JG77_Con

[216th_Jordan]

Please try to delete

\data\swf\il2\storage\saveddevicesidentifiers.txt

and try it again (without readonly)

 

Did not work, set everything to joy3 again.

[Cheebs]

I had this issue last night. If you open the file Han referenced there are lines for each device prefaced by a number before ; semicolon.

Switch those numbers and your keybinds work again rather than switching all the binds in the other config.

[216th_Jordan]

I had this issue last night. If you open the file Han referenced there are lines for each device prefaced by a number before ; semicolon.

Switch those numbers and your keybinds work again rather than switching all the binds in the other config.

 

It is always on 0, ingame however it always changes to joy3. (the number in the file also stays constant even with new start of script and game)

 

Maybe everytime I start the profile a new instance is created and something gets mixed up, but I don't know the mechanics.

Edited November 10, 2016 by 216th_Jordan

[Matt]

Maybe try copy&pasting the first line and add it for device/configID 2 and 3.

Edited November 10, 2016 by Matt

[216th_Jordan]

Maybe try copy&pasting the first line and add it for device/configID 2 and 3.

 

Going to give that a try tomorrow. Thanks

[216th_Jordan]

Maybe try copy&pasting the first line and add it for device/configID 2 and 3.

 

Does not work, reverts the settings again (also rewrites the changed file).

[216th_Jordan]

Problem persists in 2.005.

[Chief_Mouser]

I had  a different problem with 2.005. Instead of the pitch, yaw and roll assignments being messed up, this time I ended up with the rudder set on the throttle levers and the mixture had vanished completely.

The list of files to back-up provided is helpful, but isn't there some means that the devs can incorporate to stop the updates messing with them in the first place?

Cheers.

[1stCL/Jiricek]

I had  a different problem with 2.005. Instead of the pitch, yaw and roll assignments being messed up, this time I ended up with the rudder set on the throttle levers and the mixture had vanished completely.

The list of files to back-up provided is helpful, but isn't there some means that the devs can incorporate to stop the updates messing with them in the first place?

Cheers.

I have similar problem. As it seems to me:

- in "current.ACTIONS" file there are your settings (as you have set them in settings in the game)

- in "current. MAP" file there are relations between keys and devices and the actions in games (one would think that it is the same. Well, it is not)

 

What happens: After starting the game, all Joy1 changes to Joy0 in "current.MAP" automaticly while all Joy0 stay Joy0. that leads to "multifunction" of Joy0. In "current.ACTION" it stays ok. In result as i move my stick, throttle or rudder moves as well. I can even set the relations between devices and functions (in settings in game) and it regulerly writes into "current.ACTIONS". But it does not write into "current.MAP". After finishing the game, I changed wrong Joy0 backt to Joy1 manually to accordance with the "current.ACTIONS (that means according to the settings in the game). But as soon as the game starts again, Joy1 changes to Joy0 again.

 

I am thinking about repairing the file and making it "read only". But I am not sure, what would it do with the game itself, of course. But this status makes me able doing no changes in settings but manually in the file.

Edited November 16, 2016 by 1stCL/Jiricek

[310_cibule]

I have similar problem. As it seems to me:

- in "current.ACTIONS" file there are your settings (as you have set them in settings in the game)

- in "current. MAP" file there are relations between keys and devices and the actions in games (one would think that it is the same. Well, it is not)

 

What happens: After starting the game, all Joy1 changes to Joy0 in "current.MAP" automaticly while all Joy0 stay Joy0. that leads to "multifunction" of Joy0. In "current.ACTION" it stays ok. In result as i move my stick, throttle or rudder moves as well. I can even set the relations between devices and functions (in settings in game) and it regulerly writes into "current.ACTIONS". But it does not write into "current.MAP". After finishing the game, I changed wrong Joy0 backt to Joy1 manually to accordance with the "current.ACTIONS (that means according to the settings in the game). But as soon as the game starts again, Joy1 changes to Joy0 again.

 

I am thinking about repairing the file and making it "read only". But I am not sure, what would it do with the game itself, of course. But this status makes me able doing no changes in settings but manually in the file.

Copy both files mentioned above and save them anywhere. Go to the game (at this moment the game rewrites the files and reassignes periphery's IDs) and than paste both saved files back to the appropriate folder again. Map the keys in the game and leave the game. Go to the game folder and set both files as "read only". The game will complain a bit after being loaded that it can't rewrite the files but that is all it can do :-) It works perfectly and you can do that anytime you want to remap your key assignments. Edited November 16, 2016 by 310_cibule

[1stCL/Jiricek]

Thanks, Cibule. It works. But it´s not too comfortable status for the future. Just for information - it´s enough to set just "current.MAP" file as read only. The other one - "current.ACTIONS" doesn´t suffer by changing by the game.

[310_cibule]

Good to know ;-)

[216th_Jordan]

Confirm, problem is fixed.

[chiliwili69]

I was also suffering from this problem in the past. From time to time windows was assigning the joy id numbers somehow ramdonly, specially if you plug & unplug other devices. I was visualizing that using "joy.cpl" in the command line.

 

So, when I had problems I edited the "current.actions" and the "current.map" to properly replace the joyIDs.

 

Then, I discover the windows application  PJPs JoyIDs which allows you to change the assigments of the joyIDs made by Windows. So, no need to edit the mapping files again.

 

But just today, I noticed that changing the JoyIDs of windows was not affecting the IDs of BOS. Then I was reading this posts.

 

In my case, what I have done is to modify the file "devices.txt" in the data/input folder to reflect the right order specified in the "current.actions" and "current.map" files. And it works.

I understand that this devices.txt file defines what BOS understands by joy0, joy1, joy2, etc.

From now on it will be easier to edit the devices.txt than the current.actions and current.map files.