new turtle beach rudders

[Flyer626]

I just installed new turtle beach rudders to my system, I have calibrated them and they seem to be working fine. I had thrustmaster rudders before and they seem to be still in the profile not the new turtle beach. Why is this?FSUIPC6.iniFSUIPC6.iniFSUIPC6.iniFSUIPC6.ini

FSUIPC6.log

[John Dowson]

The details of your controllers are taken from the windows registry - I do not know or understand why these have not been updated.

I am also surprised that the rudder is working - the toe brakes seem to be assigned ok but the rudder assignment is empty:

Quote

[Axes.787]
RangeRepeatRate=10
0=0X,256,D,0,8,0,0    -{ DIRECT: RightBrake }-
1=0Y,256,D,7,0,0,0    -{ DIRECT: LeftBrake }-
2=    -{ DIRECT: Rudder }-
...

?

Can you attach your FSUIPC6.JoyScan.csv file please.

[Flyer626]

will do, btw under windows settings bluetooth the device does appear and the old rudders device is gone.

FSUIPC6.JoyScan.csv

[John Dowson]

That looks fine.  I don't understand why it is using the same vendor id (044F)  as Thrustmaster though, but  I wouldn't worry about this.

The only worrying thing is the empty assignment line:
    2=    -{ DIRECT: Rudder }-
I have never seeing anything like that (no assignment details but a valid comment/annotation). Can you remove that line (when FSUIPC/P3D is not running) and then try and reassign and re-calibrate your rudder, and check that the assignment line looks correct afterwards.

You should also switch to using JoyLetters - just change this:
    AutoAssignLetters=Yes

John

[Flyer626]

I do assign the rudder an axis assignment, then I go and do a configuration for calibration. This part is very unconventional, I reset the rudder and do not set them again. It seems to have a default setting, maybe the firmware does it, I don't know  but it then works perfectly. Old adage don't fix it if it is not broken might apply. I go down the runway on takeoff and rudder is very smooth and makes small adjustments accordingly. I did make the other change you advised.