iBerggman

Hipfire is added, aims coming soon!
View full update

I don't currently have access, but will add it as soon as I do!

Name: Arena Breakout: Infinite
Website: https://store.steampowered.com/app/2073620/Arena_Breakout_Infinite/
https://www.arenabreakoutinfinite.com/en/
Status: Closed Beta
Release Date: 5/8/24 (Closed Beta); Full Release TBD
Availability: Free

@DPI Wizard Would it be possible to add the Bow and Musket aim as a calculator option so you could sacrifice "hipfire" sensitivity for a more accurate aiming sensitivity?
 

Thought I'd post this in case anyone else needed the config key value for mouse wheel scroll up/down since the in game control menu doesn't seem to pick up the scroll wheel inputs:
Go to the Input.ini (Path:%LOCALAPPDATA%\Witchfire\Saved\Config\WindowsNoEditor\Input.ini) and chance the "Key=XXXXXX" of the actionmapping you want to "Key=MouseScrollDown" or "Key=MouseScrollUp".
 
For example I wanted scroll up to select my primary and down for secondary:
ActionMappings=(ActionName="PrimaryWeapon",bShift=False,bCtrl=False,bAlt=False,bCmd=False,Key=MouseScrollUp)
ActionMappings=(ActionName="SecondaryWeapon",bShift=False,bCtrl=False,bAlt=False,bCmd=False,Key=MouseScrollDown)

Name: Witchfire
Website: https://store.epicgames.com/en-US/p/witchfire-db273e
Status: early access
Release date: Not confirmed
Availability: (Free)

The problem is that it's not only the armor that affects sensitivity, different guns also have varying ads sensitivities with smgs and high powered scopes generally being a lot faster than rifle ironsights so with the current settings there's really no viable way of dealing with that. If it was only the armor I suppose you could get around it by calculating how the turn rate reduction affects cm/360 but that's not going to be enough if you use a loadout with say a 1x AK and a scoped Mosin since there's no way to deal with that difference.
It probably won't get changed either because every time someone bring it up the thread is filled with "muh realism" so we'll just have to find a way to deal with it.
 

I tested a bow and a musket now, and the sensitivity and FOV is exactly the same. The camera just moves a bit closer when aiming. Unless there's other bows or muskets that actually zoom there's no need for a different calculation.

Are you kidding me? For every game I need to:
Buy it (if not free) Download it Potentially play a bit Analyze movement Reverse engineer sensitivity formula Measure FOV/reverse engineer it Analyze potential aims and reverse engineer them Potential issues with acceleration/smoothing or similar needs to be worked out or worked around and so on Then it needs to be tested and verified to work as intended with The calculator Different DPIs Different FOVs Reporting rates Resolutions Aspect ratios Windows settings and so on. Adding a game can take anywhere from a few hours to many days. It's a bit more work than adding a game name to the calculator... And premium members usually gets priority.

https://www.nexusmods.com/cyberpunk2077/mods/1065
use this mod if you want the same zoom level for all scopes. makes things more consistent.

Updated now! FOV was a bit wrong too and fixed now, it's actually a vdeg multiplier and not hdeg 4:3 as the devs said a while ago (they said it's the same as CSGO).
The new 2.5X is identical to 3X as far as I can tell. Scopes do vary in power depending on the weapon though.

The best thing to do really would probably be to compile a proper write up on how a monitor match/usa system could be implemented complete with the explanations for why it works as well as formulas required for the coding and post it to reddit and hope it gains traction there. Honestly, I'm not sure they're even aware there's a "correct" way to scale the sensitivity based on fov. I've only really been following the development of the game since I started playing in December last year but I've noticed that proper well written/thought out suggestions on reddit tend to get noticed fast by the devs and often make it into the game.  If anyone has too much spare time there's a project for you to take on 😅

I don't know if this is directed at this site and me or the devs of the game, but when they do a full wipe and change everything requiring a quite dedicated grind to get everything back AND analyse it... It will take time. There's over 500 games here now, imagine just a fraction of them doing this. While this game is quite popular, putting everything aside to grind on a single game is not feasible. If you have any anger direct it at the devs of Tarkov who seemingly have no idea how to implement aim and scope sensitivity.
Even if we get every calculation figured out now, it might change next week. Accompanied with a new wipe... A game in development is fine, but in a game where aiming is a key component they should get aiming figured out way quicker than this.
It's not that hard. You either add sensitivity for each available scope power, or you add a scaling that is linked to the scope FOV. Right now they have scopes with identical FOV that have different sensitivity. This makes absolutely no sense, and it seems like they are just randomly assigning sensitivity to scopes.

Patch 0.12.5 is being installed right at this moment, it apparently contains fixes to the sensitivity of scopes, mainly better sensitivity support for sights with multiple zoom levels. 
Might be a good time to check the Valday and Eotech Vudu 1-6 scope if you have access to them since those are probably the most used ones. @DPI Wizard

Is 0.41 your in game sensitivity? In that case you should put that in the multiplier 1 input box instead. Sensitivity 1 is the option to account for the total turn speed reduction of the armor/helmet/backpack you use. 
Also, DPI Wizard will have to clarify how it works but since the sensitivities in eft are all over the place you might want to pick one to use as the base just to be sure instead of All since the conversion can only be correct for one of the sights anyway. 

Theoretically stable frametimes should be better for aiming due to it being consistent but I don't have any scientific proof for it, you also have to consider that the overall responsiveness could be (slightly) lower compared to uncapped however as long as the framerate is close to 240 I imagine that it should be fairly marginal on 240hz , compared to 144hz anyway. I think Battlenonsense referred to some test/study in his video on frametimes so that might be something to look into.
But honestly I don't really know much about 240hz, on 144hz I definitely prefer uncapped over 140fps + Gsync on 144hz 1440p just because it feels more responsive, I've been wanting to try 240hz but I wouldn't really want to trade my 1440p for 1080p and there's no way I'd go with 1440p 240hz since 144fps is already hard enough to achieve. 240hz + Variable refresh sync seems like it would be pretty nice though.

Fixed! Yes, I'll try to get a 1x next.

I've noticed, and I'll revisit it now. I'll play a bit and see if I can make some sense of it all

I think the little bit of extra zoom independent gives you could be beneficial, usually I tend to prefer affected since the zoom can be a little jarring however I feel like the game is slow paced enough that it isn't really an issue. The ads time is so slow anyhow that you're not going between hipfire and ads as much as in previous games.
I've been playing a lot of gunfight so I've been using independent since I feel it's easier to get headshots with weapons like the ironsight k98 although I'll probably be going back and forth a bit before I can make a final decision. 

Just tested it now, and it's the same

What is this netcode though? Feels like Ironsight all over again?

You got to realize that the amount of people that actually care enough about their sensitivity to want separate sliders not to mention proper decimal support is minuscule at best so I don't think the developers necessarily even realize it's something people want or need, I mean you only have to check the steam forums to find lots of people that think editing config files is cheating... Warframe comes to mind as well, pretty much since release some people have been asking for a better sensitivity range but it's always met by a flock of people stating that they don't have a problem at whatever dpi. I don't really get it but that's what we're dealing with here.
 It's definitely getting better all the time though, a year or two back the only games that really had separate sliders for everything were Battlefield and PUBG but now I can already think of at least double that of the top of my head so realistically it should become the norm as more and more people get used to it and start expecting new games to have it. It would probably be a good idea to try to get influencers that are in direct contact with different developers to really emphasize that separate sliders, field of view sliders as well as a proper sensitivity range with decimal support should be the bare minimum for PC games, (first person) shooters especially.

It maxes out at 135, and while ADS is affected by FOV change, scope is not. All updated now

ADS added as well, scope next!
0 is quite high, but far from the worst I've seen. The game has ADS and scope sensitivity too. No FOV option though, locked to 90 hdeg.

You can see the FOV slider in this clip from Dr DisRespect's stream -