cincinnatus

If I've been playing with stretched 1280x960 and going to native 1920x1080, what's the best way to get the same sens? I'm mainly concerned with horizontal feel, since csgo is largely left/right aim. I see people say if you use stretched resolution you should make m_yaw 0.0165. Does that mean stretched makes horizontal aim feel 1.33x faster? So should i just multiply my sens by that? Or should I be using something like horizontal viewspeed or monitor match?

Sorry, I'm very confused. You say indefinite integral but then say it has limits - is that just a typo? The inverse of which function? Do you need to find the inverse of f(x) and then integrate with those limits or are you trying to find the indefinite integral and then find the inverse of that function? Or are you just trying to find the definite integral, and then do 1/result? This seems to contradict what you were saying in the first quote. Are you just trying to integrate ((tan(c) tan^(-1)(x tan(C)))/(x^2 tan^2(c) + 1) - (tan(C) tan^(-1)(x tan(c)))/(x^2 tan^2(C) + 1))/tan^(-1)(x tan(C))^2 ? Is that result from the mean value theory? Doesn't make sense to me, you still have x in the result. Also doesn't make sense if that's not from MVT and it's from taking the derivative directly - for one, doesn't look like the correct derivative, and secondly, in that case integrating wouldn't accomplish anything - it would just return the original function and you seem to want to integrate the result. Wouldn't you just set the MVT result equal to the derivative of f(x), and solve for x? In which case, what and why are you integrating? Is the final goal to get f(c) once you get c? As in, just plug c in for x in h(x) from the geogebra page? Would like to try to help with the calculations and I've put most of your equations into mathcad, but I'm totally lost as to what you're trying to do.

I had it on factory default, i tried custom surface tuning and it didn't fix the issue. I'm using QCK heavy.

Thanks for the replies, these mouse feet were supposed to be the same original thickness - .66mm, so it seems like they should be fine. The sens never changed on the original mouse feet from it being brand new to scraping against the mousepad. But these made quite a drastic change. If it's just a change in dpi I guess that's fine I can just compensate, the thing about sensor not detecting all movements worries me though.

so should i just increase sens to compensate?

I just changed the mouse feet on g403, is there any reason this would result in a different sens? With the old mouse feet, a swipe from one end of mousepad to other always landed at the same point in game. Now doing the same swipe moves the crosshair significantly less, to get to the same point I have to change the sens from 1.55 to ~1.64 at 800 dpi. Tried re-tuning and it didn't do anything. I checked with mouse sensitivity exporter and all the points on that line up exactly as before, but when I physically move the mouse it's different. I also tried to clean the dust off my sensor lightly with an alcohol swab, could I have damaged the sensor doing this?

I use this bind mouse2 "+attack2;hipsens" bind mouse4 "+zoom;zoomsens" alias hipsens "sensitivity 1.55" alias zoomsens "sensitivity 1.3086464" You don't really need all those aliases, but I was testing a bunch of different scaling methods like this: alias zoom0 "alias zoomsens sensitivity 1.26934615" alias zoom12 "alias zoomsens sensitivity 1.86" alias zoomv2 "alias zoomsens sensitivity 1.53067615" alias zoom25 "alias zoomsens sensitivity 1.3086464" I'm fairly sure the fov of the zoom is the same as first zoom in csgo.

Thanks, that worked

Just started playing pubg again, and I did what you said and still have the same issue. I used 360 for hip fire. In csgo I use 0% MM for scope, tried it with pubg scopes and it's very slow. I tried it at 75% match and both viewspeed 1 & 2. All of these still feel way too slow. 0% MM using 2x scope I get a sens of 0.008464 using this calculator. Viewspeed 2 gave 0.010311. A different online calculator gave 0.013314 for 0% MM. Not sure if the latter feels quite right, but it feels much closer to being correct. Not sure what it's doing differently. Anything else I can try or something I might be doing wrong?

So this is probably a noob question, but does changing from a 4:3 with black bars resolution to a 16:9 resolution affect sensitivity? I understand that if the 4:3 res is stretched it will feel different, but what if it's not stretched? I get that that the 360 sens is the same, but the horizontal FOV is changing, so that would change how it feels, right? If so, what would be the correct way to convert sens? Say my sens is 1.25 on 800x600 with black bars, and I want to go to 16:9. Does using 0% MM, like I use for scoping, make any sense?

Idk if I'm doing something wrong, but the calculator seems very wrong converting from csgo to pubg. The sens in pubg feels much slower. Another site gave 0.012375, which feels right. I would just use that, but it doesn't have scope calculations. Am I doing something wrong or is this calculator not right?

Yeah, it was the Enchanced Mouse Input V2 that was causing the problem. Calculator works perfect now with it off, thanks

I tried converting my csgo sens (1.56 @ 400 dpi) to Ratz, and it says I should put in 0.69, which is way too slow. I tried a few different csgo sensitivities, converted to Ratz, and each time it was way too slow. I was judging how far I had to move the mouse for a 360 by eye, as I didn't have a ruler, but it was clearly very off. It looked like the actual sens for Ratz should've been somewhere around 0.895.