Ошибка lua frame xml

MMO-Champion
»
Forum
»
World of Warcraft
»
Interface & Macros

Annoying «LUA ERRORS» causing problems with interface.

2012-06-12, 05:29 PM

#1

Annoying «LUA ERRORS» causing problems with interface.

Hey

I installed WoW on my new laptop, added addons and i can’t get rid of the LUA errors. This is what it says:

«

Message: InterfaceFrameXMLUnitFrame.lua:218: Usage: GameTooltip:SetUnit(«unit»[, hideStatus])
Time: 06/12/12 19:05:08
Count: 3
Stack: [C]: in function `SetUnit’
InterfaceFrameXMLUnitFrame.lua:218: in function `UnitFrame_UpdateTooltip’
InterfaceFrameXMLUnitFrame.lua:205: in function <InterfaceFrameXMLUnitFrame.lua:192>

Locals: (*temporary) = GameTooltip {
0 = <userdata>
default = 1
numMoneyFrames = 1
hasMoney = 1
comparing = false
updateTooltip = 0.0089999901130796
shoppingTooltips = <table> {
}
}
(*temporary) = nil
(*temporary) = nil

It repeats every 10-15s on some BG or raids and i need to /reload every time because otherwise i can’t target raid members using Blizzard Raid Frames, because when i click on one it’s targeting the other.

List of addons that i use:

— Bagnon
— BG Targets
— BG Defender
— DBM
— GladiatorlosSA
— Healers have to die
— MikScrollingBattleText
— OmniCC
— PlateBuffs
— Quartz (i’ve got same cofiguration on my PC excluding this one and i haven’t problems, but this shouldn’t be problem)
— Recount

Could you help me? I don’t know what to do and this problem is very annoying and disturbing.
2012-06-12, 06:05 PM

#2

Dreadlord

I get the same problem using pretty much none of the addons you do (Bagnon and OmniCC being the only overlap, both of of which obviously having nothing to do with unitframes) when I use the default raid frames in pvp on my priest. Best I can figure it’s just shitty code on Blizzard’s part, it usually happens when someone leaves mid-BG when I’m in combat.
2012-06-13, 06:39 PM

#3

reply

:/ I am playing on priest too and like you said it happens usually when someone leaves BG… Thanks…

Anyone know what to do with it?
2012-06-13, 07:10 PM

#4

Fluffy Kitten

From the code you posted, it seems a Blizzard side issue, not related with addons.

More specifically, the moment when you hover over a unit frame (probably the Blizz raid frames) and the game tries to set up the tooltip (the one on the lower right corner of the screen), but something simply goes wrong.

I don’t have this kind of problem, but i use my own raid frames and not the Blizzard ones.

You tried, and you failed. What have you learned? That’s better not to try at all.
2012-06-13, 07:33 PM

#5

It’s not a Blizzard problem, it simply means one of the addons is trying to show a tooltip for a unit that does not exist, or using incorrect parameters, etc. You’ll have to disable them one by one to find the culprit unfortunately, though make sure they’re up to date first.

MMO-Champion
»
Forum
»
World of Warcraft
»
Interface & Macros

Annoying «LUA ERRORS» causing problems with interface.

Posting Permissions

You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
[VIDEO] code is On
HTML code is Off

Источник

None of those errors are particularly meaningful, and none would be causing any freezes/crashes.

� There’s some syntax error in BigWigs/modules.xml — I’m pretty sure this file is only used if you’re running a development copy (ie. SVN checkout), not a release package, so unless BigWigs isn’t working in-game, this doesn’t matter.

� oUF_Abu is trying to load a file that doesn’t exist (Modules/oUF_Smooth.lua) — the only effect this will have is that the status bars on your unit frames won’t be animated when their values change.

� Plater is trying to load the AceSerializer-3.0 library, but doesn’t actually include a copy of that library. If the addon works when it’s the only one running, then it’s probably not actually using this library, and this doesn’t matter, but if it breaks or throws errors in-game, you should report this to its author.

� xanAutoMail is trying to load LibStub and AceHook-3.0, but doesn’t actually include copies of them. See above.

� Blizzard_TalkingHeadUI attempts to set a nonexistent function as a script handler. This error is less a result of specifying a nonexistent function (though that should be fixed/removed) and more a result of something idiotic in the way Blizz parses XML. Doing the same thing in Lua will not throw an error; it will just remove the handler for that script event since it’s effectively passing a nil value as the handler.

� Blizzard_StoreUI … I don’t even know what’s going on here, because it’s claiming it can’t find the UIParent frame or the ChatFontNormal font object, but if those somehow didn’t exist, then a large percentage of everything in the UI — both default and addons — would be broken. I wouldn’t worry about this, especially if the in-game store UI works fine for you, or you don’t use the in-game store.

Here are some troubleshooting steps you should try:

1. Make sure you have an error display enabled to show you errors that occur in-game. (Yes, the default UI has an error display you can enable, but it’s unable to show you errors that happen during login, and it’s obnoxiously intrusive.)

2. Check your addon memory and CPU usage. You may have a badly written addon that’s generating tons of garbage (discarded objects like strings and tables that fill up memory) and/or hogging the CPU. (Don’t forget to disable CPU profiling when you’re done troubleshooting — running it takes up a lot of CPU time itself, so just having it on will significantly reduce your framerate.)

3. Try disabling addons to narrow down which one is causing the problem. If the freezes are predictable (eg. it always happens when you enter combat, or it always happens when you disenchant an item) you can start by disabling addons that you think do stuff in that scenario (eg. combat monitoring addons, or bag/loot/profession addons), or you can just use a binary search pattern.

__________________
Retired author of too many addons.
Message me if you’re interested in taking over one of my addons.
Don�t message me about addon bugs or programming questions.

Источник

Before the Dragonflight pre-patch, many people were getting FrameXML errors. The general gist, from my research, is that most likely an addon made a change to some of the main WoW lua frames. I believe this is now a bigger issue and has expanded out to other important main wow frame luas, since the moment I logged into WoW after the pre-patch, a BUNCH of my addons were causing tons of errors to the point that Wow’s system popped up telling me such, and asked if I wanted to disable all my addons.

Fast forward to last week and then this week, after several moments of addon updates, most errors have been fixed by the Addon creators, but a few are still causing enough of a problem that WoW asks if I want to disable the offending addon (which is a lot better than asking if I wanted to disable all of them)

Through all of this, I’ve had to regenerate the WTF, Cache, and Interface folders several times, which seemed to always get me back into a good spot.

Disabling all your addons, then enable one by one, might be a good option in figuring out what’s causing it. Worst case, you cant find the culprit as some of your main lua frames are jacked up, and you have to end up doing what I did, and regenerate the WTF, Cache, and Interface folders — if you have to do this, this might help you: https://us.battle.net/support/en/article/7549

Источник

Print view

Error on InterfaceFrameXMLCharacterFrame.lua

I am currently getting the following error, from my research it is callling the default blizzard UI frame and throwing the error. Im just curious if it is throwing the error because I am running Elvui and Elvui S+L for that character window. If this is not believed to be the case, can anyone point me in the right direction? i cant seem to find the default blizzard ui lua in the files.

Code: Select all

Message: InterfaceFrameXMLCharacterFrame.lua:180: attempt to perform arithmetic on a nil value
Time: Sat Apr 11 19:03:21 2020
Count: 1
Stack: InterfaceFrameXMLCharacterFrame.lua:180: attempt to perform arithmetic on a nil value
[string "=[C]"]: in function `Show'
[string "@InterfaceFrameXMLUIParent.lua"]:3299: in function < InterfaceFrameXMLUIParent.lua:3289 > 
[string "=[C]"]: in function `ShowUIPanel'
[string "@InterfaceFrameXMLCharacterFrame.lua"]:21: in function `ToggleCharacter'
[string "TOGGLECHARACTER0"]:1: in function < [string "TOGGLECHARACTER0"]:1 > 

Locals: ( * temporary) = CharacterFrame {
  0 =  < userdata > 
  TitleText = CharacterFrameTitleText {
  }
  portrait = CharacterFramePortrait {
  }
  SetPortraitShown =  < function > defined @InterfaceSharedXMLPortraitFrame.lua:52
  SetBackdropBorderColor =  < function > defined = [C]: - 1
  Inset = CharacterFrameInset {
  }
  SetPortraitTextureRaw =  < function > defined @InterfaceSharedXMLPortraitFrame.lua:40
  CharacterInfoHooked = true
  template = "Transparent"
  MAHooked = true
  TitleBg =  < unnamed > {
  }
  MAWasMovable = true
  SetTitleMaxLinesAndHeight =  < function > defined @InterfaceSharedXMLPortraitFrame.lua:68
  SetTitleColor =  < function > defined @InterfaceSharedXMLPortraitFrame.lua:56
  SLE_Corruption = SLE_CharacterCorruptionButton {
  }
  ItemLevelText =  < unnamed > {
  }
  SetTitle =  < function > defined @InterfaceSharedXMLPortraitFrame.lua:60
  PixelSnapDisabled = true
  SetBorder =  < function > defined @InterfaceSharedXMLPortraitFrame.lua:27
  layoutType = "PortraitFrameTemplate"
  SetPortraitAtlasRaw =  < function > defined @InterfaceSharedXMLPortraitFrame.lua:44
  SetPortraitToUnit =  < function > defined @InterfaceSharedXMLPortraitFrame.lua:36
  IsMoving = false
  Bg = CharacterFrameBg {
  }
  Expanded = false
  pixelBorders =  < table > {
  }
  SetTitleFormatted =  < function > defined @InterfaceSharedXMLPortraitFrame.lua:64
  ReputationTabHelpBox =  < unnamed > {
  }
  TopTileStreaks =  < unnamed > {
  }
  InsetRight = CharacterFrameInsetRight {
  }
  SetPoint =  < function > defined = [C]: - 1
  SetPortraitToAsset =  < function > defined @InterfaceSharedXMLPortraitFrame.lua:32
  SetPortraitTexCoord =  < function > defined @InterfaceSharedXMLPortraitFrame.lua:48
  MAPoint =  < table > {
  }
  numTabs = 3
  MALockPointHook = true
  NineSlice =  < unnamed > {
  }
  MAE =  < table > {
  }
  SetBackdropColor =  < function > defined = [C]: - 1
  selectedTab = 1
  CloseButton = CharacterFrameCloseButton {
  }
}
( * temporary) =  < function > defined = [C]: - 1

Thank you

Error on InterfaceFrameXMLCharacterFrame.lua

by Deleted User 50

1. Test with only ElvUI. To quickly disable all other addons type in chat in game
/luaerror on

Do you get an error?

2. Test with no addons, just the blizzard UI. Do you get an error?

Return to “Retail Discussion and Support”

Jump to

ElvUI Exported Profiles
Read Only
— General
— — News & Announcements
— — Introduce Yourself
— ElvUI (The AddOn)
— — Retail Discussion and Support
— — Classic & TBC Discussion and Support
— — Guides
— — Ticket Tracker
— Tukui (The AddOn)
— — General Discussion
— — Technical support
— — Guides
— — Classic & TBC Tukui Support
— — Ticket Tracker
— Featured AddOns
— — AddOnSkins
— — Shadow & Light
— — BenikUI
— — MerathilisUI
— Other
— — General Guides
— — Lua Script Help
— — AddOns
— — Tukui Client
— — Premium
— — Offtopic
— — Computer
— — Website
— — Guild Recruitment

Источник

Ошибка lua frame xml

Annoying «LUA ERRORS» causing problems with interface.

reply

Posting Permissions

Error on InterfaceFrameXMLCharacterFrame.lua

Error on InterfaceFrameXMLCharacterFrame.lua

А вот еще интересные материалы: