WiimoteEmu: Expose IMU pointing accelerometer weight setting.

[jordan-woyak]

Reducing this value can produce a less jittery pointer with reduced drift correction.

A user reported they had better results with 1% vs the default 2%.

The best name for the setting that I could come up with is "Accelerometer Influence".
I think it's descriptive and accurate enough. Anything else I can think if is ambiguous or too long.

[iwubcode]

Just based off your comment, I'm inclined to suggest "Accelerometer drift correction" or something to that effect.

And then maybe instead of a value, have a combo box with "high", "medium", "low" with some preset values. Otherwise I imagine users are going to crank it up to 100%.

[Rumi-Larry]

Consider instead "Accelerometer induced pitch-and-roll bias"

[rlnilsen]

This setting is the ratio of how much trust you put in accelerometer vs gyroscope data (at least in my original code, I don't know if the new quaternion stuff is exactly equivalent). The gyroscope is accurate but drifty, the accelerometer is inaccurate but does not drift. So we mostly trust the gyroscope (98% by default), but use the accelerometer to correct gyroscope drift. So maybe "Accelerometer to gyroscope trust ratio"? I'm bad with names.

... I'm inclined to suggest "Accelerometer drift correction" or something to that effect.

Unlike gyroscopes, accelerometers do not have drift.
Ah, I see that this can read as both "correction of accelerometer drift" and "drift correction by accelerometer".

[rlnilsen]

The code is untested by me but seems very straight forward and boiler plate, so once the wording issues are resolved this LGTM.

Edit: Gave it a spin and seems to be working well. The pointer gets pretty shaky already at 5%, so I don't know how useful it is to go above that though. This was with a DS4.

[rlnilsen]

Perhaps just "Drift Correction" would be sufficient? That's really all one needs to draw the user's attention if they are experiencing drift. Then the tooltip can give a deeper explanation.

[JMC47]

I like the idea of drift correction for the user facing option name. If that's the only thing blocking this, we should probably change this and merge it.

[jordan-woyak]

My issue with "Drift Correction" is it doesn't convey that accelerometer data is used.
In the future we might also have correction from IR data or whatever.
I'm leaning towards maybe "Accelerometer Coefficient" or "Accelerometer Weight".

[AdmiralCurtiss]

Do you want to put this as an Advanced setting now that we have that?

[jordan-woyak]

Do you want to put this as an Advanced setting now that we have that?

I'm thinking not. It's already on an "Advanced" tab.

[AdmiralCurtiss]

Well alright then, this seems good otherwise, so...