BattleBit Remastered

1 hour ago, DPI Wizard said:

This is correct, but since there's a huge difference in hipfire FOV (73.74 vs 120), it might throw the feeling off a bit. Remember that the scopes are matched to the 73.74 FOV of CSGO, not BattleBit's FOV. It might not suite the gameplay of BattleBit as much, but if you set the FOV to 74, everything will be pretty much identical.

The end result for the scopes are exactly the same as when using 26, except for as you say Ironsight witch will be very high. The recommended way is using the values from the "All" conversion as that keeps everything matched.

The reason the more powerful scopes all come out to the same value is simply because of the lack of decimals.

Thank you so much for replying and explaining. Is there any way to mitigate the FOV difference issue without changing the FOV down to 74?

I converted my sensitivities from BF5 to Battlebit with the same FOV but sometimes the aim just feels of and I can't put a finger on it. When I flick and aim I should be on target but sometimes I'm just not there. Feels like there is some mouse acceleration but there shouldn't be any. Anyone any idea or experiencing the same regarding inconsistency?

EDIT: Did some research and it might be the insane aim punch the game has.

The aim punch / flinch is indeed awful. Makes 1v1's very frustrating. I hope that gets tamed a little.

On 7/22/2023 at 7:34 AM, DPI Wizard said:

Yes, by using any conversion method other than 360 distance for hipfire, but this will obviously impact how hipfire feel, especially in terms of navigation (i.e. how far you move your mouse to turn around a corner etc).

So would I not be able to retain my 360/in of 17.0455 inches? I attempted to do this and it resulted in wildly different 360/in amounts.

In your original response you said "The recommended way is using the values from the "All" conversion as that keeps everything matched.". Unfortunately, this doesn't seem to be the case, I'm not sure why.

Examples:

• For the 1x Scope Calculation: If "Sensitivity 1: Aim Down Sight Horizontal Sensitivity = "100"", my "Multiplier 1: 1X Sensitivity = "26"". This results in a 360° Distance: "17.3077 inches", which perfectly matches my calculated Hipfire Sensitivity for Battlebit. This is great because it means my 1x (Red Dots) are 1:1 with my Hipfire movement.
   
• But, if I do the "All" calculation, it does not let me enter my own value for "Sensitivity 1: Aim Down Sight Horizontal Sensitivity = "100"" because it itself is a part of the calculation. Unfortunately BattleBit bases all of the scope sensitivity calculations off of the ADS value for Ironsights. So, if I do "All" I get an ""Aim Down Sight Horizontal Sensitivity = "26". 360° Distance: 17.3077 inches"". But, this causes me to get a ""Multiplier 1: 1X Sensitivity = "102" (Short Range). 360° Distance: 16.9683 inches"" This makes my Ironsight 1:1 with my Hipfire, but my 1x is off and different from the "1x" Calculation. All of the other values appear to be the same, such as ""4x (Acog): Multiplier 1: 4X Sensitivity = "71". 360° Distance: 97.5081 inches"" in both calculations. Is this issue due again to the limited rounding in BattleBit, and would there appear to be any practical way to eliminate this issue aside from just compromising?

Thank you so much for your absolutely incredible dedication to this amazing site.

30 minutes ago, DPI Wizard said:

Correct, using a FOV based conversion will result in a pretty huge difference in 360 distance when the FOV difference is so big.

The target for the calculation is 17.0455, so yes this is a limitation due to the lack of decimals. The ADS 360 distance is too long at 17.3077, so for the 1x this is compensated for by increasing the sensitivity to 102. With a proper amount if decimals this wouldn't be an issue.

Thank you for replying again. How would I try to do the conversion not using a FOV based calculation then? What should "Hipfire / Look" and "ADS" be set to? I'm sorry, but the options and how to choose them are confusing for me.

I'm okay with the 17.3077 being off from 17.0455. I just would like for Hipfire/1x to be consistent, primarily. In my original post I also talked about wanting scopes to "feel" consistent across all zoom levels, not have the same 360/in. I think I achieved this by using Monitor Distance - Vertical for Scope Conversion, they feel alright. I think I may just continue using a "Sensitivity 1: Aim Down Sight Horizontal Sensitivity = "100"" so that my 1x is 1:1 with my Hipfire. It's only an issue if I'm using Ironsighted weapons and if I am I can just change it to ""Aim Down Sight Horizontal Sensitivity = "26"really quick.

On 7/24/2023 at 4:08 PM, DPI Wizard said:

You can use Aim Down Sight Horizontal Sensitivity 26 and just set 1X Sensitivity to 100 instead of 102. This will give you the same result

Is there a way I can modify Multiplier 1 in the calculator to confirm this? I tested it in game and it does seem to be 1:1.

I want to have a 1:1 sens in BattleBit (32cm for 360) but it just feels wrong everytime I try to use the calculator

I strongly recommend MDH/MDV 0% as it's mathematically equivalent to scaling sensitivity by zoom level. That's to say if when you ADS everything appears 3x larger, your sensitivity will be 1/3rd.

e.g. with my sensitivity I have 46cm/360° in hipfire. At 71° vFOV the red dot has 1.23546x zoom (tan(71°/2)/tan(60°/2)=1.23546). With the calculator set to MDV 0% it recommends 56.83116cm/360. 46cm * 1.23546 ~= 56.83116cm. Another old example I made for Overwatch: https://imgur.com/a/szjlq

Am 30.7.2023 um 16:32 schrieb DPI Wizard:

1:1 sens is not a thing, you have to choose one aspect of the sensitivity to match.

If you want the same 360 distance, you have to set the ADS and Scope conversion to 360 distance.

But note that this will make the 40X etc completely unusable as they will skip a lot of pixels with the smallest movement, making it practically impossible to aim at anything.

Hey, thanks for your response. I just wanted the 1:1 for the mid range scopes so no worries. Appreciate the help

FYI they added a 12x scope apparently. My 8x and 15x settings are already so close it doesn't really matter to me though.

50 minutes ago, DPI Wizard said:

Which one is that specifically? I haven't seen a 12x yet.

I'm not actually sure  -- I just noticed in the options menu there is a 12x setting.