Alternative launcher device sorting order problem
-
I have x55 rhino setup. Stick, throttle. Saitek combat pedals. I also have for p3d alpha flight controls and saitek throttle quadrant.
Before I installed the alternative launcher I had to rearrange the device sorting.txt order as alpha flight controls is first in list then rudder pedals then x55 throttle then flight throttle quadrennial and x55 stick last.
In the standard bms launcher the order stays how I have rearranged it. X55 stick, x55 throttle, combat rudder pedals and the other two last.
After instilling alternative launcher the order reverts to the the original even if I rearrange it again -
I have x55 rhino setup. Stick, throttle. Saitek combat pedals. I also have for p3d alpha flight controls and saitek throttle quadrant.
Before I installed the alternative launcher I had to rearrange the device sorting.txt order as alpha flight controls is first in list then rudder pedals then x55 throttle then flight throttle quadrennial and x55 stick last.
In the standard bms launcher the order stays how I have rearranged it. X55 stick, x55 throttle, combat rudder pedals and the other two last.
After instilling alternative launcher the order reverts to the the original even if I rearrange it againI “think” I remember someone just making DeviceSorting.txt Read-Only for this issue and it solved his problem… ?
-
Ah thank you Icer. Do you use the alternative launcher yourself.
-
Ah thank you Icer. Do you use the alternative launcher yourself.
Yes, but I don’t have issues with DeviceSorting with my setup at this point.
-
Ok that doesn’t work. If I put my devices in the correct order and tick and apply read only in device order properties as soon as I launcher alternative launcher and exit the launcher my device order is back to the original and the read only box is unlocked.
-
Why do you have to arrange device sorting?
AL NEEDS to sort devices in the order he decided so that callbacks/axis will set to BMS just as same as you set in AL.
And usually, that works fine…
You don’t have to care about device sorting. -
Hi Chihirobelmo,
This is a great app to say first. The problem I have is I use saitek x55 setup. Stick and throttle. Then I have the saitek combat rudder pedals. For p3d I use an alpha flight yoke and a saitek throttle quadrant. The order it wants to put it in is alpha, rudder, x55 throttle, x55 stick then quadrant. If I use the provided x55 input devices hot as setup in bms the order is wrong where it should be x55 stick, x55 throttle then rudder pedals. I think the dx order is wrong so it doesn’t see some key bindings for the stick and throttle.
-
The problem I have is I use saitek x55 setup.
If I use the provided x55 input devices hot as setup in bms the order is wrong where it should be x55 stick, x55 throttle then rudder pedals. I think the dx order is wrong so it doesn’t see some key bindings for the stick and throttle.
Do you mean you are also setting up some kind of key bindings with Saitek driver?
-
I am loading a profile BMS X-55_DX.pr0 file to the X55 software.
-
If you use BMS stock X55 setup I don’t recommend using AL.
AL is designed to use without any Saitek or TARGET profile, it is designed to set up every callback in AL, they won’t work together. -
I see. So you can’t load key profile / files with AL. You have to assign all x55 buttons and rotary axis manually. Do you know if the mini joystick on the side of the x55 throttle is configurable in AL.