Values for 21:9 Conversions

[imperior]

I've read through a fair deal of posts here regarding calculations between games but I am afraid I'm not quite understanding what values I actually need when converting between games when playing on a 21:9 aspect ratio.

I want to convert my current Apex sense to a couple games and also verify I have made my scope values in apex are correct But I am uncertain on what values to use. Essentially I want my hip fire and scope values to be as close to 1:1 as possible. Would these two conversions be correct?

Apex to Apex:

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

Apex to MW II:

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

I'm mostly confused on what to put in the red circle values in the attached and how to get them.

 

Edited November 17, 2022 by imperior

[DPI Wizard]

8 hours ago, imperior said:

I'm mostly confused on what to put in the red circle values in the attached and how to get them.

You have entered the wrong resolution, unless you play with the monitor vertical. It should be 3440x1440.

Using the same FOV is step one, so you have done that correctly (disregarding the resolution).

What the correct conversion is depends on a few factors though, mainly what your current zoom sensitivity is in Apex and whether you want to have the same 360 distance or aim distance for hipfire if you are unable to match the FOV.

[imperior]

So I corrected the resolution. For the correct conversion, Let's assume I want to use mdh 0%. Would I change from MDV 239 to MDH 0 ? Essentially, I want my hipfire and scoped travel distance to be equal assuming the same mouse movement. The second question is in FOV type next to auto fov, there is no option for multiplier. For apex I put hdeg4:3 based on some posts I found where you describe it as 4:3 with a multiplier. My current apex scopes feel a bit odd but I'm not quite sure how I got them as I was fairly new with the calculator and mistakes were certainly made.

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

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

 

Existing Apex:

cl_fovScale "1.428571"
mouse_sensitivity "0.675000"
mouse_use_per_scope_sensitivity_scalars "1"
mouse_zoomed_sensitivity_scalar_0 "1.275654"
mouse_zoomed_sensitivity_scalar_1 "1.656768"
mouse_zoomed_sensitivity_scalar_2 "1.851111"
mouse_zoomed_sensitivity_scalar_3 "1.935113"
mouse_zoomed_sensitivity_scalar_4 "2.002169"
mouse_zoomed_sensitivity_scalar_5 "2.027275"
mouse_zoomed_sensitivity_scalar_6 "2.039212"

[DPI Wizard]

5 minutes ago, imperior said:

For the correct conversion, Let's assume I want to use mdh 0%. Would I change from MDV 239 to MDH 0 ? Essentially, I want my hipfire and scoped travel distance to be equal assuming the same mouse movement.

All Monitor Distances do this, but to different points on the monitor. MDH 0% is the same tracking speed, MDV 239% is the same distance to the edge of the 21:9 monitor. So it depends on what you want to achieve.

6 minutes ago, imperior said:

The second question is in FOV type next to auto fov, there is no option for multiplier. For apex I put hdeg4:3 based on some posts I found where you describe it as 4:3 with a multiplier.

There is no multiplier option because the multipliers are unique for the games the have them, so for the auto function you have to use a standard measurement. Apex is using hdeg 4:3 as a base yes, but the in-game value is not correct other than at 70, and the config file value is a direct multiplier of 70. So both of them are in reality multipliers.

14 minutes ago, imperior said:

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

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

Those are correct for achieving MDV 239%. It's a bit easier in MW2 as you can just set the coefficient instead of each scope.

As for your old values, I don't know how old they are but there's a bug in Apex when it calculates ADS sensitivity which wasn't reflected in the calculator before, but it is now.