90skidd Posted October 31, 2019 Posted October 31, 2019 22 hours ago, DPI Wizard said: Just updated the game now. Added all scopes I have access too. Adjust rounding in-game to four decimals. You can enter four and it will apply correctly, but only two decimals are shown in-game. Adjusted config file decimals to five, as it won't read any more. Removed ADS Mouse Sensitivity algorithm selection (Legacy/Relative) as it is bugged in the game (relative is always active) and it doesn't bring anything to the calculation as legacy is (supposed to be) the same as relative with coefficient 0. I did feel a difference between legacy and relative but guess I may be wrong? I usually use the 3.5x scopes. So if what you're saying is correct and the game is bugged and staying on relative how would I get the classic legacy feeling currently? Should I just change the coefficient in the game settings to 0?? I preferred the legacy feeling that was in the beta
conan1 Posted October 31, 2019 Posted October 31, 2019 (edited) IMPORTAND IS TO TELL THIS IW - why? we can disscus 1000 sites of what works...and what not..legacy not works in the current state of the game, All runns on Relative. so why you dont report this problem? no, anyone is here and crys about sens and the game is not fixed, thats doesnt make sense to me. report the prob, wait until the prob is fixed, than we can start discuss again. we have here a profi of you all the pimples in your face calculate on the basis of your size, he can do only so much what that game gives. We should not forget that Wizard is the mouse sense god Edited October 31, 2019 by conan1
TheNoobPolice Posted October 31, 2019 Posted October 31, 2019 It's not really important. It's actually a completely redundant feature. Still, I guess it's nice for those that don't want to think and just hit a "like it used to be " button.
HachiHO Posted November 1, 2019 Posted November 1, 2019 Hello! Could someone help me transfer my pubg sens to MW? I'm a noob with this. Pubg: 800dpi, 1728x1080, 90 fov, general sensitivity 30, AIM ADS and SCOPES 25 COD: 800 dpi, 1728x1080, 90 fov Also I want my scopes in MW to feel similar to pubg scopes? Thank you so much for the help
TheNoobPolice Posted November 1, 2019 Posted November 1, 2019 (edited) 2 hours ago, HachiHO said: Questions... Depends on how you want ADS to be synchronised, you will not be able to synchronise up all scopes by any one method because CoD MW doesn't allow individual sight adjustment, and the default scaling is different to some of the ADS levels in pubg. Also, you should only really try and match first person aiming - third person is fundamentally different in any case. First thing is to match your hipfire up - the important thing is the FOV difference between the games -(Pubg uses resolution based, and CoD is 16:9 aspect ratio based). You can match this up as below. Then you can choose a method for converting ADS. Most recommend either MD (monitor distance) 0%, or MD-H 50-75%. Example: Then you can input your previous hipfire sens and arrive at a setting for a specific ADS conversion, for example, converting the Assault rifle ADS to red dots in CoD matched by MD 0% If you want to do a different scope, you will get different results however. Best advice is just to choose the scopes you use the most and match those up. If you find the aiming too slow in CoD, try using monitor distance horizontal 50-75% instead. Edited November 1, 2019 by TheNoobPolice HachiHO 1
HachiHO Posted November 1, 2019 Posted November 1, 2019 I get it. Thank you so much for the explanation. Now I can play comfortably with that configuration. TheNoobPolice 1
Angelofthefallen Posted November 1, 2019 Posted November 1, 2019 I'm a little confused on how i'm suppose to convert my ADS sensitivity compared to past cod games (legacy aim) I'm a simple man-- I use 2.2 sensitivity and 400 dpi for CS:GO 1 sensitivity for Scoped weapons. What should my ADS sens be? What should my coefficient be? Should I be on legacy or relative? I would use legacy but I heard it was bugged.
TheNoobPolice Posted November 1, 2019 Posted November 1, 2019 Use Relative, and set coefficient to 0.00 with transition set to gradual. That's the same as the legacy system.
Paintballer Posted November 2, 2019 Posted November 2, 2019 Hey Mr DPI. How come the calculator uses the 3.5 zoom as the standard when running the comparison and not a red dot or no sight?
Wizard DPI Wizard Posted November 2, 2019 Author Wizard Posted November 2, 2019 Just now, Paintballer said: Hey Mr DPI. How come the calculator uses the 3.5 zoom as the standard when running the comparison and not a red dot or no sight? I'm not quite sure what you mean. The "All" conversion uses 3.25X and holo (for high and low zoom), while all other aims are available for manual conversion (where you need to provide the hipfire sensitivity).
Paintballer Posted November 2, 2019 Posted November 2, 2019 Oh I see. It's both zooms. Holo and 3.5x for the two zoom levels in relative. I get it.
Angelofthefallen Posted November 4, 2019 Posted November 4, 2019 I play on 400 DPI and 2.2 on CS:GO I know my hipfire is 7.33 I want all my scopes to match the same as my hipfire do I need to change my coefficient or all the scope sens? Thanks!
MrBayeasy Posted November 4, 2019 Posted November 4, 2019 (edited) Hey I'm having problems getting my sense to stick to anything more than 2 decimals, I run 5.1452 In game. As previously indicated it does just say 5.15, however when I go to my config file to check to see if the sens stuck it just reverts back to 5.15 as soon as I jump into a match or restart the game. I wanted to use the config file sens calcs for hipfire and ads, which gave me a few more decimals, however those didn't stick at all, the moment I boot the game up it just reverts, and if I change it while the game is on it reverts when I jump into a match as well. So regardless of whether I change it in game or in config it never sticks beyond 2 decimals, has anyone else encountered the same problem or knows a workaround for this. If this is widely known excuse my ignorance I only recently started taking my aim/sens serious about 1.5 months ago so I'm not familiar with all the tips and tricks yet. Edited November 4, 2019 by MrBayeasy
Wizard DPI Wizard Posted November 4, 2019 Author Wizard Posted November 4, 2019 2 hours ago, MrBayeasy said: So regardless of whether I change it in game or in config it never sticks beyond 2 decimals, has anyone else encountered the same problem or knows a workaround for this. If this is widely known excuse my ignorance I only recently started taking my aim/sens serious about 1.5 months ago so I'm not familiar with all the tips and tricks yet. Make the file read-only MrBayeasy 1
sithex1 Posted November 4, 2019 Posted November 4, 2019 Can someone help me? I'm trying to get my ads sens from R6 Siege, but the calculator wont change no matter what i put..
Wizard DPI Wizard Posted November 4, 2019 Author Wizard Posted November 4, 2019 2 minutes ago, sithex1 said: Can someone help me? I'm trying to get my ads sens from R6 Siege, but the calculator wont change no matter what i put.. The calculator is set to MDH 0%, which is exactly the same as Coefficient 0 in MW. So as long as you have the same FOV in both R6 and MW, the calculation won't change. But you have ADS sens in R6 set to 84, which probably means you want it to be the same 360 distance as hipfire. Have you only set the sensitivity in-game, or in the config file as well?
sithex1 Posted November 4, 2019 Posted November 4, 2019 2 minutes ago, DPI Wizard said: The calculator is set to MDH 0%, which is exactly the same as Coefficient 0 in MW. So as long as you have the same FOV in both R6 and MW, the calculation won't change. But you have ADS sens in R6 set to 84, which probably means you want it to be the same 360 distance as hipfire. Have you only set the sensitivity in-game, or in the config file as well? I only have it set in-game, I figured that was good enough? So I should change the conversion setup to 360 for both hipfire and ads, which would give the result I want? thank you
Wizard DPI Wizard Posted November 4, 2019 Author Wizard Posted November 4, 2019 Just now, sithex1 said: I only have it set in-game, I figured that was good enough? So I should change the conversion setup to 360 for both hipfire and ads, which would give the result I want? thank you Yes, and change location for R6 to In-game instead of config file. sithex1 1
Angelofthefallen Posted November 4, 2019 Posted November 4, 2019 On 11/1/2019 at 11:16 AM, TheNoobPolice said: Use Relative, and set coefficient to 0.00 with transition set to gradual. That's the same as the legacy system. What if I want my ADS and hipfire to be same sensitivity? Or like battlefield 1 with uniform aiming off.
Wizard DPI Wizard Posted November 4, 2019 Author Wizard Posted November 4, 2019 3 minutes ago, Angelofthefallen said: What if I want my ADS and hipfire to be same sensitivity? Or like battlefield 1 with uniform aiming off. For the same as BF1 with USA off set it to 1. ADS and hipfire can't be same sensitivity though, since they have different FOV. You have to choose either same 360 distance, same tracking speed (MDH 0%) or same flick distance (MDH X%).
Angelofthefallen Posted November 4, 2019 Posted November 4, 2019 14 minutes ago, DPI Wizard said: For the same as BF1 with USA off set it to 1. ADS and hipfire can't be same sensitivity though, since they have different FOV. You have to choose either same 360 distance, same tracking speed (MDH 0%) or same flick distance (MDH X%). What do I set to “1” and if I I wanted tracking speed. MDH 0% for what? ADS scope or? It might help to mention I play with 7.33 sensitivity on modern war fare. Lol sorry I’m a little confused
Wizard DPI Wizard Posted November 4, 2019 Author Wizard Posted November 4, 2019 Just now, Angelofthefallen said: What do I set to “1” and if I I wanted tracking speed. MDH 0% for what? ADS scope or? It might help to mention I play with 7.33 sensitivity on modern war fare. Lol sorry I’m a little confused Setting the coefficient in MW to 1 (and multipliers to 1) is the same as BF1 with USA off. Setting the coefficient to 0 is the same as MDH 0% and will make the tracking speed across all aims the same. For both ADS and scope.
MrBayeasy Posted November 5, 2019 Posted November 5, 2019 23 hours ago, DPI Wizard said: Make the file read-only Hey thanks so much, it worked, I really appreciate the speedy response! +)
Angelofthefallen Posted November 6, 2019 Posted November 6, 2019 On 11/4/2019 at 2:17 PM, DPI Wizard said: Setting the coefficient in MW to 1 (and multipliers to 1) is the same as BF1 with USA off. Setting the coefficient to 0 is the same as MDH 0% and will make the tracking speed across all aims the same. For both ADS and scope. Which option legacy or relative?
Wizard DPI Wizard Posted November 6, 2019 Author Wizard Posted November 6, 2019 Just now, Angelofthefallen said: Which option legacy or relative? Relative.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now