Updated with new sensitivity formula, scoping and targeting sensitivity. Acceleration issues are fixed!

my FoV is set to 120 and the calculator doesn't account for the FoV change.

 

 

13 minutes ago, BMR_ said:

my FoV is set to 120 and the calculator doesn't account for the FoV change.

Sorry about that, try now.

How did you change your FoV?

 

Edit: I tried using the value from the calculator in the ini file and disabled mouse acceleration(gotta make the file read-only or it goes back on), but the result was a lower cm/360 than expected by a fair amount.

Edited July 22, 20178 yr by ygdrad

Strange, did you set the sensitivity in the config file or in-game? My file is not getting overwritten when I disable the acceleration, weird that yours is.

Regarding FOV, I would like to know how @BMR_ changed it as well. I know the FOV affects the sensitivity, because you basically change FOV when you right click to aim. But I've tried most UT4 methods of changing it to no avail.

22 minutes ago, DPI Wizard said:

Strange, did you set the sensitivity in the config file or in-game? My file is not getting overwritten when I disable the acceleration, weird that yours is.

Regarding FOV, I would like to know how @BMR_ changed it as well. I know the FOV affects the sensitivity, because you basically change FOV when you right click to aim. But I've tried most UT4 methods of changing it to no avail.

I set the sens in the config file, was supposed to get roughly 1.5 turns on my mouse pad, got 1.25. The only part of the config file that seems to be getting overwritten for me is the mouse acceleration.

 

The calculator was telling me to input 0.041350, but after some manual fiddling around I ended up at 0.051020 to roughly get what it should be at.

Edited July 22, 20178 yr by ygdrad

Have you compared the cm/360 to another game like CSGO?

The base sensitivity for Fortnite is exactly the same as UT4, but it sound like you are experiencing (negative) acceleration or smoothing for some reason.

On 7/22/2017 at 7:49 AM, DPI Wizard said:

Have you compared the cm/360 to another game like CSGO?

The base sensitivity for Fortnite is exactly the same as UT4, but it sound like you are experiencing (negative) acceleration or smoothing for some reason.

I haven't compared it to UT4 but I did input the same value as I do for all games, 24.88cm/360. The calculator gives me the right value for Overwatch though.

 

Edit: The shifting sensitivity seems to have been linked to windowed fullscreen mode. After switching to standard fullscreen the sensitivity stayed the same but the calculator still didn't match the cm/360.

 

Edit2: nope, problem still present :/

Edited July 29, 20178 yr by ygdrad

You can go into Engine and add

[/script/engine.localplayer]
AspectRatioAxisConstraint=AspectRatio_MaintainYFOV

This will at least give you a bigger fov for your res

20 minutes ago, Akumos said:

You can go into Engine and add

[/script/engine.localplayer]
AspectRatioAxisConstraint=AspectRatio_MaintainYFOV

This will at least give you a bigger fov for your res

Thanks, updated the info on the game to include this. Doing this changes the FOV from 80 degrees horizontal to 80 degrees vertical. The sensitivity (360 distance) is actually not affected by this, so I've updated the formula as well. If you do this change, make sure you set the FOV to 80 Vertical Degrees in the calculator.

There also is a mouse smoothing option in Epic Games\Launcher\Engine\Config\BaseInput.ini which may mess with sensitivity and these two lines which affect mouse sensitivity based on fov.

bEnableFOVScaling=true
FOVScale=0.01111

Edited July 26, 20178 yr by ygdrad

The previous thing I posted, that file needs to be set to read only if you want to disable mouseaccel in there, I didn't even mention it but mouse accel is in that file too along with the other one ygdrad mentioned.



FOVScale apparently is your ADS/zoomed sensitivity so if you swap it to like 0.33333 or whatever you can actually have two different sensitivities, hope that fixes your problems with it in the OP.

1 minute ago, Akumos said:

The previous thing I posted, that file needs to be set to read only if you want to disable mouseaccel in there, I didn't even mention it but mouse accel is in that file too along with the other one ygdrad mentioned.

I edit the files under %LOCALAPPDATA%\FortniteGame\Saved\Config\WindowsClient, no need to make them read-only for me at least.

10 minutes ago, DPI Wizard said:

I edit the files under %LOCALAPPDATA%\FortniteGame\Saved\Config\WindowsClient, no need to make them read-only for me at least.

The FOV change stays but when I didn't make it read-only it put the mouse accel in there back on.

Sorry @DPI Wizard Just seen your replies. I changed the FoV before getting into the game because I remembered how bad it used to be in alpha and it turns out they just upped the FoV a little and I thought it was just my config change... Turns out it did nothing sadly 

tldr - Can't change FoV still. I was wrong

Edited July 27, 20178 yr by BMR_

i set my sensitivity calculator to translate a 43cm 360 and the number im getting for the config is giving me a 46cm one

Actually i figured it out. I did some math and I found that 0.596934, when divided by the desired 360 cm, will give you the accurate config value. It might be a little off due to human error but it seems to be correct.

Edited July 27, 20178 yr by AlexTheRed97

On 7/27/2017 at 0:25 AM, AlexTheRed97 said:

Actually i figured it out. I did some math and I found that 0.596934, when divided by the desired 360 cm, will give you the accurate config value. It might be a little off due to human error but it seems to be correct.

At what DPI though?

On 7/27/2017 at 4:53 AM, AlexTheRed97 said:

i set my sensitivity calculator to translate a 43cm 360 and the number im getting for the config is giving me a 46cm one

This is normal between the human error and actual DPI of your mouse (setting it to i.e. 400 can be anything from 360 to 440 depending in your mouse).

The important thing is that when you convert between games the sensitivity will stay the same, even though the calculated distance might be a bit off due to DPI variances etc.

Ya my dpi is always 800, but the number i figured out doesn't work for any other sens and i figured out why. I wasn't acknowledging the fact that if u divide a larger cm value by a config file that ull get a large number and the other way around for a smaller cm 360 which should have a larger config number. So I had to figure out two sensitivity config numbers and figure out the difference between the two and the correlating cm difference and then go from there

But there is definitely something skewed with the calculations I'm getting on here. The sens im being given is a 0.012 config sens for a 43cm 360 but it ends up being a 46cm 360. The actual 43 cm config value is almost exactly 0.0138, taking human error into consideration. 

1 minute ago, AlexTheRed97 said:

But there is definitely something skewed with the calculations I'm getting on here. The sens im being given is a 0.012 config sens for a 43cm 360 but it ends up being a 46cm 360. The actual 43 cm config value is almost exactly 0.0138, taking human error into consideration. 

What mouse do you have, and what is the result if you try the DPI Analyzer?

I have a zowie ec2a, but like I said I've tried it multiple times for a bunch of friends and they all have different mice and it always ends up being a slower value

I have a zowie ec2a, but like I said I've tried it multiple times for a bunch of friends and they all have different mice and it always ends up being a slower value. Also I'm getting a 346 for this dpi analyzer

Edited July 28, 20178 yr by AlexTheRed97

I just wanna get this cleared up to help people out and find my exact sens, even though I'm pretty dead on