H1Z1

Okay thanks

Is it intentional that resolution affects sensitivity in H1 while it doesn't in other games like CSGO?

By any chance is the 360 degree setting for when your in first person? Because it doesnt matter what FOV I use I get the same value

If not do you know of a way I can calculate the speed for first person in H1? I am trying to perfectly match CS and I figure if I can 100% match the first person in CS to the first person in H1 than I am set because the resolution and FOV for viewspeed changes everything and even if I have a matching viewspeed in 3rd person my first person will be off because the FOV will always stay the same. For example 12% with 67 FOV has a different viewspeed than 12% with 70 however it doesnt matter if I use 67 or 70 FOV in first person but the sensitivities will be different.

I also dont think resolution plays any role in the sensitivity. I set my sensitivity to 17.05% and was able to do an exact 360 degree rotation in first person in 1440x900, 1600x900 and 1024x768.

Hi @DPI Wizard,

What's the go with H1Z1's FOV in terms of first person & third person? The tool says that the default is 55, but the default in useroptions is 70. If first person & third person have different FOV's, which it seems like to me, does this need to be added? Or am I missing something?

Thanks for your time.

1 minute ago, knocksee said:

Hi @DPI Wizard,

What's the go with H1Z1's FOV in terms of first person & third person? The tool says that the default is 55, but the default in useroptions is 70. If first person & third person have different FOV's, which it seems like to me, does this need to be added? Or am I missing something?

Thanks for your time.

I feel like the FOV is different in third person too, but I've talked to dev's about it and they claim the FOV doesnt change, rather the camera just pans back/forward depending on first and third person.

7 minutes ago, KandiVan said:

I feel like the FOV is different in third person too, but I've talked to dev's about it and they claim the FOV doesnt change, rather the camera just pans back/forward depending on first and third person.

Yeh I feel the same. You can match H1Z1's FOV to Overwatches by setting it to 71 i think. However, Overwatch still looks more zoomed in than this...maybe its just my eyes..

2 minutes ago, knocksee said:

Yeh I feel the same. You can match H1Z1's FOV to Overwatches by setting it to 71 i think. However, Overwatch still looks more zoomed in than this...maybe its just my eyes..

yea 71 is the closest you'll get. 71 vFOV = 103.48 actual hFOV (what overwatch uses). Not perfect, but overwatch will feel more zoomed.

50 minutes ago, KandiVan said:

yea 71 is the closest you'll get. 71 vFOV = 103.48 actual hFOV (what overwatch uses). Not perfect, but overwatch will feel more zoomed.

How come it feels like that though. Is it simply an optical illusion because h1z1 has more 'distances' in it than overwatch?

EDIT: Well I did a quick test by comparing 3rd person view to 1st person and they do seem the same FOV. Guess it's just my eyes!

Should we still change the default to 70 in the tool though?

6 hours ago, Drimzi said:

Viewmodels can make a big difference in the perceived fov, if you match fovs and one game has really big viewmodels, that game will look more zoomed in.

 

The fov you set in the tool is the fov you have set for your game, if u have set the game to 70, then use 70 in the calculator. Make sure to set 70 when you change the aim type too.

I think your right. It's the viewmodels. H1Z1's are so much smaller. I'm about to say something either interesting or completely stupid but bear with me. I use 11@450dpi in overwatch at 103hfov. When I convert this to H1Z1, it becomes .20 default & .30 ADS. Now using this sens for H1Z1 is really quite different & hard because the viewmodels are much smaller and the sens is quite fast. Is it possible for any calculations to be made to take viewmodel sizes into account?

2 hours ago, Drimzi said:

The viewmodel is the first person character model (your arms, hands, gun, etc.) Viewmodels shouldn't really affect your perceived sensitivity, at least it doesn't for me. It does make it seem like the fov is smaller than it really is though if they viewmodel does not scale with the fov. Usually the viewmodel will scale, but in some cases you can end up changing the game from it's default "console port" fov to a higher one and the viewmodel's fov will stay exactly the same, making the game look like it has a lower fov than another game that has the viewmodel scale correctly.

If by viewmodel you are referring to enemy models, then what you are seeing here is aiming within your full screens width verses aiming at just the middle 5% of your screen. In H1Z1 long range encounters are common, where all the aiming is done within a tiny portion of the screen. This is where you need to specifically practice this type of aim as it will usually require very fine finger and wrist dexterity, and is not something you will usually practice. There really isn't any kind of conversion or algorithm to fix this, you simply need to practice fine aim or make a compromise with your sensitivity.

Ah thanks Drimzi! Sorry I was thinking the viewmodels were enemy models for some reason. The viewmodels are pretty much the same as overwatch when I compared screenies. I think you're spot on with your H1Z1 analysis. You can't really convert sens to it if you use a high sens in other games. Just something you either have to change or practice with. Thanks for the information.

Is the movement in 1st person faster than in 3rd person? I ask because I decided to try and match sensitivities by going into H1 1st person and doing a 360 and in CSGO and doing a 360 and to get the exact same 360 I would need to have a H1 sensitivity of 17% which is the same as your calculators 360 distance but your calculator is saying to match the viewspeed it would have to be 13%. Isn't the viewspeed the exact same if I can do a 360 in both games?

So even if I can do a 360 in both games with a specific sensitivity in 1st person, it would be a slower one in 3rd person because the FOV is different?

On 2017-6-14 at 11:18 PM, Drimzi said:

The viewmodel is the first person character model (your arms, hands, gun, etc.) Viewmodels shouldn't really affect your perceived sensitivity, at least it doesn't for me. It does make it seem like the fov is smaller than it really is though if they viewmodel does not scale with the fov. Usually the viewmodel will scale, but in some cases you can end up changing the game from it's default "console port" fov to a higher one and the viewmodel's fov will stay exactly the same, making the game look like it has a lower fov than another game that has the viewmodel scale correctly.

If by viewmodel you are referring to enemy models, then what you are seeing here is aiming within your full screens width verses aiming at just the middle 5% of your screen. In H1Z1 long range encounters are common, where all the aiming is done within a tiny portion of the screen. This is where you need to specifically practice this type of aim as it will usually require very fine finger and wrist dexterity, and is not something you will usually practice. There really isn't any kind of conversion or algorithm to fix this, you simply need to practice fine aim or make a compromise with your sensitivity.

On 2017-6-14 at 7:22 PM, knocksee said:

I think your right. It's the viewmodels. H1Z1's are so much smaller. I'm about to say something either interesting or completely stupid but bear with me. I use 11@450dpi in overwatch at 103hfov. When I convert this to H1Z1, it becomes .20 default & .30 ADS. Now using this sens for H1Z1 is really quite different & hard because the viewmodels are much smaller and the sens is quite fast. Is it possible for any calculations to be made to take viewmodel sizes into account?

 It takes time and a lot of practice like drimzi said. Im a pro h1 player matched to 4/11 windows sens at 400 dpi, im damn near the only one that plays on higher ADS sens. Everyone plays on low ADS because it makes it easier at long range to two tap, but i think the consistency that comes from viewspeed is gonna be worth it in the long run. I find doing smaller repetitive movements on your desktop, like crafting in runescape, help a lot with the ADS fine tuning on h1.

Quick question just to make sure it is working as intended.

If I am playing with 0.01 sensitivity @ 800 DPI shouldn't my sensitivity @ 400 DPI be 0.02 rather than 0.09 like your calculator says? In every other game I have tested, going from 800 DPI to 400 DPI just doubles your sensitivity except for H1Z1.

7 minutes ago, Harrison Swinson said:

Quick question just to make sure it is working as intended.

 

If I am playing with 0.01 sensitivity @ 800 DPI shouldn't my sensitivity @ 400 DPI be 0.02 rather than 0.09 like your calculator says? In every other game I have tested, going from 800 DPI to 400 DPI just doubles your sensitivity except for H1Z1.

Hmm, your right. Seems like h1z1 is the only game that doesn't just x2 the senses when you x2 the dpi's.

@Drimzi @DPI Wizard

9 minutes ago, Harrison Swinson said:

Quick question just to make sure it is working as intended.

 

If I am playing with 0.01 sensitivity @ 800 DPI shouldn't my sensitivity @ 400 DPI be 0.02 rather than 0.09 like your calculator says? In every other game I have tested, going from 800 DPI to 400 DPI just doubles your sensitivity except for H1Z1.

H1's funky, it scales weirdly. But its correct as far as im aware, as you increase sensitivity the cm/360 it decreases isnt linear. IE: From 0.05 -> 0.06 its a decrease in cm/360 of 3.0243 inches, whereas from 0.06 -> 0.07 its a decrease in cm/360 of 2.706 inches. The amount it decreases the cm/360 for a set increase in sensitivity gets smaller and smaller as you increase the sensitivity.

5 hours ago, DPI Wizard said:

No, it doesn't scale linearly with DPI, which is where the calculator comes in really handy

Several games are actually like this (almost 50 of the ones currently in the calculator), like Battlefield 1, 3, 4, Minecraft, Planetside 2 and pretty much any game with a minimum sensitivity of 0 or below.

Ah! I should have said games I play haha.. thanks dpiwizard!