somemadcaaant

Probably a bug, the in-game values should be 100% precise. I've added a special option for config file FOV now as it has more decimals and range.

Dunno if it was a bug, but changing to DirectX12 and restarting somehow fixed it 😅

There's nothing that uses just the GstInput.MouseSensitivityVehicle value, so it's not something that is calculated. In your case you should use the max value of 1.5 to get most of the vehicle sensitivity within range. But they are vastly different from hipfire, so for instance Transport Vehicles will still be out of range.
https://www.mouse-sensitivity.com/?share=ffbc50a6650be94a924bc8fe6f8b10ab

The following command will fix it for you:
$path = '\Documents\Battlefield 2042\settings\'; $infile = 'PROFSAVE_Profile'; $outfile = 'PROFSAVE_Profile_Patch3'; Rename-Item $env:USERPROFILE$path$infile $outfile; Get-Content $env:USERPROFILE$path$outfile | Select-String -pattern "ConceptYaw" -notmatch | Out-File -Encoding utf8NoBOM $env:USERPROFILE$path$infile Just paste that into powershell and hit enter.
 
It will rename the existing file and otherwise leave it untouched. It will then create a copy of it with the correct name and the broken lines removed. If you use nonstandard bindings you'll need to recreate them but chances are that's all. HTH

for people who cant move there mouse left and right, delete the 2042 prosave files in Documents, DICE is down tremendously :'D

Sorry this is a little offtopic but I have a couple tips that might be useful:

1) Getting your controller to work on PC
2042 wants to use your first game controller and only that one. Lots of devices have game controller abilities even if they aren't a controller (eg my mouse does) so your controller may not be seen by the game. You can use https://github.com/ViGEm/HidHide  to hide all but the one you want to use like so:


 
2) Getting OBS to capture 2042 with an RTSS overlay:
The new version of RTSS will work with BF2042 out-of-the-box, and OBS will capture BF2042 out-of-the-box, but combine all three, and OBS captures a blank screen.
You need to edit the bf2042.exe.cfg file (C:\Program Files (x86)\RivaTuner Statistics Server\Profiles\BF2042.exe.cfg) and add these two lines to the hooking section:
[Hooking] HookDXGISwapChainPresentVT = 1 HookDXGISwapChainResizeBuffersVT = 1
Enjoy.

Hipfire is added, aims are coming!

Hello,
is it possible to insert in the input-file the same code (to disable the mouse-acceleration) like in the Outriders input-file, because both games are using the UE4?
Thanks

Use a polling rate of 500 Hz or lower in this game to disable smoothing.
View full update

Smoothing doesn't affect the sensitivity in this game though, as in the 360 distance will still be correct. It does however add a small lag and can make it feel terrible.

First person is working like it should, it does not have the analog stick issue. Should be easy for R* to fix third person, hopefully they get enough feedback to pick it up. I might be able to make sensible third person calculations too despite the issues, working on that now.

It maxes out at 135, and while ADS is affected by FOV change, scope is not. All updated now

Omg thank you, I immedietly noticed something was wrong, negative acceleration is very strong in this one.

They need to be calculated separately, but just use the "All" option to calculate them both

Updated everything now

Updating it today!

This is correct for UE4 games that scale Y axis to 70% of X indeed.

It's working here, can you show me a screenshot of the entire calculator? There's probably a particular setting I need to fix.

I'll check the vertical sensitivity.

I see now thanks! The issue is that the calculation is out of range, but it's not displayed. If you switch to In-game sensitivity for Deathgarden you will see the correct error messages. I'll see if I can fix this.