Geahad

I've found out what's wrong: If you set the in-game setting "capped fps" (v-sync, basically), the mouse sensitivity shoots through the roof. The same happens if you cap the fps via, say, RTSS. If you leave that setting (framerate cap) unchecked, the sensitivity is as your calculator says. Hope this helps!

It's about 1,2x more sensitive. Not sure why that is. It's probably something on my end. Please disregard this post then. Sorry to have bothered You. Cheers!

Hello! Just wanted to inform about the fact that the current version of the calculator is not precise regarding converting sensitivity to this game. For instance, i used OW for my "from", set all required parameters (hipfire, sens 3, dpi 1600) and got a value of 20 that needs to be set in-game in PW. That sensitivity, at that same 1600 dpi, is nowhere near the same 28,86 cm/360. Perhaps recent patches have modified those sens values?

@DPI Wizard Thank you!

Thank you! So, if I understood correctly... I select OW in the "convert" section of the calculator, select Widow/ana under the "aim" drop-down, enter the value, and then I select again OW in the "convert to" portion of the calculator and select Ashe in the "aim" drop down? I get 40.85 for Ashe ads when converting from widow/ana 30 ads. Is that correct?

@DPI Wizard: now THAT was quick! You're really something!

Judging by how much I'm missing with Ashe's default ads of 60 while quickscoping compared to Ana, it's definitely off, probably somewhere in between 30 for Ana/Widow and that new 60. Agree with JanSteveRein, Ramses and Jeps: a separate category in the calculator that is specific to Ashe would be great! Otherwise, a quick formula to tide us over before it's integrated into the calculator would be the same.