Jump to content

V Rising

Use the config file for best accuracy.
Read more...

Vigor

The sensitivity slider is not accurate, expect some discrepancy. Use the config file for best accuracy.
Read more...

MULLET MADJACK

The config file might use either comma (,) or period (.) as the decimal separator depending on your locale settings.
Read more...

Combat Champions

All aims use the same sensitivity setting, choose the sensitivity for the aim you prefer to be matched.
Read more...

Ghost of Tsushima DIRECTOR'S CUT

The sensitivity and FOV changes depending on certain actions and where you are (indoor etc). The calculations are for the view when you move around outdoor.
Read more...

Battlefield 1


DPI Wizard

Added support for all aims, multipliers and coefficients, as well as calculations for both in-game and config file sensitivities.


User Feedback

Recommended Comments



I wana convert overwatch widow zoom sensitivity to BF1 soldier zoom sensitivity.

So i input overwatch hip:3.5, widozoom:39,  dpi:1250,  battlefield hip:2%.

Why keep saying input the '#.## Zoom Sensitivity [10-200]%'?

 

Edited by JJMMIINN
Link to comment

Hello,

In BF1, if I use USA and change the default coefficient in game, how do I reflect that in the calculator please?
See my screen shot below please.
Here, how do I know the USA is set on the in-game default of 133%? or how do I set it to 133% or else?
Thank you for your help

BF1 Grab.JPG

Edited by Jeffy14
Link to comment

Hello @DPI Wizard

I played BF4 with a sensitivity of 0.001, 2500 DPI, and an FOV of 74. 10.472 360 distance. This was on a 1920 by 1200 monitor.

I recently changed to a 2560 by 1080 ultrawide monitor, so it is vertically shorter. Does that mean I should use a Vdeg of 66.6 instead of 74 for BF1 (I ratio-proportioned it :/)?

I'm very confused about Viewspeed v1 and Viewspeed v2. When I first started playing BF1, I only used Viewspeed v1 as v2 did not exist yet. These are what I came up with, a sensitivity of 0.002112. Now when I try Viewspeed v2 it is 0.000474. What is the difference between Viewspeed v1 and Viewspeed v2? I'm very confused because for the longest time I remember my standard 360 to be 10.472 inches. I used that even in the TF2 days. That's why when Viewspeed v1 suddenly says it's now 8.346 anymore, Viewspeed v2 gives 11+ inches, so what gives?

But anyway, I've played a lot with BF1 at 0.002112 sens, 66.6 Vdeg, USA on, ADS FOV on, 2500 DPI on my 2560 by 1080 monitor for a while now, and I've decided this will be my new standard sensitivity that I will convert all games from, I've given up on the BF4 0.001 74 Vdeg, since I play BF1 excellently with this new setting anyway. 

More importantly, how do I convert all of these to PUBG? I can't seem to find what zoom ironsights and red dot/holo are in PUBG. I converted BF1 0.002112 1X zoom to ADS in PUBG but it feels weird. Please help me. Do I use 360/monitor/viewspeed 1/viewspeed 2? I really just love my new standard (0.002112 BF1) and how UsA works with all the zooms so I'm accurate with 2x, 4x, etc. I would like this same USA standard feel across all sights in PUBG (iron/red/holo, 2x, 4x, 8x). 

image.thumb.png.deb073fb168465209f76ca72a98af93d.png

Edited by Carlos Resurreccion
Link to comment
23 hours ago, Luckorr said:

Hey all,

 

short question: how come, that there is no way to convert the turret sensitivies of BF1?

I believe the turret sensitivity is just based on your vehicle sensitivity. The tank turret has a certain rotate speed that is hard locked.

Link to comment

would it be possible to check the calculations as they seem to be out by roughly 5cm as when i enter a 360 distance of 40cm for hipfire, the value the calculator give me both in game and for the config file corresponds to roughly 45cm for a 360 degree turn

Edited by InSaN3KiLLerZzonpc
Link to comment
  • Wizard
31 minutes ago, InSaN3KiLLerZzonpc said:

would it be possible to check the calculations as they seem to be out by roughly 5cm as when i enter a 360 distance of 40cm for hipfire, the value the calculator give me both in game and for the config file corresponds to roughly 45cm for a 360 degree turn

What values are you using? Post a screenshot of the calculator. Also, do you have a Logitech G keyboard or mouse? If so I can give you a script to verify.

Link to comment
  • Wizard
1 minute ago, InSaN3KiLLerZzonpc said:

Here is the requested screenshot of the calculator and i also use a logitech G mouse and keyboard.

Ok, I'll verify it a bit later today and give you a script so you can double-check it.

Link to comment
1 hour ago, InSaN3KiLLerZzonpc said:

Not a problem thank you for your help.

 

 

Hmm, why are you converting 40CM Distance in-game to Hipfire in the config file? I don't think it is related to why you're perceiving the calculation to be off, but I just can't imagine the purpose of doing so. Maybe if you knew your percentage in-game and wanted to convert to config, that would make sense but to convert based on distance from in-game to the config file is puzzling.

 

Link to comment

screenshot was just to show what value the calculator was giving for both the in game options and also in the config.

i work all my games to a 40cm to 360 for hipfire.

Edited by InSaN3KiLLerZzonpc
Link to comment
  • Wizard
21 hours ago, InSaN3KiLLerZzonpc said:

screenshot was just to show what value the calculator was giving for both the in game options and also in the config.

i work all my games to a 40cm to 360 for hipfire.

Verified that the calculations are correct now. Here's a script you can use in the Logitech Gaming Software to verify the calculation for the config file sensitivity (0.019936):

function OnEvent(event, arg)
	if (event == "G_PRESSED" and arg == 1) and GetMKeyState() == 1 then
		for i = 0, 62 do
			MoveMouseRelative(100,0)
			Sleep(10)
		end
	end
end

This will bind the script to G1 on your keyboard. Tell me if you are not sure how to add scripts ;)

This script moves the mouse 6300 counts, so it will move almost 1 count too far compared to the calculation (6299.3). But it's a lot more efficient to move this way, and it's close enough to verify.

6300 counts / 400 DPI * 2.54 (cm in inches) = 40.005 cm

You can use this test in basically any game, but note that some games do not like scripts like this. Some will drop packets and some will accelerate the movement. The best way to know it's working is if you can execute it several times and the cross hair ends up at the same spot. If it varies, the game has issues.

Link to comment

Hello
I noticed that there was a problem with the FOV an example: VFOV: 74 degrees
  Actual HFOV: 90 degrees on battlefield 1

on the converter it is written: Actual VFOV: 74 degrees
  Actual HFOV: 106.52 degrees

 

DPI Wizard can you help me please?

Link to comment
2 hours ago, Dre_MaD said:

Hello
I noticed that there was a problem with the FOV an example: VFOV: 74 degrees
  Actual HFOV: 90 degrees on battlefield 1

on the converter it is written: Actual VFOV: 74 degrees
  Actual HFOV: 106.52 degrees

 

DPI Wizard can you help me please?

BF rounds up to 74. Go to config and set fov as 73.74 to get a HFOV of 90

Link to comment
  • Wizard
1 hour ago, Dre_MaD said:

Hello
I noticed that there was a problem with the FOV an example: VFOV: 74 degrees
  Actual HFOV: 90 degrees on battlefield 1

on the converter it is written: Actual VFOV: 74 degrees
  Actual HFOV: 106.52 degrees

 

DPI Wizard can you help me please?

The HFOV+ in the BF1 menu is 4:3 based. When playing 16:9 the extra width is added on resulting in 106.52.

Link to comment
3 hours ago, danilo106 said:

i wanna play at 120 HFOV , what number ishould set on the config ? thanks

16:9 120 horizontal = 88.507 (vertical), 104.822 (4:3)

 

Set 88-90 in the config file (vertical). If you are playing Battlefield V, set 88-90 in the config file, or 104-106 ingame (4:3).

Edited by Drimzi
Link to comment

In battlefield 1, when 16:9 resolution is VFOV, it is 74, and the actual horizontal angle of view is only 90. Do they mix up 4:3 and 16:9's HFOV?

In the previous versions, I measure horizontal vertical alignment distance (2D). The result is that the horizontal vertical measurement distance is not consistent. In the current version, the measurement error is ignored. It can be considered consistent, and the difference between previous measurements is more, so it is sure that the horizontal vertical moving distance of previous versions does not agree.

The horizontal picture is stretched to 4/3 times the original image,In this way, the tan (horizontal rotation angle) needs to be changed to 3/4. If there is a previous version, it can be verified.

Link to comment

Hello, 

I use these settings in BF1

Sensitivity 1: Soldier Mouse Sensitivity 4%
DPI : 800
360° distance: 45.3389 cm
Field of View 74
ADS FOV: OFF
USA: ON with 133%
 
So when I set it to Monitor Speed I get this extra info
75% rotation: 5.6844 cm = 45.14 degrees
Base length: 3.578 cm
 
So from what I understand is that 1cm mouse movement is 3.578cm crosshair movement on screen?
 
For the zoom sensitivity I want something like 1cm mouse movent is 2.25cm crosshair movement. So this 2.25cm is like something of 63% of 3.578cm. Do I set each individual zoom setting to 63? 
I tried it with Match at "auto" and Match at "75" and I get different results.
On Auto
1x                          58%
1.25x                     59%
1.5x                       60%
 2x                         61%
2.5x - 4x               62%
5x - 10x                 63%
 
On 75
Everthing on 63%
 
Or do I need to use an other convert method? And with what method do I use these results to convert it to other Games?
Edited by Memphiss
Link to comment
  • Wizard
2 hours ago, Memphiss said:

Base length: 3.578 cm
So from what I understand is that 1cm mouse movement is 3.578cm crosshair movement on screen?

Yes, but this number is a bit misleading as it is the average mouse-to-crosshair movement over a distance. The new version (work in progress) shows this instead:

image.png

This is more accurate since it's actually measurable. 

Link to comment
  • Wizard
On 9/3/2018 at 12:12 PM, banSensitivity said:

What is the difference between GstInput.SoldierZoomSensitivity1 and GstInput.SoldierZoomSensitivity1x00?

I'm not sure what SoldierZoomSensitivity1, 2 3 and 4 does. But either way just leave them at the default value of 1.

Link to comment



Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...