Jump to content

Starfield


Recommended Posts

Posted
  1. I noticed another option "fMouseHeadingSensitivity" in the setting that affects the sensitivity. Does the game multiply them?
  2. Why are the X and Y axis values different?
    image.png.0e909e6a1a0c97126959186c20781512.png
Posted (edited)

BRUH THIS GAME GOT ADDED BEFORE ARMORED CORE 6 :((((((((((

 

For this option to show for me, I had to change the ingame slider to some random value

 

Ironsights / ADS also are missing

 

 

1st/3rd person has diff sens, seems like the calculator is only accurate to 1st person

 

image.png.7df9f86f2c973f9b88336bd4ff52a2ba.png

Edited by STR8_AN94BALLER
Posted

If possible it would be great for the following to be added or explain what values they should be set as:
1. fMouseHeadingSensitivity
2. fIronSightsLookSpeedYaw
3. fIronSightsLookSpeedPitch

Posted
13 minutes ago, DPI Wizard said:

Mouse Look Sensitivity/fMouseHeadingSensitivity and in-game sensitivity is added, ADS coming up next.

I changed sensitivity (normal, ADS) a few times in games but I could not get fMouseHeadingSensitivity  to show in the .ini file

 

 

  • Wizard
Posted
1 minute ago, STR8_AN94BALLER said:

I changed sensitivity (normal, ADS) a few times in games but I could not get fMouseHeadingSensitivity  to show in the .ini file

 

 

You need to change "Mouse Look Sensitivity" in-game.

  • Wizard
Posted
3 minutes ago, SaeedGozai said:

The vertical sensitivity seems way faster than the horizontal sensitivity.

Note that the Vertical sensitivity is listed above Horizontal in the in-game menu (opposite of the calculator output), so make sure you set the sensitivity to the correct axis.

Posted (edited)

until raw mouse input mod comes out, here is what I did in StarfieldCustom.ini:
fMouseHeadingXScale=.0210
fMouseHeadingYScale=.0210
fMouseHeadingNormalizeMax=100.0000
fIronSightsLookSpeedYaw=1.43
fIronSightsLookSpeedPitch=1.35
fLookSpeedYaw=0.73
fLookSpeedPitch=0.70
fPitchSpeedRatio=1.0000
fIronSightsPitchSpeedRatio=1.0000
fMouseHeadingSensitivity=0.0045
bMouseAcceleration=0

(I'm sure half of those are placebo, but it just works™)

fMouseHeadingYScale like those below don't work for me, Y still feels off with those, so .0210 and .0210 works best for me.  fMouseHeadingSensitivity=0.0045 is for DPI 1600, I used my fallout 4 calculations, so use your own
0.03738 for 16:9
0.042 for 21:9
0.028 for 4:3
0.0336 for 16:10
0.07467 for 32:9

Edited by AIucardd
Posted (edited)
2 minutes ago, AIucardd said:

fIronSightsLookSpeedYaw=1.43
fIronSightsLookSpeedPitch=1.35
fLookSpeedYaw=0.73
fLookSpeedPitch=0.70

yes, I did those the same numbers and used it with  fMouseHeadingXScale=0.0210 and fMouseHeadingYScale=0.03738, still felt off for me.

Edited by AIucardd
  • Wizard
Posted
17 minutes ago, AIucardd said:

fMouseHeadingYScale like those blow don't work for me, Y still feels off with those, so .0210 and .0210 works best for me.  fMouseHeadingSensitivity=0.0045 is for DPI 1600, I used my fallout 4 calculations, so use your own
0.03738 for 16:9
0.042 for 21:9
0.028 for 4:3
0.0336 for 16:10
0.07467 for 32:9

The hipfire Y scale does not change with aspect ratio (at least not for me). So unless something is affecting it in certain cases, it doesn't make sense to change it based on your aspect ratio.

When I test the vertical 360 distance it is exactly 1.777778 times further than the horizontal sensitivity with the same values, regardless of my actual aspect ratio, be it 21:9 or 16:9.

Note that ADS behaves completely differently, and will be affected differently by both aspect ratio and FOV.

I also have absolutely no issues with smoothing, acceleration, packet loss, stuttering or high polling rates, but I understand that there are quite a few issues with graphics drivers etc that probably affects a lot of players at the moment.

Posted
1 hour ago, DPI Wizard said:

The hipfire Y scale does not change with aspect ratio (at least not for me). So unless something is affecting it in certain cases, it doesn't make sense to change it based on your aspect ratio.

When I test the vertical 360 distance it is exactly 1.777778 times further than the horizontal sensitivity with the same values, regardless of my actual aspect ratio, be it 21:9 or 16:9.

Note that ADS behaves completely differently, and will be affected differently by both aspect ratio and FOV.

I also have absolutely no issues with smoothing, acceleration, packet loss, stuttering or high polling rates, but I understand that there are quite a few issues with graphics drivers etc that probably affects a lot of players at the moment.

there's no launch drivers for nvidia gpus yet

Posted
13 hours ago, STR8_AN94BALLER said:

there's no launch drivers for nvidia gpus yet

The Game Ready Driver for Starfield already came out almost two weeks ago, it's 537.13. That said, I have a strong feeling there will be another one to fix the abysmally low power draw even though the GPU is at 99% utilization.

Posted
1 hour ago, DPI Wizard said:

It works for hipfire, but the sensitivity scale is different. It does not solve the vertical axis issue for ADS though.

So we still have to use separate pitch and yaw sens value for mouse?

 

Also any idea on the discrepancy between FPS and 3rd person?

  • Wizard
Posted
51 minutes ago, STR8_AN94BALLER said:

So we still have to use separate pitch and yaw sens value for mouse?

Yes.

51 minutes ago, STR8_AN94BALLER said:

Also any idea on the discrepancy between FPS and 3rd person?

I've added 3rd person now, it's the "Mouse Look Sensitivity" value, that in turn affects the 1st person view.

For this reason it's pretty much required to use the config file to avoid the calculations being out of range.

Also added Rifle ADS!

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...