So, basically i converted my scoping and targeting sensitivity (1st and 3rd person) and they seems to be working perfectly. But how do i make the same sensitivy as my scoping one but for scopes because when i try to convet it using calc it's just not the same and when i try to spin my mouse it feels so fast and weird at all.

Edited September 17, 20178 yr by Rofl

Select Viewspeed instead of 360 Distance in the "Convert to" section, and you're good to go!

19 minutes ago, DPI Wizard said:

Select Viewspeed instead of 360 Distance in the "Convert to" section, and you're good to go!

I tried everything but it's still not even close to be perfect

Just now, Rofl said:

I tried everything but it's still not even close to be perfect

Are you setting the sensitivity in the file?

12 minutes ago, DPI Wizard said:

Are you setting the sensitivity in the file?

Yes, i do. 

And if i choose 360 distance i get sens 0.0167.. which is still not accurate to make my 115 degree spin. 

And if i choose Viewspeed i get like 0.006... sens which is 2.5 x times less

12 minutes ago, Rofl said:

And if i choose 360 distance i get sens 0.0167.. which is still not accurate to make my 115 degree spin. 

And if i choose Viewspeed i get like 0.006... sens which is 2.5 x times less

Try to set it to 46 in-game and see how that feels. The calculations should be correct (unless they changed something last patch).

1 minute ago, DPI Wizard said:

Try to set it to 46 in-game and see how that feels. The calculations should be correct (unless they changed something last patch).

46, you mean general sensitivity in-game ?

1 minute ago, Rofl said:

46, you mean general sensitivity in-game ?

No, just the 2x scope. Btw, this will probably mess up your config file entries...

Just now, DPI Wizard said:

No, just the 2x scope.

Ok, ty i'll try to do it tomorrow. Btw, i have this problem with every scope (x2 x4 x8 ( it's especially weird in game when i put sens from calc for my x8 ) and x15)

11 hours ago, DPI Wizard said:

No, just the 2x scope. Btw, this will probably mess up your config file entries...

It's already was 46

Feels bad man ((

Edited January 28, 20188 yr by Drimzi

4 hours ago, Drimzi said:

You need to find the equivalent monitor distance match % that matches your CSGO zoom sensitivity, and convert from CS:GO hipfire to every single PUBG aim type, even hipfire, using that monitor distance match.

To find the equivalent match:

1. First, set the input game to CSGO.
2. Change the aim type to 'Zoomed 1', put in your sensitivity and zoom sensitivity, and write down the 360 degree result.
3. Next change the aim type back to 'Hipfire', put in your sensitivity.
4. Set the conversion mode to monitor distance match.
5. Set the output game to CSGO as well, and set the output aim type to 'Zoomed 1'.
6. Change the match % until the 360 degree result best matches what you wrote down earlier.
7. Convert from CSGO using that monitor distance match to all of your games for the best results.

If you have 1.00 zoom sensitivity, the best monitor distance match would be 80% or 85%.

80% = zoom_sensitivity_ratio_mouse "0.988687"

85% = zoom_sensitivity_ratio_mouse "1.005694"

Change your CSGO zoom sensitivity to one of the following for the most perfect consistency.

The result of all of this, is that the sensitivity will be exactly the same as the CSGO engine, you can imagine the lower FOVs of other games behaving in the same way as changing the FOV of CSGO. The sensitivity will slow down by the exact same amount as your zoom sensitivity value.

I still don't get it, i'm sitting here for over an hour and trying to setup monitor distance match. Could you help me in skype or somewhere else ?

CSGO Sens works like this.

 

CSGO Sens x CSGO Zoom Sens

 

so there is no way CSGO sens alone will make scoping feel like csgo scope, it will only adjust the viewspeed without consideration for csgo scope sens.