Jump to content

octiceps

Premium Members
  • Posts

    45
  • Joined

  • Days Won

    1

Everything posted by octiceps

  1. Mouse smoothing is already disabled by default (m_smoothing "0"). m_smooth sets the number of frames, between 1 and 8, that mouse movement is smoothed over, when smoothing is enabled (m_smoothing "1").
  2. Aren't 80 hdeg 16:9 FOV and 65 hdeg 4:3 the same, both 51 vdeg FOV?
  3. Hmmm are you sure about this? Setting m_pitch to double the value of m_yaw makes vertical sensitivity feel way too fast.
  4. Good to know, thanks. So pitch is slower than yaw by default?
  5. After a ~250MB patch on Steam today, setting the sensitivity using the console command now saves, so no more need for the launch option.
  6. Thanks, I figured out the issue. It wasn't working because I had entered another launch parameter as well. Seems the game will only apply one at a time.
  7. Launch option doesn't work for setting sensitivity in the Steam version.
  8. Oof that's annoying. Hopefully this will be patched soon. In the meantime, looks like I will be binding a key to the "m_sensitivity" command.
  9. Is the calculator broken? Changing between All w/ 2x Zoom, 3x Zoom, and 5x Zoom doesn't change Zoomed Sensitivity Scale at all, and converting from hipfire to any of the zooms or vehicle just gives the error "Too high sensitivity 1 - Maximum is 10".
  10. Seems this game is a combination of Overwatch hipfire with Battlefield Uniform Soldier Aiming ADS/scope scaling.
  11. So I'm assuming there's no way to get every ADS to MDH 0% unless they add individual sensitivity sliders a la Insurgency: Sandstorm?
  12. Is the calculator with Uniform Vehicle Aiming on or off? If On, what coefficient should I be using? Here are my calculator settings:
  13. It should be right, assuming you are indeed using 55 vFOV in BFV.
  14. Interesting bug. It seems to show 166.2426 cm regardless of what settings you use in the calculator.
  15. Just curious, what causes this slight discrepancy? Is it due to rounding errors during calculation? BF1 Hipfire to OW Ashe ADS: 51.49 OW Hipfire to OW Ashe ADS: 51.47 BF1 Hipfire to OW Ana/Widowmaker Scope: 37.91 OW Hipfire to OW Ana/Widowmaker Scope: 37.89 I'm assuming the OW Hipfire to OW ADS/scope conversions are more correct.
  16. Hi @DPI Wizard, could you update the calculator to take into account the Metro Mouse Fix?
  17. https://battlelog.battlefield.com/bf4/forum/threadview/2979150494051524581/
  18. On second thought, I don't know what the exact FOV and zoom factors for the different ironsights and scopes on a default config are, so that number is most likely wrong. I'm using cl_ads_fov_scale 0, so ironsights don't zoom in at all, therefore ironsight sensitivity scale is at 1.00 because ironsight ADS and hipfire FOVs are identical. Scope sensitivity scale I also have at 1.00, but I'm using cl_zoom_sensitivity_fov_scope 0, which uses world FOV for sens scaling when scoped (same as RO2/RS/RS2) because I feel that the default behavior (sens scaling using FOV inside scope) is much too slow at the higher zooms. Anyway that's what works for me, instead of overthinking the myriad sensitivities in this game that is a bit of a clusterfuck.
  19. If I'm not mistaken, isn't Uniform Soldier Aiming in Battlefield the same as 75% MM or zoom_sensitivity_ratio_mouse 1?
  20. zoom_sensitivity_ratio_mouse 0.818933027098955175
  21. 1.00 irons is zoom_sensitivity_ratio_mouse 1, which is 75% MM or the same as CS:GO default. Unless you're talking about scoped sens? That's different then.
  22. Just leave it at 1.00 if you want it to feel like CS:GO.
  23. Interesting. That would means the listed zoom factors are inaccurate. tan(90°/2)/tan(46.8°/2) = 2.3x tan(90°/2)/tan(46.8°/2) = 3.3x tan(90°/2)/tan(28.8°/2) = 3.9x tan(90°/2)/tan(18.8°/2) = 6x tan(90°/2)/tan(17.2°/2) = 6.6x
  24. Fair enough, but then the issue becomes that the second zoom level and every other scope feels wrong. What I did was the closest I could find to CS:GO/USA if we ignore the FOV inside the scope.
×
×
  • Create New...