See the game notes for instructions on how to disable smoothing etc, a mod is needed to fix the current issues.

View full update

Aiming and scope coming soon™.

props for figuring out the sensitivity equation for this game bc it's nightmarish. I couldn't for the life of me figure it out. It's like a 2-step equation split at 0.5.

22 minutes ago, Skwuruhl said:

It's like a 2-step equation split at 0.5.

Absolutely correct, it's like this:

While this is not common, there's quite a few games with a different scaling before and after a specific value. The real nightmare is when there's multiple scales and the cutoff is less obvious, we've got a few of those too!

Just a tip; the FOV line in the config file won't appear unless you have changed the FOV in game.

4 minutes ago, TheNoobPolice said:

Just a tip; the FOV line in the config file won't appear unless you have changed the FOV in game.

This also goes for all the sensitivity values, and they will appear in a random order 😵‍💫

Config options in general only show up if you've changed the setting in-game. But if a setting is missing you can just add it, generally. Nothing will break if you reorder stuff either.

Edited July 28, 20232 yr by Skwuruhl

Since the mod has two versions (one removes FOV scaling, one doesn't) you might want to clarify which to use in the Notes section

Edited July 28, 20232 yr by Rukishou

7 minutes ago, Rukishou said:

IDK if it matters since we specify ADS/scope sens (once they're added) anyway, but the mod has two versions so you might want to clarify which to use in the Notes section

I've clarified it now, and will add support for both!

Unless you want to avoid this precisely due to the case of doing additional work in the event the devs patch it, I'd suggest since the site support is dependant on using a mod anyway, that you form the basis using the mod which both fixes x and y scale disparity, removes FOV scale (which is a good thing) and also downscales sens to 1 multiplier (since it is too high by default for any reasonable settings).

Actually, the xy mod doesn't disable FOV scaling and doesn't seem to affect aiming xy relationship, only "look" sens as far as I can see, so no point in the above.

Edited July 31, 20232 yr by TheNoobPolice

Support for both with and without FOV scaling is added now.

ADS and scopes added, but only for "PreserveFOVScaling" as this is how the base game actually works.

So do I understand correctly that if FOV scaling is turned off, the aim and scope sensitivities don't really matter?

Is there any advantage to PreserveFOVScaling+all sensitivities vs NoFOVScaling and only the base sensitivities?

7 hours ago, ModusPwnens said:

So do I understand correctly that if FOV scaling is turned off, the aim and scope sensitivities don't really matter?

They do still matter, but the sensitivity is scaled in a completely different way.

7 hours ago, ModusPwnens said:

Is there any advantage to PreserveFOVScaling+all sensitivities vs NoFOVScaling and only the base sensitivities?

Yes, if/when the devs fix the issues, it will most likely act exactly like PreserveFOVScaling. There is no benefit of using the NoFOVScaling version at all, other than the fact that it came first.

On 02/08/2023 at 09:54, ModusPwnens said:

So do I understand correctly that if FOV scaling is turned off, the aim and scope sensitivities don't really matter?

Is there any advantage to PreserveFOVScaling+all sensitivities vs NoFOVScaling and only the base sensitivities?

It's better for games to not tie the FOV option to camera turn-rate for "look" or what is usually hipfire etc. I don't buy for one second that any uninitiated user expects their 180 turn / navigation mouse movements to change when they change the Field of View in the graphics options, and it's annoying if you just need to lower the FOV for say, performance issues (which are abundant in this game) and it changes your mouse sensitivity etc.

So if you like being able to tweaking the FOV as you play for whatever reason, it's best to disable the FOV mouse sens scaling.

12 hours ago, TheNoobPolice said:

I don't buy for one second that any uninitiated user expects their 180 turn / navigation mouse movements to change when they change the Field of View in the graphics options, and it's annoying if you just need to lower the FOV for say, performance issues (which are abundant in this game) and it changes your mouse sensitivity etc.

To make matters worse, games like this (where the sensitivity is tied to the actual horizontal FOV) also significantly changes the sensitivity when you change aspect ratio.

23 hours ago, DPI Wizard said:

To make matters worse, games like this (where the sensitivity is tied to the actual horizontal FOV) also significantly changes the sensitivity when you change aspect ratio.

I primarily blame Epic for a lot of this as going back quite few UE frameworks now, they have persisted with strange defaults, like Vert- for game world FOV scaling which makes little sense; why would anyone move to a wider screen monitor and expect the top and bottom of the image to be cropped instead of the horizontal view expanded to fill their new screen? It is better to just not support higher aspect ratios than to make a mockery of them. Thankfully many game devs do change that one, but we see a lot of camera smoothing left enabled as you know.

Has anyone tested if inputting the following lines of code in works in version Patch Version: 384,210 (Released Today: 8/10/23) or Patch Version: 383,678 (Released: 8/04/23) without modding the game? I know it's not mentioned in the patch notes, but someone with more technical knowhow might know.

 

[/Script/Engine.InputSettings]
bEnableMouseSmoothing=False
bViewAccelerationEnabled=False

11 hours ago, xFilipinoThunda said:

Has anyone tested if inputting the following lines of code in works in version Patch Version: 384,210 (Released Today: 8/10/23) or Patch Version: 383,678 (Released: 8/04/23) without modding the game?

Still doesn't work, the mods are needed to fix the issues.

They changed something with latest patch, so your calculation all wrong with (No More Mouse Smoothing (NoMouseSmoothingOnly_PreserveFOV) mod

Have you updated the Allow Asset mod file?

Depending on when you last updated it, it may need a new version also.

That said I wouldn't be surprised if something has gone wrong because the last round of patching has been awful, so many things have been broken.

I've updated the calculations using the latest version of the mod NoMouseSmoothingReducedScaling. I've also removed the NoFovScale entry as there's basically no reason to use it over the other.

The sensitivity was changed significantly (1/3 of before), and the X and Y are now the same.