4 hours ago, DPI Wizard said:

As Scca says, it is probably the FOV. It sounds like you have set it to 100, which would correspond with your findings. I would recommend switching location to In-game if that is where you set the sensitivity, as the FOV Type is different.

OK thanks, setting my fov to 1 does correctly give me the correct value for a hipfire 34.6cm/360, but now I think the zoom sensitivity is wrong, at least for sniper it's too high (It gives me 1.25 which is impossible and 1.00 already feels too fast). The value it gives when I leave the FOV empty, 0.89, is much closer to how I think it should be.

Edited October 31, 20232 yr by drawdel

8 minutes ago, drawdel said:

OK thanks, setting my fov to 1 does correctly give me the correct value for a hipfire 34.6cm/360, but now I think the zoom sensitivity is wrong, at least for sniper it's too high (It gives me 1.25 which is impossible and 1.00 already feels too fast). The value it gives when I leave the FOV empty, 0.89, is much closer to how I think it should be.

Can you share the conversion using the purple share button?

2 minutes ago, DPI Wizard said:

Can you share the conversion using the purple share button?

https://www.mouse-sensitivity.com/?share=b0223cc18871b68d25f11cf3ca57f4cc

2 minutes ago, drawdel said:

https://www.mouse-sensitivity.com/?share=b0223cc18871b68d25f11cf3ca57f4cc

Ok, thanks. There's nothing wrong with the conversion, what you are trying to do is impossible within the limitations of the game. Your FOV in The Finals is significantly higher than Overwatch, so it's not possible to match the ADS or Scope to your Overwatch sensitivity using MDV 0%. If you instead match the FOV with Overwatch (0.464233), it will work.

8 minutes ago, DPI Wizard said:

Ok, thanks. There's nothing wrong with the conversion, what you are trying to do is impossible within the limitations of the game. Your FOV in The Finals is significantly higher than Overwatch, so it's not possible to match the ADS or Scope to your Overwatch sensitivity using MDV 0%. If you instead match the FOV with Overwatch (0.464233), it will work.

I'm not sure what you mean but 100fov, 30 sens and 85% multiplier feels about normal to me both hipfire and scoped in

is this correct? when i try changing fov i just reverts to 71 fov (there was a patch) i dont know if that changed anything, i never tried this prior to that, i have no idea how to use hex editor

Edited November 1, 20232 yr by philheath

1 hour ago, philheath said:

is this correct? when i try changing fov i just reverts to 71 fov (there was a patch) i dont know if that changed anything, i never tried this prior to that, i have no idea how to use hex editor

Does the value that you used in the hex editor (0,968325) also gets reverted after trying to change it?

21 hours ago, philheath said:

is this correct? when i try changing fov i just reverts to 71 fov (there was a patch) i dont know if that changed anything, i never tried this prior to that, i have no idea how to use hex editor

Are you following the instructions in the notes? If you add any decimals it will revert to default settings:

Before you make any changes to the config file, you should first change the sensitivity in-game to a random value that is not 0, 100, or the default 50. Make sure this change causes the sensitivity value in the config file to have six decimal places. This is important because adding new decimal places will cause the file to become corrupt, which would cause it to reset when the game is launched.

13 hours ago, DPI Wizard said:

Are you following the instructions in the notes? If you add any decimals it will revert to default settings:

Before you make any changes to the config file, you should first change the sensitivity in-game to a random value that is not 0, 100, or the default 50. Make sure this change causes the sensitivity value in the config file to have six decimal places. This is important because adding new decimal places will cause the file to become corrupt, which would cause it to reset when the game is launched.

its working now, thanks, i dont know what was happening, how do you even find this stuff out  find us a way to disable TAA  

During the Beta that just ended The Finals was using a 1:1 vert FOV type btw.

1 hour ago, NO4ce said:

During the Beta that just ended The Finals was using a 1:1 vert FOV type btw.

That's also what's already in the calculator.

Now that the game has been officially released, there's a new option for mouse sensitivity called 'Focal Length Sensitivity Scaling' that you can toggle on and off.
I believe it indicates the ability to adapt aiming speed based on the sight zoom, which might solve the issue of having to choose between prioritizing scoped sniping or iron sights.

Edited December 8, 20231 yr by HexHyte

If possible I would like a recheck of the values now that the full game is out just in case they changed anything like they did back with some versions of the BETA. It feels a bit different but that just could be me and I just  need to get use to the game again.

Edited December 8, 20231 yr by Rihta

I think this here is a new setting, in case this is relevant for the calculations:

They have changed quite a bit, working on it now!

Hipfire is updated, aims coming soon.

And now everything is updated!

Thank you legend!

My conversion from siege to Finals using MDH 0% says that the scoped sensitivity is past the maximum sensitivity. How can it be possible to convert when the lowest possible matching of monitor distance is even past the maximum sensitivity in the game?

https://www.mouse-sensitivity.com/?share=6fec5ac126de85e26cc8c6e6a725e2e7

18 minutes ago, Magico.- said:

My conversion from siege to Finals using MDH 0% says that the scoped sensitivity is past the maximum sensitivity. How can it be possible to convert when the lowest possible matching of monitor distance is even past the maximum sensitivity in the game?

https://www.mouse-sensitivity.com/?share=6fec5ac126de85e26cc8c6e6a725e2e7

just use 1.0

Mouse Focal Length Sensitivity Scaling,Can sensitivity conversion be done by turning off this option

1 hour ago, Magico.- said:

My conversion from siege to Finals using MDH 0% says that the scoped sensitivity is past the maximum sensitivity. How can it be possible to convert when the lowest possible matching of monitor distance is even past the maximum sensitivity in the game?

https://www.mouse-sensitivity.com/?share=6fec5ac126de85e26cc8c6e6a725e2e7

Since it maxes at out 100% which is MDV 0%, it can't match any higher monitor distance, and in your case it's needed because of the discrepancy for hipfire. This will be solved by the answer below

37 minutes ago, xzzzxgp said:

Mouse Focal Length Sensitivity Scaling,Can sensitivity conversion be done by turning off this option

Yes, I will add that so the range is better. It will make the difference between ADS and sniper huge, but it's probably a good tradeoff.

It is weird. The calculation result about the number in config is new, but the result in "in-game" is still the old one, even the 360 distance is way different from the standard I give it.

 

 

Edited December 8, 20231 yr by MGYBlue

Something seems off.

This game is still using 100 vertical monitor match?
I am using 100% vmm as target, but the game tells me the needed ADS-multipler would be larger than 1.0.
Would you look into it @DPI Wizard?
It was working just fine before the update and I received 1.0 as ADS-multiplier which it should be 

 

Edited December 8, 20231 yr by WhoCares?

32 minutes ago, MGYBlue said:

It is weird. The calculation result about the number in config is new, but the result in "in-game" is still the old one, even the 360 distance is way different from the standard I give it.

One of the hipfire entries was missing the update, it should be fixed now.

8 minutes ago, WhoCares? said:

This game is still using 100 vertical? monitort match?
I am using 100% vmm as target, but the game tells me the needed ADS-multipler would be larger than 1.0.
Would you look into it @DPI Wizard?
It was working just fine before the update and I received 1.0 as ADS-multiplier which it should be 

No, it uses MDV 0% now, so going above 0% isn't possible with Mouse Focal Length Sensitivity Scaling on. I'm updating to support it being off now.