Battlefield 1

DPI Wizard · November 6, 2016

Added ADS FOV on and off for both in-game and config file!

Always fill out your configured FOV now

It was a little messy before and easy to get wrong numbers.

jabbothehut · November 6, 2016

Added ADS FOV on and off for both in-game and config file!

Always fill out your configured FOV now

It was a little messy before and easy to get wrong numbers.

yet again pls give this man a nobel prize <3

WhoCares? · November 6, 2016

Are your sure the calculator is correct after the ADS FOV Update?

For me it seems wrong. Before the update is was right.

Here an example:

Yesterday this settings gave me 269.875 cm:

Sense 0.0027; DPI 1200; SoldierZoomSensitivityAll 1.00; Coefficient 0.00 SoldierZoomSensitivity8x00 1.715219; FOV 73.73979

I handtested it and it was correct

Today, when I am using the ADS FOV OFF calculator (cause I am using ADS scaling OFF) I get this value for 269.875 cm : 1.843169

(Both times I used an FOV of 73.73979!)

But this value isnt correct.

When I test it In-Game I get arround 255 cm

Is seems like all sights values given by the calculator are to high, so it takes less cm for 360° turn

Edited November 6, 2016 by WhoCares?

DPI Wizard · November 6, 2016

What are you converting from? It's not impossible that there's some tuning needed.

WhoCares? · November 6, 2016

Since the FOV OFF/ON update I get different values for the calgulator and these values are wrong in contrast to yesterday.

I'am not not really converting, I am using a fixed 360° distance for a specific sight.

Bf3 had a x 0.16 reduction in speed for a 8 times zoom. So when I need 43.18cm in hip, I need 269.875cm when ADS.

To get 269.875 and a 8 times zoom in bf1 I had to increase the GstInput.SoldierZoomSensitivity8x00 value to 1.715219. And this value was correct.

But today when I want to get 269.875 cm the calculator gives me GstInput.SoldierZoomSensitivity8x00 1.843169. And thats not correct. Its too fast :/

Am I missing something? :/

Another example with an 6x scope:

But I Need 353 cm (Handtested) In-game.

I dont know the excact distance the claculator gave me yesterday, but it was pretty close to arround 355 cm.

I know why handtesting isnt that great, but 15 cm difference seems a little bit too much

Edited November 6, 2016 by WhoCares?

DPI Wizard · November 6, 2016

Yesterday was wrong, it included the FOV part twice.

Just tested this now, and todays numbers are correct as far as I can tell. What deviation do you get the DPI Analyzer?

Your hand-tests are about 5% off, which is not unlikely caused by the sensor not being exactly the DPI it is configured as.

WhoCares? · November 6, 2016

Well, I guess I have to trust you that your calculations are correct

I dont understand how the DPI Analyzer works, but I guess it is just my mouse than.... :/

Unfortunate coincidence that the false calculator from yesterday fits to my mouse better than the correct calculator from today^^

Edited November 6, 2016 by WhoCares?

SevenFreak · November 6, 2016

Hi,

@Wizard, is it intended that the configured FOV for the "second game" get´s reset each time when I switch to a different scope?

DPI Wizard · November 6, 2016

Hi,

@Wizard, is it intended that the configured FOV for the "second game" get´s reset each time when I switch to a different scope?

Yes, it is intended. Whenever you select a new game/aim it reverts to the default FOV type and FOV value for that game/aim. But admittedly it's a bit annoying when you play around with the same game. I'll see if I can change it to only reset the FOV settings when changing game, and not aim. It resets when changing units as well, which is not intended.

mattiasheen · November 6, 2016

Since the FOV OFF/ON update I get different values for the calgulator and these values are wrong in contrast to yesterday.

I'am not not really converting, I am using a fixed 360° distance for a specific sight.

Bf3 had a x 0.16 reduction in speed for a 8 times zoom. So when I need 43.18cm in hip, I need 269.875cm when ADS.

To get 269.875 and a 8 times zoom in bf1 I had to increase the GstInput.SoldierZoomSensitivity8x00 value to 1.715219. And this value was correct.

But today when I want to get 269.875 cm the calculator gives me GstInput.SoldierZoomSensitivity8x00 1.843169. And thats not correct. Its too fast :/

Am I missing something? :/

Another example with an 6x scope:

47599452241.JPG

But I Need 353 cm (Handtested) In-game.

I dont know the excact distance the claculator gave me yesterday, but it was pretty close to arround 355 cm.

I know why handtesting isnt that great, but 15 cm difference seems a little bit too much

You have 6x selected

Edit: Never mind, didin't see the whole text

Edited November 6, 2016 by mattiasheen

SevenFreak · November 7, 2016

Edit: Ok, blame me, first I´ve thought the calculator is off since the 360° for example from the 1.25x scope was pretty much the half of what the calculator showed, then after reading the description I just saw that I have to turn on USA even when the value is 0.

But what´s basically the difference or the opposite when I dont want to use USA at all even with value 0?

Edited November 7, 2016 by S7evenFreak

poppe · November 9, 2016

Are vehicles just forgotten?

WhoCares? · November 10, 2016

Should I set the coefficient in Bf1 to 1.7777 (or 0.5625^-1) when using 21:9 aspect ratio ?

jabbothehut · November 10, 2016

how do I get the same ration in rainbow six siege between hipfire and acog to be like the uniform soldier aim on bf1 at 133% coefficient? do i just do "measure screen distance at 75%?

CaptaPraelium · November 17, 2016

Kinda hyped for vehicles!

DPI Wizard · November 17, 2016

My BF1 crashes right to the desktop when loading a game after the last update

No error or anything.

Edit: Got it working now, analyzing vehicles!

big engine · November 21, 2016

Does anyone have a different feeling with the mouse even using the same sens in bf4 and bf1? I don't know why but in bf4 the input are so precise while in bf1 it feels like the mouse it's a little slower :huh:

PS: can't wait for vehicles in the calculator great job Wizard!

NoMaD.oW · November 21, 2016

Does anyone have a different feeling with the mouse even using the same sens in bf4 and bf1? I don't know why but in bf4 the input are so precise while in bf1 it feels like the mouse it's a little slower

PS: can't wait for vehicles in the calculator great job Wizard!

Maybe it's related to some sort of additional input lag?

However it feels the same for me using the Calculator converting my sensitivity from overwatch to BF1.

Edited November 21, 2016 by NoMaD.oW

big engine · November 21, 2016

Maybe it's related to some sort of additional input lag?

However it feels the same for me using the Calculator converting my sensitivity from overwatch to BF1.

The feeling that i have it's pretty close to some input lag, but I play with no v-shync and my frames are capped to 65 with no drops at all (same as in bf4)

DPI Wizard · November 21, 2016

Sensitivity differs for a lot of vehicles, so I'm not quite sure how to go about this yet. I could add all, but I think some share sensitivity setting... Still working on this.

big engine · November 21, 2016

Sensitivity differs for a lot of vehicles, so I'm not quite sure how to go about this yet. I could add all, but I think some share sensitivity setting... Still working on this.

Not sure about the exact problems that you are facing but I think that having just tanks and turrest would be great

DPI Wizard · November 21, 2016

Not sure about the exact problems that you are facing but I think that having just tanks and turrest would be great

Tanks have different movement-rate on turrets etc, so it's really hard to find the base sensitivity of them. And for a lot of aims you can't turn 360 degrees, while others have obstructions left and right, so you can't see the monitor edges... Makes the analyzing part a whole lot harder!

DPI Wizard · November 22, 2016

Added both file-based and in-game calculations for land vehicles now! Select "Battlefield 1 (Vehicles - File or In-game)". I will clean up all the different games and input methods in an upcoming update.

SevenFreak · November 23, 2016

Edit: Ok, blame me, first I´ve thought the calculator is off since the 360° for example from the 1.25x scope was pretty much the half of what the calculator showed, then after reading the description I just saw that I have to turn on USA even when the value is 0.

But what´s basically the difference or the opposite when I dont want to use USA at all even with value 0?

Need to quote myself but somehow I still dont understand why I have to USA? Even with 0 USA is something "calculating" in the background based on the information´s which have been provided here. I just want to understand it, I´m not against it or something like this as long as its might be helpful but I thought it would be just a more "raw" input without using all those stuff.

DPI Wizard · November 23, 2016

0 means movement around the crosshair will be matched between zoom levels, the default 1.33 means it will be matched at 75% of the monitor distance for 16:9 monitors (9/16*1.33). The Coefficient do extremely small changes when close to 0, barely calculable. But the difference becomes large the further up you go.

In other words, this is a fine-tuning mechanism to select where on a 2D plane (your monitor) you want the movement to match, since it can only be matched to one point when the FOV is different as it is between scopes etc.

If you turn USA off, the sensitivity between scopes will simply be (for default values): CONFIGFOV/AIMFOV* 360 COUNTS. This is effectively the same as setting Coefficient to 1 (since VFOV is being used), but you do not have any option of fine-tuning it, nor the options for the individual aims.

Sign In

V Rising

Vigor

MULLET MADJACK

Combat Champions

Ghost of Tsushima DIRECTOR'S CUT

Battlefield 1

User Feedback

Recommended Comments

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Create an account or sign in to comment

Create an account

Sign in