-
Notifications
You must be signed in to change notification settings - Fork 22
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
[Request] Higher than 100% gain #29
Comments
I'm not sure about this. It seems most FFB settings are migrating from drivers to the apps on Windows. The game in the link has settings to set the FFB above 100% and a minimum force. In case it's needed for other games, I'm not sure what would be best, having up to 150% gain or having a minimum force setting. Let me think about it and maybe collect some comments. |
I think a min force setting would be better, something like this?
I did notice some games have a min force setting, like Assetto Corsa for example which is nice, although not all have it unfortunately, especially ones that are not getting updated anymore. |
That's just one way to do it. This way any force detail below the threshold would be lost. Perhaps a better better way to do it would be to compress the force levels up. |
I'm finally thinking I should add min_torque and "higher than 100% gain" settings. I'm used to play with these settings in rFactor 2 and they can help tune Logitech wheels to get more out of them. I don't want to crop the output but rather scale the input to the desired output range. Suggestions are welcome. |
On the Windows driver, it's possible to go higher than 100% (I believe 150% is the max).
Setting the gain to somewhere between 105 and 112% on the G25/G27 reduces the FFB dead zone when the wheel is center, they added the dead zone to prevent the 2 motors from fighting each other, causing a type of reverb effect, but at ~110% it doesn't seem to happen while reducing the dead zone to almost nothing.
You can read more about the issue here: https://www.racedepartment.com/threads/bad-deadzone-on-g27.145463/
The text was updated successfully, but these errors were encountered: