Erick Avila

There is a config file with the sensitivity, but changing it in the file does not actually change it in the game.

0.7 

Having used a mouse on console for several years in the past my experience is that this is going to be almost impossible. Even the games with the best look mechanics have some form of acceleration built into them on console. Most of them have crazy amounts of acceleration, with crazy curves and oddball deadzones.
 
Call of Duty is considered to have one of the best look mechanics. It's mechanic is almost perfectly linear except for the first 100ms of turning which has acceleration starting low and steadily increasing over 100ms. If all games were like this it may be possible, however the large majority of games have crazy look mechanics.
 
Borderlands for example is reasonably linear up to about 70% of the analogue stick, this allows you to get nice 1:1 below 70% turn speed, but the turn speed is crazy low at <=70%. After 70% the acceleration kicks in, and the turn speed rapidly increases, but not in any form of linear or predictable manner. Unfortunately the large majority of games have their own special, equally crazy and entirely unique implementation.

Fixed it now so it rounds to 6 decimals 

I notice that even past 4 decimals, I instantly noticed a difference. For instance, my current sens is 2.17725, and I instantly notice a difference between 2.1772 and 2.17725. The thing is, I believe that the amount of numbers you can have is actually unlimited, but to an extent, you don't notice a huge difference.
 
I believe you should take off the limitation of decimals to allow any sens to travel over to all games if possible.

Updated with in-game sensitivity.
View full update

Sensitivity is usually not affected by resolution. Regardless of resolution, your 360 distance stays the same, but aspect ratio can affect it. As long as both monitors are 16:9, you shouldn't need to change anything.
 
Do note that while the sensitivity does not change, it might feel different due to the bigger monitor.

Correct.

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.

I noticed this myself recently, I think I know what's causing it. Will look into solving it quickly!

Added! But as usual with these console ports, mouse sensitivity settings are really bad.

View full update

I'll look into it!

I just done did it!

Tonight I hope! Having some issues with it since this is a PC port. Lazy devs!

Both added to the upcoming list!

Hi!
 
Not sure what went wrong here, but I've refunded the last payment and given you two months subscription for your troubles.
 
The account management could be better on this framework, I'll see if I can do some tuning!

I'll try to get it done on release day, or sooner if there is any kind of beta release.

You can check that the default value is 90 if you start a private game and enable cheats. Setting "fov_cs_debug 0" (which is default) and "fov_cs_debug 90" should yield the same FOV. The actual FOV you are seeing on your screen does indeed change with resolution change (e.g. at 16:9 it is 106.26), but the configured FOV is still 90, and this is the value that is important for the calculations

Greatly appreciated! There's holiday time here now, so updates will be a little slow. But come October and things will happen at a much higher rate!

Desktop mode is a new feature that lets you convert your Windows desktop settings to a game.
 
The way this works is a little different than distance mode, in that it adjusts the sensitivity according to FOV.
 
This mode matches the sensitivity like this:
If you want to target an object at the edge of your screen, you will have to move the mouse the exact same distance as moving from the center of the screen to the edge in Windows. This means that the calculator must account for FOV for all games.
 
I'll try to make a video showing the different methods in action, but I gotta figure out a good way to actually show the result and how pixel accurate it is. And maybe get some youtube personality to voice it

Added!

View full update

Far Cry 4 added! Since this is a PC port, expect some acceleration. Calcualtions are most accurate if you use high DPI.

View full update