Jump to content

Hunt: Showdown 360 calculation, probably bug


Recommended Posts

Posted

Hello,

i just tried to convert my cs go settings to hunt: showdown.

As i wanted to match the 360 distance to the normal view and the ads view i figured out that the calculation may be is wrong.

I set both to 360 conversion from the same cs go value. But in game (hunt showdown) after several measurements, i got different in game degrees after travelling with the mouse same distance. 

I think this shouldnt be. Maybe im too stupid, but as is understood the system it shouldnt be like this. Maybe could someone look into this.

 

greetz

elrocko

  • Replies 24
  • Created
  • Last Reply

Top Posters In This Topic

  • 5 months later...
Posted (edited)

i have the same problem. in hunt showdown is it much slower

have the same fov, dpi, resolution

 

i convertet it from Battlefield V, from aim lab and from Starwars Battlefront II

Edited by zatek1991
  • Wizard
Posted
3 hours ago, zatek1991 said:

i have the same problem. in hunt showdown is it much slower

have the same fov, dpi, resolution

 

i convertet it from Battlefield V, from aim lab and from Starwars Battlefront II

Can you show a screenshot of your calculation?

  • Wizard
Posted
2 minutes ago, zatek1991 said:

calculated 360deg ratio is 35cm, but in game it is over 42cm "default look"  and 45cm or more in hipfire. thanks for help

Are you playing with the gunslinger? It uses the shoulder aim by default (HipMouseSensitivity), and that is tagged as ADS.

But this seem to cause some confusion, so I tagged it as hipfire now, so try the calculation again.

  • Wizard
Posted

I'll take a closer look at it tomorrow. I just verified the look sensitivity though, it is correct.

Does the 360 distance change in the game if you change FOV? Like set it to the default 55?

  • Wizard
Posted
Just now, zatek1991 said:

with default fov "55" (85 ingame) it ist 38cm hipfire. am I doing something wrong?

It's either a known bug with Unreal Engine 4, or they have change something in the game.

To check if it's the bug:

  • Check if you have a file called UserInput.ini under the folder %LOCALAPPDATA%\Unreal Engine\Engine\Config (important to note the space between "Unreal" and "Engine").
  • If you do, try to delete it and see if it changes the sensitivity behavior in Hunt.
Posted

is there something new? 

 

I'm not sure if this is related to the monitor distance (e.g. 4 cm mouse movement = 23 cm ingame or so) and I'm not sure if this is calculated correctly for both games or not. That's the reason why I use it, respectively why I need it.

But if I want to determine the 360 degree distance directly for Hunt: Showdown, I get the same result and that's unfortunately not true, because the calculated sensitivity is to slow. I don't know. Maybe they changed the Cry Engine. Other Games (Battlefield V, AimLab, Battlefront II, Kovaak's) are calculated correctly. I measured that.

  • Wizard
Posted

I checked now, and there was a change to the shoulder aim sensitivity, it scales differently now, but not by very much. So this is now updated and verified.

However since you get a different 360 distance when changing FOV you are probably affected by a bug in the Unreal Engine as mentioned earlier, but I'm not quite sure how to fix it if you don't have the folder and file on your system.

  • Wizard
Posted
3 minutes ago, zatek1991 said:

I thought the game uses the cry engine?

Sorry yes, CryEngine not Unreal Engine. Then it's actually more weird that your 360 distance changes with FOV.

Can you test something? Set FOV to 55 and sensitivity for look and shoulder aim to 1 and see how far a 360 is. Then set the FOV to 74 and try the same. 

Posted (edited)

ok i did it

 

dpi: 600

FOV "55" (config) sens 1- free look  -> approximately 47,5 cm

FOV "55" (config) sens 1- hipfire  -> approximately 52 cm

FOV "74" (config) sens 1 -free look -> approximately 47,5 cm

FOV "74" (config) sens 1 -hipfire -> approximately 52

it's hard to do that exactly, not 100%, but i hope it's ok so

FOV transformation is ok i think, but the sens aren't. ~12 cm more than calculated in free look.

Edited by zatek1991
  • Wizard
Posted
1 hour ago, zatek1991 said:

ok i did it

 

dpi: 600

FOV "55" (config) sens 1- free look  -> approximately 47,5 cm

FOV "55" (config) sens 1- hipfire  -> approximately 52 cm

FOV "74" (config) sens 1 -free look -> approximately 47,5 cm

FOV "74" (config) sens 1 -hipfire -> approximately 52

it's hard to do that exactly, not 100%, but i hope it's ok so

FOV transformation is ok i think, but the sens aren't. ~12 cm more than calculated in free look.

Thanks, FOV doesn't affect it then that's good.

It seems like your DPI is actually 450 and not 600 here (then everything lines up), do you have a mouse driver that might load another profile when you start the game?

Posted (edited)

i use the roccat swarm software and actual mouse drivers (roccat kone aimo). but why is there only in hunt showdown a problem? the calculations for battlefield v and other games are correctly, only in  hunt showdown i have these issue.

 

I do not have a saved profile in this software, the dpi switch is deactivated. The mouse settings are always activated, i.e. both in the game and in windows itself. if I change the dpi, I change it for everything.

 

Software Ver:  V1.9361

Driver Ver: V1.22

 

 

Hunt Sensitivity3.PNG

Edited by zatek1991

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...