WhoCares?

Thank you

Is it possible to use hex edit for more decimals?

That would be great! Tho,..I could swear someone already tested diagonal fov some time ago. And we came to the conclusion is wasn't the right direction. Not sure if it was this thread or one of there others were we were discussing viewspeed. Maybe I remeber wrong, I read some much information about this topic today (again), maybe my brain just trick me

So viewspeed v2 could be correct for 2D to 3D as well? Or do you mean one of the newer formulars but with diagonal fov like: (360 × vertical-resolution)/(dpi × fov) ?

All right And for 2D to 3D? We are mostly sure that no method is completely correct atm, right?

Testing a formular for 2D to 3D convesion? Or from 3D to 3D? In your posted video Viewspeed v2 looked on point! (And I always felt it was really good, but maybe because I always used 75% match distance before, which is very Close) I am sorry that I ask, but there were so many new ideas in the last weeks...and most of them got knocked over that I am confused which formular is in progress and which not

Did you use 90 or 73.74 (vfov) in the formula? Drimzi said that scaling to 90 is probably wrong! 73.74 its slower just looking at the numbers

The last update changed the sensitivity slider to 1 less !!!! decimal? Why would you patch it to the worse?!

Looks pretty good! Which version it is? is it a modification of your last recent posted formular?

Not sure what you mean. We need some more informations so we can help you better What game are you talking about?

Just to make so (so I dont mess with new sensitivitys and thus my muscle memory all the time), both Windows to 3D AND Viewspeed need some improvement at the moment right? I would relly like to help with bringing this forward, but unfortunately my mathmatic skills arn't good enough

Thank you for all your effort in this Drimzi! Right now, I can't play games, but I will spent some more time with this new method! I am sure I will like it in the long run even tho It felt too fast at the first sight And thank you for the charts potato psoas I hope the DPI Wizard will update/add this to the calculator in the near future

Do you really mean 1440x1080 ? Or 2560x1440 ? If not, thats another aspect ratio and thus another fov in games, so sensitivity might messed up in a lot of circumstances

Hmm, I never was a big fan of this aim practising applications, but maybe I should give it a try...Looks impressive

Even tho it feels strange, I am doing quite good in games I will test it a little long and will report you

Hmm, It feels too fast to be honest but maybe just because I am used to a lower sensitivity This is only for Windows-2D to 3D environment and not for 3D fov to another 3D fov, right? For ADS I am using the regular viewspeed v2 right now. Can I just use the fov for that specific sight/ironsights if I know the value and put it into the calculator? Btw, greatly appreciate your effort !

I followed your steps, (dunno if i did everything right) and for my settings I get a significant higher sensitivity. My hip 360° distance changed from 47.8778cm to 41.7667cm (from old viewspeed 2 to your here posted method) Is this possible? Or did I do something wrong? For me it feels way to fast :/ Edit: Why do I have to use 90 for x when this formula is for vertical fov? Wouldn't 73.74 be more logic?

Isn't it the opposite? 100% is the slowest and 0% the fastest?

For hipfire only ist fine, but for every game with some kind of ironsights or scopes it's outdated and there are better options such as viewspeed or match distance at 0% or 75 % @Famatic Did you double check if everything in correct typed into the calculator? Correct fov?

Its third person game. And third person isn't possible at the moment. And unlikely to get a perfect conversion in the future probably

Thanks for the tip

Unfortunately I dont have a logitech mouse Just out of interest: is there any way to match viewspeed for 50 fov aim down sights (ARs, Snipers with ironsights and LMGs) and not 55 (SMGs)? The calculator doesnt change when changing the fov while ads. @Crankenstein The calculator works as intended. What exacly you want to do? Do you mean the same 360° distance for hip and ads with "1:1" ? Older CoD used 0% match distance. If you dont like it, use 75% or viewspeed. But be aware, only ironsights will match to your choosen calculation methode. All other scopes will scale with 0% match distance

I still might use viewspeed v2 for hipfire and 0% match distance for ADS sensntivity for this game, because every cod (nearly) was using 0% match distance so far. Since I don't remember the default number for ADS sensitivity, do I just have to use 0% match distance for ads in the calculator?

Well for a CoD ist an improvement having a ADS sensitivity slider at all

Since pistols, smgs and ARs use different ironsight-fov, to which default fov does Viewspeed v2 matches to? 55 (smg) ? Is that what you ment @Drimzi ?