Apex Legends

16 minutes ago, DPI Wizard said:

If you are using 4:3, then the correct conversion would be MDV 100%/MDH 75%.

mouse_zoomed_sensitivity_scalar_0 "1.070593"
mouse_zoomed_sensitivity_scalar_1 "1.168017"
mouse_zoomed_sensitivity_scalar_2 "1.199889"
mouse_zoomed_sensitivity_scalar_3 "1.211063"
mouse_zoomed_sensitivity_scalar_4 "1.219046"
mouse_zoomed_sensitivity_scalar_5 "1.221840"
mouse_zoomed_sensitivity_scalar_6 "1.223133"

I think we have firmly hit the "about right" stage. That actually felt really good even on ultrawide. Obviously long horizontal flicks aren't going quite where they should, but anything vertical or horizontal within roughly half a screen's length feels accurate.

Thanks a lot.

Hello, i'm trying to convert my cs go sensitivity to apex ( i obtain a weird scope sensitivity). i'm doing something wrong ? 

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

On 01/04/2023 at 19:06, DPI Wizard said:

There was an issue when selecting another FOV Type than "multiplier" after the update to support multiplier up to 1.7, it should be fixed now.

Not sure its working correctly for me.

Old maximum of cl_fovscale 1.642857 reports Hipfire HFOV 16:9 128.922798

New maximum of cl_fovscale 1.7 reports Hipfire HFOV 16:9 128.922807 

Shouldn't cl_fovscale 1.7 be like close to quake live 120 fov or HFOV 16:9 133.173551 

Also its not accepting anything other than multiplier for me with the increased values

Hey guys, I've just subbed here for the calculator and I need a little help making it work. 

I've been training in Kovaak's with top 100 to 300 scores in every scenario I practice, while whiffing shots in Apex routinely. I'm here hoping to fix this. 

I've worked out that the scope_sensitivity_scalar in Apex is a huge part of my problem. I'm trying to get the right values for 2x scopes and up especially. 

I tried this calculator https://jscalc.io/calc/6gCfepwF6YtTP6lB which has you enter your Apex FOV and then uses a 1.33 coefficient to calculate new scalars.
Already, my in-game results are far closer to what I expect based on Kovaak's, but things still don't quite feel right. 

I'm on 101 FOV in Apex, but Apex distorts that number when slid in-game so I entered the actual 101/70 calculation for the fov_scale into the settings.cfg.
This means my actual FOV_Scale is 1.442857142857143. This is supposed to equalize the FOV between Apex and what I'm practicing on in Kovaak's. 

And now I've just heard that the 1.33 coefficient is supposed to be for 1920x1080 monitors.

I'm on a 27" HP Omen, 2560x1440.

So I subbed here after hearing that a 1.78 coefficient is appropriate for my monitor, and looking for a tool that would help me to do that. From what I understand, the issue is that these numbers based on 1.33, and on Apex's distorted 101 FOV instead of my actual 101 FOV, are still slowing my scope speed down by an inappropriate amount. 

Now, when I try to enter the values into the calculator here, I'm getting numbers lower than 1, or I'm getting numbers lower than what the 1.33 calculator gives me.

So I must not be entering something correctly, but I don't know what I could be overlooking. 

I'm showing 16:9 aspect ratio in in-game video settings in Apex, while Kovaak's doesn't display this as far as I know. 

I don't have any clue what the "FOV type" entries are for in the calculator here.

The jscalc.io page based on 1.33 coefficient and Apex's false 101 FOV gives me 
mouse_use_per_scope_sensitivity_scalars "1" mouse_zoomed_sensitivity_scalar_0 "1.1039575785869957" mouse_zoomed_sensitivity_scalar_1 "1.2662782420181493" mouse_zoomed_sensitivity_scalar_2 "1.32575600611312" mouse_zoomed_sensitivity_scalar_3 "1.3475397529978426" mouse_zoomed_sensitivity_scalar_4 "1.3634282256835493" mouse_zoomed_sensitivity_scalar_5 "1.3690558967639974" mouse_zoomed_sensitivity_scalar_6 "1.3716726145580913"

Entering these numbers has allowed me to drop my effective DPI (using Raw Accel to get the same in every game, program, and Windows) to 747, and three or four tap with the Wingman and also get one-clips with the R3 while scoped in. Previously I could do one or the other depending on my sensitivity settings, but never both. I found myself needing to raise the sensitivity up for 2x scope tracking, to the point that the Wingman was completely unreliable. So I've already gone a long way to solve my problem, but I'd like to know what the 1.78 coefficient and a more accurate FOV_scale (mine is 101/70 or 1.442857142857143, which is not what using the in-game slider to enter 101 FOV would result in) would give me. I'd also like a clearer understanding of the math involved here and what all these terms mean! I've already done a single monthly sub, but I'm likely to get lifetime membership and recommend this to all my squads if I can get some help here :))

Questions about digital threat x1

Is the output value of the digital threat higher than the value entered as 'mouse zoom sensitivity'? It's not accurate, but I think it's a little fast when I measure it.

8 hours ago, DPI Wizard said:

Can you share your calculator setup? 1.33 means setting the ADS and scope conversions to MDV 133%.

It's explained in the instructions.

These values assume an actual 4:3 hdeg FOV of 101, or like your cl_fovScale "1.442857", and is the same as this: https://www.mouse-sensitivity.com/?share=cf7f8ef9e7490e6938c263166c7755d8. Apex has a bug where the actual 4:3 FOV is rounded to the nearest whole number before calculating the scope sensitivity. It doesn't affect you since you are using exactly 101, but if you were using say 101.5 instead, then 102 would be used by the game for calculating the scope sensitivity. The calculator replicates this bug

Something about the way the guides are written is making me reread sentences 15 times even though I deal with technical writing for work.

Am I right that this https://www.mouse-sensitivity.com/?share=24e6d156800f1c3cdfb779a5b8f869d2 gives me my 360° values? I think I do need to keep my iron sight / 1x scopes closer to this value. The main way I get killed is when people cross close enough that I misjudge the 45 or 90° turn to recenter on them based on whether I’m scoped in or not. And the transition to punching distance is where I really inexplicably screw up.

I set FOV Type to Hdeg 16:9 there, but I’m not seeing anything that tells me how Kovaak’s and Apex calculate it, and I don’t know why this section wouldn’t be auto-filled and locked based on the game selected. I’m also not seeing it affect the output with a quick swap back and forth...

With the two different values for scalar_0 depending on whether you’re using a pistol or an AR, am I right that you can’t enter anything in the .cfg to equalize these values since you can only put a number to scalar_0 once? I’ve always ran out of tracking space or tracked too slowly when I try to use iron sight ARs in this game do I just avoid it. I’m assuming there’s no workaround and you just have to pick which weapon class to make fit your target, one always being faster or slower by an amount that’s arbitrary when you’re not shooting for 0%? 

And if I want to try 1.78, I just change that 133.333% value in your link to 178%, right?

On 4/26/2023 at 12:41 PM, DPI Wizard said:

It's unlocked because you can use it to convert the FOV. Say you want 74 vertical degrees for all your games, then you can simply select Vdeg and enter 74 as the value, and the output will show you the correct config FOV value to configure to get exactly this. Also, the FOV value will be automatically converted to the FOV type you select. So if you for instance want to know what the 4:3 horizontal FOV the 1.442857 multiplier in Apex is, simply select Hdeg 4:3 and the value will update. Which is why the output doesn't update, because the effective FOV is the same. In your link though you are using Hdeg 16:9 and 101, this will not result in the same output as 1.442857 multiplier or 101 Hdeg 4:3.

Got it. Perfect, thanks!

Any idea why the numbers I'm getting when I try to put in 0% horizontal matching aren't quite 1 for Apex scopes? If that's a quirk with the game then I don't think I need to ask further questions about what I might be misunderstanding about setting my own mm% yet... https://www.mouse-sensitivity.com/?share=f654de02ead498c8676fbc47299ac1a8 
 

Quote

Correct, and this is why there's a split between ADS and scope in the conversion setup. So you can do exactly this; keep the same 360 distance for ADS (which is usually anything below 2X, but depending on the game it might vary), and use tracking speed or flick distance etc for the scopes.

I see! May be worth noting the reason I didn't consider that is that Apex doesn't have a separate "hipfire" sensitivity, it has a "scalar_0" that shows up under the scoped section, so it changes with the other scopes and the hipfire section -- I'm not sure if it even does anything to Apex, actually. 

Hey guys. I apologize if I'm asking something that's already been asked - I checked almost everything but if I missed something, please refer me to it. 
I want to convert my Apex sens to CSGO since I've been training with it for a while, but whatever I input in the calculator the output is always the same sens that I started with. Now I assume that's because both use Source, however my FOV in Apex is 110, while in CS I believe it's always 90. So while my cm/360 might be the same, just aiming around doesn't feel right. 

Can someone please tell me if I'm missing something? My settings are the following:
Apex: 1920x1080 (native), 1.4 SENS, 110 FOV
CSGO: 1280x720, widescreen 16:9 

DPI: 800
Monitor: 21.5''

 Could you check if the ads 1x/hip conversion is correct? I'm using cm/360 and apex preset in the aim lab, but the game and converter don't match.

10 часов назад, DPI Wizard сказал:

Can you be a bit more specific?

I tried to convert hip sensitivity to 1x ads and it gave me the value I entered in Aim Lab (Apex profile). Aim Lab shows that ADS sensitivity is different from Hip by cm/360 (and not by much). Used the type of conversion "360 turn". That's what I'm trying to understand, maybe in Aim Lab or converter somewhere sneaked a mistake in the calculations.

On 5/1/2023 at 2:26 PM, DPI Wizard said:

It's a bug in the game, the one mentioned here:

 

I thought he was showing here that the numbers are slightly off, even with - his example - 90 FOV. 

I didn't know about that. Thanks, I'll try it later.

I know this reflects something basic about the overall concept of sens-matching that I'm still not getting, but can you explain why viewspeed-matching my Kovaak's hipfire at 435 edpi to Apex hipfire at 435 edpi, and the same 108 FOV, in both results in a sensitivity of 1.05... instead of 1? I thought that if you're on the same FOV and the same edpi, the concept of monitor matching wouldn't apply, you'd already be matched everywhere automatically; it's only when scoping in changes your FOV that some criteria has to be set. Why would any of the options here result in anything but 1? https://www.mouse-sensitivity.com/?share=96467cf263651c594518d704f75d0a52 

Can I get some clarification please, if I'm trying to get MDV 0%, do I need to:

Set mouse_use_per_scope_sensitivity_scalars "1" and input the corrected scalars for each scope (in my case it's 1.004245 for all values)? Or does mouse_use_per_scope_sensitivity_scalars not matter?