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

Reduced ELEVATOR_TRIM_EFFECTIVENESS #170

Open
wants to merge 1 commit into
base: development
Choose a base branch
from

Conversation

dneiss
Copy link

@dneiss dneiss commented Feb 8, 2022

My Honeycomb Bravo throttle quadrant couldn't dial in the right amount of elevator trim,
it was either too much or too little for each bit of adjustment on the trim
wheel. I swagged this down to .1 and it takes more turn movements in
exchange for what appears to be finer resolution, making it easier
to dial in the right amount of trim.

It looks like this was actually increased to 1 and so Im not
sure this will be accepted, as someone else needs a way larger
number for some reason.

throttle quadrant couldn't dial in the right amount of elevator trim,
it was either too much or too little for each bit of adjustment on the trim
wheel. I swagged this down to .1 and it takes more turn movements in
exchange for what appears to be finer resolution, making it easier
to dial in the right amount of trim.

It looks like this was actually increased to 1 and so Im not
sure this will be accepted, as someone else needs a way larger
number for some reason.
@weptburrito
Copy link
Collaborator

This is not the correct place to properly make that change, What will end up happening is that when/if you max out the trim in either direction, you will have no where near the amount of trim available that you used to..

My bravo trim is moving it in 0.1 degree increments according to the tooltip on the trim in the cockpit.

Are you using the sims control options or a third party? If the control options, I see what you're talking about. It's a bit jumpy. Try to do a small amount and it does nothing, then suddenly moves a lot. I use spad.next for everything and don't have this issue there, can easily make small adjustments.

@N95JPL
Copy link
Member

N95JPL commented Feb 9, 2022

The effectiveness will cause bigger issues, so in this instance I won't merge this request.
Like Wept said above, you can change your devices sensitivity/travel for changes, using SPAD or through FS itself (IIRC)
We've already got the increments set pretty low as a kind of a happy medium for keyboard users and peripherals.
Give your settings a tweak and let us know!

@N95JPL N95JPL added the On Hold label Feb 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants