-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pitches up with tailwind on ground #517
Comments
Did you check that the aircraft AND FlightGear version is the most recent? I just tried, and yes, the aircraft is pitching up with winds more than 15ktn. The values should have been realistic once I set them, but may be altered some time ago. I'll check that |
Also look at the CoG: how was the plane loaded when this occurred? (Tanks, Passengers, Baggage) |
I'm on master branch and put the CoG as much forward as possible. FG is next branch. |
I could reproduce it. The first impression is comparing different numbers, that it is not the elevator- there is something else. |
Any new insights into this? 🙏 |
Not yet, at least I can say it is not related with the climb rates issue. I do know that the C182 is sensible to wind on the ground and therefore it will need correct inputs of the yoke wheel in order not to roll over while taxiing, But here there inputs doesn`t have the needed effect. I have to try different things to rule certain things out. |
Interesting read, maybe related, on the Forums: https://forum.flightgear.org/viewtopic.php?p=417356#p417356
and also that the fdm models gear is not spot on the 3D-model ones for the 172, something we should ceck here too |
Unless something had been changed on the fdm since I started the model, the fdm gears should be spot on. That was something I checked really early on the model. |
Had the mood to poke around with versions a bit to try to get a grip on when this was introduced.
So that does in principal verify it is indeed not flightgear itself causing this, but FDM related.
So... I
Verified that by reverting it at masters Head (resolving the conflicts), and indeed the problem went away. |
@hbeni |
That would be awesome; |
Can the pitch coefficient also introduce more lift? |
I testet it and it works for me flawless. I guess I might have changed it, as there had been complaints about to be too sensitive on the elevator controls. But I remember some cockpit videos from real aircraft, which showed it needs only little input to takeoff |
No, and the climb numbers stayed the same with. I might have some time on the weekend, to finally correct this issue. |
@hbeni I will push/ pull request do tomorrow or saturday, as I need to update my authentification. |
Signed-off-by: hhs81 <heiko.h.schulz@gmx.net>
The pitch up with tailwind is also a problem on the c172p (winking to @wlbragg ) and was there introduced with the ommit 3680740 while changing the adverse yaw effect. |
See also: c172p-team/c172p#1489 |
The formula without taking propwash into account and using a simple sin-expression can certainly be improved. |
current FGAddon stable has:
The sin-expression is not present on current github:
If there is a high negative alpha due to tailwind, a high pitch up angle occurs. |
Thank you for investigating further! My programmers mind just wants to add clamping to high negative alpha due to tailwind… which is certainly an ugly, if not evil, hack. |
The non-ugly fix would be to use the first code, instead of the second in Ysops last post ! ;) |
From a simple NACA0012 (using factors for 3D, different thickness, neglecting fuselage, main wing.....):
|
Thanks, but where does this need to go (code wise)? |
will be completed to a full commit after having a look at a few things |
Thank you, will test and report back! |
When I'm on the ground with a tailwind somewhere above 10 kts, the plane pitches up until the tail hits the ground. I noticed a big difference in behavior to the c172p. I don't know if it's relevant, but when I look at the wind pitch moment in the properties, the c172p show much smaller values and reacts to elevator movements. The c182s has a much bigger value and doesn't react much to elevator movements.
The text was updated successfully, but these errors were encountered: