Leaderboard

Here's a full comparison between BFV and BF 2042 scopes (10x missing on BF2042, working on it!). These are the base values showing the true optical zoom, those under 3.00x will be affected by ADS FOV on/off. BFV are using the actual optical zoom for the scopes. BF 2042 uses seemingly arbitrarily assigned values, but they almost line up on a linear axis. Scope Zoom BFV Zoom BF 2042 1.25 1.250 1.710 1.50 1.500 1.997 2.00 2.000 2.586 2.50 2.500 3.188 3.00 3.000 3.793 3.50 3.500 4.405 4.00 4.000 5.016 5.00 5.000 6.00 6.000 7.482 7.00 8.711 8.00 8.000 9.950 10.00 10.000 12.420 12.00 14.907 Edit: 10X scope added!

I probably should pipe up on this one since the concept is originally mine... but I never could get the math right and eventually decided not to bother, so I'm glad you've made some effort, Jedi. The concept with this is simple: if you're using some monitor distance, it's always going to be wrong everywhere but one place, so let's just minimise the error overall, right? But it's not so simple as splitting your 0% and 100% distances (averaging) because it's nonlinear. That's where the math gets fun. It's not totally hard math but it's not garden variety either Then it gets saucy when you realise there's a difference between minimising error magnitude (how wrong is it, 1 dimension) and error volume (how much of the screen is wrong and how wrong is it? 3 dimensions....) Reason I decided not to bother in the end was because, put simply, the more I brushed up on my calculus (it's been a long while) the more I realised that 0% was 'the way'. Buuuuut, back then I was completely focussed on in-game matching, and cared not for the desktop. And I had the same experience as you, jedi: I'd leave game from flicking to heads like it was easy and I couldn't flick to an OK button or a text box if my life depended on it. And I don't know about the rest of you, but I use the windows desktop a LOT. More than I do 3D gaming, such is life. As far as I can see it, if there's any value to maintaining sensitivity between games and zoom levels, there is that same value in maintaining it to the desktop. Trouble is there's absolutely no way you're matching the desktop to any more than one FOV. So you've definitely got to pick one. I tend to play the same kind of games so my hipfire FOV is always the same and it's not an issue for me: match desktop to my standard hipfire, then 0% from there in the 3D world. But for people who don't have a standard hipfire, I'm not sure there's any way to extract any benefit in matching to desktop at all. And then there's the million dollar question of what defines desktop speed in the first place. 0%? 100%? Horizontal? Vertical? Fight! And the very real consideration of how far we are from the monitor/monitor dimensions, which matter less in the 3D space, but actually help to answer the above question, in a 2D space. Welcome to my years-old rotting can of worms.

Ideally, I feel it would be an improvement that when the website is expanded on the desktop to sufficient page width, that the "Game Info" data could be shown along side the "Calculations", rather than underneath. Apologies if there is a way to do this already I have missed. This would make it much easier when entering many values into a new game that uses config files where you don't know where to paste the values yet, and / or to quickly gather information without lots of scrolling up and down all the time. Rough mockup in paint:

I guess "zoom percent" is rarely intuitive for gamers anyway. You could mean different things by a "2x zoom", you could literally cut the vertical FOV in half, but then any object at the centre will be 4x larger in area as it's a 2D image, so I would say the better way would be to calculate using the square root of the width and height, so any object in the centre would be double in area. This then of course means that you still would not get a 40 vertical FOV, when zooming in "2x" from an 80 vFOV which would still boggle peoples minds. So in once sense I kind of understand why the devs may just freely move the zoom by hand in dev tools, and then say "lets call that 1.25x" because with the map sizes in 2042 and engagement ranges, it makes sense to have lower aimed FOVs. Also, since the game has legacy gun stats in portal, using BF3 guns at an aimed FOV equivalent to high hip fire FOV's would result in practically zero perceived pitch/yaw recoil, I guess the devs felt they would be too easy to manage since those gun stats were originally designed with a fixed FOV in mind. Not that I think that's important, Halo has zero camera recoil on many guns and they feel a ton of fun to shoot. I personally preferred the BF1 approach where you could just tune the ADS FOV by preference.

There are separate Hipfire Pitch and Hipfire Yaw calculations which have this. This is done to make it as accurate as possible when using the limited in-game sensitivity, but it should say in the game notes that the Hipfire calculation assumes default yaw and pitch values, I'll fix that!

ADS FOV is bugged (or works differently by design) in BF 2042, so you can't use the same settings as in BFV. If you have both USA and ADS FOV Off, you should turn USA on and set it to 100 in BF2042 to match BFV. Try that and see if it helps

There's a bit of an issue with the alignment though, since the game info needs to align with the game if side-by-side, and be pushed down and ignore the alignment if the resolution is not wide enough. But I'll find a solution eventually

I'm actually working on exactly this, it should be ready for the next version.

Name: Super People Website: SUPER PEOPLE on GeeGee Status: closed beta Release date: tbd Availability: currently invite only