Starfield

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?
   

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

Edited September 3, 20232 yr by STR8_AN94BALLER

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

Just now, DPI Wizard said:

All will be added, (including in-game sens) working on it now

sir how about armored core? :DDDDDDDD

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

The vertical sensitivity seems way faster than the horizontal sensitivity.

I don't use the in-game menu, it's purely through the ini file, but something still feels off.

Thank you for your rapid responses and for your efforts.

fShipReticleMovementSensitivity

For flight controls

Seems to play similarly compared to war thunder?

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 September 3, 20232 yr by AIucardd

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 September 3, 20232 yr by AIucardd

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

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.

TRUE AIM at Starfield - Nexus Mods
Thoughts on this?

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?

I have tried this and it seems perfect for me:

• I put both ratio to 1 to get sensitivity x=y.
• I keep yaw and pitch to 1 as they seem to multiply the mouse heading sensitivity
• ADS pitch and yaw seem to have lower multiply than normal ones. I kept them to 1 since I don't mind too much slightly slower ADS.
• I just change "fMouseHeadingSensitivity" to adjust sensitivity.

I use 37.1104 cm/360° (400 DPI) and this is right on point. I feel like it would be way easier to go about it this way and simply adjust one line for sensitivity (+2 for ADS if we find proper ratio with normal look). These settings also make 3rd person use the same sensitivity as 1st person, I don't what does it though.

[Controls]
bMouseAcceleration=0
fMouseHeadingSensitivity=0.01629628
fPitchSpeedRatio=1
fLookSpeedPitch=1.0000
fLookSpeedYaw=1.0000
fIronSightsPitchSpeedRatio=1
fIronSightsLookSpeedPitch=1.0000
fIronSightsLookSpeedYaw=1.0000

Edited September 5, 20232 yr by Iron