gbtg

On 10/26/2019 at 10:30 AM, Guest ZSfGuBcu said:

no not even close to 360 distance , if you use 0.818933 then you will get the same FEELING with the first level of the zoom with awps and guns like that . it is far far slower when it comes to 360 distance . the 0.8189 is MDH 0% meaning fine adjustments and good tracking . 

quoting an old post here but just so i understand this right: what would be the equivalent COD setting to the 0.818933 csgo zoomsens? i want all my scopes to feel the exact same in cod. i assume its the monitor coefficient setting in cod? what value?

thanks

hey,

i am trying to transfer both my warzone sens and FOV settings over to kovaak's aim trainer. hipfire to hipfire seems simple enough so i think i managed to do that.

but when it comes to for example AR ironsights in warzone -> kovaaks scope i am not quite sure if i am doing things right.

basically what i did is enter my wz settings into the calculator, then look at the FOV that it tells me i get for AR ironsights, then i enter that (actual) FOV into the calc for kovaaks scope and then adjust the kovaak scope in kovaak itself using the actual fov and sensitivity multiplier that the calc puts out. in the calc i also selected "overwatch" for both sensitivity scale and fov measurement under kovaaks.

cant seem to get the share function of the calc to work, but here are the results of the calc:

does this look right? setting up a scope for a weapon in kovaaks in this way does seem to give me the right 360 distance, but i feel like the FOV might be a little too high, as in: it does not zoom in as much as it does with ironsights on an AR in WZ. but that might just be my perception, as i dont see a weapon model in kovaaks.

thanks for the help

2 hours ago, DPI Wizard said:

Have you set the ADS (Iron-sight) sensitivity after the patch? What sensitivity are you using, and what is the issue? 

found the issue. they changed the way the ini saves the sensitivity values.

(SensitiveName="Normal",Sensitivity=6.098196,LastConvertedSensitivity=0.002704),

this is how it looks now, old one was MouseSensitivityName and MouseSensitivity and so on. this screwed me over cause i was copy/pasting the complete "block" of text into the ini after the update.

On 6/24/2018 at 8:16 PM, borysn said:

After the Sahnok patch all ADS calculations are incorrect. Pls fix.

yea i am running into the same issue

34 minutes ago, Drimzi said:

Benefits don't cap out, but I wouldn't go too extreme as mice are inconsistent at incredibly high DPI, and it can cause conversion issues for some games since many have ungenerous sensitivity sliders or suffer from negative acceleration if the sensitivity value is too low.

WPS is bypassed, that is the reason why you lower the game sensitivity instead.

If 1600 DPI is your preferred 2D sensitivity, then increase to 3200 DPI and set 4/11 WPS. In the calculator, raise the DPI to 3200, halve CSGO's sensitivity, and then convert to PUBG. I would usually recommend 3/11, but not in your case since 1600 is a pretty high baseline, and 6400 DPI is pretty extreme for the majority of cheap mice.

i just did exactly that and i have to say i think i can feel the difference, not only when slowly moving my mouse as little as possible but it does feel better all around. some of that might be placebo, or not, but i am definitely keeping this. thanks again.

On 3/9/2018 at 3:57 AM, Drimzi said:

For 3D, you want the angle increment to be infinitely low, as the benefit is endless. The only way to achieve a lower increment is to reduce the game sensitivity, but in doing so, it also requires more CPI to preserve the physical distance for rotation. This also affects the 2D sensitivity, so this is where the Windows sensitivity comes in handy. For convenience sake, I highly recommend using 3/11 with 4x higher CPI if you have a decent mouse with a good sensor. This will allow you to use a game sensitivity low enough for smooth angular increments. 

i am currently playing with 1600dpi and ~22 ingame hipfire sens in pubg. would you say that lowering the ingame sens even more (and adjusting by increasing dpi) would make a noticeable difference? do those benefits cap out at a certain point or should i just go as low as possible? thanks!

6 minutes ago, Drimzi said:

Viewspeed v2 is independent. It uses the 1:1 fov value. Viewspeed v1 uses horizontal fov value, so it will give different results for different aspect ratios.

which one do you recommend?

On 4/20/2018 at 11:47 AM, Drimzi said:

The calculator uses a percentage of your width. If you had a square monitor, then 100% would be identical to 16:9's 56.25%.

 

Just to add, these are the equivalent values for other aspect ratios:

1:1 - 100%

5:4 - 80%

4:3 - 75%

16:10 - 62.5%

16:9 - 56.25%

21:9 - 42.1875%

32:9 - 28.125%

 

hey, i still do not quite understand what you are saying and i am actually really sorry to bother you with this since i feel really stupid.

currently i use VS2 to convert my sensitivity to the different scopes of PUBG, i got a 16:9 monitor and now i would like to try your method. so do i use 'monitor distance' and 'match at' 56.25%? how will that compare to VS2? will it feel slower or faster when the FOVs get lower?

thanks!

edit: and about discrepancy.. using VS2 converting my hipfire FPP sens to the 4x scope (90 hfov to 20 hfov) i get a discrepancy of 0.002cm. this is low enough to not affect me?

there seems to be an error in the calculator.

when selecting "vehicle" the calculator shows a hfov of 90 when selecting config file 1 and a hfov of 80 when selecting config file 2 (independent of selecting FPP or TPP).

@DPI Wizard could you confirm whether or not this affects the actual calculation/output of the calc? i assume in FPP the fov while being inside of a vehicle is the same as hipfire, so i should use the same sens?

3 hours ago, DPI Wizard said:

I can confirm that this works, and will give you a true 1:1 sensitivity!

Here's how:

Open %LOCALAPPDATA%\TslGame\Saved\Config\WindowsNoEditor\input.ini and add this to it:

[/Script/Engine.InputSettings]
AxisMappings=(AxisName="Turn",Key=MouseX,Scale=1.000000)
AxisMappings=(AxisName="LookUp",Key=MouseY,Scale=-1.428571)
AxisMappings=(AxisName="WorldMapZoom",Key=MouseWheelAxis,Scale=1.000000)

You will lose some bindings, I lost all bindings to A and S as well as a few MouseWheelDown ones. You can simply re-bind this in the option menu and they will stay. Making the GameUserSettings.ini file read-only did not work for me.

that's great! does csgo have 1:1 horizontal:vertical sens?

13 hours ago, DPI Wizard said:

It is correct that for different FOV's you can only match the sensitivity perfectly to one specific method. The difference between 103 in PUBG and 106.26 (if you have a 16:9 monitor) is very small though.

You need to set fov_cs_debug to 86.63 to match 103 in PUBG (with a 16:9 monitor), but as you probably know this only works on custom games with cheats enabled in CSGO.

Unless they have changed anything in PUBG lately you can alternatively set the FOV in the config file to 106.26 instead to match CSGO.

thanks! i know it will only work with sv_cheats enabled but since pubg has no practice mode i want to use CS to practice raw aim.

could you also tell me the fov_cs_debug to match the ADS fov, as well as the different scopes?

using this method of using the exact same FOV in cs and then using the sensitivity calculator to match my sens to the adjusted FOVs in cs should be the most accurate way to practice?

On 1/19/2018 at 8:40 AM, gbtg said:

i play only pubg but i want to use csgo to practice aim since pubg has no practice mode. help me understand a few things please:

first of all, am i right when i say that whatever conversion method i use, the sens CAN never feel 100% the same between the games because of the different FOVs? lets say i use monitor distance at 75% (and viewspeed1/2 follows the same principle, doesn't it?). am i right thinking that in that there are exactly 2 points on the screen where my sens will feel the same when i move the crosshair from point A to point B in both games, but there will be small differences between all other points on the screen? that's just the nature of the different FOVs, right?

if that is true, can't i just change csgo's FOV to match my pubg FOV? would the 2 sensitivities be 100% correct then?

anyone know an answer to this? i want to set my csgo fov to be identical to my pubg fov (103).

what fov_cs_debug setting do i have to use in CSGO to match my 103 fov setting in pubg? thanks

3 hours ago, SevenFreak said:

Option 2 is nonsense - why would you use e.g. a 30cm/360 distance for any scope? That will be far too sensitive. Based on the descriptions Wizard provided (e.g. Monitor distance video) you should use always option 3 -> convert the main sense to the new game and then convert this new sens to any scope you need by using the monitor distance again. But you need to figure out which percentage of monitor distance gives you the best feeling (e.g. 25%).

But as long PUBG does not provide any training map/mode this will be never be easy...

well, option 2 i was obv not gonna use the same 360 distance for every scope but the same value of sensitivity for each one, ie 50 for all scopes.

i really struggle to find the right conversion method.

i see 3 main options:

1. converting my csgo hipfire sens into every sensitivity for every scope in pubg.
2. converting my csgo hipfire sens into pubg hipfire sens and then use that sens for every scope.
3. converting my csgo hipfire sens into pubg hipfire, then convert that pubg hipfire sens into every other sensitivity/scope.

does anyone know what makes the most sense?

read the notes in the calculator after you selected pubg as the game to convert to.

i play only pubg but i want to use csgo to practice aim since pubg has no practice mode. help me understand a few things please:

first of all, am i right when i say that whatever conversion method i use, the sens CAN never feel 100% the same between the games because of the different FOVs? lets say i use monitor distance at 75% (and viewspeed1/2 follows the same principle, doesn't it?). am i right thinking that in that there are exactly 2 points on the screen where my sens will feel the same when i move the crosshair from point A to point B in both games, but there will be small differences between all other points on the screen? that's just the nature of the different FOVs, right?

if that is true, can't i just change csgo's FOV to match my pubg FOV? would the 2 sensitivities be 100% correct then?

looking forward for this, has anyone tried it already?

do you guys think practicing aim in csgo will help for pubg? i am not really sure how all those conversion methods work, but from my understanding, my sensitivity will be matched for moving my mouse from point A to point B on the monitor and in that case it will feel the same for both games. but will it feel exactly the same for moving from point C to D? i guess my question is: could using csgo to practice aiming help or hurt my muscle memory for pubg?

edit: my bad i am dumb.

also, what is the difference between viewspeed V1 and viewspeed V2?

thanks

hey, i was wondering if

On 10/1/2013 at 2:00 PM, DPI Wizard said:

As you can clearly see, lower sensitivity gives you a finer grid, which again gives you more accurate aim and smoother movement. Even at a 1:1 ratio between the grid and pixels, the movement is quite choppy.

hey, i got a question regarding this, but i am not sure if there is a definitive answer to it:

the vast majority of csgo pros use 400dpi. why do they not increase their dpi and reduce their ingame sens accordingly, in order to gain accuracy and smoother movement? is there such a thing as "too much accuracy", at which point having your mouse pick up on the tiniest of movement becomes a disadvantage?

thanks for the fast answer!

thanks, i used viewdistance (edit: viewspeed)iirc and matched all my scopes to my csgo hipfire sens. which csgo zoom sens should i use in that case?

quick question: since pubg does not have any kind of practice mode and i spend a lot of time moving around / looting without shooting in this game, i am using csgo to keep my muscle memory sharp. the calculator translates my csgo hipfire sens into all those different pubg sensitivities, which is great. but how about if i scope with say the awp. i read somewhere that zoom_sensitivity_ratio_mouse "0.818933027098955175" should be used to make the 1x scoped sensitivity in csgo feel the same your normal csgo hipfire sensitivity. so, should i use zoom_sensizoom_sensitivity_ratio_mouse "0.818933027098955175" in csgo, when i use csgo to practice for pubg?

thanks

thats great! sucks that the game makes it so hard to set exact values though.

nvm