Latent

The calculator for Toxikk is failing to register correct variables. For instance: When converting sensitivity from Toxikk to game X. The calculator outputs: 360° rotation: 0 inches / cm Converting sensitivity from game X to Toxikk ouputs: Sensitivity: Too low sensitivity or too high new DPI 360° rotation: Recommended new max DPI: 0 DPI Produced the same results on different games with Toxikk being the common denominator using low, medium and high DPI in combination with low, medium and high sensitivity.

It may require more effort but perhaps you could implement all available options.

Game: Toxikk Official Site: http://toxikk.com/ Steam: http://store.steampowered.com/app/324810/ Toxikk will be on Steam's Early Access on January, 22. Game Engine: Unreal Engine (possibly UE3 - not confirmed) Update: Steam store link added

Game: Wickland Official Site: http://wicklandgame.com/ Steam: http://store.steampowered.com/app/321260 Game Engine: Unreal Engine 3

Blizzard recently announced their new multiplier shooter game Overwatch. http://www.playoverwatch.com/

Game: Depth Official Site: http://www.depthgame.com/ Steam: http://store.steampowered.com/app/274940/ Game Engine: Unreal Engine 3

Game: Minimum Official Site: http://www.playminimum.com/ Steam: http://store.steampowered.com/app/214190 Game Engine: Unreal Engine 3 Private Match: Open DES01_BASE //Desert Canyon (Titan) Open TER01_BASE //Zen Garden (TDM) Open TER03_BASE //Path of Lanterns (Titan) Open CIT01_BASE //The Event (TDM) Open CIT03_BASE //Disaster Zone (Titan) Open SPA01_BASE //Space Station (TDM) Open IND04_BASE //Titan Factory (Titan) Open JUN03_BASE //Altar of the Ancients (TDM) Open Spec_TestMapTemplate //Completely blank map Open Spec_TDMTestMapTemplate //Completely blank map, enemies falling from sky and die Horde Mode Append: ?Game=MinGameModeDC Eg: Open SPA01_BASE?Game=MinGameModeDC

There are some variables which may influence your calculations. In Strike Vector players have the ability to toggle between different aiming modes called Harrier Free Aim. Switch Fly Mode (toggle Harrier Free Aim): Spacebar Free Aim: Enabled - Greater freedom of crosshair movement (able to extend to the edge of screen). Free Aim: Disabled - Crosshair confined to small zone. Note: Harrier Free Aim: Off - Range of crosshair movement diminishes at higher sensitivity. Change view preferences First Person: F2 Third Person: F3 Precise Aiming (Zoom): Left Ctrl Mouse settings found in UDKInput.ini and UDKStrikeVector.ini UDKInput.ini [Engine.PlayerInput] MouseSensitivity=1.100000 bEnableMouseSmoothing=False UDKStrikeVector.ini [harriergame.HarrierLocalPlayer] _Sensitivity=137 _HarrierFreeMouse=False _MouseSmoothing=False Note: UDKInput.ini - unable to save sensitivity in cfg (reverts changes made to sensitivity). UDKStrikeVector.ini - sensitivity value saved to cfg, no affect in-game. Using SetSensitivity command does not save to any cfg's (one at point was able to save to UDKInput.ini however unable to replicate) MouseSensitivity and _Sensitivity share a relation to sensitivity sliders in-game but obviously have different numerical representations. By default (first game launch) sensitivity settings are: MouseSensitivity=1.100000 _Sensitivity=137 Settings get loaded from DefaultInput.ini and DefaultStrikeVector.ini. However these settings above get automatically replaced with the values below ie player uses any in-game settings eg changing resolution or turning of a feature reverts to different sensitivity Second default settings: MouseSensitivity=1.093726 _Sensitivity=92 (values reset to these using reset button) Might be worth noting: Minimum sensitivity of in-game slider: MouseSensitivity=0.300000 _Sensitivity=0 Maximum sensitivity of in-game slider: MouseSensitivity=2.500000 _Sensitivity=255 ConsoleKey: F1 and Tilde (~)

See existing thread: http://www.mouse-sensitivity.com/forum/topic/171-world-of-tanks/

Some games have more restrictive sensitivity limits than others. The calculator alerts you with this: To compensate for these restrictions you are given a recommended CPI (DPI) setting. In your case: Your original DPI (entered in the first DPI field) stays the same. You'll need to enter the recommended DPI setting in the second DPI field for the calculator to calculate your recommended sensitivity.