Search the Community

if im not wrong this should give the same 360, 180, 90 , 45 distances and everything in between for hipfire conversion (instead of just regular 360 matching) and same monitor distance matching of hipfire at all zoom levels for both horizontal and vertical so i was trying to convert my valorant sens (.569 800dpi) to cs2, instead of sticking to one mdh % i wanted all of them at different mouse accelerations i ran a code for all the mdh %s for converting the sens from and it spewed all these numbers out, they look alright to me now i had to convert it to counts of the mouse, my monitor is 1366 pixels width so 100% mdh is at 683th pixel from the center or something at 1 sensitivity of cs2 at 800 dpi, on my 1366x768 pixel monitor, the mouse speed is 0.1966 pixels/count so 683/0.1966 pixels= 3474.05900305 counts or around 3474 counts of the mouse to move at the 100% mdh this is the kind of curve i get for it now the only problem is this is a counts vs sensitivity graph but i need to make it into counts/ms vs sensitivity? do i just assume i can move 3474 counts of the mouse in 50ms? 100ms? how do you even measure that lol, scaling is the only issue now it looked like it took 300ms for me flick 100%mdh so i just went with that For vertical 768/2= 384, 384/0.1966 = 1953.20447609 counts personally it feels like it worked So is the math mathing? Is something like this done already i have no idea nothing comes up on search

Hello everyone. I want to share my findings and observations after a long study and testing. I will not try to transfer everything from my head to the text - it is corny it is difficult. But I can try to answer the questions you may have. My learning path began with a professional overwatch player "EFFECT". Who trained a lot and already had a set of settings in osu (2D) and overwatch (3D). It is not known where he got the settings, but it is known that he changed them and looked for similarities, most likely empirically. Even I managed to easily transfer from osu to hipfire overwatch. It remained to figure out how to transfer to ADS and Scope. He just needed to train and slowly achieve accuracy. Recently I read the threads on the forum and was surprised that I am the same person as others, who was looking for an answer, what to choose when converting and what numbers to write. People who understand how formulas work, which is the most appropriate, say 0% or 100% (start with these) You cannot aim without eyes. You shoot with your eyes, the eyes transmit information to the brain, the brain decides to move the mouse - to press the button. You need to train the motor skills of the hands, eyes, body, etc. But when you play games, at first you adapt, the discomfort is removed. After that, you already find yourself on an empty field, because the adaptation stage will pass, and you need to create something that will develop you. There are several rules that I will highlight at once. In mathematics, there are no wrong numbers. The calculator gives the correct values anyway. These numbers in the answers are simply at odds with your habits. You always need to create settings for yourself: sensitivity, FoV, hand position, type of mouse grip, etc. There is no magic pill that will help you from 2D to become effective in 3D. Hipfire is no different from ADS, Scope, etc. These are the same numbers, the same movements in the game. They also need to be trained separately as Hipfire. To train them, you need to get to know them. The topic is extensive and I might miss something. But the first rules that come to mind are enough. When I use the standard conversion scheme of 0% or 100%. My cursor will feel slow in 2D and fast in game. But in the game there is a displacement along the sphere, and in 2d along the plane. How to train such different movements? I went further, and started increasing the %MDV to FoV, thereby starting to decrease the monitor in the monitor (if I can put it that way) https://www.mouse-sensitivity.com/?share=6bbebf26c14ce140e9782268b252c306 Having achieved some similarities in the movements and range of work of the eyes, brain, hand. I understood what had happened. Having a different focal length from the monitor to the eyes. The eyes will work in different ways. I play in osu and track each note in different positions on the monitor with my eyes, my eyes learn to move quickly and focus on a specific point on the monitor. Next stage What grip to use and what part of the hand to use when moving. I will not disassemble other types of grips, as having a 20-21 cm long and 10-11 cm wide palm, I am not able to use the correct palm grip and claw grip. I began to study. What are the types of mouse grip, there is a lot of information, but in short, AS IT IS COMFORTABLE FOR YOU AND KEEP. This approach did not suit me. And I began to disassemble in detail the grip of the fingertip / fingers. After studying and testing, I decided to use a similar grip like that of a professional player. Now, having knowledge, you need to apply them. I have a training ground and this is Osu! It can train hand / finger motor skills, eyes, finger grip. Trying to put it all together! Eyes move and focus on different positions on the monitor. Finger movements are synchronized with your eyes, then where you want to move the cursor. Fingers range of motion appears в 2D, now you need to transfer this range to 3d. Here AimHero enters the ring with its convenient field size. The principle is the same, now the eyes are being trained in the 3D sphere, more precisely, it is the same 2D monitor, but the sensations from the movements are now 3D. The eyes also move to the same positions on the monitor as in osu. But the effective distance is changed by the field. Now about the distance of flick and / or fingers tracking. What is the point of these trainings if the aiming style is not created? I created mine and it is an example. Grip - fingers. The fulcrum on the table is the forearm. The wrist is not in contact with the mousepad. The elbow hangs. Flick (diagonal) - fingers. Flick (horizontal) - wrist. Flick (Vertical) - fingers. Horizontal tracking - wrist. Vertical tracking - shoulder. The rest of the movements in 360 (fine-tuning for the working range for the wrist, fingers) on the fulcrum is the forearm. Since there is no more friction between the wrist and the mousepad, movement feels uncertain - it's all a process of adaptation. Now how does the conversion take place not to hipfire, but to ADS, Scope, or, more simply, to a smaller FoV. There are several options, but I'll show you 2. Make a 1-to-1 sense of the pixel speed Viewspeed-Vertical In Osu, the value remains x1.07, in the calculator when calculating with VSV x0.76. These two values are equal. When calculating for different FoV using VSV, the visual speed will always be different, but the muscle memory will hit the target. It all works and has been tested my aim style. The settings may be convenient, but not effective. Mouse grip can be handy, but not efficient. etc. Everything needs to be created for yourself. And not blindly copy from other pro players. Science has not entered this market, so you need to study and create for yourself. I put everything in a heap and did not paint everything down to the pixel. Therefore, I will try to answer for those who will correctly formulate the question.

This is more or less a conceptual question/proposal for those of you who have been working with methods of mouse sensitivity calculations across various in-game FOV's for many years now. Personally, I have tried all of the different conversion methods and coefficients. There are pros and cons to each one for me specifically. That's beside the point. My question for you guys is: Do you think that an ADS multiplier applied to let's say 0% vertical monitor distance would provide more aim consistency than increasing the coefficient to 133% if you find 0% to be a little too slow and do not want to increase your base hipfire sensitivity? That way the increase in "turning speed" is consistent across all FOV's, and is simply applied over the monitor distance calculation? You are not changing the point on the screen at which the matching has been calculated per say. You are simply multiplying all matched values by another number thus increasing each by the exact same amount. For example: 1.06(0% MDV of 1x optic), 1.06(0% MDV of 2x optic), and so on and so forth. Also, if you wanted high magnification optics to be much faster than lower magnification optics, would it not be better to just increase the multiplier rather than the coefficient? For example: 1.33(0% MDV of 6x optic), 1.33(0% MDV of 8x optic), and so on and so forth. The "monitor distance match" more or less remains the same. The way I see it, all you're doing is increasing the speed at which the center of the screen reaches that point without effecting that underlying monitor match consistency across all FOV's, but I could be entirely wrong about that. This is the approach to ADS sensitivity that I've found works best for me. When I try to increase the monitor distance match to increase speed, my aim across all FOV's feels way off. They all feel way too fast. Rather than adjusting my monitor distance with each game, I just change the multiplier until it all feels right, and my tracking/flicking is as accurate as possible. For example, on Modern Warfare/Warzone, I use 133% MDV match with a 1.06 multiplier on the low zoom optics, and a 1.33 multiplier on the higher zoom optics. On Apex Legends, I am currently using 133% MDV match with a 1.03 multiplier across all optics, though I have also used 1.06 on low and 1.33 on high magnification in the past. Again, I am just curious to know what you guys think about this.

Hello.I want to convert the sensitivity used by Kovaak into MW COD.Please check to see if my conversion method is correct.Kovaak/800 dpi/Fov100/1.25sensYou want to change to Cod sensitivity.Here are some questions.1. I think it is best to set COD Fov value to 115 that is the most similar. Is it right?2. Hipfire sensor is a 360cm or mdv problem If Fov were exactly the same, it would be the same.To make the most of my muscle memory,Is it best to use Mdv?3. For Cod, it seems to recommend sensor2 as 1.33. For Mdv or mdh, use 0% value, but is it also correct that mdv takes full advantage of my muscle memory?4. One of the COD options is when to convert ADS sensitivity. Is it better to set it to Immediate?5. Which option is best for REGACY OR RELATIVE?