![]() ![]() However, that would be rather unintuitive, so I feel it’s more likely than not, to be a 1:1 conversion. In other words, 1.5 might not necessarily translate to an actual multiplication of exactly 1.5. I want to re-iterate that I am NOT sure what the EXACT conversion formula being applied is, so it might not be a 1:1 conversion. However, if I remember correctly, this option essentially multiplied the DPI your mouse is set to.įor example, if you have DPI in Quake Live's menu set to "1.5" and your mouse's DPI set to "800", then you'd essentially be using 1200 DPI.Īgain, I'm not absolutely 100% certain I am fully correct when it comes to this option, but I believe this is the case. It’s been a while since I converted my own sensitivity, so I am not 100% certain about the exact percentages and calculation formulas, so I cannot provide those details right now. And if you don't want to re-learn, then you'd want the option to be left un-checked. HOWEVER, if you are used to the older method where different break-points start applying different acceleration curves, then this will take getting used to. It will still feel different to hipfire at varying distances, but THE CURVE of acceleration is a single speed in terms of how fast it ramps up.Īs such, focal length scaling is much better for building muscle memory. When focal length scaling application is applied (aka, the box in the menu is "ticked", and the option is being used), there is a smooth single acceleration CURVE being applied. ![]() Personally, it’s probably worth adjusting to, but if I recall correctly, Quake Live's method of calculating and adjusting scoped speed is on a somewhat arbitrary (and staggered) series of "break-points" where different acceleration curves kick in. If you are having trouble getting scoped/zoom aim to feel correct, then you may need have this box UNCHECKED. You can still adjust pitch and yaw in Quake Champions, if need be. This is what your Quake Live config should show (if you were using the correct settings). Whole numbers can still feel fairly different (and you can’t be absolutely certain they will round in the direction that works better for you).Įven if sensitivity and DPI are the same, if you weren't already using 0.022 pitch and yaw in Quake Live, then even the sensitivity will still result in a completely cm/360. If you do need to use these, its far better if you can find a calculator that gives you an answer to AT LEAST 1 decimal place. If you need to do so, there are FOV calculator out there that are easy to find and convert with. Using the same FOV as you use in Quake Live will equate to a COMPLETELY DIFFERENT field of view in Quake Champions. In Quake Live was calculated using VERTICAL degrees (aka, vDEG / vFOV), but in Quake Champions they calculate it using HORIZONTAL degrees (aka, hDEG / hFOV) KEY NOTES about the above categories (aka, sneaky differences that may be the issue): Mouse acceleration (if you use any, otherwise make sure its set to 0)Īnd, finally, the option you referred to earlier, which Quake Live has, but Quake Champions DOESN'T:ĭPI (which should show up in the config as -> seta m_cpi "0") Sensitivity isn't the only thing that affects how mouse speed will feel.Ĭheck to make sure ALL of these are the same as Quake Live (or as close as you can get them): Let me know if you sort everything out! :) Hey dude, I just wrote up this beast of a guide for you. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |