sonorciff

So in my case, I can set the following values, and never need to touch scalar_1 through scalar_7, right? mouse_use_per_scope_sensitivity_scalars "0" mouse_zoomed_sensitivity_scalar_0 "1.004245"

So even if every value is the same, it is still needed?

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?

The m79 is in training mode with side arms, and so is the VSS (sorry I keep editing my posts). I think both of them are only found in one block of buildings and not the other, if that makes sense.. m79 is with side arms and the VSS is with DMRs.

Thank you. I edited my post to clarify, I meant "unique", not "different" . I also wondered about the VSS, which looks like the 4x to me, but again I'm not sure? Are the m79 and panzerfaust also unique?

Wow, pretty mental. I was just blindly thinking "same FOV = same visual experience", didn't even consider that. Thank you. Another question though, how about those weapons that at least seem like they have unique zoom level/FOV? Went into training mode and tried to emulate what you did with the Tommy. Took a couple of pictures but to me it looks like some of them might actually be unique? winchester - seems like it matches to a 3x, can you confirm? VSS - seems matched to a 4x? panzerfaust - kind of looks like an AR 1x, but not sure.. crossbow - I can't seem to match this to any 1x? P90 - I incorrectly called this an AR, but it's an SMG. It doesn't seem to match 1:1 to SMG or AR 1x though? m79 smoke launcher (sidearm) - doesn't seem to match to sidearm 1x

This is a little bit blowing my mind. If you look through the iron sight of a tommy compared with another SMG, you see a considerably larger amount to either side - this is because the camera is further back on the gun, even though the angle is the same? Would this theoretically affect muscle memory?

I noticed a long time ago that some guns don't seem to have the same FOVs, even within the same category. Today, I've tried to do a short comparison. I picked the guns up and pointed them at a wall, standing still, while switching back and forth between weapons and looking at reference points on the wall to compare. Some of these are different by mere pixels. And they're all with ironsights, or with their default scopes. Tested on separate machines. @DPI Wizard, if you have the will and patience can you please confirm? Could you potentially update the calculator in some way? There are so many different values though, so I'm not sure how.... Zoom level from largest to smallest: winchester (SR) > crossbow > m79 smoke launcher (sidearm) > panzerfaust > P90 (AR) > MK14 (DMR) > mini (DMR) > MG3 (LMG) > MK47 (AR)> Other AR/SR/LMG > Other DMR > G36C AR > shotguns > SMG > PP Bizon (SMG) > Tommy (SMG)/Skorpion (sidearm) > r45 (sidearm) > r1895 (sidearm) > sidearms No idea about the flare gun. Another fun part comes when you attach scopes. When I noticed the MG3 FOV changed with a red dot but not some of the other guns... oh boy. So many variables.

I tried Valo for the first time today - the Ares and Odin seem to have the same zoom sens as the SMGs Spectre and Stinger, can anyone confirm? The calculator may need to be updated.

That's weird, for me I think even hipfire and ADS were correct even without lastconverted. In any case, yikes on the rounding... and knowing PUBG corp, this may take a long time to fix if it ever is.

Thanks, actually it worked like you said without lastconverted once you added back in the missing line for copy and pasting. But am I reading this right, PUBG is rounding up the decimals on some scope sensitivities..? Oof.

Heya, I used the calc for PUBG yesterday and it worked fine, but now it seems it doesn't work anymore - the LastConvertedSensitivity is default (0.020000) for every line, and it's missing the ScopingMagnified line. Copy and pasting the results into the ini now resets all in-game sens to default (50).

I suppose then "relative" is the preferred for 1 and I'll have to test ADS FOV. I didn't see the option in the calculator before, just the result ^^.

Looking for some help and opinions about the following options: 1. ADS Mouse Sensitivity - what's the difference between relative and legacy if Monitor Distance Coefficient is set to 0.00? I'm trying to get MM 0%. 2. ADS Sensitivity Transition Timing - what do people recommend if I'm used to PUBG/Overwatch/Apex Legends? Going by description, I'd imagine gradual is most intuitive, but late sounds like it could be better for quickscoping/flicking? 3. ADS FOV - IIRC in PUBG/Overwatch/Apex Legends it's independent and independent is the default here, but the calculator states "affected" - is this preferred, and if so, why? Is it a matter of preference? Will both modes result in MM 0%?

Is this config relevant for the Quake II RTX game?

Thanks

I'd like to request the feature that allows additional games to be converted at once. You click a button (e.g. +Add Game) below the second game under "Convert to" to add each new game, allowing one input to convert to more than one outcome at a time. It's just a matter of convenience; yes I can save and load profiles for multiple games at once, but it'd be handy to see all outcomes at once :).

I hope it stays that way then. Which cheat engine is it? I've found a few but can't seem to find reference to sensitivity. Also can it edit zoom sens?

Imagine if you get banned for trying to use a basic setting that should have been in base game. Gearbox....

Sorry, but can you explain why 1.240857? Assuming the scale is a multiple of 70, and Overwatch's Hdeg Res is 103, shouldn't the multiple be more like 1.2376?

I already do as you suggest, and in practice I don't care about the difference. I figured it could be rounding, but there was another specific and odd number anomaly in the calculator a while back and I wondered if this could be a similar situation ^^

Hi~ I was converting the Overwatch monitor match 0% scoped value of 37.94 to PUBG's various FPP aim types. I noticed out of the 10 aim types in PUBG, only ADS (AR/LMG/DMR/Sniper) showed a different value when converting from Overwatch 37.94 scoped than Overwatch hipfire. Every other conversion between FPP PUBG and Overwatch shows the same mm 0% value to 4 decimal places, yet this one conversion shows a small difference. At 2.42 Overwatch sensitivity, hipfire to PUBG ADS (AR) returns 64.2359cm/360, and Overwatch scoped to PUBG ADS (AR) returns 64.25cm/360. I am aware Overwatch's 37.94 scoped sensitivity isn't a precise value as the game only supports 2 decimal places for sens, and also that .141mm/360 discrepancy is humanly imperceptible. Still, I wouldn't sub here if I weren't anal about these things ^^. I tried 2.4 and 2.39 instead of 2.42, and they actually returned same values to PUBG ADS (AR) from both hipfire and scoped, to 4 decimal places. From what I can tell it's just this specific combination of sensitivity and aim type which shows an anomaly. Could you please let me know what the cause of this difference might be?

Hahah, I think you originally replied saying you fixed it ^^ good timing hahah. Thanks though, and thanks for replying~

For some reason, converting Overwatch hipfire to scoped sens shows a significant discrepancy at 1600DPI and 2.39 sens, -3.5713% (-0.1449 inches). However, any other combination of DPI and sens I've tried shows 0% (0 inches). Seems to be a bugged result.

Title explains the problem. Calculator fails to load proper FPP value for PUBG vehicle sens for the menu value.