Just a note: always scale DOWN your dpi, NEVER UP!!

Edited July 31, 20215 yr by randomguy7

I do not know these games. But i'm guessing that you are trying to have same MDH 100% for both games and you are using RawAccel not for acceleration but for scale your sensitivity (DPI). To be more close to Kovaak? because Destiny 2 can set minimum sensitivity increment only by 1? 

Good shout - possibly better option in the Calculator would be to just have "Required DPI" as an aim output , so you could just arrive at the required effective dpi without doing the discrepancy calculation.

You could then just do (output dpi/actual mouse dpi) = Rawaccel sens multiplier.

There's also nothing wrong with scaling up the dpi either with a multiplier above 1. Math is math.

Edited July 31, 20215 yr by TheNoobPolice

Works like a charm, gotta love raw accel, but I think some games straight up just block it. For instance, I gave it a try on Ironsight and no matter how I set up the sens multiplier, the game still felt the same.

"For instance, I gave it a try on Ironsight and no matter how I set up the sens multiplier, the game still felt the same"

Just to note this isn't true. There are no games that block it.

Ironsight gets it's mouse input from the same place the desktop or any other game does, and since drivers like rawaccel / custom curve etc update the (x,y) mouse packet underneath the OS proper at kernel level and don't even require any user space process to apply the math, this would not be possible. This was not the case for interception based programs like Povohats, since they applied the math in a user space process before communicating with the interception driver, so a game's anti-cheat could block this user process from interacting with the driver.

In order this to happen with rawaccel, Ironsight would have had to write a kernel-mode signed driver itself to read the (x,y) packet even before the rawinput queue, and also before any other filters in the low-level input stack, which for a game would be unheard of, expensive, unnecessary, and stupid.

as someone, using custom curve to do exactly this for borderlands 2 ( 0.25 multiplier with 1600 dpi to make the game playable even when using the lowest ingame value without the hex editing stuff )

i must say that having this as another function in the calculator would be nice for games with shitty inputs like bl2 destiny etc

even tho id have no idea on how to implement it @DPI Wizard

Edited December 18, 20214 yr by fortunate reee

1 hour ago, fortunate reee said:

even tho id have no idea on how to implement it

 

Edited December 18, 20214 yr by MacSquirrel_Jedi

2 hours ago, fortunate reee said:

even tho id have no idea on how to implement it @DPI Wizard

All you need is the output to tell you the ideal DPI and multiplier, correct? I could do something like this mockup for the advanced output:

2 hours ago, fortunate reee said:

as someone, using custom curve to do exactly this for borderlands 2 ( 0.25 multiplier with 1600 dpi to make the game playable even when using the lowest ingame value without the hex editing stuff )

i must say that having this as another function in the calculator would be nice for games with shitty inputs like bl2 destiny etc

even tho id have no idea on how to implement it @DPI Wizard

You can already do this via the discrepancy, if you change to advanced view, it shows you the DPI required for zero discrepancy for each aim

Edit : just saw dpi wizards reply, although the calculation is extremely simple, it would be simpler to expose it to the user in that way with the multiplier 

Edited December 18, 20214 yr by TheNoobPolice

On 12/18/2021 at 8:35 AM, TheNoobPolice said:

Just to note this isn't true. There are no games that block it.

Ironsight gets it's mouse input from the same place the desktop or any other game does, and since drivers like rawaccel / custom curve etc update the (x,y) mouse packet underneath the OS proper at kernel level and don't even require any user space process to apply the math, this would not be possible. This was not the case for interception based programs like Povohats, since they applied the math in a user space process before communicating with the interception driver, so a game's anti-cheat could block this user process from interacting with the driver.

In order this to happen with rawaccel, Ironsight would have had to write a kernel-mode signed driver itself to read the (x,y) packet even before the rawinput queue, and also before any other filters in the low-level input stack, which for a game would be unheard of, expensive, unnecessary, and stupid.

I see, the more you know! But, weirdly enough I gave it a try again on Ironsight, I even went as far as reinstalling the game and stuff, making sure I did the calculations right, and yet again it just refused to acknowledge the changes made by rawaccel. Just to be safe and make sure rawaccel was working properly, I tested it on COD IW right after I tested it on Ironsight, and it had zero problems, my sensitivity was pinpoint accurate.

This is just weird at this point.

As a sanity check, I just tried rawaccel in Ironsight and it works fine.

My guess is your settings are quite subtle and / or the fact that Ironsight has incredibly low input latency and feels highly responsive compared to other games is making you feel like your settings are not applied, or perhaps you literally did not apply the settings in error.

if you set the sens multiplier to something crazy like 0.01 or 10 and hit apply, you will see.

Thanks for the help! It seems like the culprit of my problems was sensitivity matcher (I know it isn't perfect/doesn't really work in certain games, now more than ever I guess), even at 0.01 it does a perfect 360 when that shouldn't be the case. 

I see, yes, sensitivity matcher sends synthetic mouse events in user space, so these would not go through the Rawaccel driver.

For all intents and purposes, you should imagine Rawaccel exists along the cable from your mouse to the PC.