[CLIENT/AUDIO] Gladiator Draven's Spinning Axe audio bug (missing/delayed sound?)
Bug Description
tl;dr Pretty much Draven (using the Gladiator skin) is missing the "woosh" sound of his blade when it's flying in the air with Q activated, and the sound gets played once the target gets hit (so I'm assuming the audio is delayed by around half a second)
At 0:36 of the linked video at the top, that is what the sound is supposed to sound like, at other parts shortly afterwards and before this point of the video, the blades currently sound bugged.
You can make an accurate comparison to how it SHOULD sound (and how it DID sound pre-patch 4.12) by looking at the Gladiator Draven Skin Spotlight video:
http://youtu.be/NjIxfiAC-rM?t=40s
For some reason, as shown in the video I made (draven audiobug), the audio fixes itself VERY rarely for a short duration and I don't know why.
I'd say this is almost a gameplay bug and is fairly important due to how Draven has to move to a certain direction after his autoattacks to control his axe placements. And the audio of the axes being thrown is a good indicator for when you know your autoattack is flying, so you don't accidentally cancel it.
Little clarification (rant 
) on how long the bug has been around for and how little attention it has received (wall of text/links warning)
This bug has been around since patch 4.12 and hasn't been addressed publicly. And because it's been so long since the audio started to get bugged, people who are just getting the skin now don't realize what the blade sounds were supposed to sound like over half a year ago. Friends of mine tell me, "There's a bug with his audio? I thought that was what it was supposed to sound like?" but when I used to play Draven a lot more back then, I only used this one skin and I know for a fact there is a bug with the audio.
So, just to recall, I addressed this issue all the way back in July and August 2014, back when patch 4.12 just came out. I addressed this issue in the following ways, in order: - PBE bug report (late July 2014, no response): http://boards.pbe.leagueoflegends.com/en/c/bugs/F9PaQFw8-gladiator-draven-audio-bug-on-spinning-axe-q - Player support ticket (mid August 2014, response from Riot Thanatos): https://support.riotgames.com/hc/en-us/requests/13152467
The PBE bug report didn't get any responses, and after I thought that it was a bad idea putting it on the PBE board due to the bug not being directly related to PBE as the bug made it all the way to the live servers; I sent a player-support ticket. And thankfully, it had a response from Riot Thanatos.
"However, I appreciate that you have reported this to us. We will surely look into this and will address this as soon as possible.
...
I can't provide a timeline for when we might see a fix on this issue, but thank you again for the report. Please let me know if you have any other questions!
Thanatos✪ Riot Player Support Specialist"
The problem is, this issue was NEVER addressed, and it has been around ten patches now. And just for some reassurance, I'm not the only one who noticed this bug, a keen player Valoren also picked up this problem shortly after I made my video and report and made his own bug report and video on the issue:
Bug Report (from Valoren): http://forums.na.leagueoflegends.com/board/showthread.php?p=49036000
Video: https://www.youtube.com/watch?v=bSfmqGYHN08&feature=youtu.be
Funny thing is, the bug report also received attention from a Riot employee, Belligerant Swan, who actually works on the sound design:
Hey Volaren,
Thanks for letting us know! I'll take a look at it and see whats going on.
But I don't think there was any further notice on this issue at all. I don't want to rewrite the entire "bug fix" format as this has already been looked into by two different Riot employees.
But I was just wondering; has there been any progress?
Is the bug just extremely difficult to fix for some reason, or did it just get lost in the fog due to it being a lesser-impacting bug? Because this bug made me start to use the classic Draven skin instead due to the audio being rather irritating due to the "midway flight" sound playing as soon after it successfully hits a target.
