Apex Legends

Possible bug in the current version of the calculator - please see attached image.

The FOV value seems to be inverted. 'In-game' tries to use raw degree values even when multiplier is selected, and 'Config-file' uses the multiplier even though the actual value in the .ini is in degrees. Something seems to have inverted the correct behaivour.

2 hours ago, koglelang said:

Possible bug in the current version of the calculator - please see attached image.

The FOV value seems to be inverted. 'In-game' tries to use raw degree values even when multiplier is selected, and 'Config-file' uses the multiplier even though the actual value in the .ini is in degrees. Something seems to have inverted the correct behaivour.

config file : uses the multiplier

in game:  uses degrees but is messed up slightly so it says multiplier due to the fact that it is innacurate and the calculator has to compensate

i am somewhat certain that this has been mentioned somewhere within teh 900 ish mesages in the apex thread

------------------------

if you want an example for this

set auto fov to this and comapre in game 90 which should be the exact value 

Ah so listing 'multiplier' for the in-game value is intentional to illustrate that the in-game value is still not an explicit vfov/hfov value. Makes sense. Perhaps a note to that effect could be added in the FOV notes section for the Apex profile. 

9 hours ago, koglelang said:

Ah so listing 'multiplier' for the in-game value is intentional to illustrate that the in-game value is still not an explicit vfov/hfov value. Makes sense. Perhaps a note to that effect could be added in the FOV notes section for the Apex profile. 

yeah something along the lines of it trying to use hdeg 4:3 in game, yet missign their target in the accuracy department and thus dpi wiz gives you the actual number

------

might not only serve illustrative use but also make calculating the actual fov easier since youd end up with wrong numbers if youd set it to 4:3 as intended

but this is me just interpreting pretty sure this was discussed some time a few years ago couldnt find the actual reasoning after a short search so this is mostly from memory.

yes a note letting you know that could be good for those new to the calculator and its functions

---------

to be fair i generally recommend just using auto fov

pretty much serves as a set and forget utility if you have a preferential fov setting youd like to use across games with different fov`s

Pre-sale question: Would the advanced settings allow me to play games like Apex at higher fov, and other games, say Destiny 2, which doesn't have an FOV that goes past 100 or so, and get a more consistent experience? I don't know if I am asking that as clearly as I could.

Destiny 2 may be a bad example because it doesn't have consistent zooms across so many weapons, Universal Soldier Aiming co-effients, or fine sens controls.

Like let's say even for hipfire, I can match them for a 360 in the free version, but I don't want to play Apex at an 84 FOV. Could I adjust Apex's sens to feel more consistent with D2's FOV? I'm not sure if you always want hipfire to be the same regarless of FOV or not.

For aiming, given the wide range of scopes in D2 or any other game that doesn't have seperate sens for different scopes, and the fact that they don't match any of the magnifications of other games, is it a futile effort to try to improve the experience with the calculator?

22 hours ago, nathanial-san said:

Pre-sale question: Would the advanced settings allow me to play games like Apex at higher fov, and other games, say Destiny 2, which doesn't have an FOV that goes past 100 or so, and get a more consistent experience? I don't know if I am asking that as clearly as I could.

there is a method you can use where you give up some screen realestate for an identical 360 distance experience with slightly differing fovs 

this will give you black bars to match the focal length and actually works

Is there a possibility to have the calculator go to 3 decimal places for in game, because for sensitivities below 1 e.g. 0.5 the game can take up to 3 decimal places if you don't type in the 0 at the start e.g. .555 instead of 0.555

18 hours ago, DPI Wizard said:

I can't make it do 3 decimals for just values below 1, so it will probably cause some confusion for users when the sensitivity is above 1 and output is more decimals than the game supports. I think for these cases it's best to just use the config file calculation instead.

So when adjusting in the config file, do you know if the sensitivity will stay the same every time i launch the game? Because when using the in game settings and assigning my own specific sensitivity, the game will always round up the sensitivity after I close and relaunch the game. I would love to try and avoid that if possible when using the config file.

Why monitor distance 0% gives mouse_zoomed_sensitivity_scalar_0 "1.003223"  and not 1.0?

so we know mouse_zoomed_sensitivity_scalar 1.0 is 0% MDV.

Is there also an universal number for 100%MDV or do i have to change it for everye scope seperatly?

18 hours ago, Quackerjack said:

so we know mouse_zoomed_sensitivity_scalar 1.0 is 0% MDV.

Is there also an universal number for 100%MDV or do i have to change it for everye scope seperatly?

always depends on a games default scale so unless a game lets you change the coefficient liek battlefield or cod you wont have a uniform number for all methods of scale

1 hour ago, fortunate reee said:

always depends on a games default scale so unless a game lets you change the coefficient liek battlefield or cod you wont have a uniform number for all methods of scale

Yea but 1 = 0 mdv so there should be one for 100 mdv also? Or i dont understand the system

10 hours ago, Quackerjack said:

Yea but 1 = 0 mdv so there should be one for 100 mdv also? Or i dont understand the system

"mouse_zoomed_sensitivity_scalar = 1" is an identifier specific to Apex. Basically, the name is something that the developers came up with and the units are whatever made sense to them at the time.

It could pretty much be anything.

Valve has a similarly named option for team fortress 2, but 0 mdv is some weird shit like 0.794 or something.

Overwatch's variable has a completely different name.

I'm not sure if dpiwizard came up with "MDV" theirself or where that term came from. I'm not sure if there is any sort of industry standard name for what this website is dedicated to.

So i was wondering if there is something wrong Im doing here, while the 1x and 10x settings seem actually pretty good for me, the rest not so much.  They feel too fast.

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

14 minutes ago, DPI Wizard said:

Wrong FOV, 110 is the in-game value and you have selected config file.

Oh damn, didnt notice that, Thanks 

Hey, Can someone double check my setup and let me know if Im doing this correct? 

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

 

Just now, DPI Wizard said:

Unless it is intentional, you should stick to one viewspeed method for both ADS and Scope. And you can do this conversion by just selecting "All" for the input game

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

Thank you!

hello guys, I got a different result from aimlab, when I convert from CSGO to Apex with MDH 100%, all the ADS and scope.

This question confuse me for a long time, I don't know which one should I use.