This site works best with JavaScript enabled. Please enable JavaScript to get the best experience from this site.
I have to Disable and Enable the "Latency" setting for it to work every time I log in to a character. It seems the "Latency" option, even though showing as enabled, it disables itself by default.
Funny part about that latency module issue is that for me the latency text shows up but the red overlay part isn't.
if you want you can test my ugly workaround...go here https://pastebin.com/x28s9EHW, copy everything, open "...Wow\_retail_\Interface\AddOns\Quartz\modules\Player.lua"
and replace it with the pastebin content. Save and reload ui.
First cast after reload or login will not look correctly yet but it will fix itself from the second cast on.
changed lines:
35-36, 139-140, 377-383
I dont know lua too well so I call this "ugly workaround" instead of a fix as it doesnt fix the why and just covers up the symptom.
If you dont want to alter files you can try my other more manual workaround.
I just copy my response from the other issue:
#
make a new makro and put this in it:
/run LibStub("AceAddon-3.0"):GetAddon("Quartz3"):GetModule("Player"):ApplySettings();/run LibStub("AceAddon-3.0"):GetAddon("Quartz3"):GetModule("Latency"):ApplySettings();
Drag it to your hotbar and click it after login or when you notice your settings not applying correctly.
A little gotcha is that for some reason the macro only starts working after the quartz castbar displayed at least once since logon / reloadui, i.e. casting a spell first then clicking the macro once or twice. Not perfect but better than going into the settings everytime.
Hopefully this gets fixed soon but fun sidefact about quartz: looking back on old footage it looks like the (in my opinion) connected other bug with the border texture not loading correctly just like latency does is that it seems this bug is around since almost as long as quartz is out xD recogizable in old videos when there is this thick black shadowy outline around quartz castbars that made it look cool kind of but now realized it is just a really old bug most likely.
Funny part about it is that it still not fixed lol
To post a comment, please login or register a new account.