NilValue

Sad, but thanks :)

The path to the config file does not exist and the calculate sensitivity value is incorrect. Setting 804 DPI, 110° FOV and 39.314cm for 360° gives AxisConfig=(AxisKeyName="MouseX",AxisProperties=(DeadZone=0.000000,Sensitivity=0.009469,Exponent=1.000000,bInvert=False)) AxisConfig=(AxisKeyName="MouseY",AxisProperties=(DeadZone=0.000000,Sensitivity=0.009469,Exponent=1.000000,bInvert=False)) But that results in around 43cm per 360° New path seems to be: ...\AppData\Local\WitchIt\Saved\Config\Windows\InputUserSettings.ini :)

Is that already reflected in the calculator?

Then this would mean that we can have 0% with everything set to 1, as a result, I suppose? Because the way it is now, you'd ahve to decide for which 1-2x scope you want it to be correct

That is sad, it means that you cannot really make a setting that perfectly gives you 0% monitor distance, can you? Does not look like that to me from the gameplay videos though:

So that means that the actual zoom level "within" the scope is not the same as outside of it, in this game? Like Tarkov, for example?

Setting Monitor distance vertical to 0 in the calculator and then the monitor distance coefficient to 0, I get different sensitivities for the different settings, is that correct? Should they not be at least all the same, at least for the individual setting options (see the 0.87 for the 1-2 option)? Otherwise, what is the point of having a monitor distance coefficient in this game?

Just checked the calculator and it seems perfect now

Updating the input.ini works for me, just as the calculator states. However, there is no need to set different values for vertical and horizontal mouse since settings horizontal==vertical makes it 1:1. I have not tried actually making changes to the FG.MouseSensitivity value in the file.

Hi I have started to play Satisfactory and noticed the following things: The calculator gives me different values for X and Y axis to configure in the config file. However, I do not think that this actually correct, it feels like (and I also measured it) it already is at 1:1 vertical to horizontal sensitivity. Also, the mFOV value does not exist in the config file (seems to be called "FG.FOV" now), while the bEnableMouseSmoothing=False key-value is not contained in the file either. I also think that there is a new mouse sensitivity setting available in the GameUserSettings.ini: "FG.MouseSensitivity". I think that the calculator configuration is very outdated

So setting vertical to the same value as horizontal ingame would be the best approach Thanks

Is that intended? Does the game need me to do that? I would expect that this would result in different sensitivities for vertical and horizontal (which I do not think anyone would want, at least not by default).

Okay then, thank you

Btw, some additional info: - The Steam version seemed to be fine (Vulkan and DirectX). I bought it on Ubi Store directly and after installing the Ubisoft Connect Only version, the raw input seems inconsistent. - I play the Vulkan version

1000hz mouse, raw input seems bugged to me when I measure it (360° turn distance is inconsistent). Can anyone here confirm this?