[1.13] VTOL takeoff problem hotfix #20568
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
to avoid float rounding errors leading to tiny acceptance radii getting considered
…r takeoff items otherwise a previously adjusted or uninitialized radius from the last flight can cause problems during the new takeoff
|
@MaEtUgR Thanks for doing the Backport! SZ is one of my colleges. We want to share our findings here with the Community, that's why you got the information twice. |
|
@OfficerJannis Nice, thanks a lot for the clarification and sharing your findings! That's helpful 👍🏻 |
julianoes
approved these changes
Nov 11, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Describe problem solved by this pull request
@OfficerJannis reported that the problem I fixed in #20171 also happened to him on the release 1.13. Also I got basically the same report a second time on Discord from SZ#6337 sadly in private (will not accept that in the future anymore).
So I'm following @julianoes 's valid request here #20171 (comment) and backport the fix to 1.13.
FYI @OfficerJannis
Describe your solution
See #20171
Test data / coverage
This was tested by many people by now on
mainand reportedly also backported to older versions to fix the original issue.