TheNoobPolice

CoD now defaults to 133 vertical MD by default since relative is always active, Apex uses 0%. So provided you just set the Coefficient in CoD to 0% and don't have an ADS sens multiplier other than 1.0 in Apex (or CoD) it is then already matched by that method across all scopes. The settings for base FOV can just be matched to the same thing anyway. Apex uses a multiplier scaled off Hor 4:3, not vertical, but you can match that up using the calculator very easily. like so if you wanted 80 vertical degrees for hipfire for both games, for example: Whether you want a fixed ADS zoom or one that is scaled in relation to your hipfire in CoD is entirely personal preference. Just depends how much zoom you want compared to hipfire. It doesn't affect the scaling method.

I guess you'd have to test if it actually allowed a greater value than 2. If not you can just adjust the ADS sens sliders up slightly depending on your whatever your FOV settings are.

Thanks! It does it with CoD MW 2019 also btw

It happens pretty much with all games that I have tried that have special options. For example , lets take CoD Black ops 4. I like that when I load up the game in the lower portion of the calculator, it automatically shows me the default FOV type and value, this is useful to know. HOWEVER, once I know that, I then always change it where possible to 84 vertical degrees as that is what I am used to and use in all games that allow it. The first problem is I have to always remember to change the FOV type first, and then enter the number, if I do it the other way around, the I have to enter the value a second time. The second (larger) problem is that the options "Aim", "ADS field of view", "ADS Mouse Sensitivity" and "Location" ALL reset the FOV to the default value. This means I can't enter my desired FOV once, and then select different options quickly to arrive at different values without always having to re-configure the FOV fields.

Is there any possibility that the FOV type and value can be set permanent in the calculator (once it has been edited initially) so it isn't overridden by changing other aiming types, or special options etc. Not sure if it's the same for anyone else, but I do find this pretty irritating that I keep having to reset it.

Use Relative, and set coefficient to 0.00 with transition set to gradual. That's the same as the legacy system.

Depends on how you want ADS to be synchronised, you will not be able to synchronise up all scopes by any one method because CoD MW doesn't allow individual sight adjustment, and the default scaling is different to some of the ADS levels in pubg. Also, you should only really try and match first person aiming - third person is fundamentally different in any case. First thing is to match your hipfire up - the important thing is the FOV difference between the games -(Pubg uses resolution based, and CoD is 16:9 aspect ratio based). You can match this up as below. Then you can choose a method for converting ADS. Most recommend either MD (monitor distance) 0%, or MD-H 50-75%. Example: Then you can input your previous hipfire sens and arrive at a setting for a specific ADS conversion, for example, converting the Assault rifle ADS to red dots in CoD matched by MD 0% If you want to do a different scope, you will get different results however. Best advice is just to choose the scopes you use the most and match those up. If you find the aiming too slow in CoD, try using monitor distance horizontal 50-75% instead.

It's not really important. It's actually a completely redundant feature. Still, I guess it's nice for those that don't want to think and just hit a "like it used to be " button.

Immediately = Frostbite legacy style for old Battlefield players After zoom = CoD legacy sniping style Gradual = FOV transition based id say the latter makes the most sense, but entirely personal preference.

Although there is no independent scope sensitivity adjustment, I too would like all the different sights FOV values added. There is a whole bunch but they all fit into around 5 or 6 actual zoom levels I believe. You can test them in private games where everything is unlocked by default. Any chance @DPI Wizard?

^ The above is normally caused by a program / game dropping packets from the mouse. Probably just a bug but can also be caused by mouse driver issues.

I recommend Custom Curve 2.0 because its interface is very easy to see your settings and how they relate to your hand movements. It also has a feature for recording hand movements and providing recommended settings, it's found at mouseacceleration.com. You can also use Kovaak & Povohats combined effort; called Interaccel. http://mouseaccel.blogspot.com/p/blog-table-of-contents.html The latter is freeware, but is not anywhere near as easy to use for someone new to it. Both provide similar accel functionality and both use the same driver that will work in all programs and across the whole operating system as applies the values at kernel level.

Cod always used focal length scaling.

My advice would be the following: For matching hipfire, use 360 distance unless the game's meta is heavily predicated on aim, like an FPS game. If you just want familiar 180s and 90 degree turns. It's pretty much always best to match 3rd person games with 360 distance for example, since 3rd person aiming is different anyway. For FPS games you should really be trying to match hipfire FOV anyway. 0% Monitor distance (or focal length), maintains the actual sensitivity at the point of aim. This is generally the most useful for ADS transitions, especially in games where there is a lot of tracking, recoil control and / or slower ttk. For games with high zooms and more sniping-style aiming mechanics (or at least where they are more important) use a monitor distance conversion - depending on the amount of zoom anywhere from 50-75% horizontal Monitor Distance will probably feel the most natural. Focal length generally feels too slow compared to hipfire once the ADS FOV change gets to be greater than 40 vertical degrees or so of reduction. This is why it's really great when games give per-scope ADS sens control, so you don't need to compromise.

well, 121.28 to be precise, but yes.

In my opinion you should always set the FOV to the same type in the calculator, and let it work out the value for you to configure depending on the output game. As below, BF1 uses vertical FOV, and Black ops 4 uses Horizontal resolution based FOV. By inputting "90 vertical" for the output game, it automatically gives me the correct config value for horizontal 16:9, in this case 121.28.

Yes. I would read through the stickied post by Skidushe so you form a better understanding of the fundamentals.

If a 360 doesn't feel the same, it is usually because it is a different FOV.

In other news; Shroud reveals he prefers polyester shirts - Millions of gamer's throw their cotton shirts in the trash in response. "That's what was holding me back!!" They cried. "Now I have a wardrobe of polyester shirts I too will be able to attain god like aim, competitive FPS success, and huge streamer popularity."

Who cares what dpi someone else uses?

^ As above. No such thing, as "your sensitivity". It's all learned behaviour. Most people gravitate towards a fast sensitivity when they start gaming because that is what was most similar to the mouse pointer that they probably had it set to when first using a computer. (most people don't like to move a mouse very far when using a computer if they are non-gamers believe it or not), and so low gaming sensitivities feel very alien. People typically habituate fully to a new sens, even a drastically different one, in less than 10 hours gameplay.

People shouldn't be thinking of monitor distance as a type of match, rather it's a just a measurement for a sensitivity change. No matter what system you use to attempt to maintain a perceived sensitivity of the game world at a different FOV, it will ALWAYS be equivalent to at least one monitor distance, therefore monitor distance itself can not be flawed. When people have a preference for 75% Mdh, for example,. its not because they want accurate flicks to a part of the screen; it;s nothing to do with that at all - it's the fact that the speed of the gameworld seems most consistent to them when calculating turn-rates across FOVs using that method. It's almost impossible for anyone to deny, that if using focal length or 0%, that when ADS'ing with a high zoom scope it always feels much slower than hipfire, therefore, with the exception of making slow tracking the most consistent, it doesn't have much value for sniping play styles. This is why approx 75% feels the most consistent across multiple FOVs, but if you only use small FOV changes when aiming, it starts to have less value.

^ The config file in the beta was encrypted. It may be possible to edit with a hex editor, but given the menu supports two decimal places it should not need a config file edit.

Where the mouse velocity synchronises to on the monitor is not related to your aspect ratio choice directly. It's still just preference. Monitor distance is just a measurement of sensitivity at the end of the day. You could play on a 1:1 square aspect ratio and still sync to 178% of vertical FOV if that's the speed you were used to.

The ADS multipliers in the game are currently buggy, including the MDC which keeps resetting itself, there's no point in even worrying about it right now. No such thing as same sensitivity on two different FOVs. You either compromise all but one part of the screen and/or 180/flick familiarity on ANY FOV change no matter what you do. Having said that the game uses monitor distance 0% by default on legacy mode, which is probably the best way to convert for ADS anyway.