Frank3XD

Everything. I'm partially wondering if it's input lag I'm feeling and changing the fov is offsetting that "feeling". I know apex really hasn't done much towards optimization. Edit: Removed the stuff about input lag because I'm pretty sure that's not the case.

Sorry, I got tied up and forgot about this thread. I appreciate the explanation on how you calculate all of this. At the moment, I don't really have anymore input, but I will test some other stuff later. I'm very curious as to why setting the FOV to what the calculator says throws my aim off so much even if I set the fov and sensitivity the same as the other games I play. It's not just like "bad aim". I can feel that it's off and it's really annoying. As soon as I use my method for calculating FOV, my aim feels perfectly fine. Which is weird because will all the other games I play, mouse-sensitivity calculator works like a charm and my aim feels perfectly transferred.

I'm not sure how you do this but if you could explain or link me to a post that explains how do you measure the FOV? And also how do you compare FOVs across games to say they're both say, 90 4:3 FOV? Also, I'm pretty sure the in-game representation of 4:3 FOV is correct. The only "incorrect" thing about is that it rounds its FOV display value to the nearest whole number when you edit the config file. That's why the game says 90 FOV at it's default value because the actual 90 4:3 FOV multiplier value is 1.275. The whole reason I'm sure is that my friends, and I have used mouse-sensitivity for a while to do conversions and it's great. It has always been perfect, but this game it isn't. So it bothered me. When they use my FOV conversion they said their aim feels good now, but when we use the one on the calculator it feels terrible.

I'm pretty sure whatever conversion is going on for between "Hdeg 4:3 fov" and the APEX legends FOV multiplier is wrong. I believe this is the correct formula for Hdeg 4:3 to multiplier conversion: 1 + ((x - 70)*(0.01375)) where X is the Hdeg 4:3 fov value you want Why do I think this is correct? My aim always felt off using the current settings the calculator gives so I knew something was wrong. First, I confirmed that the mouse sensitivity calculations were correct by using an autoit script to do 360, and the calculations are correct so I knew it had to be FOV issue. Next, I realized that the in-game FOV slider is moving the multiplier by a constant value (0.01375 per 1 FOV). Which means if you manually set the FOV config multiplier value in the profile.cfg file, it will be moving at that constant when you move the slider. After that, I realized that 70 fov in game will always set the cl_fov value to 1. I concluded this a "0 point" I can use and that moving at increments of 0.01375 per 1 FOV will yield the proper HDeg 4:3 FOV because it is based off the source engine. Sure enough, when I did the calculations and set FOV to the proper FOV that I normally play on other FPS games (86.6 HDeg 4:3 FOV), my aim felt normal again. Here's a JScalc I made for people who are lazy to do math: https://jscalc.io/calc/sjaxm3vHaXvjqmf5