DPI Wizard

Updated with instructions on how to enable the console.

It had some serious acceleration issues when I first tested it, but will try again now.

For games that support raw mouse input, the WPS field is disabled. If L4D2 supports raw mouse input, I must have missed it, and should update it. If they are marked as "affected by WPS" that means that they do not have the option to use raw mouse input. But games do get updates all the time, so this may change over time. Anyway, the default value is 6 (this is 1:1, effectively the same as raw mouse input)

This is high up on my priority list!

Added to upcoming list. Added to upcoming list. Will look into it. I should be able to add HL1 pretty soon Added to upcoming list. Added!

Gib with precision! View full update

Just added! Be sure to check the notes on how to adjust the sensitivity. View full update

Quake 4 is unaffected by FOV I think, even though they are based on the same engine. But let me re-check that...

Just added! Will look at the BFG version later and Doom 1 and 2, but I think it's the same for Doom 3. Pretty standard sensitivity

Just took a look at it, and in its current state the sensitivity is only written to the registry in a very complex hexadecimal format, and there's no value in-game, or even the possibility to adjust it in accurate steps with the arrow keys. So unless they update it, it can't be added

Yes, you need to cancel it on Paypal. I have re-enabled your sub, and refunded your last payment for your troubles

That's dependent on the mouse software. Logitech Gaming Software will switch back and forth between DPI's depending on the program/game you have in focus. But for any given game you have a "magic" sensitivity that equals to the dekstop sensitivity for a given FOV, assuming you use the same DPI in game and in Windows. So 400 DPI in-game and in Windows and 8000 DPI in-game and in Windows will give you the same result.

Correct, as long as you have the same DPI on desktop and in the game, the sensitivity stays the same. If you start using different DPI's (e.g. 400 in Windows and 800 in-game) and/or changing FOV, things will change.

That's a personal preference really, some prefer a constant 360 distance, others a constant on-screen (!) distance. But if you do the desktop conversion, you need to convert all games from desktop with correct FOV, and not convert from one game.

It might seem weird at first glance, but it actually makes sense. When you convert between games, it is the 360 degree rotation that is matched, regardless of FOV. When calculating desktop to game sensitivity, FOV plays a big factor. Default FOV for CS:GO is (in 16:9) 106.26, default for Dying Light is 81.86. So the 360 rotation will be quite different since the FOV is different, but the movement to aim at an object at the edge of the screen is the same. I'll add some graphics later to better explain it!

Yes, just do like this (you need to enable Advanced Mode): Streched don't affect it

2.5156 is correct, let me break it down: 2.5156 = 6505 counts for a 360 degree rotation 2.7128 = 6032 counts With 1920x1080 the displayed FOV is 106.26 degrees. Counts to turn 106.26 degrees: 6505/360*106.26 = 1920.05917 (desktop width) 6032/360*106.26 = 1780.44533 (too short) With games like CS:GO you need the aspect ratio (both horizontal and vertical resolution) to calculate the real FOV and desktop sensitivity.

In theory yes, with 6/11 is should still be accurate. But with raw input disabled and 6/11 Windows can in some cases mess with the mouse signal and make it wrong compared to the calculator.

I removed the "old" BF4 entry since it was outdated and replaced by BF4 USA, but didn't consider the consequence. I have done what you suggested, hipfire and vehicle are now non-premium

Vehicle = on foot actually

I found a clever workaround, see if it works like intended for you now

OK, so I have identified the problem. Every time you change something in the calculator, there is a script running updating all the calculations. So when you click the resolution field and enter "1920" that's six requests alone, one when you click the field, four when entering the digits, and one when clicking out of the field. I made the calculator this way to feel "alive". The problem is that when this happens too often (30-50 times within a minute), the server returns an error code instead of the calculations. This is a protection on the hosting environment I can not do anything with unfortunately. So I think the solution will be to make a "Calculate" button instead of everything being calculated all the time.

Yes, if they come with an update to support sensitivity in the config file, you will be able to set values below 0, i.e. negative numbers. Yes, will try to add it tomorrow.