Hunt: Showdown

On 8/23/2019 at 4:57 PM, DPI Wizard said:

67 vertical degrees is about 100 horizontal degrees. The game uses different FOV types in-game and in the config file so it can be a bit confusing.

Yesterday you said change the vdeg to hdeg like overwatch. but why am i changing the hdeg if when i click to convert to hunt, it auto applies vdeg? I'm confused. I just want to find the right conversion from 3.76 sens 800 dpi in overwatch to hunt showdown. vdeg and hdeg show very different results @DPI Wizard

11 minutes ago, DPI Wizard said:

You change vdeg to hdeg in the calculator so it automatically calculates the correct config FOV for you. It will tell you what you need to configure in whatever FOV type the game uses to get what you want. So if you want 100 hdeg, it will tell you to configure 67.67 in the config file, because this is the vdeg equivalent of 100 hdeg.

When you switch FOV type it will also convert the value, so if you have entered 100 for Hdeg 16:9 then switch to Vdeg, the value will change to 67.6727. 

I guess I'm misunderstanding why it'll show 100FOV when its set to Vdeg then. I feel like Im overthinking a lot of this and it's very simple

19 minutes ago, DPI Wizard said:

In-game and config file just show the value using different FOV types. The end result is the same

So if I was converting to another game like CSGO, I don't need to mess with Hdeg? Cause I've started changing all my senses according to hdeg since you told me to.

19 minutes ago, DPI Wizard said:

Actually CSGO is locked to 90 Hdeg 4:3 (which is 106.26 Hdeg 16:9 or 73.74 Vdeg), so you can't change it without enabling cheats.

The important thing when you want to match FOV is that the Actual Hdeg and Vdeg in the output is identical for all games whenever their settings allow you to change FOV. Equally important is it that the Config FOV in the output matches what you have configured in the game based on your location selection (as in-game and config file values may differ).

So if I wanna convert from Overwatch to another game, do I just leave the FOV type as the default it selects? Or will I not get an accurate conversion

50 minutes ago, DPI Wizard said:

No, you match the FOV value and FOV type from the game you are converting from, and check the output for the config FOV for the game you are converting too.

Like in this example if you were to convert from CSGO to Apex:

Ah ok. So I just copy the FOV and FOV type from what I'm converting.

It seems the hipfire calculation is off for me. I'm doing my normal sensitivity conversions as well as matching the FOV to what I always use, but my hipfire sensitivity is quite a bit different than what it should be. I'm using the exact same methods that I use for all other games which is usually bulletproof and gives the same results for each game. But for Hunt the hipfire result that I'm getting in the calculator is giving me a lower in-game sensitivity than what it should. 

Edit: The calculator is saying that the 360 distance should be the same as the game that I'm converting from, which is what I get for all other games. But in Hunt my 360 distance is like 3-5 inches longer than it should be. I don't have exact measurements right now, but it's quite a bit off.

Edit 2: Here's my conversion setup that I've been using for a long time. Got this from the 'Conversion method guide' sticky post in the Technical Discussion section.

The calculations that I get from this:

I think my issue may have something to do with the fact that I am using gunslinger mode in Hunt instead of the traditional hunter mode of aiming. I am finding a "HipMouseSensitivity" setting of 1.6 results in a hipfire 360 that is much closer to the 15.1038 inches that I expect. 

I have not tested this yet, but I wonder if when using the "hunter" style of aiming in Hunt the FOV changes when you go to the first stage of aiming, which is equivalent to gunslinger mode hip fire. If this is true, then gunslinger mode may have a lower FOV than what you set in the options/config file. 

Edit: I just watched some older videos of Hunt on youtube. The FOV does in fact change when you go from regular stance to gun ready. Gunslinger mode always has the gun at ready.

Using these settings give me much better hip fire results in gunslinger mode:

I am still using 59 for the "FieldOfView" setting in the config. In-game the FOV shows 90 in the options as it should.

maybe rename hipfire to "default (look)" and "shoulder aim" to "shoulder aim (hip fire)".

@DPI Wizard

It seems off to me. 
How shoulder aim and iron sights have a higher value than the default? They zoom in so they should be slower, that's how i felt in-game by using the calculated sens...

1 minute ago, DPI Wizard said:

The actual sensitivity values in this game have nothing to do with each other, there's no connection between aim/zoom and sensitivity. So it's not unlikely to get a very high or very low number for a conversion that in many other games produce similar numbers for all aims.

There might be small variations based on the exact weapon and aim etc, what exactly are you testing with?

I'm using 110 FOV In-game, what i'm trying to achieve is the same speed in all types of scopes in-game: 49.9cm/360º. But by using the calculator, both hipfire and ironsight seems really off, since their speed are higher compared to the default value.

I want to throw another question in there: would it be possible to get the sensitivity calculations for ingame settings to two decimal places? Since the new update it is possible to adjust the sensitivity to for example 0.43. Would be great to get more accurate sensitivity transfers (for people like me who can't find the config file to make adjustments there ). 

Going back to the calculations being off when using Gunslinger mode, I can confirm this. 

Gunslinger mode  means there is no FOV change when the stance changes from "look" to "shoulder aim".
Hunt mode has or used to have the FOV change when going from "look" to "shoulder". 

If you look to the calculations below, you can see 55cm 360º @ 90Hdeg FOV for CS:GO and converts to 103cm 360º @55Vdeg FOV.  The only way to fix the 360º distance is to increase Hunt FOV to 92.21.  However,  max fov in Hunt config is 80!!! There is no way to increase it 92.21. 

55Vdeg FOV - showing the 360º mismatch 

92.12 Vdeg FOV - showing  how to match the 360º distance but it's an impossible fov in hunt
 

@DPI Wizard What do you think?

What I also don't understand is why is the 360º distance changes with different hunt FOV settings if, on cryEngine, FOV does not affect sensitivity, meaning,  HUNT FOV 85 or HUNT FOV 110 will be exactly the same 360 distance, right?

Does anyone has any idea if I'm doing something wrong or if it's the conversion calculation that is incorrect as I suggest on my previous comment?

I manually matched the 360º distance between CS:GO and HUNT. What I confirmed is the following
1  - HUNT 360º distance is not affected by FOV
2 - Because of 1), changing HUNT FOV on the conversion calculation should not affect the 360º distance
3 - Scopes calculations are off because of FOV influence

It seems the conversion calculation is somewhat broken for HUNT and I hope someone can tell why I'm wrong or, if not, fix the calculation. 

Bah.. sorry for wasting your time with what turned out to be a stupid question. Thank you for the clarification! 

Just wanted to notify that either the calculated "ingame" values for some sensitivities are wrong or the "config file" ones. At least the results are not equal when doing a calculation (same FOV of course). Maybe you could check?

Best regards