Just added!

View full update

Thanks! But no difference between first and third person or am I missing something?

7 minutes ago, PepperForASalt said:

Thanks! But no difference between first and third person or am I missing something?

No difference, same FOV and 360 distance for both perspectives.

just tested it, I think the 360 distance doesn't exactly achieve a proper 360 degrees distance. in my own setting: 19600px is what allows me to hit the close approximation.

5 minutes ago, AL2009man said:

just tested it, I think the 360 distance doesn't exactly achieve a proper 360 degrees distance. in my own setting: 19600px is what allows me to hit the close approximation.

What value are you using, and how are you testing? Note that there will be negative acceleration if the testing method is too fast.

9 minutes ago, DPI Wizard said:

What value are you using, and how are you testing? Note that there will be negative acceleration if the testing method is too fast.

naturally, i use Steam Input and set "Camera Turn" action (set to 360-degree turn) as I was calibrating it manually.

in-game sens is set to 10 (Normal Gameplay only) across both Leon and Grace and both perspectives. for Grace's first person: I had to increase it to match Leon's.

edit: turns out, While Aiming sens functions thte same as Normal Gameplay sens

Edited February 27Feb 27 by AL2009man
added While Aiming, as both Camera modes are 1:1 sens wise

I’m not doing any formal testing or measurements, this is just based on feel. I’m converting from 40 cm/360, and the suggested values (11 for normal gameplay and 6 for aiming) do not feel close to that in Grace’s first-person camera. It feels noticeably slower, more like around 50 cm/360.

53 minutes ago, AL2009man said:

naturally, i use Steam Input and set "Camera Turn" action (set to 360-degree turn) as I was calibrating it manually.

in-game sens is set to 10 (Normal Gameplay only) across both Leon and Grace and both perspectives. for Grace's first person: I had to increase it to match Leon's.

edit: turns out, While Aiming sens functions thte same as Normal Gameplay sens

While aiming has a different FOV, but the sensitivity, i.e. 360 distance, is the same.

17 minutes ago, eggpoop said:

I’m not doing any formal testing or measurements, this is just based on feel. I’m converting from 40 cm/360, and the suggested values (11 for normal gameplay and 6 for aiming) do not feel close to that in Grace’s first-person camera. It feels noticeably slower, more like around 50 cm/360.

Just tested again now, and the calculations are correct. However I have not tested above 1000 Hz. Also note that these kind of games might change sensitivity and FOV during gameplay, I will play further and test if this is the case.

12 minutes ago, DPI Wizard said:

While aiming has a different FOV, but the sensitivity, i.e. 360 distance, is the same.

Just tested again now, and the calculations are correct. However I have not tested above 1000 Hz. Also note that these kind of games might change sensitivity and FOV during gameplay, I will play further and test if this is the case.

I tested the polling rate change you mentioned by dropping from 4000 Hz to 1000 Hz, but it didn’t feel any different, so I went back to 4000 Hz. The settings that actually match my muscle memory are the 400 DPI values even though I play at 800 DPI: 17 normal and 11 aiming. I do a lot of 360s in-game just to show off, so I can tell quickly when the sens is off. These feel close (maybe slightly faster), but they’re way closer than the converted 11/6.

9 minutes ago, DPI Wizard said:

While aiming has a different FOV, but the sensitivity, i.e. 360 distance, is the same.

Just tested again now, and the calculations are correct. However I have not tested above 1000 Hz. Also note that these kind of games might change sensitivity and FOV during gameplay, I will play further and test if this is the case.

Like @eggpoop, the calculation I get is much slower than my normal 58 cm/360, with both normal gameplay and when aiming. I've double-checked my calculator entries, tried both 1000hz, 500hz and different DPIs, with all acceleration and deceleration set to 0.

2 hours ago, AL2009man said:

naturally, i use Steam Input and set "Camera Turn" action (set to 360-degree turn) as I was calibrating it manually.

in-game sens is set to 10 (Normal Gameplay only) across both Leon and Grace and both perspectives. for Grace's first person: I had to increase it to match Leon's.

edit: turns out, While Aiming sens functions thte same as Normal Gameplay sens

55 minutes ago, eggpoop said:

I tested the polling rate change you mentioned by dropping from 4000 Hz to 1000 Hz, but it didn’t feel any different, so I went back to 4000 Hz. The settings that actually match my muscle memory are the 400 DPI values even though I play at 800 DPI: 17 normal and 11 aiming. I do a lot of 360s in-game just to show off, so I can tell quickly when the sens is off. These feel close (maybe slightly faster), but they’re way closer than the converted 11/6.

53 minutes ago, trackm said:

Like @eggpoop, the calculation I get is much slower than my normal 58 cm/360, with both normal gameplay and when aiming. I've double-checked my calculator entries, tried both 1000hz, 500hz and different DPIs, with all acceleration and deceleration set to 0.

I'm getting consistent results here, there might be a setting that affects things. Note that the sensitivity values will change when you change perspective.

You can use REFramework nightly releases to adjust FOV (and disable vignette)

https://github.com/praydog/REFramework-nightly/releases

click "Show all 19 assets", "RE9.zip"

*Also worth noting, ticking "use custom global FOV" under camera makes it so that the FOV is the same at all times, even when aiming down sights and such

Edited February 28Feb 28 by spyder256

Okay so turns out with the Nightly version currently you get massive random stutters

However there's this "FOV only version" that seems to work fine, until the main is updated

https://github.com/BlueCookieWookie/REFramework_RE9_FOV_HOTFIX

17 hours ago, DPI Wizard said:

No difference, same FOV and 360 distance for both perspectives.

An update here, the FOV is different for 3rd person for the most part, so I've updated it. Also moved the calculations to a lookup table since the scaling is broken, which means they are 100% accurate but certain features like discrepancy won't work.

Please update the calculator for REFramework's custom FOV fix 🫶

Better yet, using this mod (still requires REFramework) lets you set custom FOV for hipfire and ADS in both first-person and third-person without messing up cutscenes!

Edited March 2Mar 2 by Rukishou

On 3/2/2026 at 2:21 PM, Rukishou said:

Please update the calculator for REFramework's custom FOV fix 🫶

Better yet, using this mod (still requires REFramework) lets you set custom FOV for hipfire and ADS in both first-person and third-person without messing up cutscenes!

Support for this is added now.