DPI Wizard
-
Posts
18,149 -
Joined
-
Last visited
-
Days Won
1,763
Content Type
Profiles
Forums
Updates
Release Notes
Store
Everything posted by DPI Wizard
-
Added with hipfire, scope and aim sensitivity.
-
Added with hipfire, scope and aim sensitivity. -
Will add all these this weekend (if I get access to them all).
-
Excellent, that would help a lot!
-
The FOV's are matched, look at the Actual FOV in the output. And since we are matching the ironsight/ADS you can't compare the numbers directly. Check the 360 distance and as mentioned the Actual FOV and see that they are identical.
-
Since I also match the FOV it doesn't actually matter. When the FOV is the same, all conversion methods will give the same result. If you don't want to match FOV, do indeed use Viewspeed instead.
-
Ok I see, you don't want the scope etc for the practice. Then it will be for ironsight (note the FOV for Aim Hero!): And for ACOG:
-
I know them based on the FOV scaling in R6, which is 0.9 and 0.35.
-
Like this (I see the game lack some decimals though):
-
The settings I gave you adjust the FOV of zoom 2 to be identical to ACOG in R6
-
I'm not sure if you need that, you have the exact ACOG sensitivity in the zoom 2 with the settings I gave you.
-
How do you mean, ACOG in R6 to hipfire in Aim Hero?
-
Ok, so the 16:9 stretched to 16:10 doesn't actually affect the sensitivity, so you can ignore that. For hipfire, do this: Then match both Zoom 1 FOV and sensitivity to Ironsight: Lastly match Zoom 2 to ACOG:
-
So you are playing 1920x1080 stretched to 16:10?
-
Yes, that should work.
-
Just leave the FOV type at the default, only change it if you want to convert from another type.
-
Just enter the correct resolution for the games in the calculator and everything else will happen automatically.
-
I can help you, but can you show a screenshot of your error so I can see what's wrong?
-
Yes, different engine and different formula for the sensitivity. -
Rainbow six siege sens to csgo
DPI Wizard replied to tacosdearepa's topic in Feedback, suggestions and bugs
Can you show how you fill out the calculator? -
Vsync on might be outdated information actually. The sensitivity used to fluctuate a lot with vsync off, but I think they have fixed this.
-
Sensitivity is the same as it's always been, but make sure some settings like raw input is still on after the update.
-
Try to convert from hipfire to hipfire instead.
-
I've added the zoom sensitivity with the inaccuracy as a sidenote. It is within 2% accurate above FOV 106. Hopefully the devs will fix it soon. I analyzed every FOV step between 100 and 140 to get all the data, the blue line is the actual 360 distance, the orange line is the calculated 360 distance.
-
Yeah, it's really illogical that the hipfire sensitivity is unaffected by FOV change while the zoom is affected by it even though it has a static FOV...
