0
Description: 'Clan Hex WarHorn' plays 'Ghost Bear WarHorn' audio when in 3rd-Person and dealing a Killing Blow to another Mech.
Game Mode: All of them! (I'm NOT joking!)
Selected Mech: Any and All Mechs, this Bug happens without regard to what you choose!
Problematic Item: Cockpit Item - 'Clan Hex WarHorn'
Location: Anywhere, while having 'Clan Hex WarHorn' equipped in the Cockpit on Any Mech, and viewing in 3rd-Person while dealing a Killing Blow.
Reproduction Rate: 100%, and infinitely repeatable (This should have been fixed before release. How was it missed?)
Steps to Reproduce:
- Equip 'Clan Hex WarHorn' in the Cockpit of Any Mech you wish to choose.
- Enter 3rd-Person View in Any Match at Any Time.
- Go deal a Killing Blow to Any Mech, while still in 3rd-Person View, regardless of Targeted or not.
- 'Clan Hex WarHorn' will fail to play the proper audio, and plays the 'Ghost Bear WarHorn' audio instead while in 3rd-Person View.
What should NOT happen: 'Clan Hex WarHorn' playing 'Ghost Bear WarHorn' audio in 3rd-Person View.
What should be happening: 'Clan Hex WarHorn' plays it's own audio while in any View Mode.
Initially Noticed: Shortly before 2016-06-13, during Patch 1.4.69, but was likely present before the May 2016 "Kodiak LeaderBoard And Challenge Event", and is still happening now.
Comments: This Bug has been Ongoing since the 1.4.69 Patch or before. It is still happening even as I'm writing this Bug Report. I only found this Bug after I earned a 'Clan Hex WarHorn' during the Event noted above, and then later decided to check in 3rd-Person View while dealing a Killing Blow to an Enemy Mech. This Bug still happens regardless of whether the Enemy Mech is being Targeted or not. I'm left to wonder what sound is heard by other teammates when I'm dealing a Killing Blow to an Enemy Mech while they're standing near me.
~D. V. "PGI, please fix this before the Next Patch, avoiding this thread going to the Archive until it's fixed?" Devnull
(p.s.: PGI Staff, I couldn't get a Moderator to move the previous edition of this thread back out of the Archive after discovering this Bug had NOT been fixed. I tried to send a report on my previous thread in order to prevent having to start another one, but to find no help in being able to update the older thread with newer information. So here we are with thread #2 about the same ongoing issue!)
