Anthem

11 hours ago, Bunnikinz said:

@DPI Wizard

I found this on reddit. Maybe we were looking at the calculations wrong? What do you think?

https://www.reddit.com/r/AnthemTheGame/comments/ak8h8x/no_spoilers_how_to_disable_mouse_acceleration/

Setting GstInput.MouseSensitivity to 1 in the beta solved some acceleration issues when in 1st person, but didn't have any effect on the Javelin. For the release version 1st person is fixed and doesn't have acceleration anymore, but the Javelin is the same.

I just realized they completely broke the scaling for GstInput.MouseSensitivity in the release though, so I removed it from the calculation and added a note saying it has to be set to 40 for the calculation to be correct. Using 40 doesn't come with any limitations though, so it should work for everyone.

In the beta it was a pure multiplier, but it doesn't scale in a mathematically sensible way anymore.

23 minutes ago, SteveMeli said:

The calculator seems to be wildly inaccurate for this game. Calc says both sens and zoom sens should be around 2.5 for me to match my Overwatch sens, when in reality I had to set both of these  values to around 0.1 in the config file.

Was a bug in the calculations after the multiplier was removed, try again now.

Just now, Flare_de said:

I think there's still something wrong with the zoom sensitivity - when I select to convert via sensitivity and for instance enter 25 (%) ingame setting at a DPI of 400, it properly translates it to 36.5829 cm for hipfire. Changing it to zoom however it calculates the 25% to a distance of 2.1336 cm.

Seems like somethings wrong indeed, I'll take a look now.

15 minutes ago, Flare_de said:

I think there's still something wrong with the zoom sensitivity - when I select to convert via sensitivity and for instance enter 25 (%) ingame setting at a DPI of 400, it properly translates it to 36.5829 cm for hipfire. Changing it to zoom however it calculates the 25% to a distance of 2.1336 cm.

Found an error in the in-game calculation, try again now.

Looking into it now.

Anthem is updated. This game still has serious issues with packets drops and acceleration, setting GstInput.MouseSensitivity to 100 solves the packet loss so support for this is added.

3 minutes ago, Groen28 said:

When I select Config file option, it's not showing the results, it used to work before the update.  Also, "all" option is no longer available, I only see Aim, Pilot, and Zoomed.

You need to enter the GstInput.MouseSensitivity value as it asks for:

"All" is unfortunately no longer possible since they all use different FOV settings.

Just now, Groen28 said:

Another question, it says " It's highly recommended to set GstInput.MouseSensitivity to 100 to avoid severe packet loss. ", if I set it to 100, wouldn't that make the sensitivity in game extremely high, my in game sensitivity is currently set to 4.

Yes, in-game sensitivity will be almost useless because of the range with the value set to 100. But if you set it through the config file you can go much lower so it shouldn't be a problem.

If you move the mouse very slowly with the value set to 40 you'll notice that the game misses a lot of movement.

1 hour ago, Groen28 said:

I am still kind of new to the calculator tool.  I have 2 questions.

Where do I get GstInput.MouseSensitivity  value it asks for as shown in the screenshot if it's not given to me in the first place? Do I enter the other game sensitivity and plug it into the Anthem sens 1 box?  It'll give me a totally different 360 value if I do that so it's not really giving me the converted 360 value for Anthem.

Also please correct me if I'm wrong, I assume Pilot sensitivity is when you're out in Fort Tarsis, and Aim is hipfire Javelin sensivitiy, and Zoomed is when you right click aiming in the Javelin, am I right?

The GstInput.MouseSensitivity you get from your config file, where it defaults to 40. You can in theory use any value between 1 and 100 here, but 100 is recommended as it fixes a critical issue with dropped packets from the mouse. 

You get a different 360 distance in your screenshots because you use a different GstInput.MouseAimSensitivity (1.510511 vs 0.7).

1 hour ago, Groen28 said:

Also please correct me if I'm wrong, I assume Pilot sensitivity is when you're out in Fort Tarsis, and Aim is hipfire Javelin sensivitiy, and Zoomed is when you right click aiming in the Javelin, am I right?

Correct, this is also shown in-game if you hover over the sensitivity options.

@Tyler Huffman

That definitely seems a lot wider than 106.26, I will check the FOV calculations.

In regards to the actual sensitivity and 360 distance, regardless of the FOV calculations this game is so terribly inconsistent and inaccurate it's hardly worth supporting. I'll make a short video showing exactly why so you know what to expect.