Jump to content

DPI Wizard

Wizard
  • Posts

    18,142
  • Joined

  • Last visited

  • Days Won

    1,762

Everything posted by DPI Wizard

  1. Actually, if you want to keep your Rainbow Six sense for hipfire and ACOG, this is correct: Rainbow Six (unchanged): Sensitivity 1: MouseYawSensitivity=60 Sensitivity 2: AimDownSightsMouse=82 Multiplier 1: MouseSensitivityMultiplierUnit=0.00223 Multiplier 2: XFactorAiming=0.02 CS:GO: Sensitivity 1: sensitivity "1.538635" Multiplier 1: zoom_sensitivity_ratio_mouse "1.518333" What I've done here is convert hipfire to hipfire, and then ACOG to Zoom level 1.
  2. Yes, if your hipfire sensitivity in Rainbow Six feels good, those numbers will adapt that sensitivity.
  3. Actually it's wrong because your ACOG sensitivity is too fast compared to hipfire in Rainbow Six. Ideally you would have in Rainbow Six: Sensitivity 1: MouseYawSensitivity=60 Sensitivity 2: AimDownSightsMouse=82 Multiplier 1: MouseSensitivityMultiplierUnit=0.00223 Multiplier 2: XFactorAiming=0.008895 And then in CS:GO: Sensitivity 1: sensitivity "1.538635" Multiplier 1: zoom_sensitivity_ratio_mouse "0.954171"
  4. Ok, if you change that and use Viewspeed as the conversion method, you should get 2.448368 as CS:GO sensitivity. Use this for the zoom sensitivity, and it should be 0.954171.
  5. Are you sure those numbers are correct? 0.002x is extremely slow in Rainbow Six. 0.02 is the default.
  6. Leave them default and make sure the resolution is correct. If you check the output, you will see that the actual horizontal FOV is automatically calculated.
  7. Set scope 4x, 8x and 15x to 40 and the rest to 41.
  8. I would suggest trying Viewspeed for all conversion, as that method adjusts itself based on FOV or desktop.
  9. Check out this video if you haven't already: In short, the "Match At" percentage is where on the screen between your cross hair and monitor edge to match the sensitivity. If the FOV is different in the games you are converting between, you can only perfectly match it to one point. The Viewspeed conversion is a dynamic version of Monitor Distance, which usually lands between 60% and 70%. It converts using a constant arc length.
  10. You're at the wrong location. Paste this into the address bar: %LOCALAPPDATA%\TslGame\Saved\Config\WindowsNoEditor
  11. Use Viewspeed for all. 360 distance won't be the same, but that's usually not desirable when the fov is different.
  12. Try the Viewspeed conversion. You will see that the different aims end up with pretty much the same numbers.
  13. 8X and 15X scope added as well, finally!
  14. Added in-game calculations for Targeting, Scoping and Scope 4X!
  15. You have to make sure the entire line is there, i.e. MouseSensitiveName="Normal",MouseSensitivity=50.000000,LastConvertedMouseSensitivity=0.014174 The value of MouseSensitivity is not important, but the sensitivity is reset if it's not present when you change the LastConvertedMouseSensitivity value. The game will then remove the MouseSensitivity=50.000000 upon start.
  16. Added scoping and 4x scope for config file, and fixed an error with the targeting calculation. Working on the in-game calculations!
  17. Tested, double checked and triple checked now, with your exact settings. Everything is correct, but I think the issue is that a 3rd person feels slower than first person view because the camera pivots around the character. If you compare how far you have to move your mouse to aim at something 3-4 inches away from your monitor edge, you'll see that the distance is about the same between the games.
  18. What FOV are you using?
  19. I'll re-check it. Did you check if the calculated 360 distance is correct, or does it just feel too low?
  20. I wish this game had a sandbox mode where you could play around with all the weapons and attachments... Now I have to play the game until I find the right equipment, then survive long enough to analyze it
  21. Added! Finally, it's working now. Just added it.
  22. 382
  23. 379 380 381
×
×
  • Create New...