DPI Wizard
-
Posts
18,144 -
Joined
-
Last visited
-
Days Won
1,762
Content Type
Profiles
Forums
Updates
Release Notes
Store
Everything posted by DPI Wizard
-
It's a personal preference, but try Viewspeed first. It's about the same as 70% Monitor Distance.
-
PUBG: BATTLEGROUNDS (PlayerUnknown's Battlegrounds)
DPI Wizard replied to DPI Wizard's topic in Supported Games
They are all based on FOV 80 yes, but as a general rule always enter your configured FOV in the calculator regardless. It will just ignore what you entered if the FOV is fixed. -
Game added No Man's Sky Games update Lawbreakers - Adjust minimum and maximum sensitivity. Team Fortress 2 - Added sniper calculations. War Thunder - Added in-game sensitivity.
-
Added! View full update
-
Added! -
Ok, it needs updating then.
-
Actually it was a small typo here, the aiming sensitivity is the "MouseAimingSensitivity": value in the config file, not the "MouseSensitivity": one. Try again with the correct value
-
convert csgo awp sensitivity to tf2 sniper zoom
DPI Wizard replied to hrtz's topic in Technical Discussion
Added it now Makes most sense to use it with Monitor Distance or Viewspeed obviously. The FOV is 20 in 4:3 res. -
This causes some confusion from time to time, but it is referring to entering the sensitivity in the console in-game as opposed to in the menus, not the sensitivity setting on a gaming console
-
They probably changed something as this game is in development. Is the closed beta ongoing now, so I get immediate access if I buy the game?
-
They fixed it now, 0.1 is the new minimum
-
Just tested it, and yes they finally fixed it! Need to do some analysis, aiming to add it tomorrow.
-
They moved things around a bit, I've updated the path and filename and added in-game calculations as well
-
It apparently has both acceleration and aim assist you can't turn off at the moment.
-
It's Unreal Engine 4 though, so it might work fine unless they removed the ability to disable smoothing and acceleration.
-
I'll check it out in a day or two, but those kind of games are often lazy console ports when it comes to mouse sensitivity
-
Black bars is a bit more tricky, but if you're playing with 4:3 stretched to the edges of the monitor, entering the 4:3 resolution will be correct.
-
It does matter, but as long as you enter the correct resolution the FOV will be calculated and shown in the output (Actual HFOV).
-
Are you entering all the values for CS GO? You need to enter both the base sensitivity and the zoom sensitivity.
-
As the calculator works now, just enter your 4:3 resolution and the calculations will be correct
-
If you're not using raw input you can select the Hipfire (Advanced) calculation. This will require you to also enter the m_yaw value. The reason WPS is grayed out is because sensitivity without raw input on is a lot more inaccurate, so you should always use it when possible.
-
This is because the FOV's are different. You could match 360 distance instead of Monitor Distance for hipfire, which some might prefer because they find it more important to have the feeling of a 90 or 180 degree turn, than to snap to an object on the monitor (which Monitor Distance is for).
-
This game scales very weirdly with the scopes and FOV... Not sure what to make of it yet. And the fact that it only really zooms the scope makes it even weirder.
-
Was thinking about scope sway, I guess I'll just have to handle it... Makes analyzing it a bit harder
-
I will look at it tomorrow. Anyone knows if it's possible to disable weapon-sway through console?
