Thank you for using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.
2 tags are required: One for platform, and one for aircraft.
Are you using Developer Mode or made changes in it?
No
Have you disabled/removed all your mods and addons? 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.
Yes
Which aircraft are you reporting an issue about? (Please also add the proper tag for it)
ATR 42 & 72
Which aircraft version are you experiencing this issue on? (You can find this listed in the Content Manager under the Aircraft Name)
1.0.36
Brief description of the issue:
Altering the Ramp Tolerance appears to have no effect on the Ramp setting “snap-to” range when moving the throttle levers via peripheral. Additionally, the setting reverts back to the default of 250 when leaving and reloading the aircraft, therefore it is not retaining any setting change.
Provide Screenshot(s)/video(s) of the issue encountered:
Detailed steps to reproduce the issue encountered:
Load C&D into either ATR, go to Options > Throttle Setup on EFB, release gust lock, move throttle via peripheral axis to Ramp position, gently move throttle axis forward and backward noting the narrow snap-to range, increase the Ramp Tolerance to 2000, again move the throttle axis gently and note no change in the snap-to range – it remains narrow, click Validate on EFB, click Close on EFB, Click OK on EFB, exit to Main Menu, reload C&D, go to Options > Throttle Setup on EFB, note Ramp Tolerance has reverted from 2000 back to the default of 250.
PC specs and/or peripheral set up if relevant:
Honeycomb Bravo
Build Version # when you first started experiencing this issue:
1.37.19.0
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: