Anthem

[Bunnikinz]

@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/

 

 

Edited February 18, 2019 by Bunnikinz

[DPI Wizard]

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.

[SteveMeli]

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.

[DPI Wizard]

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.

[Flare_de]

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.

[DPI Wizard]

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.

[DPI Wizard]

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.

[Flare_de]

Can confirm, now it works. Thank you for the fast support!

Edited February 22, 2019 by Flare_de

[ProuDBeasT]

Does the recently added "pilot sensitivity" (1st person) share the same values as the other ones?

OK, dumb question, sorry.

Pilot sensitivity can be edited in the config file now ("GstInput.MousePilotSensitivity") and the value is the one that the calculator gives for "Default (1st person)."

Edited March 9, 2019 by ProuDBeasT

[Captain Funsponge]

There's also FOV support now, would be wonderful if you could take a look.

[Groen28]

Any update on Anthem FOV option?  Like the above poster said FOV support is available now. 

 

Edited April 25, 2019 by Groen28

[DPI Wizard]

Looking into it now.

[DPI Wizard]

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.

[Groen28]

1 hour ago, DPI Wizard said:

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.

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.

Edited April 27, 2019 by Groen28

[DPI Wizard]

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.

[Groen28]

10 minutes ago, DPI Wizard said:

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.

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.  Also 100 is the maximum sensitivity in game.

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.

Edited April 27, 2019 by Groen28

[DPI Wizard]

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.

[Groen28]

38 minutes ago, DPI Wizard said:

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.

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?

 

Edited April 27, 2019 by Groen28

[DPI Wizard]

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]

@DPI Wizard

Alright so I hate to work you so hard but I think the calculator with the new zoomed FOV is way off. For example, I set this sensitivity at this FOV:

and I put it in the config file, open the game and test it out. I realize that the zoomed FOV in-game is not around 106 horizontal degrees because I have it as my normal aiming FOV here:

And now the zoomed FOV:

Additionally, the 360 degree distance is way shorter, even though the calculator says it should be normal. It may be an issue with the game, like some weird high FOV sensitivity scaling or something, but I just wanted to point this out so that you might see it. So basically the actual FOV calculator and 360 distance is a little off.

[DPI Wizard]

@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.

[Tyler Huffman]

Awesome! Hopefully Anthem will improve in the future but only time will tell.

[cenorazer]

Any news about 

GstRender.ZoomedFOV

Would love to understand what is the best value / comparison for this game

[Carlos Resurreccion]

On 5/27/2020 at 7:06 PM, cenorazer said:

Any news about 

GstRender.ZoomedFOV

Would love to understand what is the best value / comparison for this game

Any updates on this? @DPI Wizard there's still negative accel. I'm using 125 hz and these settings:

I set GstInput.MouseSensitivity to 100 as per your instructions in the calc to alleviate packet loss.

Update, setting GstInput.MouseSensitivity to 1 fixed it.

Edited June 17, 2023 by Carlos Resurreccion