Leaderboard

I plan to add a auto-generated Logitech LUA script you can download for each calculation to confirm they are correct. Makes it a lot easier to verify the calculations and to pinpoint if an error is in the calculator or locally on the users computer.

Convert using monitor match % set to height / width * 100. In Logitech Gaming Software, set it to the game profile mode. Createa profile for Warhammer, tick the box to import default settings. Right-clickthe profile, click scripting. Import mousemove.lua. change the values for resolution, CPI, and wps. Run the game and look at something with a flat top, look down so it lines up with the top of your screen. Clickthe scroll wheel, it should look up. If you have the correct sensitivity, whatever was at the top of the screen will now be under your crosshair. Thiswill confirm that mouse-sensitivity.com's calculator is correct and then you can convert using any method you want.

You could also convert Windows to Warhammer with the monitor match percentage set to: vertical_pixels / horizontal_pixels * 100 Then use a script to send this many y-axis mouse counts: vertical_pixels / 2 * wps Play the game, line up something at the exact top of the screen, and run the script. If the sensitivity is correct in the calculator, then it will rotate to the object that you lined up. Attached is my lua script for Logitech Gaming Software. MouseMove.lua

Cheers, you just made it very easy to test different formula. Tested with 25-165 FOV, 140 increments, 5-15 second zoom durations. Viewspeed v2 actually felt the best tbh. The zoom transition feels a little weird but I think that is just because it is scaling by incrementing the fov value rather than the actual zoom factor, so the zoom transition speed quickly slows down, which can throw off the perceived sensitivity scaling. I attached an edit of the script that I used to quickly test different formula. It will generate from the desktop sensitivity. Install Python 3.65, download this script, right-click the script and click edit with IDLE, add/remove the comments '#' before the newSens variables to change what formula the script will use. creator.py

For your python script, you don't necessarily need a mouse-sensitivity.com subscription. You could do the math yourself to generate all the sensitivity values. This should be enough to get you started. Should convert a CSGO sensitivity for the default FOV to a sensitivity value for any other FOV using the monitor match method. (90 / output_fov) * inputs.sensitivity * conversionMethod Here are various values for conversionMethod. It's in lua. Monitor match, using a percentage of the horizontal math.atan(((inputs.percentage / 100) * (inputs.resolutionWidth / inputs.resolutionHeight)) * math.tan((math.pi * (360 * math.atan(3/4 * math.tan((math.pi * output_fov)/360)))/math.pi) / 360)) / math.atan(((inputs.percentage / 100) * (inputs.resolutionWidth / inputs.resolutionHeight)) * math.tan((math.pi * (360 * math.atan(3/4 * math.tan((math.pi * 90)/360)))/math.pi) / 360)) Monitor match, using a coefficient of the vertical like Battlefield Uniform Soldier Aiming math.atan(inputs.coefficient * math.tan((math.pi * (360 * math.atan(3/4 * math.tan((math.pi * output_fov)/360)))/math.pi) / 360)) / math.atan(inputs.coefficient * math.tan((math.pi * (360 * math.atan(3/4 * math.tan((math.pi * 90)/360)))/math.pi) / 360)) Zoom ratio. Same as 0% monitor match. math.tan((math.pi * (360 * math.atan(3/4 * math.tan((math.pi * output_fov)/360)))/math.pi) / 360) / math.tan((math.pi * (360 * math.atan(3/4 * math.tan((math.pi * 90)/360)))/math.pi) / 360) Using 0 coefficient or percentage will return an error, so you need an if/else statement to use the zoom ratio code instead. Probably best to avoid the reliance on mouse-sensitivity.com's calculator as any new proposed formula that needs testing will not be on the calculator. Here is an example of the sensitivity conversion in Wolfram Alpha, using 3 sensitivity, 56.25% monitor match, 1920x1080, and converting to 40 4:3 HFOV. (90/40) * 3 * (ArcTan[((56.25/100) (1920/1080)) Tan[(Pi ((360 ArcTan[(3/4) Tan[(Pi 40)/360]])/Pi))/360]] / ArcTan[((56.25/100) (1920/1080)) Tan[(Pi ((360 ArcTan[(3/4) Tan[(Pi 90)/360]])/Pi))/360]])

I've attached a cue profile with the macro for executing the scripts, the toggle is the END key, place the files in the cfg file, exec the fov<min>+<max>.cfg, and press end with this cue profile and you should see it start to work FOVTestingCorsair.cueprofile You would have to change the number of times the 1 key is pressed on either side of the 2, as we can't do any pre-processing, but that's just a copy pasting exercise, it's setup by default for the FOV range 15-100 which from my testing seems adequate. Note that there is a 'remove all delays' button if you're having trouble with the delay blocks.

I have created a python script to create the files for the cs fov testing @Drimzi made with his lua script here : https://github.com/Skidushe/sens-fov-scalar It should allow us to test the different monitor distance ratios efficiently rather than copy pasting. You should be able to put the python file inside the cfg folder and then run from there if you want to do it that way too.

If you want to test the perceived movement speed of the crosshair at different FOVs for different formulas, I have attached a script for Logitech Gaming Software (LGS) to use in CS:GO. The script essentially makes the game zoom in and out. It presses 1 repeatedly, which will be bound ingame to change FOV, and then presses 2 or 3 to change the zoom direction. Someone can create a more accessible format that doesn't depend on LGS if they wish. To get this to work, you first need to define how large the zoom spread is by creating a config file to bind 2 and 3 to the lowest and highest zoom levels. Example: fovscale30+77.cfg bind 2 "exec up_30" bind 3 "exec down_107" Then in the LGS script specify how many times 1 needs to be pressed before changing direction. This is the variable 'fovIncrements'. After, you need to create 2 config files for every FOV. These config files will change the FOV, the sensitivity, and rebind 1 to execute the next FOV config file. An example looks like this: up_90.cfg fov_cs_debug 90 sensitivity 0.3879408422332074 bind 1 "exec up_91" down_90.cfg fov_cs_debug 90 sensitivity 0.3879408422332074 bind 1 "exec down_89" Once all the config files are created, and you have created a game profile for CS:GO in LGS and imported the attached script, play CS:GO on a workshop map and execute the cfg that binds 2 and 3. Then enable 'Scroll Lock' on your keyboard and click your middle mouse button. The script should activate. The script will press 1 repeatedly, executing the down cfg files until 2 is pressed, and then execute all the up cfg files until 3 is pressed, and the cycle will continue. The game will zoom in and out seamlessly and you will be able to test how the sensitivity formula feels as it progresses through the FOVs. Alternatively, you can press one of the side buttons on your mouse, it will change FOV every x number of left clicks. Example of the script in action: The main problem with this method is that the zooming rate is going to be completely wrong since it scales linearly through the FOV values and not the actual zoom amount. As many are aware, the zoom ratio does not scale linearly when using basic multiplication / division on the FOV values. 179 vs 179.999 is a 1000x zoom, and 10 vs 20 is a 2x zoom for example. This very inconsistent zoom scaling may skew the results and make more bias towards certain match percentages. drimzi-fov-changer.lua