Skip to content
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

Port STICK-FORCE-PER-'g' and the effect of dynamic pressure on flight controls from c172p #539

Open
hbeni opened this issue Nov 28, 2023 · 4 comments

Comments

@hbeni
Copy link
Collaborator

hbeni commented Nov 28, 2023

Port STICK-FORCE-PER-'g' and the effect of dynamic pressure on flight controls from c172p

See: c172p-team/c172p#1472 (comment)

While at this, do it in such a way that the control surfaces are decoupled from input, so we might easier support dual control later on.

@Murmur79
Copy link

While at this, do it in such a way that the control surfaces are decoupled from input, so we might easier support dual control later on.

What do you mean precisely? With dual controls you mean manual+autopilot?

@hbeni
Copy link
Collaborator Author

hbeni commented Nov 29, 2023

Its is mandatory that the autopilot will work like before.

with "dual control" i mean, that currently the tie between the yoke and the control surface is so tight, that the FGFS dual-control module cannot be used to induce yoke movements from the copilot instance.
This is something what would be enabled when you implement it, because we then get a layer of "technical indirection" between the actual yoke input and the effect on the flight controls surfaces.
In other words: For the yoke position (and resulting effects) we can more easily add another "pilot effort", from the copilot.

@TheFGFSEagle
Copy link
Contributor

I guess the aileron, rudder and elevator from FG should be used as a force applied to the yoke, instead of translating it directly to the surfaces.

@hbeni
Copy link
Collaborator Author

hbeni commented Nov 30, 2023

Yes Eagle, and no.
It hugely depends on the individual assumed model (effort based vs. movement based) and the used input device.

We had a lenghty discussion about this in the c172 ticket.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants