Re: [w3c/pointerlock] Option needed to disable OS-level adjustment for mouse acceleration (#36)

Initial specification discussions did include this topic.  The spec FAQ
summarizes as in 12.4
https://www.w3.org/TR/pointerlock/#why-bundle

In email group discussions it was raised that some games do use raw mouse
movement, before OS level adjustments.  Those adjustments are tuned to
making a relative motion pointer work well.  Other uses of mouse movement
may not work well with those same curves.  E.g. First person viewpoint
adjustment.  Further, there are also higher resolution updates for
precision aiming.

The 2011 specification selected a pragmatic choice of shipping something
that could be clearly specified and consistently implemented across
platforms.  It handles the majority of client applications -- there are
many web games using pointer lock after OS level adjustments to inputs.

See discussions in the proximity to:
https://lists.w3.org/Archives/Public/public-webapps/2011JulSep/1043.html

If there is developer demand, I personally do believe an iteration that
provides increased access to raw mouse input would be useful.

On Tue, Oct 2, 2018 at 8:20 AM smaug---- <notifications@github.com> wrote:

> I don't have enough experience on games to say what is preferred here. I
> would expect people to look at the platform prefs. Perhaps @juj
> <https://github.com/juj> has some feedback to this.
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/w3c/pointerlock/issues/36#issuecomment-426314548>, or mute
> the thread
> <https://github.com/notifications/unsubscribe-auth/AAXnmxM8OMYPpJp7y7gV3dh1zoM7c3a4ks5ug4QmgaJpZM4Wn7_N>
> .
>


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/pointerlock/issues/36#issuecomment-427718756