[Artist]

Hi BrassEm,

thanks for that source. It nicely sums up the problem, tallies with my knowledge as described in the opening post, and (with what FC99 wrote) throws a light on what Oleg's team did not consider, when they implemented DirectInput: The code just takes the first four controllers and does not save/remember their GUID. So any additionally connected controller which messes up that window's internal sequence will in consequence mess up the assignments within IL-2.

There are two solutions: Change IL-2's behaviour from using controller one through four identified by their places in the sequence returned by DirectInput->EnumDevices() to identification by GUID. But, and this is a substantial "but", this means quite a lot internal reorganization. And I doubt that there are that many IL-2 pilots out there which do have a problem with a fifth, sixth, or nth controller which cannot be solved with YaDeLi and Autohotkey (except for the new mixture axis, see my signature, TD, will you please?) to merit that effort.

The other solution you already expressed hopes in and I in fact had in mind is: Programatically influence the sequence in which DirectInput->EnumDevices() returns the devices, therefore controlling which devices IL-2 'discovers' and in which order. I'll investigate the possibilities, but it will take some time, spare time that is.

Artist