YAW & ROLL Storing Bug in Custom Profiles

[US103_Baer]

Overview:

YAW and ROLL sensitivity is NOT storing as part of a Custom Profile.

It remains in the last set position no matter what profile/plane you're using.

......................................................

 

Details:

While flying Camel I create a 'Camel' profile with custom Engine Blip button. No other changes from global are made. Joystick inputs all 0% sensitivity.  

I assign the profile to the Camel.

 

I jump in a SPAD180 and create a Spad180 profile with 60% YAW sensitivity.

Assign profile to SPAD 180.

 

Now go back to fly the Camel. Rudder feels odd. Check profile. Its using 'Camel' and custom engine Blip is working, but YAW sensitivity is 60%!

I set YAW back to 0% and 'accept'.

 

Back to the SPAD180 and yup, its using the correct profile but YAW is now 0%.

.............................................

 

Is this a bug, or expected behaviour because .responses are saved in different format/files to .actions?

Seems a real shame if this is expected as they'd be the only Inputs that can't be made plane specific. I assumed YAW sensitivity would be customisable and it would be valuable in FC.

Edited August 14, 2022 by US103_Baer