Fluvio

The calculations for "Old" seem to have broken and aren't usable now. So you can no longer convert the old sensitivities to the new one. Seems to only happen on the Old 4x - ACOG setting. It just doesn't convert/bugs out. I know that with 12 hipfire and 50 ADS on the old settings should be somewhere between 80-100cm/360 on old ACOG, but the calculation either doesn't update/calculate for the 4x ACOG. The calculations are also just completely incorrect, they seem to be calculating 12 hipfire, 50 ADS, 400 DPI on old 1x as being 33cm/360. I used this sensitivity for years and I still run it, it should be around 55cm/360. Not sure what's happened but yeah, the whole "old" setting has broken. EDIT: Found a workaround, it seems setting the "Location" from Config File to In-game solves the problem and calculates properly. I guess by having it at "config file" it's trying to calculate based off of the new sensitivity method rather than the old one in the game?

Basically just the title. And also, is it the best for going between Aspect Ratios with fairly different FOV's?

Oh yeah I know that it's impossible to match all three. I wanted to be able to show that mathematically because I'm very active on the Reddit subs for Siege and a lot of people seem to believe that you can set them to be equal. Which just isn't the case because ACOG is practically faster for it's FOV than it should be (Or 1x is too slow. Either way. One of them isn't lined up). And like I said, I wanted to test some stuff with regards to 360 distance and FOV. Like being able to show that ACOG is faster than Iron Sights when comparing the 360 distance and the FOV differences. Which reminds me. Do you mind looking at something for me? I was wondering if a ratio between FOV and 360 distance could be used to convert sensitivity, and if so, are there any downsides to it? I keep thinking about it and I keep coming to the conclusion that it would be very accurate. Am I missing something? Kinda like this https://docs.google.com/spreadsheets/d/1PKCO0nKiKfrtiWv0IdFjiE_ABymyyaadV9NohSKGnjo/edit#gid=854093420. For it to convert sensitivities I'd need to do some more work but is the general idea behind it viable as a conversion method?

The standard calculator does achieve this. But I was wanting to create an excel spreadsheet to prove that the ACOG, 1x sights and Hipfire in Siege all have different speeds to them regardless of how you set them. And also try something out in regards to using FOV and 360 distance to convert sensitivities. And well I ended up needing 360 distance along the way. Which I could find absolutely no information about. I finally found out the CSGO 360 distance equation thank God. And how to convert back and forth between Siege and CSGO for 360 distance. So I got there in a super roundabout way eventually after I posted this.

Can someone please tell me the 360 distance equation for CSGO or Siege. I cannot for the life of me work this out or find any information about it whatsoever.

What's wrong with it? How is anyone supposed to help when you haven't told anyone what's wrong with it?

What's the issue?

Try this out. Change your FOV to 60 and run around terrorist hunt for a bit. Then change it to 90. You will notice the difference... This is the hand-eye coordination change that I mentioned. The higher the FOV, the slower it will feel. This is why when you increase FOV, You should reduce your 360 distance to compensate. That realigns the sensitivity if you will. So you have two options to transfer the sensitivity. 1) Reduce your FOV to 65 like in my picture: To realign the sensitivities as closely as possible. This won't give you the EXACT same FOV since you cannot match the FOVs exactly as far as I'm aware so you do need a tad of compensation but it's literally minuscule. Or 2) Use 82 and use your new, faster sensitivity that will be converted. Like you have done above. Both of these will work equally well. One maintains Hand-Eye will changing 360 distance, the other changes Hand-eye while maintaining 360 distance. That's just the way I've came to understand it. Try them both out and see which works for you. You might hate the FOV change or you might hate the 360 change. You won't know until you try.

The way I try to think of it is: When it comes to mouse sensitivity, there are two factors at work: Muscle memory, and hand-eye coordination. If you change the in-game numbers, they alter the muscle memory, if you change FOV, it alters the hand-eye coordination. If you increase the FOV, you need to alter the muscle memory a little in order to compensate if that makes sense. Like if you have 3 * 4 = 12. And you change the 3 to a 2. It needs to become 2 * 6 = 12 for the equation to work. You need to alter things proportionately to eachother. The calculator does this for you which is why you end up with a smaller 360 distance (changed muscle memory) due to the FOV being different (Changed hand-eye coordination). If you go in-game and put your FOV down to 60 and do a few T-hunts, then change it to 90 and do a few, You'll notice that it feels slower on the 90 setting. That's the hand-eye coordination fucking up because the FOV got changed. That's the way I explain it. Essentially just do what the calculator says and you'll benefit. Trust me. I play Siege, BF4, CSGO, Fortnite and recently Overwatch. And using Monitor Match at 0% I maintain my aim through all the games, despite them being different 360 distances doe to the difference in FOV. If you want the same 360 distance, you definitely wanna match FOVs. Specifically, you wanna match Horizontal FOV. You see that "Actual HFOV =" number. Reduce the 21:9 FOV until that HFOV matches, or is as close to the same as the standard 16:9 one. That can also give you the same sensitivity. It'll probably need be between 65 and 75 I would guess.

The outcome shouldn't have the same 360 distance since Ultrawides provide you with additional FOV. The calculator is taking that extra FOV into account and providing you with a faster sensitivity to compensate for the higher FOV. This is perfectly normal. If you look at the "actual HFOV" between the two it changes from "106.32" to "121.72". This is the ultrawides additional FOV. That's from my understanding at least.

Any change on getting the ELO sight as a conversion option?

Don't touch the FOV type they're correctly set by default. What you're confusing it with is Aspect Ratio and by extension Resolution. (Some people play CSGO on 4:3 Aspect Ratio). If you just use 1920x1080 on every game you don't need to touch anything like that in the conversion.

You can use it if you want. Just copy that into the calculator and change the setting yourself if you wanna use Vertical. It's up to you which you use. I don't know which is technically the best.

You've been escalated from "Legend" status to "Godlike" status. Thank you!

You absolutely do not need to use the same FOV and Aspect Ratio. The calculator is capable of converting across FOVs and Aspect Ratios... There is a reason they allow you to change those settings in the calculator. Make use of them. Also, drastically changing your XFactorAiming factor will change your Hipfire:ACOG ratio compared to your Hipfire:ADS ratio. It's illadvised to change this too much. Better to increase your AimDownSightsMouse until XFactorMultiplier gets as close to 0.02 as possible.