Raenatus

***EDIT***
Made a mistake, FOV stays the same at 103.

Only the UI and HUD gets stretched on 4:3

Listen Wizard,

It's called VALORANT, OKAY!? 
Thanks brah!

Lets go Chief!

6 hours ago, etienne00123 said:

Anyone experiencing mouse input lag? I've forced Vsync off in the Nvidia control panel, max pre-rendered frames to 1 and i'm getting more than 110 fps but the mouse still feels sluggish. 

No, I don't notice any input lag in BO4. Aiming feels really good in this game as well.

I'm getting consistent 160+ FPS though...

46 minutes ago, DPI Wizard said:

There will likely be minor adjustments to the ADS sensitivity the coming days btw, as I get more data in.

Thanks for keeping up with this!

Looking forward to the updates.

10 hours ago, stereo3D said:

default ads coefficient is 1.33, so that's 133 % vertical monitor distance, which results in 45.41 at FOV 103 in OW.

I must have entered the information incorrectly then.

Thanks a lot!

4 hours ago, stereo3D said:

simply multiply the ads coefficient with 100 and use that as monitor distance vertical % in the calculator.

That literally makes my Widow sense 100 in OW...

I don't think it's that fast.

I'm using Relative ADS sens for BO4, and loving it. 

How do I translate this to other games like OW (Widow) and D2 (ADS)?

For Relative ADS settings in the config, do I need to change both Pitch and Yaw?

I can't get the sensitivities to stick using the .ini file.

Anyone know how to get this to work?

31 minutes ago, potato psoas said:

You don't even need to worry about using 360 Distance. Even if there is a slight difference in FOV, why not just use one conversion method. It's easier and gives you more consistency. If the FOV between games is the same then monitor matching will still give you the same 360 distance.

Also, no matter what monitor match percentage you use, it is never going to feel perfect because of distortion.

Also, don't use 56.25% because it's actually arbitrary and based on a bad assumption. See this post to understand why.

Thank you for your reply!

I'll test out 0%MM and 100%MM and see which I like better.

Hello,

I was wondering if someone could help me on how I should be doing the sensitivity conversion from Overwatch to Fortnite.

I'm currently using 360 Distance for Hipfire, and 56.25%MM for ADS, and Scoping.

However, I can't seem to get these sensitivities to feel correctly when trying to fight people in close range with a shotgun in Fortnight.

Any advice would be appreciated.

Thank you!

Great! Thank you very much!

16 hours ago, subzerogts said:

Why Viewspeed or monitor distance?

I have 6.4 @ 900 dpi in Overwatch (equivalent to 7.2 @ 800 dpi and 14.4 @ 400 dpi). Overwatch FOV is 103.

Should I set FOV to 107 in Destiny 2 to compensate? The error % changes drastically for some of the values when I do that. Not sure if I should

105 is the max FOV for D2.

I do wonder, which ADS should we use? Viewspeed or monitor distance?

Thank you very much!

2 minutes ago, DPI Wizard said:

First convert to hipfire, then select ADS and use the value from hipfire in the Sensitivity 1 field. The output will show you the ADS sensitivity to use in-game.

I'm using 6 @ 800 DPI, but when I use "Look Sensitivity 6"

It says:

Calculated sensitivity too high
Increase either sensitivity 1 or new DPI 

Don't really get how to use the ADS sensitivity configuration. 

I put Sensitivity 1 in there between 1-100, but it gives me an error. Furthermore, the multiplier is grayed out.