When 'harvesting' with the Hammerhead the sound effect that plays when 'harvesting' is complete seems to loop more than intended.
The fact that this sound effect has changed is a good thing for sure(That "got it" sound really was weird back in the day).
This also appears to be tied to the framerate in some way, which means maybe there is an issue in some script somewhere.
Here is a video showcasing the issue:
Video
Community AdminPlease this this bug it really hurts my ears. Its got to the point were i almost have to mute my game just to be able to do firewalker missions.
Have the same issue. Tried different framerate settings but could not get it to go away.
It's a truly awful sound and much louder than anything else in game.
Unfortunately this behaviour is still seen in the June 7th Update for Mass Effect Legendary Edition.
Playing on pc, I too can confirm this horrible und completely unnecessary sound is still in the game. Bug or "feature", it would be very nice if the soundfiles could be somehow fixed or even reverted back to the legacy state if a fix is not possible.
@EA_David Tagged you just to remind you that this still is an issue =]
I also posted about this awful sound. I don't know if they changed it or it's just a glitch. The old sound is much easier on the ears though.
If you're going to fix the Hammerhead sound issue outlined here, then please fix the broken surround sound issue in ME1. As it stands now, the sound in ME1 only comes through the front & center speakers on my 11.2 Dolby Atmos home theater system which I have plugged into my PC/55" display. Seriously, the ME1 surround sound bug dates all the way back to the original release back in '08. Please fix this issue. It's long overdue for a fix...
There is already a topic about the ME1 surround issue, and @EA_David has been tagged over there:
@Schachmatt123 I'm re-iterating that issue here since the surround sound issue has yet to be fixed. That issue should have been fixed in the 6/7/21 patch that BROKE achievements for scores of players but for whatever reason wasn't. That bug dates all the way back to the original release in '08 & is long overdue for a fix.
