Are you using mouse acceleration settings in Reflex or QL and want to get the same feeling in the other game or driver? Do you want to take your driver settings and use them in a game where the computer doesn't have the driver installed? I can help (if QL is involved, I'm assuming cl_mouseaccelstyle 1). First, here's a table of the equivalent options/commands between the driver, Quake Live, and Reflex:
| Driver | Quake Live | Reflex |
| Sensitivity | sensitivity | m_speed |
| Acceleration | cl_mouseaccel | m_advanced_acceleration |
| Sensitivity Cap | cl_mousesenscap | m_advanced_sensitivity_cap |
| Offset | cl_mouseacceloffset | m_advanced_offset |
| Power | cl_mouseaccelpower | m_advanced_power |
| Post-Scale X | m_yaw | m_advanced_postscale_x |
| Post-Scale Y | m_pitch | m_advanced_postscale_y |
Use this calculator if you want to convert from Quake Live to Reflex or the driver:
Note: Once you've set post-scale values to work as m_yaw and m_pitch values, you will want to set m_yaw back to 0.022 and m_pitch back to 0.022 or -0.022 (depending on if you use inverted mouse).
Use this calculator if you want to convert from Reflex to Quake Live or the driver:
Use this calculator if you want to convert your driver settings to a specific game:
There are multiple ways to perform these conversions. If you want to do any math yourself, keep in mind that sensitivity is multiplied in before the acceleration, offset, and sensitivity cap calculations are performed, whereas post-scale values are multiplied in after.
Nice guide, I was going to do something similar to a friend of mine who wants to test out the good kind of acceleration. For example, I have a 12K DPI mouse but I use post-scale to lower the output DPI to something comfortable, like 800 DPI. This allows me to retain the higher rate and the lower sensitivity. I then use mouse-sensitivity.com to find my baseline sensitiviy using Reflex. For example, if I want 100 cm/360 then I input Reflex as the game, 800 as the DPI and then try out different sensitivity values until I find something close or equal to 100 cm/360. In this case, using a resolution of 2560 x 1440, the sensitivity I need to enter in Reflex is "1.994916".
ReplyDeleteI find this process to be the easiest but of course, converting the sensitivity in Reflex to another game is never easy since many games don't go low or high enough on the sensitivity scale. That sucks, but I believe it can be remedied by changing the post-scale and DPI around until you find something that is supported by the game, I.E a sensitivity that is not too high or too low.
Still though, keep up the great work!
sorry dont know where to put this but is there an alternative to mouse-sensitivity? it seems they require you to subscribe and pay in order to calculate newer games.
ReplyDeleteHrm, that's kind of lame. I didn't know they did that sort of thing since no game I'd ever looked up had an issue :<. I'd probably just get the ruler out and measure with my offset set to 1000 (so that my sensitivity is flatly on the "slow" speed) in a familiar game then tweak my settings for whatever game I'd be switching to.
Deleteyeah, i was going to buy rainbow six siege and have some fun with it but given it's an fps i demand a proper sensitivity. so i went to mouse-sensitivity and apparently i had to be a premium member/subscribe in order to get access to that game. i believe they do so with newer games.
Deleteso the only way is to do it old-school, with a ruler? wouldn't temporarily turning off acceleration (setting it to 0) work as well as setting the offset to 1000?
There might be a better way, but I don't know of any. Turning off accel has the same effect, so your choice.
DeleteTrue. But I just went ahead and spent $30 on a lifetime premium membership. I don't think it's worth it considering the few competitive FPS games I play, but I'd rather do this than whip out my ruler and spend several hours perfecting the sensitivity.
DeleteThis isn't entirely related to this post but what is you opinion on using offset? I am used to fairly low sens from CS with no acceleration and am currently using an offset of 15 then an accel of .04 (3200 DPI/1000HZ/.1 Post Scale) with a sensitivity cap of 3.6. This causes the mouse to stop accelerating around a speed of 80 and starts accelerating at 15. This feels comfortable right now but do you think it would be worth learning a smaller offset or no offset?
ReplyDeleteOn a separate note, I can't seem to get the profile hotkey switch to work. I attempted to use a trigger of !{PGUP} and !{PGDN} to switch between high sens for my touchpad and lower for my mouse on my laptop but it doesn't seem to work. Removing the ! marks works though.
I don't like offset much - I find that when you are making small tweaks to your accel curve, an offset makes it harder to adjust to the changes.
DeleteFor the hotkeys, I just tried !{PGUP} and !{PGDN}, and alt-pageup and alt-pagedown are changing profiles for me when I release the keys (with any modifier held down, it has to wait until you release it before changes are made). Maybe your laptop is overriding alt+ those keys somehow and not sending them to the OS?
Ok, I'll try getting used to no offset, do you think it would be better to reduce the acceleration or reduce the overall sensitivity. I want to keep the starting sens about the same as before and keep the max sens about the same as before removing the offset.
DeleteRight now I'm leaning towards reducing the acceleration as I am still learning mouse accel and I think a slightly lower accel will be more reliable overall.
Thank you for your passion towards this project! I wish you luck getting this officially approved for more anticheats, people like you are what makes communities better as a whole!
...not sure why my first reply didn't show up with my name. lol
DeleteBlogspot seems wonky at times, but it gets the job done (generally).
DeleteAnyway, reducing your accel isn't a bad idea - a sens cap of 3.6 seems like it's a fairly aggressive curve. I use a cap of 2, but then again, I stick to games where I only need accuracy at a distance with 20 inches/360 at my lowest point.
Yeah, I actually increased my cap to 4 with a decreased accel curve. It tops out around .4 effective sens at a speed of about 110. And the lowest sens is around .15. This is very comfortable for me, I don't have a problem moving mouse at about 140 speed according to the driver, probably due to being used to 40-60cm/360 that I'm used to. This is with 3200 dpi and 1000hz
DeleteThanks for the help!
I'm just trying to understand, so please don't think I'm trying to correct you or something.
ReplyDeleteBut for conversion from Quake to driver, why does acceleration value vary with respect to sensitivity? Shouldn't acceleration be a static value?
Thanks for your work!
Changing your sensitivity in QuakeLive does actually affect the acceleration there too. The three variables that are relative to sensitivity are acceleration, offset, and sensitivity cap.
DeleteIn quake no matter how hard I flick, it has a snap and stops about 180 each time for about a 3 inch flick. I cannot for the life of me get this to work in a similar fashion for overwatch. Plugging in my exact quake settings into the driver gives me some wonkey accelerations. Not sure whats up
ReplyDeleteIt seems adding a speed cap gives me the functiationality Im looking for, but my quake settings dont have it. Odd
DeleteSpeed cap is kind of a gimmick - it probably shouldn't be used. Sensitivity cap is definitely a good and useful setting though.
DeleteAs for the settings you had in Quake, were you using default m_pitch/m_yaw? And when you take your settings from QL to the driver, then to Overwatch, you need to take your Quake sens and multiply by 10/3.
This comment has been removed by the author.
DeleteIts tough to get an accurate sense because my quakelive sense is 2.39, and my post y scale in quake is .0135 while post x scale is .012. So I basically with my myaw/pitch divided 2.39 by 2 and did kinda the same thing. SO right now the best "feel" for overwatch is 6 sens with a 6 speed cap to give that nice 180 snap with mouse accel. Not sure I'm happy with the quake config for overwatch though. Needs a little more testing. I appreciate this tool though. Not like blizzard is going to add mouseaccel anytime soon.
DeleteWhat the difference between mouseaccelstyle 1 and 2 in QuakeLive?
ReplyDeletehttps://pastebin.com/TK4FCyu6 explains what it used to be, **but it was removed**. instead power/offset etc were made too work with the original settup.
Deletewhat about changing from 400dpi to 800 dpi does it affect the accel?
ReplyDeleteIf you will downscale then no but you will have profit from higher dpi
Deletei never know the use of adobe shadow until i saw this post. thank you for this! this is very helpful. Best Gaming Motherboard 2019:10 Hand-Picked
ReplyDeleteCan someone explain how to convert acceleration from quake champions ( for example 0.17) to the driver? Thanks guys
ReplyDeleteI try to understand too, because current settings is not working in the same way. QC and RAW Accel params is different.
DeleteDo you have the formulas for Quake Live params to avoid how it's calculating in code (their logic in code I mean)?
ReplyDeleteFor all params like a:
Sensitivity - sensitivity
Acceleration - cl_mouseaccel
Sensitivity Cap - cl_mousesenscap
Offset - cl_mouseacceloffset
Power - cl_mouseaccelpower
Post-Scale X - m_yaw
Post-Scale Y - m_pitch
And how it calculates in Quake Champions in the same way or with some different formulas?
Thanks!
Any answers?
Deletewhenever I enter Valorant angle snapping just stops working
ReplyDelete