DPI Wizard
-
Posts
18,144 -
Joined
-
Last visited
-
Days Won
1,763
Content Type
Profiles
Forums
Updates
Release Notes
Store
Everything posted by DPI Wizard
-
You tried this just as an update was published, so the FOV didn't get filled in. Also, for the sniper you need to enter the regular sensitivity for the calculations for work. And doing this with 360 distance doesn't work well, but if you use the default setting of the sniper it is the same as Monitor Distance 75%.
-
It uses iron sight. A more powerful scope will have the sensitivity equivalent of 0% Monitor Distance compared to this, which is how the game handles FOV changes. Changing the FOV setting in-game does not affect the scopes however.
-
Multiple conversions for one game
DPI Wizard replied to CaptaPraelium's topic in Feedback, suggestions and bugs
The FOV part is fixed now! -
Calculator updates Front-end code completely re-written. It looks visually identical, but it should be a bit more responsive. Calculation code is untouched. Some saved input will not load from the previous version, you need to enter it again. This is Sensitivity 1 and 2 for the input game, FOV and DPI for the output game. The game info is cleaned up a bit. FOV will now be kept when selecting different aims!
-
A new version of the calculator is rolled out, and the following is changed: Front-end code completely re-written. It looks visually identical, but it should be a bit more responsive. Calculation code is untouched. Some saved input will not load from the previous version, you need to enter it again. This is Sensitivity 1 and 2 for the input game, FOV and DPI for the output game. The game info is cleaned up a bit. FOV will now be kept when selecting different aims! Please report anything that does not work here!
-
I think I will replace the old Viewspeed with this one in the next update, unless someone would like to keep the old one. Since the old one is very close to 70% Monitor Distance, I would say that can be used instead.
-
360 distance and Monitor Distance/Viewspeed are not interchangeable. Having the same 360 distance with different FOVs is actually the opposite of these methods. If you have the same 360 distance with drastically different FOV, the sensitivity will be very different, as you can see here: As you can see, having a scope (i.e. different FOV) and hipfire at the same 360 distance does not make much sense. The whole point of Monitor Distance and Viewspeed is to match sensitivity based on what you see on your monitor, so moving the cross hair to a certain position on the monitor is identical between different FOVs.
-
I'll use Monitor Distance 100% to explain this since it's a bit easier to understand than Viewspeed, but they are affected similarly. If you match CSGO to OW @ FOV 103, you are matching turning (106.26/2) 53.13 degrees in CSGO to turning (103/2) 51.5 degrees in OW. Now if you instead match OW @ FOV 90, you are matching 53.13 degrees to (90/2) 45 degrees. So the distance you have to move your mouse for 51.5 and 45 degrees in these two scenarios should be identical, meaning the 360 distance (and hence sensitivity) must be different.
-
If you could set the FOV in Overwatch to 106.26 it would match perfectly with both 360 and Viewspeed/Monitor Distance. As you point out, sensitivity in Overwatch is not affected by sensitivity. This means that the 360 distance will stay the same regardless of configured FOV. But if you change FOV, you will affect Viewspeed and Monitor Distance since these matching methods only relates to your field of view (i.e. what you can actually see on your monitor), and does not take into account 360 distance at all.
-
The configured FOV affects only 1st person view (as stated in the game info), but not the others. The "Affected by: FOV" info is only in regards to whether or not changing the FOV in the game affects the sensitivity, not if using a scope or ADS with different FOV affects it.
-
Yes.
-
Set all the in-game sliders to max and enter a game (to make sure the change is written). Exit the game completely, and look for the value 00 00 20 41 repeating four times with two bytes between them like this (thanks to @Drimzi for the pic): They may or may not be at the same positions as in the pic, but they should be around the same lines. There you have your values
-
UltraEdit 30 day eval or HEX Editor plugin for Notepad++. Not sure if it works on the newest version though. I'll make a guide and check out the plugin tomorrow.
-
Yes, it is using the equivalent to 0% Monitor Match. Some might prefer around 75% though, but at least it is consistent.
-
Game added Call of Duty: WWII
-
Added hipfire and ADS sensitivity with both in-game and HEX calculations. -
Added hipfire and ADS sensitivity with both in-game and HEX calculations. View full update
-
Hex calculations added
-
Added ADS, which is essentially the exact same slider but for scopes.
-
Damn, positions are not fixed. I have them at slightly different places, but the order is obviously the same.
-
Added hipfire now! Refresh frontpage to see it. ADS next.
-
The sliders (luckily) have 50 defined steps, so I'll add a calculation for how many steps to set.
-
Found the issue here at least... Game crashes and won't start if procmon.exe is running (process monitor to see events on the computer). Thanks devs!
-
It's starting again here now, did another reboot and then the game asked to start in safe-mode. ...and crashed.
-
Still broken here. I merged two threads btw, @Robert Duarte-Dias your last post got lost.
