Scca Posted January 6, 2022 Posted January 6, 2022 Hellow :3 Since I was about to make a topic about FOV I wanted to ask how necessary actually conversions from a game to another actually is if the target FOV is the same. Set auto-FOV to a desired number and know the cm/inch for a 360° from the game that you want to convert from, an actual conversion shouldn't be needed if I am correct. Simply put the desired numbers in the Calculator Settings like usual, and then put the game you want to convert to in the "convert from" section with the "Convert from Sensitivity" option in the calculator settings. That way you could skip the "Convert to" section and just leave it empty because the results would be the same either way, just less effort, unless I am overseeing something.
TheNoobPolice Posted January 6, 2022 Posted January 6, 2022 Games have different yaw values, so although you wouldn't need a different 360 distance if it's the same FOV, you still may need to know the value as games rarely expose their yaw value or sens formula to the user.
Wizard DPI Wizard Posted January 7, 2022 Wizard Posted January 7, 2022 4 minutes ago, Silbesco said: Set auto-FOV to a desired number and know the cm/inch for a 360° from the game that you want to convert from, an actual conversion shouldn't be needed if I am correct. It's still a conversion from distance to a usable sensitivity value, both (converting from a game and converting from a distance) are essentially the same in the calculator. Both require a reverse-engineered formula to calculate the sensitivity.
Scca Posted January 7, 2022 Author Posted January 7, 2022 (edited) 10 hours ago, DPI Wizard said: It's still a conversion from distance to a usable sensitivity value, Well yeah, it was a poor choice of words for me to say that "no conversion" should be needed. It's obviosly still one even if you don't convert from a game to another. But what I mean is that you don't need to input 2 games in the calculations, but only the game you want to convert to if the cm/inch for a 360° rotaion is known and auto-FOV on. So the two ways of calculating my sensitivity for Battlefield 4 that are shown in the attached picture should get the same results no matter what game is used in place of BF 4. Edited January 7, 2022 by Scca
Wizard DPI Wizard Posted January 7, 2022 Wizard Posted January 7, 2022 38 minutes ago, Scca said: So the two ways of calculating my sensitivity for Battlefield 4 that are shown in the attached picture should get the same results no matter what game is used in place of BF 4. Correct, as long as both games support the same FOV. If you can't match the FOV because it's locked or out of range, then the ADS and scope calculations will be different.
Scca Posted January 7, 2022 Author Posted January 7, 2022 (edited) 54 minutes ago, DPI Wizard said: If you can't match the FOV because it's locked or out of range, then the ADS and scope calculations will be different. What would be the preferred calculation method in that case? Still use your preferred game as a "host game" (in my case always Apex Legends) and convert it to whatever game has a locked FOV, or just put whatever that game might be right in the "convert from" section and use the results made with the calculations from the calculator settings? Or just unmatching FOV in general. Sometimes you may not want to match the FOV's of two games because of preference even when it is advised to match them. Edited January 7, 2022 by Scca
Cannon Posted January 7, 2022 Posted January 7, 2022 MDV/MDH 0% if you are coming from apex. 1 ADS in apex is = 0%
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now