The Outer Worlds

Well, the

MouseSensitivityValue=0.042861

doesn't give me 360, it gives me somewhere 270 degrees for 45.1781 cm

21 minutes ago, hoodfury said:

Well, the

MouseSensitivityValue=0.042861

doesn't give me 360, it gives me somewhere 270 degrees for 45.1781 cm

Same with me, sensitivity advised by caculator makes aroun 270' not 360'.

15 minutes ago, DPI Wizard said:

The bug is that UE4 reads some generic file.

Check if you have a file called UserInput.ini under the folder %LOCALAPPDATA%\Unreal Engine\Engine\Config.

If you do, try to delete it and see if it changes the sensitivity behavior in the game.

NoUserInput.ini file in my unreal engine folder : (

14 minutes ago, DPI Wizard said:

 

For both of you, Epic or Windows Store version? And if you change FOV does the 360 distance change? Should be easy to check if you set it from 75 to 110 for instance.

I just verified that the calculations are correct for Steam.

Do you have any files/folders there at all?

Windows Store version

Yes the 360 ingame distance changes with FOV changing.

Inside this folder i have 3 folders named 4.11, 4.16, 4.21 inside those are anothers folders and finnaly "manifest" file.

Well i did it and i dont know what to say but the spin with this program is right.

I  converted form apex legends to outter worlds and i see that this spin is right but it just feels off.

thanks anyway, sorry for problem.

A heads up: For people using the Game Pass version of the game, the config file location is:

%LOCALAPPDATA%\Packages\PrivateDivision.TheOuterWorldsWindows10_hv3d7yfbgr2rp\LocalCache\Local\Indiana\Saved\Config\WindowsNoEditor\

Just now, DPI Wizard said:

The last part after Windows10 (hv3d7yfbgr2rp) is a unique string for your system. Either way I'm pretty sure this is only a temporary file. I've got both versions now (Epic and Game Pass), and the file isn't currently there.

But when I launched the Game Pass version the first time (after first have been using Epic) it had all the settings from Epic, so it should be reading from the same file %LOCALAPPDATA%\Indiana\Saved\Config\WindowsNoEditor\GameUserSettings.ini as far as I can tell.

Do you have this file?

Alternatively maybe the game first checks for %LOCALAPPDATA%\Indiana\Saved\Config\WindowsNoEditor\GameUserSettings.ini, and if it doesn't exist it creates a file in the inaccessible part of the filesystem that Windows Store is so keen on using, then makes a shadowcopy in LOCALAPPDATA. I'll check some more!

I've taken this exact location from https://www.pcgamingwiki.com/wiki/The_Outer_Worlds, the string does not seem to be unique as it works perfectly on my end. The location listed in the converter didn't work for me, don't even have a %LOCALAPPDATA%\Indiana folder.

the sens is too slow for me for some reason.

ms store, 36 cm/360°, 1040 dpi, fov 120, MouseSensitivityValue=0.018319

but i need more like ~0.021 sens to get that distance.

just with a measuring tape.

yes, i also just realized it's the same problem that i have in gears 4 and 5.

when i alt tab out and change polling rate to 250 hz in the logitech gaming software, the sens becomes a bit faster and if i then change it back to 1000 hz it will be incredibly slow.

so basically the same polling rate results in a different sens depending on whether i start the game with that polling rate or switch to it while the game is running.

I changed form 1000 Hz to 250 and differnece is so clear. Can i keep it at 250? Does it make a difference in other games like Apex legends?

This is from mouse smoothing. Deep rock galactic had the same exact issue until the devs added a toggle to options from my bug report. I believe the config entry to fix remove it is:

[Engine.PlayerInput]
bEnableMouseSmoothing=false

In Input.ini

Possibly also 

bViewAccelerationEnabled=false

but I don't know if it actually does anything or not.

2 hours ago, DPI Wizard said:

The weird thing is that it's impossible to provoke using scripts or mouse emulators as far as I have tested. Smoothing is usually very easy to both test and visually see. And the fact that it overshoots with 500 Hz and undershoots with 1000 Hz while 125 and 250 is correct is also very strange.

Back when I was testing it in deep rock galactic I was able to somewhat reproduce it with the following AHK script:

#NoEnv
#MaxHotkeysPerInterval 99000000
#HotkeyInterval 99000000
#KeyHistory 0
ListLines Off
Process, Priority, , H
SetBatchLines, -1
SetKeyDelay, -1, -1
SetMouseDelay, -1
SetDefaultMouseSpeed, 0
SetWinDelay, -1
SetControlDelay, -1
SendMode Input
SetWorkingDir %A_ScriptDir%

pixels := 30 * 800 / 2.54
steps := 1000
pixels := Round(pixels)
stepSize := Round(pixels / steps)
steps := Ceil(pixels / stepSize) - 1
lastStep := pixels - steps * stepSize

End::
	t := 0
	while t < steps {
		t++
		DllCall("mouse_event", "UInt", 0x0001, "UInt", stepSize, "UInt", 0)
		DllCall("Sleep", UInt, 1)
	}
	DllCall("mouse_event", "UInt", 0x0001, "UInt", lastStep, "UInt", 0)
	KeyWait, End
Return

Numpad0::
	DllCall("mouse_event", "UInt", 0x0001, "UInt", pixels, "UInt", 0)
	KeyWait, Numpad0
Return

Numpad2::
	DllCall("mouse_event", "UInt", 0x0001, "UInt", 0, "UInt", pixels)
	KeyWait, Numpad2
Return

NumpadAdd::
	pixels++
	DllCall("mouse_event", "UInt", 0x0001, "UInt", pixels, "UInt", 0)
	KeyWait, NumpadAdd
Return

NumpadSub::
	pixels--
	DllCall("mouse_event", "UInt", 0x0001, "UInt", pixels, "UInt", 0)
	KeyWait, NumpadSub
Return

NumpadEnter::
	MsgBox, %pixels%
	KeyWait NumpadEnter
Return

Home::Reload
	

pixels is the number of steps to turn to the right, steps is how many "chunks" you want the turn divided into. So in this case it divides the turn into 1000 steps. End to run the script.
DllCall("Sleep", UInt, 1) is more accurate that AHK's default sleep and is able to get closer to 1ms delay so it simulates high polling rate mice better.

On 26/10/2019 at 23:53, Skwuruhl said:

 

[Engine.PlayerInput]
bEnableMouseSmoothing=false
bViewAccelerationEnabled=false

In Input.ini

With the Xbox Game Pass version of the game these 3 lines inside the input.ini seemed to fix it for me. It certainly got better at least. If i get some trouble later on i'll change the polling rate to 250.

Regarding Polling Rate. It's the amount of times per second the mouse updates the position. Lower Polling Rate = more choppy mouse movement.