Page MenuHomeFeedback Tracker

Footsteps obstacle reduction sound issue 1.66
Reviewed, NormalPublic


It seems a new obstacle's reduction footsteps sound system is applied in a too rude way. It seems to exactly match the video visibility of a character.


Operating System
Windows 10
Steps To Reproduce
  • Stay behind an obstacle or inside a building.
  • Put Ai running the other side.
Additional Information

Event Timeline

Roddis created this task.Dec 8 2016, 6:41 PM
Roddis updated the task description. (Show Details)
razazel claimed this task.Dec 9 2016, 9:42 AM
razazel changed the task status from New to Reviewed.
Roddis added a comment.EditedDec 9 2016, 2:55 PM

I can't be able to reproduce this inside a building cause i can't find a way to make Ai running or fast walking inside.

Now in 1.66, in multiplayer sessions i always being caught by enemies that run inside the building where i'm hidden popping out by doors without any sound until the character become visible.

Until 1.66 not even be walking slow in combat pace was enough to be stealth inside a building. It was needed a trick in crouch stance.

We moved from one extreme to another.

This comment was removed by Chefkoch182.

I got to say, I like the Idea behind that whole sound overhaul.
But its way too extreme!
I tested it with a rangefinder and i couldnt hear a running AI at a street until he had 15m distance to me (with lvl5 Vest full gear).
The running sound is way too less hearable. I think i heard players running at least 25m or id even say 35m away, and thats ok and should be done again as it was before. Moving in a slow combat pace shouldnt make that much sound, as it is now.
So: make rushing hearable and realistic again, and keep the quiet advantage for those who wanna sneak

Roddis edited Additional Information. (Show Details)Dec 13 2016, 2:32 PM

This is an issue harming MP games, muting enemy footsteps. Hopefully addressed soon, thanks.

Issue should be already fixed in dev branch and should be available in next stable/main branch update.

Issue should be already fixed in dev branch and should be available in next stable/main branch update.

Seems to be not razazel!!!

This video with today 1.67.139925 Dev Branch version.

Please address this issue guys please!!! I no more be able to enjoying with ARMA since that.

Here's another video showing the same issue, using Today's DEV branch.

In 1.67.139940 seems to be solved, I just received the update.

I wait for some hints in today's dev branch changelog.

Issue appears resolved in 1.67.139969

Yes it seems to be solved since 9940, but no evidence in any changelog since then.