increasing sensitivity wont increase speed more

[pranshuthegamer]

ive raised the sens by 4x and it still it slow

[systemofapwne]

Can you please post your config and tell me, how you raised your sens? Did you maybe also apply a speed-cap?

[serossi]

the sensitivity value does nothing, and its redundant anyway.
either we have sensitivity or we have prescaler, both doesnt make much sense.

so we need to set prescaler to starting value then use acceleration and speedcap to control

and if we have both i would suggest to update help text in config file to let people set prescaler to 1000dpi not 400
that would make math a lot easier like 1f=1000 so sense at 1.46f is 1460 dpi

[systemofapwne]

The sensitivity value in fact does something but its meaning is rather subtle and mostly not clear to people.
On the other hand, PreScale(X/Y) is like a pre-applied sensitivity factor and that is what people might be mostly looking for, when searching a "sensitivity"-factor. RawAccel (on Windows) merged both together which made me a bit unhappy: I for example created a (for me perfect) curve using one specific mouse by mostly tweaking "Sensitivity". When using another mouse of different DPI, I just touched the PreScaleX/Y to "scale up" that other mouses "DPI" counts to the one I created my previous curve with. That made that mouse feel the same and this is also, why this is still in the code.

I will also most likely not change the behavior right now (regarding your 400 or 1000 DPI comment). I am currently in a rewrite of the code anyway, which will allow more curves and will get leetmouse closer to rawaccel. That process (getting closer to rawaccel) anyway means, moving to their config variables sooner or later. But I have to ETA there yet.

[pranshuthegamer]

ive learnt that decreasing acceleration actually increases it ill post an update in a few hours, please remindme

…

On Wed, Jun 22, 2022, 00:51 Klaus ***@***.***> wrote: The sensitivity value in fact does something but its meaning is rather subtle and mostly not clear to people. On the other hand, PreScale(X/Y) is like a pre-applied sensitivity factor and that is what people might be mostly looking for. RawAccel (on Windows) merged both together which made me a bit unhappy: I for example created a (for me perfect) curve using one specific mouse by mostly tweaking "Sensitivity". When using another mouse of different DPI, I just touched the PreScaleX/Y to "scale up" that other mouses "DPI" counts to the one I created my previous curve with. That made that mouse feel the same and this is also, why this is still in the code. I will also most likely not change the behavior right now. I am currently in a rewrite of the code anyway, which will allow more curves and will get leetmouse closer to rawaccel. That process (getting closer to rawaccel) anyway means, moving to their config variables sooner or later. But I have to ETA there yet. — Reply to this email directly, view it on GitHub <#13 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AOUJCT7SOROYRX7VUF5AZSTVQII23ANCNFSM5SVQME7Q> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[systemofapwne]

ive learnt that decreasing acceleration actually increases it
…
On Wed, Jun 22, 2022, 00:51 Klaus @.> wrote: The sensitivity value in fact does something but its meaning is rather subtle and mostly not clear to people. On the other hand, PreScale(X/Y) is like a pre-applied sensitivity factor and that is what people might be mostly looking for. RawAccel (on Windows) merged both together which made me a bit unhappy: I for example created a (for me perfect) curve using one specific mouse by mostly tweaking "Sensitivity". When using another mouse of different DPI, I just touched the PreScaleX/Y to "scale up" that other mouses "DPI" counts to the one I created my previous curve with. That made that mouse feel the same and this is also, why this is still in the code. I will also most likely not change the behavior right now. I am currently in a rewrite of the code anyway, which will allow more curves and will get leetmouse closer to rawaccel. That process (getting closer to rawaccel) anyway means, moving to their config variables sooner or later. But I have to ETA there yet. — Reply to this email directly, view it on GitHub <#13 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOUJCT7SOROYRX7VUF5AZSTVQII23ANCNFSM5SVQME7Q . You are receiving this because you authored the thread.Message ID: @.>

Yes, in fact, that value appears in the denominator of the full equation in the end. I will attach the formula for the code in a second in a readable way.

This is the math behind it (sort of reduced).

As you can see, the actual acceleration "curve" is in the middle part while PreScale allows you to make a slower DPI mouse appear faster (thus seeing the same acceleration curve), while PostScale could be used as some "1080p -> 4k" "Monitor-DPI" scaler.

[serossi]

im sorry but this is indeed redundant.
sensitivity is a bad word anyway we shouldnt use. we know only velocity, this is the end product
with CPI / time as input.

anything you can achieve with sensitvity can be achieved with tweaking acceleration itself.
the pre scaler already allows you to use different mice on different cpi (dpi) settings without further tweaking acceleration

however keep in mind that both, accelerations as your "sensitivity" will have different results on different dpi even with prescale
if cpi or cps (counts per second) are not adjusted

this is the reason why rawaccel now has a new feature, that is the normalize checkbox in the USB device settings.
it will change scales from cpi to cps and normalize dpi value to everything is 1000 dpi.

this way you can truly run different dpi with the same curve settings and the same result.
even tough iam not fully sold on their approach either and it also has some problems currently

anyway i still dont see any good reason for that sensitivity value. not saying you should change it, but based on the math here it just is redundant and also the description is kind of confusing.

as for your mouse curve, you could simply divide your acceleration factor by what you have set in sensitivity to achieve the same effect. that wont change with any other mouse either any better or worse.
how good either solution will work on different cpi (dpi) mouse settings will solely depend how prescale exactly is used and applied