Jump to content

Recommended Posts

Posted

Hey Dev Team :)

 

I was switching my Joystick to the MS FF2 Sidewinder Stick last night to give the KA 50 a ride

with realistic stick behavior after trimming. I have done that before when I bought the KA and it worked fine but later moved to a non FF Stick with standard springs for most of the time I am flying.

 

As said, I switched the stick to MS FF2 Sidewinder and upon setting the trim with RCTRL-ENTER open to check the trim point was stored exactly 90° off the left which it didn't do before the recent updates. It used to work before, that I know.

 

Maybe its a typo in the code, messing x and y coords, should be simple I hope.

 

I tried all directions, each trim position is set 90° offset to what the red box shows and makes flying the KA 50 with that stick impossible. It may only be that stick, maybe others are effected too.

 

I got my Logitech Freedom 2.4GHz back on it and curved around that issue.

 

 

Check Six !

 

Bit

Gigabyte Aorus X570S Master - Ryzen 5900X - Gskill 64GB 3200/CL14@3600/CL14 - Sapphire  Nitro+ 7800XT - 4x Samsung 980Pro 1TB - 1x Samsung 870 Evo 1TB - 1x SanDisc 120GB SSD - Heatkiller IV - MoRa3-360LT@9x120mm Noctua F12 - Corsair AXi-1200 - TiR5-Pro - Warthog Hotas - Saitek Combat Pedals - Asus XG27ACG QHD 180Hz - Corsair K70 RGB Pro - Win11 Pro/Linux - Phanteks Evolv-X 

Posted
Hey Dev Team :)

 

I was switching my Joystick to the MS FF2 Sidewinder Stick last night to give the KA 50 a ride

with realistic stick behavior after trimming. I have done that before when I bought the KA and it worked fine but later moved to a non FF Stick with standard springs for most of the time I am flying.

 

As said, I switched the stick to MS FF2 Sidewinder and upon setting the trim with RCTRL-ENTER open to check the trim point was stored exactly 90° off the left which it didn't do before the recent updates. It used to work before, that I know.

 

Maybe its a typo in the code, messing x and y coords, should be simple I hope.

 

I tried all directions, each trim position is set 90° offset to what the red box shows and makes flying the KA 50 with that stick impossible. It may only be that stick, maybe others are effected too.

 

I got my Logitech Freedom 2.4GHz back on it and curved around that issue.

 

 

Check Six !

 

Bit

Check out "FF Tune" under Options->Controls for the relevant axes.

Posted

I will, thanks.

 

I doubt that that will help cause all that is wrong is the trim position stored relative to where the stick is at the moment of trimming. The position being stored as new centre is 90° offset.

 

The stick works great, all axis are correct and respond as usual, just that you shouldn't store a trim point cause it is stored 90° offset which indicates another axis with negative value being referred to, mathematically...more or less

 

But I will double check what you said to not let horses go where there are non :)

 

Bit

Gigabyte Aorus X570S Master - Ryzen 5900X - Gskill 64GB 3200/CL14@3600/CL14 - Sapphire  Nitro+ 7800XT - 4x Samsung 980Pro 1TB - 1x Samsung 870 Evo 1TB - 1x SanDisc 120GB SSD - Heatkiller IV - MoRa3-360LT@9x120mm Noctua F12 - Corsair AXi-1200 - TiR5-Pro - Warthog Hotas - Saitek Combat Pedals - Asus XG27ACG QHD 180Hz - Corsair K70 RGB Pro - Win11 Pro/Linux - Phanteks Evolv-X 

Posted

Hi

 

It's a known issue, check the box saying "swap axis" in the FF Tune, for the pitch axis, and you don't have to do it for the Roll axis again, it's enough to do it only for one axis.

 

Good Luck!

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...