MutedNzky

(sorry for the late reply) would you mind elaborating? I'm aware that my current sensitivity values between the two games are different. The battlebit settings are the ones that I found through experimentation and felt close enough. Running those values through there is a major discrepancy in the calculated values. Based off your explanation and what I'm understanding, I need to change my Battlebit FOV. How would I go about calculating what FOV I need to run in order for my sensitivities to be the same?

Sure thing. The First link is from Siege to Battlebit, the second is from Battlebit to Siege (ignore the scope values for battlebit to siege, I primarily use 1x so the other values are filler) https://www.mouse-sensitivity.com/?share=7ce63dbab06005647097551cc6e2f009 https://www.mouse-sensitivity.com/?share=f438839deb090e6ebc2d73bb7b13a5a5

I gave it a shot and things still feel a little funky. I tried it going from siege to battlebit, and then I reversed it for battlebit to siege. I originally assumed that the discrepancies in the hipfire values were affecting the ads more than expected. However, when I tried to go from my current battlebit ads to siege, the calculator completely changed my ads values. I currently play 102 h/v hipfire with 100 h/v on ads, with my 1x on 71. Imputing that into the calculator spits out the h/v ads as 74 and the 1x as 100. Any idea as to what's going on?

I've been trying to get my ads sens from siege to translate over to battlebit and I can't seem to get it right. I've tried multiple different configurations and the ads always comes out far slower than expected. Any help would be greatly appreciated

Assuming you're playing 90 FOV, the values would be 58 98 100 102 103 104 105 161. If not to to 6sads.netlify.app and put in 83 for your old ADS sens and your current FOV. That should get you the closest to 1:1. If it still feels off, you can change your ads multiplier to 0.01 in game files to get half value increments.