Jump to content

DPI Wizard

Wizard
  • Posts

    18,161
  • Joined

  • Last visited

  • Days Won

    1,764

Everything posted by DPI Wizard

  1. Use config file sensitivity for best accuracy.
  2. PK-06 is added! They are indeed the same, finally got to analyze it fully now. Also adjusted calculations slightly to be perfectly in line with hipfire.
  3. I just picked this one off of a SCAV: Had three other aims that went on, but the PK-06 said not compatible. I might have done something wrong, not sure
  4. More scopes added! Thanks to @TheYellaKing for dropping them to me! Still missing the PK-06, didn't find the correct AK for it. Still working on it...
  5. If I someone somehow could give me the scopes, alternatively let me use their account to analyze it in an offline raid, that would be really helpful!
  6. Try to set WPS to max and see if it is drastically different in-game. Note that some mods do change the sensitivity scale though, is the range of the sensitivity in-game 1-17?
  7. It's definitely not affect by WPS here, and I don't think I have any mods loaded. Might you have a mod changing how it behaves?
  8. Try this, lower your DPI to 200 and set killer to 26 and survivor to 13.
  9. Too low as 0, you mean it's too slow? This game has a notoriously high range so that would be weird.
  10. DPI Wizard

    8.5.k

    Game added HYPERCHARGE: Unboxed Games updated Roblox - Added Recoil Escape from Tarkov - Revised aims and scopes.
  11. Added to the Roblox entry.
  12. Impossible since the FOV is locked in CSGO and Valorant. So you have to choose between 360 distance or some kind of monitor match. In other words you can only match one aspect of the sensitivity perfectly, everything else just follows this. Personally I prefer 360 distance though, since hipfire is mostly used for navigating the map.
  13. Probably due to acceleration, what's your sensitivity numbers?
  14. Added another scope (VOMZ Pilad 4x32 riflescope).
  15. Correct, you need to add up all the change in turning speed (disregard the minus) and enter it as Sensitivity 1
  16. Forgot indeed, thanks! Updated now.
  17. Added config file sensitivity.
  18. Added config file sensitivity.
  19. Of course you're gonna get a different sensitivity when the first conversion is using 360 distance and the second is using MDV 0%. If you use 360 distance when converting back you will get the same sensitivity: You are using sensitivity numbers that are matched using 360 distance (1.699091 for CSGO and 0.534 for Valorant). Converting these to osu will and should give you different results since they're not matched using a FOV based method. If you instead use 0.503 for Valorant like in your conversion higher up (which is matched to CSGO using MDV 0%) you will get the same osu sensitivity as with CSGO:
  20. What's your aim sensitivity and can you link your conversion? (Use the purple share button).
  21. Scaling seems completely arbitrary, just a fixed 360 distance with no correlation to the FOV, and a multiplier for this 360 distance. It's what it seems like for now at least, I'll get a better overview with more analysis.
  22. Did check it, didn't find anything different. But make sure you add up all your "Change Turning Speed" values!
  23. Osu to CSGO: https://www.mouse-sensitivity.com/?share=9bf53f060ff718adcfa2030f98c19d6e Osu to Valorant: https://www.mouse-sensitivity.com/?share=c84720c29e7041af49b314aeec9279de Valorant to CSGO: https://www.mouse-sensitivity.com/?share=0943179d2693eb89b4832c33dc9b3956 Except from some small discrepancies due to the lack of decimals in Valorant, this is pretty much spot on.
×
×
  • Create New...