This applies to ALL sensitivity settings, even those taken at random. I could get used to the settings xkullx uses, even though they are about 30x slower than mine. I've tried (but I still don't understand why he plays like this, with his 70cm mouse pad and all).Kerr Cameron said:Hobonicus, I'm glad you tried it. Once you get used to it, and that takes only a couple of hours or less, you will find it better.
This is a video of me playing BF2 at 60FPS, which is so slow that the game doesn't register hits any more. The game is basically unplayable at any less than 120FPS. This does not have to do with sensitivity, this has to do with update frequency. The game is just running too slowly when running at 60FPS. I want to see you make a video where you play faster than the game can respond, THEN we can talk about the optimal aim formula.
But I'll try it anyway. Here we go:
The number 8.000 isn't used anywhere... Give a worked example please?Kerr Cameron said:1. Measure the width of your screen. For example, let us use 14 inches.
width of screen = 53.2cm = 20.944in
2. Calculate using Phi what lengths two pieces would have to be to add to give 14 inches and also be in perfect Golden Ratio. For example: 14 multiplied by the reciprocal of Phi is 8.652 inches. Subtract that from 14, so the other piece is 5.348 inches. These are your two ideal 360-degree-turn mouse lengths which we will set to work using Phi as your mouse sensitivity. If you like you can work out a smaller or larger length that is also in Golden Ratio to the screen, but we will use just either of these two.
20.944/phi = 12.944
20.944 - 12.944 = 8.000
3. Determine how fast you want to turn verses how accurate you want to be. The larger of the lengths used to make a 360-degree-turn (that is, dragging the crosshair over 100% of the gaming environment on the X-axis) will require a lower sensitivity than the other, but gives a steadier crosshair than the other, yet both will work effectively.
approx. 4cm for 360º horiz, 3cm for 90º vert. (1.5cm for vert in games with rapid elevation changes, such as 2142.)
4. Select a sequence of numbers in Phi that begins with a number that, if your mouse sensitivity were set to it exactly, would let you do a perfect 360 on dragging the mouse the length you have selected, either of the two.
My mouse sensitivity is a function of my DPI, my pulldown DPI, my windows pointer speed, and my in-game mouse sensitivity. Using default windows mouse sens, no pulldown and 4000 DPI, this translates to an in-game sensitivity of about 0.03 in BF2.
Let's say that this works out to be a 5 for you. You can then use the sequence beginning here: 58683436563, and then put the decimal point after the first five and then keep many digits after, as many as you like and the more the better. . . but we must be sure to round off properly, and this sequence will round to 6. So let us instead use the sequence beginning here: 4989484820. You will need to go back and select different sets of digits to be sure to make the turn be as close to a perfect 360 as possible. Try to get it on the pixel. The trick is to use a large segment from the Golden Ratio whose initial speed will work out to make the proper 360 in the length that is also in Golden Ratio with the size of your view.
5. Now your mouse sensitivity would look like this with many digits of Phi in it:
Be sure to round the last digit in the right direction.
I found the sequence 00281210427621771117778053153171410117. Plugged in to BF2. I can now no longer use the menu properly, because my windows pointer speed is so ridiculously high. In-game aim is also worse than where it started.
You also have no information about the windows pointer speed and various DPI settings on the mouse. You also have no info on the mouse acceleration found in most new FPS games.
I know that in BF2 you're better off with an in-game mouse sensitivity of around 1.0, as this has the least affect on the non-linearity of the acceleration. A higher value works great if you have tweaked the network connection, such that the server-side numbers out-resolve the client numbers, thereby dramatically increasing your hit registration when spraying (random deviation tends to "deviate" to the exact same angle you started, giving two rounds landing in the exact same place!). Sensitivities of <1.0 work better for quick near-far encounter transitions, because it lets you place shots at sub-pixel resolution. The acceleration is least noticeable with a sensitivity of around 2.
This means that there is a trade-off between server-client resolution discrepancy, sub-pixel resolution and acceleration, and to tweak your actual "sensitivity", you use the windows pointer speed and DPI; NOT the in-game settings! Bet you didn't know this!
You need to take ALL these factors into account.