Viewspeed v2

[CaptaPraelium]

I'm saying I think there is a problem with the calculator. It's definitely NOT a trick of the mind, it's  MASSSSSSIIIIIVVVEEE drop in sensitivity. The values I get are near half the old ones.

[DPI Wizard]

9 hours ago, CaptaPraelium said:

I'm saying I think there is a problem with the calculator. It's definitely NOT a trick of the mind, it's  MASSSSSSIIIIIVVVEEE drop in sensitivity. The values I get are near half the old ones.

This is an error in the BF1 formulas I think, they need to be updated.

[Bryjoe]

16 hours ago, CaptaPraelium said:

I think I may have found an issue with this. Something's not right with the BF1 vehicles. The tanks are SOOOO slow. It's like I set my mouse to 20 DPI.

 

BF1 vehicles are broken right now, use the in-game sensitivity version. The wiz altered the calculations recently and I think moved the decimal one over. For me, it recommends about 11% in game but in the config the calcuator says 0.016009 . This would be like under 1% in game. Use the in-game sensitivity, it is "close enough".

 

I should clarify, someone posted about an error in the cavalry sensitivity, I "think" the Wiz altered vehicle sens when he fixed it. Regardless, the problem with the calculation right now is large enough that an 11% becomes less than 1% on the config file versus the in-game. My first logical conclusion is a decimal error because of the discrepancy, but I don't know.

 

11% is  0.165000 to give you an exact idea. So .165000 compared to .016009.

Edited September 26, 2017 by Bryjoe

[CaptaPraelium]

"close enough" won't really be good enough here since I'm testing, and the differences are often several decimal places deep. but I'll sure try the *10 trick, thanks for that tip

[DPI Wizard]

Working on BF1 now, updating it soon!

[DPI Wizard]

Fixed BF1 now.

[Bryjoe]

44 minutes ago, DPI Wizard said:

Working on BF1 now, updating it soon!

Nice! Is there any way to know what FOV the plane uses? They have separate sensitivity for it and in the plane feels a bit too slow compared to the tanks.

[CaptaPraelium]

HYPE thanks Wizard

You can't really match mouse sens for a plane since it has a ton of acceleration, but I could find out the FOV if Wizard doesn't already know which he probably does

[CaptaPraelium]

Sorry Wizard, I think there may still be a small issue... The vehicles sensitivity seems correct now, but for the Heavy tank/Cavalry I get a very low number and cavalry actually gives me the "sensitivity too low" error.

Battlefield 1 (Vehicles - File) - Light tanks / Heavy tanks

Sensitivity 1:

GstInput.MouseSensitivityVehicle 0.185639           <<<<<---------------  LOOKS GOOD NOW THX

Multiplier 1:

GstInput.VehicleSensitivityTank 0.133261            <<<<<---------------  TOO SMALL

360° rotation:

67.9704 cm

Base length:

40.624 cm

 

Discrepancy: 0% (0 cm)

Config FOV:

GstRender.FieldOfViewVertical 80

Actual VFOV:

50 degrees

Actual HFOV:

79.32 degrees

[Bryjoe]

11 hours ago, CaptaPraelium said:

Sorry Wizard, I think there may still be a small issue... The vehicles sensitivity seems correct now, but for the Heavy tank/Cavalry I get a very low number and cavalry actually gives me the "sensitivity too low" error.

Battlefield 1 (Vehicles - File) - Light tanks / Heavy tanks

Sensitivity 1:

GstInput.MouseSensitivityVehicle 0.185639           <<<<<---------------  LOOKS GOOD NOW THX

Multiplier 1:

GstInput.VehicleSensitivityTank 0.133261            <<<<<---------------  TOO SMALL

360° rotation:

67.9704 cm

Base length:

40.624 cm

 

Discrepancy: 0% (0 cm)

Config FOV:

GstRender.FieldOfViewVertical 80

Actual VFOV:

50 degrees

Actual HFOV:

79.32 degrees

Are you using viewspeed? I think the Heavy Tank has a lower FOV. Also, I think it might be best to just match the vehicle sens on 360 because of how often you use them in 3rd person and how much less precise FOV accurate aiming matters in a tank.

Where it gets tricky is the cavalry. It always is in 3rd person, but I wonder if it is worth matching the FOV for the aimed portion, I would lean towards no, because like every vehicle, I think your movement is more important.

Edited September 27, 2017 by Bryjoe

[DPI Wizard]

Try again now. Since vehicles use 0.3 as default and normal sensitivity use 0.03, it messed up my templates a bit.

[CaptaPraelium]

Sorry to make you fiddle with it mate. Heavy tanks look good now - FYI I previously had 1.51...

 

GstInput.VehicleSensitivityTank 1.491966

Cavalry is still giving me the error though

 

Battlefield 1 (Vehicles - File) - Cavalry (USA ON)

Sensitivity 1:

Calculated sensitivity too low
Reduce either sensitivity 1 or new DPI

Multiplier 1:

-

360° rotation:

Recommended new max DPI: 600 DPI

Base length:

cm

 

Discrepancy: % ( cm)

Config FOV:

GstRender.FieldOfViewVertical 80

Actual VFOV:

80 degrees

Actual HFOV:

112.33 degrees

 

 

 

 

[CaptaPraelium]

OK so my new mouse sensitivity 'clicked' tonight, and holy mackeroli. Man, I hit some absolutely insane shots. Depending on playstyle, my stats basically improved by about 150% in either score per minute or KD ratio or kills per minute. It's like I'm me-and-a-half.

Definitely putting my stamp of approval on your formula Drimzi. I'm done testing. This is the beez kneez. Well done and thank you.

Edited September 28, 2017 by CaptaPraelium

[DPI Wizard]

17 hours ago, CaptaPraelium said:

Sorry to make you fiddle with it mate. Heavy tanks look good now - FYI I previously had 1.51...

Don't be sorry, the calculations need to be correct

Fixed Cavalry now, had the same issue.

[CaptaPraelium]

Thankyou Sir
Man, this is just great. I'm really pumped.

[Bryjoe]

2 hours ago, CaptaPraelium said:

Thankyou Sir
Man, this is just great. I'm really pumped.

In the tank or on foot?

[CaptaPraelium]

All of the above

Some examples: an ELEVEN second flight time tank shot on a bomber. From A on Empire's Edge to beyond F.
Hitting 8 planes in  a row on Monte Grappa
Being shot in the back with an automatico at 6m range, do a 180 and quickscope him in the face.
An off-screen dragscope headshot on a full-speed running horse through smoke.
At least 5 20-kill streaks as infantry.
Shot out 3 aircrew (A pilot and two gunners)
Jumpshots and a nice 180 jumpshot quickscope at 96 metres (yes I was trickshotting in BF1)
I'm OK at this game but that was a really good night by my standards.

Edited September 28, 2017 by CaptaPraelium

[CaptaPraelium]

Hi guys, in my conversations encouraging people to try this out, I've had a few "so how do I do this, anyway?" type requests. I thought I might put together a short tutorial document, but before I get too far into it I should ask - what will the formula be called? Viewspeed? New viewspeed? Something else?

[DPI Wizard]

I think I will replace the old Viewspeed with this one in the next update, unless someone would like to keep the old one. Since the old one is very close to 70% Monitor Distance, I would say that can be used instead.

[jabbothehut]

1 hour ago, DPI Wizard said:

I think I will replace the old Viewspeed with this one in the next update, unless someone would like to keep the old one. Since the old one is very close to 70% Monitor Distance, I would say that can be used instead.

when would that be roughly?

[Snook_]

Now? lol.

Now it's confusing as there is a v1 and v2

It would be best to just pick what is universally the most 'correct' and standardize on that IMO

[JayCapo]

Would V1 or V2 be better for  H1Z1 to CSGO hipfire training?  Would I use Horizontal degrees based on 4:3 ?

[Quackerjack]

yea iam with u Snook_, engl. is not my native language its hard to understand the difference for me for V1 and V2

[Bryjoe]

13 hours ago, JayCapo said:

Would V1 or V2 be better for  H1Z1 to CSGO hipfire training?  Would I use Horizontal degrees based on 4:3 ?

They really are extremely similar. I don't know anything about the technical aspects of each, but Viewspeed V2 is superior as it works better at the extreme ends of FOV. Viewspeed 2 is a faster conversion, but not by much. Use Viewspeed 2 unless for some reason you like the lower sensitivity the the original viewspeed offers. 

Viewspeed 2 should feel identical to CSGO default AWP sens in most situations. You sensitivity increases and decreases based on your FOV, so if you are unscoped you will move faster, if you are scoped you will move slower, it sound counterintuitive but it really is the best way to do things.

If you like consistent movement, you can use 360 distance, but I recommend matching FOV if you want to use 360 distance. Actually, if you match FOV, Viewspeed is meaningless in hipfire.

Edited November 2, 2017 by Bryjoe

[Quackerjack]

@Bryjoe for me V2 gives the lower sensitivity