<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - Libinput 0.19 and 0.20 ignore POINTINGSTICK_CONST_ACCEL"
href="https://bugs.freedesktop.org/show_bug.cgi?id=91369#c42">Comment # 42</a>
on <a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - Libinput 0.19 and 0.20 ignore POINTINGSTICK_CONST_ACCEL"
href="https://bugs.freedesktop.org/show_bug.cgi?id=91369">bug 91369</a>
from <span class="vcard"><a class="email" href="mailto:peter.hutterer@who-t.net" title="Peter Hutterer <peter.hutterer@who-t.net>"> <span class="fn">Peter Hutterer</span></a>
</span></b>
<pre>First analysis here. The range differs greatly. Pressing hard on the trackpoint
I have here (which most of libinput's accel is tested against) I can easily get
into the 30+ range for REL_X/Y. Both recordings in Commment 41 go up to a max
of 15. In addition, the sample frequency is lower, ~70Hz vs my 100Hz.
This results in significantly different speeds being calculated. The
CONST_ACCEL in libinput isn't just used as a straightforward multiplier but it
adjusts the acceleration curve so that it accelerates sooner and has a higher
maximum. [1]
This works provided we get into that range.
Looks like Iiro never gets close to the maximum. The data I get from this,
overlaid onto the acceleration curve matches exactly. The problem is that it
just never really gets into the differing range. For reference, look at the
low-dpi graph here:
<a href="https://wayland.freedesktop.org/libinput/doc/latest/pointer-acceleration.html">https://wayland.freedesktop.org/libinput/doc/latest/pointer-acceleration.html</a>
The events are almost all left of the x:0.001 marker, where the difference
isn't as pronounced yet and CONST_ACCEL has relatively little effect.
In other words: we need to a) rethink the trackpoint acceleration for these
devices and b) possibly need some property to auto-scale the range of the
trackpoint. I'm not sure CONST_ACCELERATION fits the bill as well as we hoped.
[1] A straightforward multiplication can make pixel-precision impossible, a
delta of 1/1 would move 3/3 with a a simple const accel of 3</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>