VALORANT

6 minutes ago, harrypotter said:

Hey guys ! New subscriber here !  I just did a conversion for my desktop sensitivity to Valorant. Desktop 6/11 400dpi translated to 1.072 in Valorant for hip fire. It feels about the same far as I can tell with the eyeball test - Is it really that simple ?! Or perhaps I'm missing something

id recommend checking the instruction and technical diskussion forums for some insight if yu are using 0% you should be fine

the only issue you might run into could be different fovs  (just use auto fov to keep the same feel)

Went through the Instructions and seems I've got it setup correctly - I think. using MDH 0% as recommended puts me at 1.072   - I tried 100% and drops the sens to 0.766 and felt a bit too slow. Oddly enough trying MDV 100% gave me .933% and felt pretty good. Although I'm understanding its not quite as close of a calculation. 

Am I correct to stick with MDH 0% and roll on with the 1.072?

Yes I also convert from Windows to games with 0% monitor distance and got 1.072 for my sens. However, I found 400dpi at 1.072 was too high of a 360 so I run 300dpi and its the sweet spot for me at VFOV of 73.74. Also I spotted you use Monitor distance vertical for ads/scope however, I think it's better to use all conversions as monitor distance horizontal 0% or all monitor distance vertical 0% otherwise its kinda messy and confusing. Just my two cents though

8 minutes ago, Badmon said:

Yes I also convert from Windows to games with 0% monitor distance and got 1.072 for my sens. However, I found 400dpi at 1.072 was too high of a 360 so I run 300dpi and its the sweet spot for me at VFOV of 73.74. Also I spotted you use Monitor distance vertical for ads/scope however, I think it's better to use all conversions as monitor distance horizontal 0% or all monitor distance vertical 0% otherwise its kinda messy and confusing. Just my two cents though

Good eye !! I actually didn't notice that ! I did however notice I didn't read the " notes " section at the bottom that says I should have my " Aspect Ratio " set to 16:9 Black bars since I'm using 16:9  1920x1080 @ 240hz

This caused some significant changes in the sensitivity conversion. I think now I've got this setup correctly ( I hope ) It certainly does take some trial and error ! Even while following the instructions its quite easy to over look something  

As for now 6/11 windows sens @ 400dpi seems to be 0.981 in Valorant.  1.072 wasn't correct for me, 0.766 wasn't correct either since I had my Aspect ration selected as " Native " before reading the * Notes *

I'm assuming I understand the note correctly otherwise my number will be incorrect again  

Hopefully my " thinking out loud " here will help other folks not make the same mistakes I have so far !

2 hours ago, harrypotter said:

Good eye !! I actually didn't notice that ! I did however notice I didn't read the " notes " section at the bottom that says I should have my " Aspect Ratio " set to 16:9 Black bars since I'm using 16:9  1920x1080 @ 240hz

This caused some significant changes in the sensitivity conversion. I think now I've got this setup correctly ( I hope ) It certainly does take some trial and error ! Even while following the instructions its quite easy to over look something  

 

As for now 6/11 windows sens @ 400dpi seems to be 0.981 in Valorant.  1.072 wasn't correct for me, 0.766 wasn't correct either since I had my Aspect ration selected as " Native " before reading the * Notes *

 

I'm assuming I understand the note correctly otherwise my number will be incorrect again  

 

Hopefully my " thinking out loud " here will help other folks not make the same mistakes I have so far !

Oh actually you should only set it to 16:9 black bars if you're playing on an ultrawide monitor if not use native

Also windows/2d and hipfire is better set to 0% as well so your tracking aim is consistent in all games as 100% is more suited to flicking aim which isn't reliable.

So in summary this is what I believe to be the best conversion for windows to valorant or any game in general:

you are totally right ! I read that Note completely wrong LOL. Well shoot I guess I had better get back on 1.072   Thanks !!

Hello guys, I have that weird impression of having mouse acceleration on Valorant, is that normal ? Anyone else got that problem ? (PS: I did lock my FPS, wich helped a  little, but the problem persists)

17 hours ago, Badmon said:

Oh actually you should only set it to 16:9 black bars if you're playing on an ultrawide monitor if not use native

Also windows/2d and hipfire is better set to 0% as well so your tracking aim is consistent in all games as 100% is more suited to flicking aim which isn't reliable.

So in summary this is what I believe to be the best conversion for windows to valorant or any game in general:

black bars is not only usefull for ultrawides its great for preserving aim when coming from another fov without being able to match the fov ( you can check that out in one of the older threads , think it was skidushes )

found it  ^

also you dont have to stick to 6/11 and instead go with something like 1000dpi at 4/11 (or any other setup )

this can feel far better during general use and will reult in the same / a similar 360 distance in game with a far greater desktop experience

5 hours ago, fortunate reee said:

black bars is not only usefull for ultrawides its great for preserving aim when coming from another fov without being able to match the fov ( you can check that out in one of the older threads , think it was skidushes )

 

 

found it  ^

 

also you dont have to stick to 6/11 and instead go with something like 1000dpi at 4/11 (or any other setup )

this can feel far better during general use and will reult in the same / a similar 360 distance in game with a far greater desktop experience

Thanks! That was an interesting read for sure, defo gonna do some research into this as it seems ive barely scratched the surface

So after finding out that you can get the same 360 distance for valorant and csgo I tried it in the calculator however, the suggested res of 1810x1018 doesn't give the same 360 distance as my input even when I selected "16:9 black bars" instead I get an extremely low 360 distance. Can anyone explain this? Thanks!

6 hours ago, DPI Wizard said:

That was a bug regarding aspect ratio, check again now

So sorry if I got this wrong this info is all new to me

But when I set my res as 1810x1018 and aspect ratio to 16:9 black bars in VALORANT does that mean I have the same focal length as in csgo even though the fovs differ

Which will mean my sensitivity still won't be the same 360 distance but it'll feel the same?

If I'm wrong could someone post the correct way to calculate the right sens when emulating the same fov as for me I seem to get the same value as native.  Thanks 

5 minutes ago, Badmon said:

So sorry if I got this wrong this info is all new to me

But when I set my res as 1810x1018 and aspect ratio to 16:9 black bars in VALORANT does that mean I have the same focal length as in csgo even though the fovs differ

Which will mean my sensitivity still won't be the same 360 distance but it'll feel the same?

If I'm wrong could someone post the correct way to calculate the right sens when emulating the same fov as for me I seem to get the same value as native.  Thanks 

as far as i am concerned ,you should be able to set it to 360 distance in this case

it just 3.26 deg and makes them your black bars so that you feel the exact same

@Pyroxia you used this for a while didn't you ?

correct me if i got this wrong

11 minutes ago, fortunate reee said:

as far as i am concerned ,you should be able to set it to 360 distance in this case

it just 3.26 deg and makes them your black bars so that you feel the exact same

@Pyroxia you used this for a while didn't you ?

correct me if i got this wrong

Hmm thanks shouldn't the calculator automatically change your 103fov game sensitivity to the same 360 distance as the 106.26fov one instead it leaves it as if you were playing valorant on native so the 360s don't match  

Just now, DPI Wizard said:

It does if you tell it to

Ohh so if I left it at mdh 0% I wouldn't get the correct value for hipfire.

I feel that'd be a neat feature to implement into the 16:9 black bar aspect ratio, will make it useful to calculate resolutions for lower fov games in the future  

Also one LAST question lol since I convert from windows to games I'm unable to use 360 distance so is the only way to convert from windows to lower fov games, is to:

• Convert desired game sensitivity (e.g csgo) to windows(different dpi and wps)
• Use desired game sensitivity (csgo) to convert sens to all other games

Would this be the same as matching all games with windows? Thanks one more time  

28 minutes ago, fortunate reee said:

as far as i am concerned ,you should be able to set it to 360 distance in this case

it just 3.26 deg and makes them your black bars so that you feel the exact same

@Pyroxia you used this for a while didn't you ?

correct me if i got this wrong

yes I'm using this method since I learned. Actually I'm playing valorant right now with this method. Works really good for me. For this method you need to choose 360 degree distance for hipfire and MDV for scopes. 

Hey guys, I also have the feeling that something is going on with the mouse input, but I dont think its necessarily acceleration.

Knowing the Unreal Engine and having played UT4 for a while though, I have my concerns that there might be something weird going on.

Many UE games have something called GPU buffer in their video options, which is missing here. In UT4 that was adding a lot of input lag, but could be turned off.

For Valorant it also feels a bit like input lag, or mouse smoothing.

@ Wizard, do you check for something like this when analyzing?

I heard shroud says if ı divide 3.18181818 my cs:go sens it will be my UE4 sens but in here its show less so what kind of method you guys using(I play 4:3 Streched on CS:GO and 16:9 Native in Valorant) btw ı use 1024x768 res in cs but when ı change it in settings here it dont makes any difference

@DPI WizardAre we able to input more than . 3 decimal in the sensitivity box? some game will only display 3 on the option but internally can go further than 3 decimal. thanks