BattleBit Remastered

Hello,

i dont understand how to convert the fov.

I have 110 fov in Hunt Showdown, i now want the same fov in Battlebit.
 

From every calculation I make it comes out complete nonsense, I also do not know which paramater I have to set.
I have also read through the tutorial and now somehow know even less than before.

Thanks !

i managed now to convert fov and all aim settings.

Im really amazed tbh, its now feels exactly like Hunt, Flick Shots on Point !

I used same sens for "Aim Down Sight Horizontal Sensitivity", if thats correct.

Hi just a quick question,

I have configured my hunt settings to match up to battlebit but the ads speed doesnt feel like 0%MM more like 100%, can you have a quick look over my conversion and see if it is correct

Thanks

Hi, I'm trying to convert here and the hipfire 360 is about 8 inches off using these values? 

1 hour ago, DPI Wizard said:

Hipfire should be spot on here, are you sure your mouse driver doesn't load a different DPI profile or something when starting Battlebit?

Yeah, it was one of the first things i checked, still 7 or 8 inches off

I think there is a a weird calculation in battlebit itself because my iron sights are unusually high compared to using any red dot where it feels normal and I think it has to do with my dpi being 4000.

19 hours ago, DPI Wizard said:

You are comparing the hipfire of Valorant with the hipfire of BattleBit, correct? Have you set all the calculated values in the BattleBit config? You should set Aim Down Sight Horizontal Sensitivity to 80 to match your calculated Mouse Horizontal Sensitivity btw, not have it set to 100.

yeah, I read the other posts, changed it from 100 to 80. I've verified I'm using the correct values in Valorant and also battlebit. Still is 3-4inches off.

Edit: the size it was off actually went down without me changing anything except scoped sensitivities which shouldn't effect hipfire

48 minutes ago, DPI Wizard said:

Can you link the conversion and let me know exactly which aims are slow/fast?

my bad I haven't tried the new calculation method for battlebit so idk if it still happening but I'll get back to you if I still got problems

1 hour ago, DPI Wizard said:

But you are comparing hipfire to hipfire, correct? Have you tried to verify the 360 distance with scripts?

I am, im just doing it with a ruler right now, but I can do a script at some point if you like.

1 hour ago, DPI Wizard said:

But you are comparing hipfire to hipfire, correct? Have you tried to verify the 360 distance with scripts?

I figured it out, im a complete moron and this is user error only, sorry, forget I existed please.

I don't know if the issue on my hand but I can't modify the ADS sens in the calculator. When I first used it 2 days ago I could put a different ADS sens (I let it at default 100, it was under multiplier 1) and hipfire sens (I use 75), but now when I use it and put my hipfire sens (75) the ADS sens is automatically the same value as the hipfire (so 75 in my example and multiplier 1 is greyed out).

ADS Horizontal/Vertical should be set so that "1x Sensitivity" is 100. Iron sights have the same FOV as 1x sights as far as I can tell but they just use 100% of ADS Horizontal/Vertical and not 1x Sensitivity.

Pretty frivolous question - but I always based my sens off overwatch do these values for battlebit make sense? I'm happy to just trust but how are Aim Down Sights sens 45? I just recently came back to the sight and I noticed inputting the same values I had maybe two weeks ago, all my sens have lowered slightly basically across the board for scopes and I believe my aim down sights went up. Did something change?

Also this is one of my only posts but I gotta say this website is an unreal service man thank you so much for this work. I had been doing this sort of shit with rulers FOR years until I saw this website, immediately bought a lifetime membership such a great product.

5 minutes ago, DPI Wizard said:

There's been an update recently, mentioned just above your post: 

In the previous version when the game was analyzed, ADS and Ironsights shared the 1x setting. Since it's separated now, it affects all calculations.

Do note that the old calculations were correct for everything except ironsights, and now that Aim Down Sight Horizontal Sensitivity is linked to ironsights it changes all the other values accordingly.

In short; all values will be updated compared to your old calculation, but in effect everything will be the same as before since they account for the change in the ADS sensitivity which only affects ironsights directly. Previously ADS sensitivity had no direct affect on any aim, so it was treated like hipfire, and all the scopes were based on this. But now since ironsight is affected by it, it changes the source for all other scopes.

thank you for the clarification and apologies for missing such a obvious change. thanks for keeping everything updated and hope you have a great weekend you absolute legend

Hey, I've been a long time fan of the site and have used it for many games, I'm having some trouble though. I've read the Instructions and this more detailed description of Conversion Methods, but I'm still not sure if I'm doing things correctly. I'm wanting to convert my Sensitivity from something like CS:GO or Overwatch, to BattleBit. I've h ad the same problems in the past with games like PUBG, Battlefield: 4, BF1, games with different Scope Zoom Levels, FOVs', Scaling. I understand from personal experience and this post that taking the raw hipfire 360/in and applying it across all scopes will make higher magnification scopes extremely sensitive. What I think I want is for all of the Scopes to "feel" the same, either physical distance, or maybe viewspeed wise? The information and discussions in Skidushe's post helped me understand more about the conversion methods, but I'm just wanting to make sure I did it right.

My 360/in is 17.0455 inches, I use a DPI of 3200.

I'm using my "Distance" as my Conversion Source. "Hipfire/Look" is set to "360° Distance"; Windows / 2D is set to Monitor Distance - Horizontal with "0%". I'm using 360° for ADS; and, Monitor Distance - Vertical with "0%" in the first box, and "100%" in "Scale".

• Source Game: Counter Strike: Global Offensive - Hipfire
  • Sensitivity 1: Mouse Sensitivity 0.30
    • 360° Distance: 17.0455 inches
    • Discrepancy: -0.0003% (-0 inches) - DPI for 0%: 3199.9904 (Multiplier 0.999997)
    • Pixel ratio: 0.0829 pixels/count
    • Actual VFOV: 73.739795 degrees

• Convert to: BattleBit Remastered - All
  • Mouse Horizontal Sensitivity 13
    • 360° Distance: 17.3077 inches
    • Discrepancy: 1.5385% (0.2622 inches) - DPI for 0%: 3249.232 (Multiplier 1.015385)
    • Pixel ratio: 0.0354 pixels/count
    • Actual VFOV: 120 degrees

• 1x: 102
• 2x: 73
• 3x: 72
• 4x-40x: 71

Is this correct? It doesn't really feel right but it also doesn't feel bad? It seems like there should be more variance.

When I do the conversions for the scopes individually it defaults "Vertical Aim Down Sight" to "100". If I don't enter "26" manually, or verify "100" is being used, I get different values. These values also don't feel quite right but don't feel bad, either. There is still a lack of variance at the different magnifications. Doing the cconversions this way also results in my Ironsight Sensitivity being extremely high because it is tied to "Vertical Aim Down Sight" to "100". I'm fine with this if this way is more accurate for what I'm wanting because I hardly ever plan to use Ironsights, and if I want to I can change it to "26".

• 1x: 26
• 2x: 19
• 3x: 19
• 4x: 19
• 6x-40x: 18

I know this is a lot of information and I'm sorry if it complicated things. As I said before I'm just wanting all the scopes to "feel" right at tracking. Like in this video? I think.

Here's an image showing my setup for these conversions when converting to "BattleBit Remastered - All":

Thank you so much to anyone who can understand and help. And thank you to the amazing people who have worked so hard to put this incredible site together. I wish I could afford an outright Lifetime Membership.