Jump to content

V Rising

Use the config file for best accuracy.
Read more...

Vigor

The sensitivity slider is not accurate, expect some discrepancy. Use the config file for best accuracy.
Read more...

MULLET MADJACK

The config file might use either comma (,) or period (.) as the decimal separator depending on your locale settings.
Read more...

Combat Champions

All aims use the same sensitivity setting, choose the sensitivity for the aim you prefer to be matched.
Read more...

Ghost of Tsushima DIRECTOR'S CUT

The sensitivity and FOV changes depending on certain actions and where you are (indoor etc). The calculations are for the view when you move around outdoor.
Read more...

Atomic Heart


Recommended Posts

  • Wizard
1 hour ago, zhou707377543 said:

The field of view of the Atomic Heart can be changed through the plug-in, using (Flawless Widescreen), this plug-in can modify the game FOV, modify the game sensitivity after FOV you see how much.

I won't be able to add support for this until tomorrow. 

Regarding smoothing, please let me know if lower polling rates solve the issue. 

Link to comment
42 minutes ago, DPI Wizard said:

Atomic Heart is back now, the issue was an error in the sensitivity formula. Fixed this and added support for FOV change!

I'm currently on a laptop, but can't detect any smoothing. Do let me know if you think you have smoothing issues though, and I'll look into it later.

I was digging around and unpacked pakchunk0-WinGDK.pak in the Atomic Heart 'Content' folder to find the hidden ini files (DefaultInput.ini, DefaultEngine.ini, DefaultGame.ini, etc) and found that mouse smoothing is enabled at the project level. 

Screenshot 2023-02-21 152126.png

Link to comment
  • Wizard
On 2/21/2023 at 9:22 PM, LeopardTurret said:

I was digging around and unpacked pakchunk0-WinGDK.pak in the Atomic Heart 'Content' folder to find the hidden ini files (DefaultInput.ini, DefaultEngine.ini, DefaultGame.ini, etc) and found that mouse smoothing is enabled at the project level. 

The way it's implemented seems to negate the smoothing issues due to high polling rates, at least below 1000 Hz.

13 hours ago, nevva said:

No matter what I input, the calculated sensitivity is always 0.5. Is this correct? The error is about 16%.

The "Mouse Sensitivity" value will default to 0.5, the other two values, X and Y-Axis Sensitivity are the ones that are calculated.

If you get a very high discrepancy you can try to adjust the "Mouse Sensitivity" value manually to get the discrepancy lower. Adjust it in steps of 0.05 so you can match it in-game.

Link to comment
  • 3 weeks later...
  • 1 month later...

Hi, I've found a mod for ADS sensitivity - hopefully links are allowed: www.nexusmods.com/atomicheart/mods/43

There's an instructions file in the downloaded mod, with the following text

'1.Open WeaponsAttributes.json (in Atomic Heart\Content\AtomicHeart\Content\GameTune on GamePass ver) with WordPad. Click on top of document (when text start).
2.Use CTRL+F to find. U need every "AimFieldOfView" line
3.Find every AimFieldOfView line and change his value to 0 everywere
For example: First that u will find is "AimFieldOfView": 15, will change to "AimFieldOfView": 0,
4.Do same for "AimSensitivityMultiplier" line and change his value to 1 everywere if u need 1:1 360 Sensitivity. 


If u want change all weapons to same fov and sens as your favourite weapon. Default sens/fov modificators

KS-23: "AimSensitivityMultiplier": 0.77 | "AimFieldOfView": 10 // lowest fov modificator, highest sens multiplier = closest feel to 360

Electro: "AimSensitivityMultiplier": 0.5 | "AimFieldOfView": 30 // very high fov modificator, very low sens 50% of 360

Ak-47: "AimSensitivityMultiplier": 0.5 | "AimFieldOfView": 25

Krepysh(Rocket launcher): "AimSensitivityMultiplier": 0.55 | "AimFieldOfView": 25

PM: "AimSensitivityMultiplier": 0.55 | "AimFieldOfView": 25 

Railgun: "AimSensitivityMultiplier": 0.35 | "AimFieldOfView": 38 // high fov modificator, veryy low sens 

Dominator: "AimSensitivityMultiplier": 0.8'

 

The creator of the mod seems to be saying that an AimFieldOfView value of 0 leaves the ADS FOV the same as Hipfire FOV, and that an AimSensitivityMultiplier value of 1 keeps the 360 distance the same between Hipfire and ADS. I haven't verified this myself, but I'm posting this in order to ask:

If someone has time, would it be possible to implement ADS sensitivities to the calculator, or explain how to calculate the values myself so I can put them in my config file? If it helps I use MDV 54% for ADS and Scope.

 

Thanks in advance!

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...