brobot6565 Posted August 15, 2021 Posted August 15, 2021 Alright so i have seen a few posts about this already, but the issue still has not been fixed. Whenever I play Minecraft 1.8.9, the senstivity feels and is substancially higher than newer versions such as 1.16 and 1.17 even with the same in game percentage sens and dpi. i believe there was an option for sens conversion between pre/post 1.13(when they changed how the sensitivity worked) but that has been removed. The person who is responding to these complaints about the removal of this feature, keeps saying, "There is no difference between the versions that I can find" and they eventually said "I've tracked down the problem now. If you use version 1.8.1 or lower you need to disable vsync and use a polling rate of 500 Hz or maybe even 250 Hz for the sensitivity to work correctly." But the thing is I'm on 1.8.9, where this glitch or whatever it is is already fixed, but the sensitivity is still different. This may have come off a bit aggressive to the person who I was quoting from and im sorry about that. It would be so amazing if someone help me with this or atleast turned back the option to convert between pre/post 1.13 sensitivty. Thanks!
Wizard Solution DPI Wizard Posted August 15, 2021 Wizard Solution Posted August 15, 2021 This is 100% sure an issue with the game. As stated in the notes, if you experience any difference in later versions, try the same fixes. Minecraft has never changed the actual sensitivity, but have had issues with FPS, vsync, polling rates and conflicts with keyboard input and sensitivity, which this is likely related to also. If you can try a tool like this in both versions you should see that they are exactly the same (granted vsync is off, and expect a few tests to be slightly off due to packet registration issues in the game), any difference you experience is basically down to a bug in the game that is inconsistent and impossible to account for. Also, the difference between the old pre and post 1.13 calculations was just a slightly lower base sensitivity (about 1.3 % lower) that was so insignificant that it was barely measurable. It turned out to be down to packet losses in the old versions, which again doesn't actually change the sensitivity so having it as a separate calculation was wrong. The base is the same, and how the bug is experienced will vary a lot. brobot6565 1
brobot6565 Posted August 15, 2021 Author Posted August 15, 2021 alright so now i know that the calculations u did for the pre/post 1.13 feature is a 1.3x multiplier, i just multiplied my 1.8.9 sensitivity(0.52) by 1.3 to get 0.676, and i used that sensitivity for 1.17 and it felt the same as 1.8.9! So in a way you gave me the answer i was looking for, so thanks!
Wizard DPI Wizard Posted August 15, 2021 Wizard Posted August 15, 2021 7 minutes ago, brobot6565 said: alright so now i know that the calculations u did for the pre/post 1.13 feature is a 1.3x multiplier No, 1.3% not 130%, so a 1.013 multiplier. It sounds like your issue is related to the vsync problems, do you have it off?
Wizard DPI Wizard Posted August 15, 2021 Wizard Posted August 15, 2021 1 minute ago, brobot6565 said: Yes i have vsync off Ok, and what polling rate is your mouse set to?
brobot6565 Posted August 15, 2021 Author Posted August 15, 2021 125, i set it to the lowest i can because if it goes higher my mouse just spazzes out. and by the way, i already have my issue fixed. the 1.3 multiplier(1.8.9 sens x 1.3= same sens for 1.17) maybe you got the pre/post 1.13 option confused and it was actually 1.3 x and not 1.013
Wizard DPI Wizard Posted August 15, 2021 Wizard Posted August 15, 2021 1 minute ago, brobot6565 said: 125, i set it to the lowest i can because if it goes higher my mouse just spazzes out. and by the way, i already have my issue fixed. the 1.3 multiplier(1.8.9 sens x 1.3= same sens for 1.17) maybe you got the pre/post 1.13 option confused and it was actually 1.3 x and not 1.013 No, I'm sure it was the base sensitivity that was 1.3% lower (not the actual sensitivity, it will vary slightly), so it was a tiny difference (I still have the old entry available). Also note that a multiplier doesn't make sense in Minecraft. Let's say your sensitivity is 0%, multiplying that by any number still gives you 0. Just like 0.1 is not half the sensitivity of 0.2, it scales completely different than that. Half of 0.2 is actually 0.08997361. Did you try the sensitivity matcher program?
brobot6565 Posted August 15, 2021 Author Posted August 15, 2021 (edited) alright so i have download the program and launched it but im not a super technical guy and i have no clue what any of this means, and how its a sensitivity matcher. do you want any settings for me to specifically put in? it might be complicated to explain but its fine i dont care how long the explanation is. edit: i found out how to use it but the spin function is not working in minecraft. i am ressing the correct keys. Edited August 16, 2021 by brobot6565 tttt
brobot6565 Posted August 16, 2021 Author Posted August 16, 2021 ok so i figured out the mouse sensitivity matcher and i used it and it worked! i changed my 1.8.9 sens to 59, so now im trying to convert that to 1.17 sens which turned out to 66/66.5/67. does this make sense?
Wizard DPI Wizard Posted August 16, 2021 Wizard Posted August 16, 2021 12 hours ago, brobot6565 said: ok so i figured out the mouse sensitivity matcher and i used it and it worked! i changed my 1.8.9 sens to 59, so now im trying to convert that to 1.17 sens which turned out to 66/66.5/67. does this make sense? If that works for you, stick with it The issue with Minecraft is not consistent, it probably depends on both your settings and hardware.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now