Having to reassign controls on every single launch

I have three wheels from Asetek and they have them split into multiple devices in order to get around the 32 input limit. I did also have the same issue with my Simagic wheels prior to changing over to Asetek. AMS2 is the only sim I have this issue with.

I have always set it as custom and separate, that does not seem to be a workaround for this type of issue

I have had this happen at random times too.

 

Awesome, thanks Marius

 

I have the same issue with Logitech G Pro Wheel and Simagic GT Neo. I have to reassign all the controls, although they are still "assigned", very often, which is super annoying. Thank you for investigation.

 

The same issues exist here, everytime I switch wheels I have to reassign the buttons on the wheel. Three buttons assigned to the button box and pedals keep working.
Think there are quite a lot of other people having the same issues

 

I was wondering also, whilst not directly linked to this issue, could the Devs make changes to the code so that multi position switches work as MP switches and not have to be in encoder mode or is that a limitation of the game engine?

 

Just for another data point; the most recent update and subsequent patches caused my controls to be 'reset' again, even without switching wheels or switching control profiles. The steering axis and buttons look properly assigned, but do nothing until you reassign them all over once again.

 

I'm no sure if it's the same issue you guys are having but I have very occasionally needed to re-bind controls in ETS2 and AMS2 and with both games, the 'new' setting seems to have a new joystick ID, e.g., my button box might go from Joystick(4) to Joystick(5) (or however it is annotated). I might do some looking into how Windows allocated device IDs to game controllers and see if that can bring some insight into the problem

 

So there's quite a lengthy discussion on the DCS forums about this exact issue. It does ultimately seem to come down to how Windows assigns GUIDs to game controllers (and then how each game interacts with these devices). Not having any expertise on the subject I don't really want to talk any further - it seems to be something that the devs would need to discuss as to how AMS2 handles devices and if there is any way to modify it within the engine or codebase.

 

I used to use Joy2Key to solve the issue with 2 button boxes that AC Content Manager saw as one. Using Joy2Key you can set your devices as Joy1, Joy2, etc. Just disable it when using games with kernel level anti-cheats like EA WRC.

 

I think it's likely that this is the underlying issue behind many of the issues mentioned in this thread.

I don't have control binding loss issues, and I have noticed that in SimHub - where the control mapper component shows the device GUID - my wheel base reports the same GUID whichever of my wheels I have attached to it. Removing a wheel doesn't cause Windows to think a device has been disconnected, and putting a different wheel on doesn't cause Windows to think a new device has been connected.

This has advantages and disadvantages.

Advantages: I can swap wheels while AMS2 or other sims are running without an issue (I do have to change the control profile in the AMS2 menu if I want the binds to align properly to the new wheel).

Disadvantages: I cannot have different control mapper schemes in SimHub because SimHub cannot tell the difference between the wheels.

Ultimately the decision on whether to present wheels as different devices or the same device is one that the manufacturers of those wheels / bases have taken. Whether it is feasible for the Madness Engine to be adapted to be able to recognise new devices on the fly or not I cannot say.

Also on the topic of button limits - after some testing and discussion with Marius we determined that the limit supported per device by AMS2 is 64. Not germane to the original topic but since other replies touched on it I thought I'd mention it.

 

I'm not sure I agree it has anything to do with GUIDs.

1- My wheelbase never changes - just the attached wheel. So the USB device isn't changing, just the buttons on that device.

2- I have no problem in any other game.

3- Simhub always sees the correct device buttons.

4- I play DCS and don't have any issue with usb devices. I can unplug/replug them in any order and there is no problem - using joystick, throttle, control panel, UFC, shifter, pedals(not used but plugged in), and wheel base which can be turned on or off without causing any mismapping in dcs. If you reinstall windows you can run an automatic text search/replace and copy all the new GUIDs into the control files and everything is back as it was.

5- The settings amnesia happens even when there has been no change in GUIDs, or when I haven't even swapped the wheel or controller profile (ie. after the latest update).

6- It only happens to the wheel, not the pedals or shifter (at least in my case).

This issue is specific to AMS2.

Old games had the problem of reordering USB devices if you unplugged them - so you had to use joy2key or similar to remap to consistent shortcuts. But any game developed in the last 10 years should not be doing this. And I don't think this is what is happening in AMS2. Something else is wonky with the controls saving/recall.

 

Just out of curiosity, if you open AMS2, drive with a 'working' wheel, swap it out, attempt to drive with a non-working wheel, and then swap back to the one that was working, do the bindings then work again without being reassigned? That might help narrow down where the problem lies

 

If I change profiles and the newly selected profile has been erased again, I can switch back to the first profile and it works.

 

Ok I didn't realise you were swapping profiles (I don't use them), so is it that additional controller profiles are disappearing, not the currently selected settings? E.g., if you use the 'wrong' wheel on your currently active profile, do the button mappings work at all?

If it's disappearing profiles and not just the current mappings stop working then that is a totally different problem to what it was sounding like

 

It is just " the current mappings stop working".

By profiles, I mean the in game controller profiles - which allows you to have and swap between 5 separate controller configs.

The settings (and profiles) don't disappear; ie, when you look at the in game profile, the profile is there and the correct buttons are displayed. However they don't do anything - pressing the buttons has no effect in game. You have to reassign the same buttons again to have any affect in game.

It doesn't matter what physical wheel I am using.