Fortnite

51 minutes ago, Mixthat said:

Found this on the internet. Not sure if it may work.

1. Now navigate to your Fortnite executable file (usually C:/Program Files/Epic Games/Fortnite/FortniteGame/Binaries/Win64). The executable is called FortniteClient-Win64-Shipping.exe
2. Right-click the file and select Properties
3. Select the tab Compatibility and check Override high DPI scaling behavior and Disable full-screen optimisations
4. Click OK

That didn't help, but I've tried a few more things that makes it a lot better.

1. Set Frame Rate Limit to 30 or 60. Lower is better for mouse input. At unlimited it's useless, 120 works a bit.

2. Disable vsync.

3. As mentioned earlier, lower report rate to the lowest you can.

Nice, I'll update it later today.

Updated!

And they have fixed the report rate/acceleration issues it seems.

20 minutes ago, bebeto said:

Did you test in BR mod or PVE ? i'm not too sure, considering how they manage the 2 game mods, that it's affecting both game mod but only BR.

The mouse smoothing is written under BR patch note.

i would like to know if this is the same thing for both game mod.

I only checked BR, PVE might still have the old sensitivity and issues actually.

Added Save the World and Battle Royale as separate games. Will add more scopes when I get them analyzed.

11 minutes ago, big engine said:

another question, it's normal that while calculating targeting sens a multiplier of 0.1 gives an higher 360 that a value of 1?

Lower is slower, 0.1 basically means "distance/0.1". Divisor would be a more appropriate name than multiplier

4 hours ago, Mixthat said:

What's the targeting FOV in Fortnite? I think it's 80 but it's not preset for me.

 

EDIT: Admin, can you look into the preused FOV when calculating games? I had a 45 FOV grayed out most of the time when calculated the FOV for Fortnite and the results were wrong. I think it's an javascript/browser problem.

Targeting FOV is 80, and should be loaded automatically. If you have saved a Fortnite input earlier, it might have the old values saved, if so clear the input and select it again. The 45 degree FOV was only for aim calculations that used the same sensitivity as hipfire. I removed it when they added scope and targeting.

23 hours ago, big engine said:

One little issue it's the fact that both the sniper rifle and the scoped ar are sharing the same slider. Maybe you should add to the calculator the option to choose for witch weapon have the correct sens

Added calculations for Scoped Assault Rifle as well!

1 minute ago, Portmanteau said:

I'm trying to match my settings to my Overwatch settings. I try to keep it so my hipfire is a 360 degree turn across my mouse pad. This calculator is almost perfect 100% of the time for this basic function, but for Fortnite, something still isn't working out. I'm trying Save the World, and I put the number into my config file, which checks out to be something like a .0012% discrepancy, but in game it's like, a full 40 degrees or so. I've got the mouse acceleration turned off, so I can't quite figure out what else I need to change.

Save the World has issues with reporting rates. Try with 125Hz if you can, it works a lot better than 1000Hz. Also if you try in Battle Royale it it should be perfect regardless. It uses different sensitivity though, so re-calculate for Battle Royale, and see if the 360 is perfect.

Targeting sensitivity is a multiplier applied to targeting with guns that do not have scope. I.e. holding down right mouse button so the view is moved slightly forward over the shoulder of the character.

This view has the same FOV as you normally have, but is at a different position. If targeting is set to 1, you have the same 360 distance as normal/hipfire sensitivity.

The problem when converting to it, is that your 0.06 sensitivity has a small discrepancy, so the calculated targeting sensitivity is probably 1.01 or something. If you increase the Sensitivity 1 in the output game to 0.061, you will likely see that the targeting multiplier is calculated to 1 or 0.99.

So to sum up, if you want the same sensitivity for targeting, set it to 1. If you want slower sensitivity, use another conversion method for it. For instance use 360 distance for hipfire, and Monitor Distance 75% for targeting.