Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 07/10/2024 in all areas

  1. Just for hipfire (and in some cases maybe ADS), but scopes should use one of the other conversion methods that are FOV based. The conversion methods are explained here
    1 point
  2. It's showing you the vertical distance since the conversion setup selected is vertical. Switch it to horizontal and it will show you the correct value for this axis: Converting from Windows does not necessarily feel correct for everyone, even though it's mathematically correct. There are many different ways to go about the conversions, the best is probably to base everything off of a game you are comfortable in, that have proper sensitivity settings for different aim levels. If you don't have this, basing it on Windows is a good option. However, as you found out, the 360 distance for hipfire will be different based on the FOV. So a good workaround is to find one game that are converted from Windows that feels good, let's say MW3, and use this as the source for all future conversion, but then do 360 distance for hipfire and MDV 0% for scopes. For scopes you can never expect the same 360 distance, so they will with this setup still be based on Windows.
    1 point
  3. This is not what converting from Windows does, it converts based on monitor distance, i.e. how far you have to move your mouse to hit a certain point on your monitor. For instance MDH 100% matches the distance you have to move your mouse in Windows from the center of the monitor to the edge, to the movement in-game to aim at something at the edge of your monitor. For MDV 0% it matches the same tracking speed, which for Windows is how fast the pixels are moving under your cursor. So this is all based on the FOV of the games, so with a different FOV you will also get a different 360 distance. This is indeed just a coincidence, but I guess it can seem weird at first.
    1 point
×
×
  • Create New...