I think that’s a bit premature to say it’s solved with 7.1
There are only two developers who’ve reported back, one of whom is still testing.
There are quite a few different a/c categories that need to be tested and reported clean before you can realistically check this off the list.
I’m not the a/c dev though, so it’s not really my responsibility to do this.
Who’s is it? Asobo, for breaking it (and didn’t notice, I might add)?
Or does every a/c dev have to revalidate all their product FM’s, or just go on the word that’s it’s fixed based on anecdotal evidence from a tiny % of the a/c user base?
It certainly shouldn’t be up to the users and customers.
In fact, it’s worth remembering that this whole mess likely exists because somebody, somewhere, signed off on a testing sample that wasn’t representative of the broader aircraft ecosystem. Whether that was specific aircraft types, specific flight regimes, or simply an inadequate test matrix, the result was the same: a regression that appears to have affected many users escaped into release because a limited sample was assumed to represent the fleet as a whole.
There also appears to be a variety of other fight model related issues which may or may not be drag bug related but are certainly in the category of SU 7.x broken flight model under specific flight scenarios/use cases. People don’t seem to be imagining these issues, they’ve been replicated by multiple users.
So no, I don’t think we’re at the point where anyone can responsibly declare this solved. We have some positive reports, which is great, but positive reports are not the same thing as verification.
A regression that affected a broad range of aircraft requires broad validation before it’s signed off. Until we see that, “appears improved” is a fair conclusion. “Solved” isn’t.