RealUI beta
In order to prepare RealUI for its release, I need your help!! Specifically, I need to know what changes need to be made for your class/spec. I don't play all the classes so I don't know what changes will be necessary for things like the AuraTraker. Known Issues: Unit Frames: These are being re-writen and are currently in a rough state. Skada: Division by zero Bug Reports
|
3 Attachment(s)
The Debuff from a glyphed Avengers Shield is lingering on top of the minimap when it should be above the target frame. (see attached image)
Information: Class: Protection Paladin with Glyph of Dazing Shield Addons: just Blizzardsstuff and those that came with RealUI Beta Some Error From Bugsack I got while fighting mobs in the southern half of Gorgorond: Code:
32x Skada\modules\Debuffs.lua:153: Division by zero a) put the Garison minimap button with the other minimap buttons please, maybe make it visible for a short while when/if it would flash, if that is possible b) bartenders cooldown overlay is a bit to bright at least for my tastes and its cooldown doesn't seem to be that reliable, but that prolly is just the lagging server Edit 1: After playing in an area that was a little more crowded I think its all debuffs that end up in the upper left corner, additionally they cover each other as if they are all anchored to the top left most point of uiparent. (seen Frostbolt, Frozen Orb, Censure (Judgement from Seal of Truth) and Execution Sentence up there so far. Edit 2: The descriptive Texts in the rewards section of both the quest accept and quest hand in frames are too dark. (see lower half of the 2nd image) Edit 3: And another error, might be related to Edit 2 or to this: Noticed that the highlighting for the selected questreward is not showing up, selecting itself and then finishing the quest still works fine though. Quests I noticed this on were 2 of the Wanted: ... Quests in Talador on the alliance side (the bird and the riverbeast one, forgot the names sorry) anyway this is what bugsack caught: Code:
14x Aurora\aurora-6.0.lua:2084: attempt to index field '?' (a nil value) The Cooldown overlay ignores the visible state of the bar, only noticed that during combat not sure if it shows up out of combat (see image 3) |
Quote:
The Garrison button is a tough one, and i'm not really satisfied with where it's at. That said, I don't think putting it with the other minimap buttons would be a good solution considering the impact it will have in WoD. I have tried to have it hidden by default, but the pulse animation is somehow preventing it from being shown again. The Skada error is a result of tighter asserts in the code for beta, and will not be present on live. Due to this, it is unlikely to be fixed. |
The quest stuff is being worked on :)
|
My chat keeps getting spammed with Map: WORLD_MAP_UPDATE
edit: I see you posted something about skins and I figure this falls under that category, but I figured I'd mention anyway. |
Quote:
Please see the OP about bug reports. What you have here is not much to go on, especially since I'm not getting them. |
Quote:
Server: Beta Leveling Realm 02 Class/Spec: Paladin/Ret Level 98 Location: Everywhere Other addons: Monomyth, DBM Turning off the !Aurora addon made the chat spam stop immediately. The spam occurs more often when I open the world map or turn in/accept quests. It happens out in the world as well as in instances regardless of what I'm doing. Code:
1x Aurora\aurora-6.0.lua:272: attempt to index local 'f' (a nil value) Code:
2x !Aurora\Misc\MiscSkins.lua:34: attempt to index upvalue 'F' (a nil value) |
Quote:
Note: !Aurora is being renamed to !Aurora_RealUI to remove ambiguity with Aurora. Please be sure to delete and copy over the correct addons. |
It looks like a bunch of spells got officially removed in the latest build. Due to this, there are a number of errors resulting from looking for a non-existent spell. Once I track down these changes I'll post an update.
|
Thanks for getting this going for beta. I just got in today and I will be doing some testing later this week. I haven't posted anything previously as RealUI has just worked out of the box for me, but I see that some work will need to be done to get it working well for WoD.
All that said, I'd probably have a rough time playing this game without RealUI. Not to say that I would quit altogether, but this is just such an awesome solution. Blizzard should take a note out of your design if they ever decide to redo their UI. Either that or hire you. :) Edit: https://github.com/NibelheimInt/RealUI-80/tree/Beta Is this the correct spot for most up to date (beta 3) download? |
Quote:
Quote:
|
RealUI beta 4
1 Attachment(s)
Hi
I have some spam in chat with "GetauraInfo" If i disable nibRealUI, it's disappear. Thanks |
Quote:
|
I've noticed that if I have quest items and try to use them from the on screen quest tracker that I get an aurora pop up as such. In order to use the item, I have to open my bag and find the item.
|
Quote:
|
Quote:
Code:
1x [ADDON_ACTION_FORBIDDEN] AddOn '!Aurora_RealUI' tried to call the protected function 'UseQuestLogSpecialItem()'. |
That function is not used *anywhere* in RealUI or any of the addons it includes. Make sure you're using the most recent version, and disable any other addons you're using.
|
just got the same error moodib posted using just beta4 and the 'usual' blizzard addons
I wouldn't be surprised if that error comes from their addon code, wouldn't be the first time |
"X tried to call the protected function Y" errors are not meant to be taken literally. (Well, maybe Blizzard intended for them to be taken literally, but if so they royally botched the implementation, because it just doesn't work that way.) It almost never means that X actually tried to call Y directly. It just means that X touched something that touched something that touched something that touched something that touched something that's somehow involved somewhere in the chain of Blizzard code that calls Y, rendering the whole chain of execution tainted.
Look for any places in your code where you overwrite functions or variables that are originally defined in Blizzard code, or if it's not obvious, you can enable taint logging to get a full report of everything you're tainting. Find the ACTION_FORBIDDEN error in the taint log, figure out which variable it says is tainted, and then trace that variable back through the log to see where it was first tainted. |
Well some how I'm not getting this error, and you guys are. I even rolled back my local version to beta4 just to be sure, no dice.
So Ordrosh and Moodib, do this: Get to an area where you can get this error, then start logging by entering Quote:
Quote:
Then go to World of Warcraft Beta\Logs, upload the taint.log file to your favorite file sharing site, and PM me the link. |
All times are GMT -6. The time now is 02:37 AM. |
vBulletin © 2024, Jelsoft Enterprises Ltd
© 2004 - 2022 MMOUI