I backported the addon... However, due to limitations with the older 3.3.5a API you won't be able to stop sound from playing once it's started like you can in the original addon. I kept all the buttons there, they're just disabled.
The play button apperas, when I click it though, nothing happens. When I look at the Addon Memory, the Vanilla Package only has 3,54MB of Data instead of 1,08GB.
The play button apperas, when I click it though, nothing happens.
"due to limitations with the older 3.3.5a API you won't be able to stop sound from playing once it's started like you can in the original addon. I kept all the buttons there, they're just disabled."
It should only play when you talk to an NPC, or click the play button within your quest log. There is no way around this. The 3.3.5a client is missing the StopSound function that was added in later game versions.
I backported the addon... However, due to limitations with the older 3.3.5a API you won't be able to stop sound from playing once it's started like you can in the original addon. I kept all the buttons there, they're just disabled.
edit: unfortunately, every time i gather a quest item, the game experiences a pretty significant lag spike. Tsoukie, do you think you might have a memory leak in your port of the addon?
edit: unfortunately, every time i gather a quest item, the game experiences a pretty significant lag spike. Tsoukie, do you think you might have a memory leak in your port of the addon?
It actually happens whenever you complete a quest objective and when you turn in quests.
To Tsoukie. I don't think it's your port at all. The issue is that it always updates the Quest frame on the QuestLog_Update event. And that seems to be called multiple times when completing an objective.
For me the resolution is to adjust the hook on that as follows (Voiceover.lua line 88):
hooksecurefunc("QuestLog_Update", function()
if (QuestLogFrame:IsShown() or false) then
self.questOverlayUI:UpdateQuestOverlayUI()
end
end)
Which only calls the code to update the buttons on the quest frame if it is shown (the event is triggered when the quest frame is opened).
Hmm, I personally didn't have the lag issue myself when testing... But I will add the change to only update if the quest log is visible in the QuestLog_Update hook. It appears Blizzard also does this themselves in the actual QuestLog_Update function for 3.3.5a.
edit: unfortunately, every time i gather a quest item, the game experiences a pretty significant lag spike. Tsoukie, do you think you might have a memory leak in your port of the addon?
I updated it with the fix by r00tk1t. You can download the whole thing over again, or just grab the updated main addon here. Just replace the existing "AI_VoiceOver" folder you have. Hopefully it solves the issues.
As for the memory leak stuff, I really haven't changed too much from the original addon to make it work.. just some simple changes to understand the older client unit information. There could always be issues with the original addon itself though, since it's being rapidly updated.
Hmm, I personally didn't have the lag issue myself when testing... But I will add the change to only update if the quest log is visible in the QuestLog_Update hook. It appears Blizzard also does this themselves in the actual QuestLog_Update function for 3.3.5a.
It's where I stole, I mean borrowed the code from :)
I found the lag was variable. Sometimes unnoticeable sometimes huge. Probably depends how many quests you have visible in the quest log at the time.
He actually said he wants to make it work for 3.3.5 and 1.12.1, and also add TBC/Wrath quests. He has a donate page to pay for the online AI tool he uses to do them and that has the plans detailed. At 59% of the target last I looked.
That's a really game changing addon but it's a shame they didn't include TBC into it. If they did can anyone give me a tip where I can download a voicepack?