Regression of the control profile management in a configuration with several identical joysticks

1 tag is required - add it in the tag section next to the title above:

Feel free to delete this quote section after adding your appropriate tags.


ISSUE DESCRIPTION

Description of the issue:
It is no longer possible to assign a specific profile to each of my five saitek pro flight throttle quadrant since obviously as soon as I assign a profile to any joystick, the five joysticks of the same type are automatically configured with this same profile.

[PC Only] Did you remove all your community mods/add-ons? If yes, are you still experiencing the issue? yes

FREQUENCY OF ISSUE

How often does this occur for you (Example: Just once, every time on sim load, intermittently)? every time

REPRODUCTION STEPS

Please list clear steps you took in order to help our test team reproduce the same issue:

  1. assign profil 1 to saitek pro flight throttle quadrant 1
  2. assign profil 2 to saitek pro flight throttle quadrant 2
  3. assign profil 3 to saitek pro flight throttle quadrant 3
  4. assign profil 4 to saitek pro flight throttle quadrant 4
  5. assign profil 5 to saitek pro flight throttle quadrant 5
  6. Checking the profile assigned to each saitek
  7. ==> profile 5 assigned to all saitek !!!

YOUR SETTINGS

If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.

What peripherals are currently plugged in? Please name all of them as there could be a potential conflict.
1 : SideWinder Force Feedback 2
2 : MFG Crosswind V2/3
3 : Saitek pro Flight Throttle Quadrant
4 : Saitek pro Flight Throttle Quadrant
5 : Saitek pro Flight Throttle Quadrant
6 : Saitek pro Flight Throttle Quadrant
7 : Saitek pro Flight Throttle Quadrant

[PC Only] Are you using Developer Mode or have you made any changes to it?
No

[PC Only] What GPU (Graphics Card) do you use?
RTX4080 super

[PC Only] What other relevant PC specs can you share?
all saitek pro flight throttle quadrant connected to a D-Link DUB-H7 hub

MEDIA

Please add a screenshot or video of the issue occurring.

[END OF FIRST USER REPORT]


:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?
•

Provide extra information to complete the original description of the issue:
•

If relevant, provide additional screenshots/video:
•

Yeah, all controllers would have a separate ID through windows, but somehow the sim takes the name of the controller and duplicates it’s settings…
Having the same issue with 2 of my buttonboxes by the same manufacturer, even though they are slightly different, they have mistaken identities in msfs2024.

I also have this problem with the beta.

VKB Joystick
VKB THQ Throttle Quadrant

Before the beta, one would be correct, the other would vary in its incorrect profile assignments.
Now, with the beta, the first device will be correct and the second device always has the same assignment as the first device (which is wrong).

If I change the second device to its correct profile, hit ESC and Save to go back to the sim, everything works. But the next time I fly, I have to do the same thing all over again.

Bill

1 Like

Given that obviously, Asobo was not able to maintain on msfs 2024 what at least worked correctly on msfs 2020 regarding the management of configurations using several joysticks of the same reference, I would like to know what the level of diploma is necessary to be able to correct all this mess in the next update…
It seems to me that we are here on a very basic functionality. The way in which this subject is treated is not very glorious for Asobo’s image

I gave up on 2024. I have 0 bind issues with 2020 but 2024 makes it impossible.

Did this work for you correctly before the Beta?

Do you have the same issue if you follow the OP’s steps to reproduce it?
• Yes I do. Two (virtual) USB devices with matching names are now defaulting to same control profile and will always change to be on the same single profile. This breaks the functionality of the second device (axis are named the same per device, so the profiles need to be separate to function).

Provide extra information to complete the original description of the issue:
• I am using a VKB Gladiator NXT joystick with a THQ unit and FSM connected through the joystick. The THQ is split into a second virtual device to accommodate several axes.

Just like MichingBill222, before SU1, I had to manually change the second device to it’s own profile for each plane in each game mode - but it would then stick and work until I closed the game. Now, both devices apparently only can use the same profile. This will be a problem for users of VKB devices (in particular) and anyone using duplicate hardware.

If relevant, provide additional screenshots/video:
•

I am using a similar VKB setup, but I can’t get the profiles to separate at all - not even temporarily like you mentioned being able to. My THQ Throttle Axis is called “Axis X”, as is my Aileron axis on the Joystick. So without being able to use different profiles per device, I drop throttle when I bank left, and crank it when I bank right.

Before the beta see https://forums.flightsimulator.com/t/assigning-profiles-to-joysticks-not-saved-same-bug-with-1-2-7-0-and-1-2-8-0/671215

2 Likes

Tested on several planes with 1, 2, 3 or 4 engines the problem finally seems to be corrected with beta 1 version 1.3.10.0
Many thanks.
This defect really irritated me

1 Like

I also have a VKB Gladiatior NXT with a connected THQ lever module, which show up as two devices with the same name.

For me, the issue is still present in the latest update,
the device containing the THQ axes seems to have its profile messed up.
The control settings still show the correct profile selected for both devices,
but the THQ profile has the assignments from the Gladiator NXT profile added into it. In my case, the throttle and propeller levers now also control the camera.

Screenshot of the THQ profile, it should only have the propeller axis bound, the rest is from the NXT profile:

Before the Beta, the THQ device would simply “forget” the assigned profile and I would quickly reassign it, while I now have to unbind several controls each time this happens.