Jump to content

DPI Wizard

Wizard
  • Posts

    18,155
  • Joined

  • Last visited

  • Days Won

    1,764

Everything posted by DPI Wizard

  1. Then go for 110 in 4:3
  2. It depends on what you want achieve, Hdeg 4:3 110 will calculated the FOV to be 110 for the 4:3 portion of the screen (making the 16:9 FOV 124.59), while Hdeg 16:9 will calculate 110 for the full 16:9 portion. In both cases it's important to check the output for the Config FOV you need to configure to get this FOV in the game. This is crucial for the sensitivity calculation to be accurate.
  3. Correct, but only if you play stretched. If you play with black bars your should enter your monitors native resolution.
  4. ADS is added now, it scales to MDV 100%. Updated the sensitivity, it was indeed outdated. Also added in-game sensitivity. And you are impressively close, the correct value for 23 cm with 1000 DPI is 0.262835 (assuming the sensor is 100% accurate ofc)
  5. The DSR scope you get when starting a sniper match is what I've used. I haven't unlocked anything, not sure if I have access to more scopes? Either way I slightly updated it now as the FOV was off by a little bit.
  6. The FOV Type is referring to the kind of FOV the game uses, it's not related to your aspect ratio. If you play with a 4:3 resolution, set the corresponding resolution in the calculator. The FOV you use should be entered as it is configured in the game with the default FOV Type unless you want to convert from another type.
  7. Viewmodel FOV is as you say only the render FOV for the weapon etc. If you check the output for CSGO you'll see that the config FOV is fov_cs_debug, which does change your FOV. But it only works with sv_cheats enabled or playing on a server with cheats. If not, then 90 is the only correct value as the game will be locked to this.
  8. Can you post an image of your calculation?
  9. I'm getting the same behavior in both.
  10. Indeed!
  11. Like this, note the conversion setup for ADS and scope being MDV 133, this is to match 1.33 coefficient.
  12. Strange, it actually feels ok here now. Nothing like a good FPS game, but miles better than at launch.
  13. The latest updates seems to have fixed any deadzone issues and smoothing as far as I can tell. Is your smoothing off?
  14. It's not a bug, it changes because the in-game calculation assumes you have not touched the config file (so the multipliers are both 0.02), while the config file calculation calculates the multiplier based on you sensitivity 1, 2 and multiplier 1 input. The end result is almost the same as you can see in the 360 distance, but the config file is more accurate since it has more decimals.
  15. If this exact example is the reality, then you need to measure the cross hair to edge distance and extrapolate how many percent 2 cm is of this. For instance for a 27" 16:9 monitor this would be just shy of 30 cm, so 2 cm would be 6.67%. So by using MDH 6.67 you would then make sure that the movement to this exact spot is equal between all aims and games. But do note that a lot of games have limitations in their sensitivity precision making exact matches impossible.
  16. This is the tracking speed of the cross hair (MDH 0%), so there isn't really any distance, but rather a constant speed:
  17. If what you're aiming to do is to set up Kovaak's to mimic your ACOG, you should do like this: Set the FOV Measurement to Vertical 1:1 and FOV Type to Vdeg, then enter the Actual VFOV from R6. This way the Kovaak's FOV matches the R6 ACOG FOV. Then change the Sensitivity Scale to R6 and see what the calculated sensitivity is. PS, this assumes your ACOG sensitivity is "Mouse Sensitivity Horizontal 14" and "Aim Down Sights 50" as in your screenshot.
  18. The FOV you configure in BFV is always vertical degrees, so Vdeg is automatically selected. But the horizontal FOV shown in-game is not the Actual HFOV shown in the output unless you have a 4:3 resolution
  19. Added a bunch of iron sights now
  20. I'm not seeing any difference, is if off for hipfire or ADS for you? Or both? Are all curves set to 1 and of course smoothing and acceleration off? Also what settings are you using, and what is the experience compared to the calculation?
  21. The horizontal FOV shown in-game is Hdeg 4:3 (same as in CSGO etc), not the horizontal FOV for your resolution. If you switch to Hdeg 4:3 in for the FOV Type you'll see that the FOV value shows about 86.
  22. Like this would be the best. MDH 75% is the same as zoom sens 1, this is achieved by setting the coefficient in MW to 1.33. The FOV is matched by setting it to 106.26. If you don't play in 16:9, change the values accordingly.
  23. It should be correct then. But I'll add a separate hipfire calculation soon for modified FOV so it can be calculated
  24. The calculations are correct, but note that you can't actually change FOV in CSGO unless you have sv_cheats enabled offline or play on a server with cheats enables. Also zoom sensitivity actually affects hipfire when changing FOV, so if you do have cheats enabled and change FOV, the calculated 360 distance is only correct if the zoom sens is 1.
×
×
  • Create New...