FIne Tuning using Povohat's Accel Driver (With accel turned to zero)

[randomguy7]

first of all, grab this and install it:

https://github.com/KovaaK/InterAccel/releases/tag/1.0

and restart. then, convert your base sensitivity to quake 1 using fov match in 360 degrees. (be sure to change it from 16:9 to 4:3, etc.)

then save that as a preset, by copying the sensitivity and the fov to the first box.

when converting to a game of your choice, match the true fov you use in the game to a second quake 1 choice, making sure to use the hdeg res option, and copy that to your calculator using 360 degrees match. Now, you want to put your game in the first box, and convert the game's closest option to quake's 1.0 sensitivity by looking at the second box this is what you will choose in-game. then subtract the first number you converted to quake sensitivity from the second number you converted to quake sensitivity.

BASICALLY, ALL SENSITIVITIES HAVE TO BE CONVERTED TO QUAKE SENSITIVITY FIRST. THIS IS BECAUSE POVOHAT'S DRIVER FORCES EVERY GAME TO EMULATE QUAKE LIVE'S SENSITIVITY OPTIONS.

by subtracting the ingame value from the wanted value, you will be tricking the game to use the exact amount if you cannot fine-tune.

open the povohat utility. set accel to zero, post scale x/y and pre scale x/y to 1, and set the sensitivity to be the final result of the subtraction. This will scale your input to be the exact sensitivity.

[randomguy7]

you can also keep sensitivity at one and use post scale x instead.

[fortunate reee]

7 hours ago, randomguy7 said:

you can also keep sensitivity at one and use post scale x instead.

this could be viable when set up correctly  be viable

https://docs.google.com/document/d/1wuQln99lQVBU9L8_QbpifrarpJ1xjPuKsKD2FY026Hc/edit#heading=h.lfs62ifyg4km

 

this can work for games that limit the input with their crappy settings but i wouldnt rely on it too much

since it might not perfectly work

 

 

Edited June 13, 2020 by fortunate reee