You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Angle and Horizon Mode improvements should not be forced on existing users. Regarding #12231 I think this should be made a CLI option or a new flight mode for several reasons.
There is no current precedent for yaw to be based on anything but the aircraft, it is a new mode of operation.
All existing documentation online regarding angle and horizon will become confusing and out of date.
It makes it more difficult for new users to transition from angle to acro where coordinated turns are necessary.
Existing users of angle mode that have already taken the time to mix yaw and roll will be forced to change.
All existing users of angle mode that want to keep using the normal implementation will have revert with CLI.
All new users that simply want a quad that flies like any out of the box toy will have to use CLI.
For those that fly acro this would be like changing acro to acro trainer and then saying everybody needs to use CLI to switch back because we've decided to redefine what acro is. The way acro trainer was implemented seems like a much better way to roll out this type of change.
Allot of Betaflight users aren't active developers and don't really have a voice on new changes. I hope there is at least some consideration to change how this is implemented because I don't think a forced change to such a basic flight mode is a good idea for most users.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Angle and Horizon Mode improvements should not be forced on existing users. Regarding #12231 I think this should be made a CLI option or a new flight mode for several reasons.
There is no current precedent for yaw to be based on anything but the aircraft, it is a new mode of operation.
All existing documentation online regarding angle and horizon will become confusing and out of date.
It makes it more difficult for new users to transition from angle to acro where coordinated turns are necessary.
Existing users of angle mode that have already taken the time to mix yaw and roll will be forced to change.
All existing users of angle mode that want to keep using the normal implementation will have revert with CLI.
All new users that simply want a quad that flies like any out of the box toy will have to use CLI.
For those that fly acro this would be like changing acro to acro trainer and then saying everybody needs to use CLI to switch back because we've decided to redefine what acro is. The way acro trainer was implemented seems like a much better way to roll out this type of change.
Allot of Betaflight users aren't active developers and don't really have a voice on new changes. I hope there is at least some consideration to change how this is implemented because I don't think a forced change to such a basic flight mode is a good idea for most users.
Beta Was this translation helpful? Give feedback.
All reactions