View Single Post
07-17-17, 12:20 PM
A Theradrim Guardian
Join Date: Jul 2012
Is there's anyone that could maybe elaborate for me how/why this new SOUNDKIT approach is better?
I don't quite see the logic in why Blizzard would change PlaySound() from accepting an input string (i.e a filepath) into taking a numbered id instead.
How much more costly (time, cpu, memory) is it to support an occasional lookup of a new string (I presume they implemented a cached table of most used paths for faster re-lookup) compared to pre-enumerating ALL sounds in the game into a LUA table and having to maintain such a table.
Edit: Seems I got PlaySound() and PlaySoundFile() mixed up. It all makes sense now.
Links in Chat
Last edited by Jarod24 : 07-17-17 at
View Public Profile
Send a private message to Jarod24
Find More Posts by Jarod24