FrameXML error

Support Bug Report
1

I got this error on my 60 Hunter when I got onto the “Huey” Gryphon to start the Beast Mastery artifact weapon scenario

2x FrameXML\AnimationSystem.lua:61: Action[SetPoint] failed because[SetPoint would result in anchor family connection]: attempted from: PlayerFrame:SetPoint.
[string “=[C]”]: in function updateFunc' [string "@FrameXML\AnimationSystem.lua"]:61: in function SetUpAnimation’
[string “@FrameXML\PlayerFrame.lua”]:370: in function PlayerFrame_UpdateArt' [string "@FrameXML\PlayerFrame.lua"]:274: in function OnEvent’
[string “@FrameXML\UnitFrame.lua”]:928: in function <FrameXML\UnitFrame.lua:926>

Locals:
(*temporary) = PlayerFrame {
0 =
portrait = PlayerPortrait {
}
vehicleHidesPet = true
inSequence = false
healAbsorbBarLeftShadow = PlayerFrameHealAbsorbBarLeftShadow {
}
totalAbsorbBarOverlay = PlayerFrameTotalAbsorbBarOverlay {
}
animPostFunc = defined @FrameXML\PlayerFrame.lua:384
healthbar = PlayerFrameHealthBar {
}
overAbsorbGlow = PlayerFrameOverAbsorbGlow {
}
threatIndicator = PlayerFrameFlash {
}
state = “player”
myHealPredictionBar = PlayerFrameMyHealPredictionBar {
}
name = PlayerName {
}
overHealAbsorbGlow = PlayerFrameOverHealAbsorbGlow {
}
feedbackFontHeight = 30
healAbsorbBar = PlayerFrameHealAbsorbBar {
}
myManaCostPredictionBar = PlayerFrameManaCostPredictionBar {
}
PlayerFrameHealthBarAnimatedLoss = {
}
statusSign = -1
unit = “player”
feedbackText = PlayerHitIndicator {
}
totalAbsorbBar = PlayerFrameTotalAbsorbBar {
}
animating = true
statusCounter = 0.320010
manabar = PlayerFrameManaBar {
}
OnEvent = defined @FrameXML\PlayerFrame.lua:197
isAnimatedOut = false
menu = defined @FrameXML\PlayerFrame.lua:56
animStartTime = 0
healAbsorbBarRightShadow = PlayerFrameHealAbsorbBarRightShadow {
}
animReverse = true
otherHealPredictionBar = PlayerFrameOtherHealPredictionBar {
}
inSeat = true
}
(*temporary) = “TOPLEFT”
(*temporary) = UIParent {
variablesLoaded = true
firstTimeLoaded = 1
0 =
}
(*temporary) = “TOPLEFT”
(*temporary) = -19
(*temporary) = 136

2

Are you using framing addons? Examples would be MoveAnything, TipTac, Dropdowns, Quest-based stuff, etc.

Some frames cannot have stuff overlapping them or be relocated.

1 Like
3

No, nothing of the sort was loaded.

4

Disabling them doesn’t fully prevent them from interacting with the game. Additionally, if you moved something on top of a frame Blizzard deems necessary in base UI, then you’d continue to see the error.

5

:man_shrugging: If something is happening outside of my perception there’s nothing I can do about that. If Blizz deems it’s user error so be it, all I can do is report the bug.

6

I understand, but it doesn’t sound like a bug, it sounds like something you can fix. If you reset your UI and it doesn’t happen, you know addons you’re using are creating the problem.

7

Thanks that worked :ok_hand:

First I tried moving my addon folder somewhere else and that didn’t work, then I renamed my WTF folder and deleted my Cache folder and that worked. Restored my WTF and the error returned, also this error goes away if I get rid of my WTF folder as well

so it was a me problem but there’s another problem, I love my data more than I like playing without bugs :laughing: So I started moving all of my files from my old WTF back to my new WTF and logging in to see if the error was there, if it wasn’t I logged out and moved more files back and continued doing this until I found the problematic file, AddOns.txt. Everything else the same, but let the game create a new AddOns.txt and no more bug :]

Edit3: (I know my edits are out of order :laughing: )
I figured out why deleting AddOns.txt worked, it didn’t make sense to me because … why? But looking through my old AddOns.txt file I found that somehow the Blizzard_ObjectivesTracker addon (along with a couple others) had somehow gotten in there and they were set as disabled so they never loaded. This also explains why it was only on two characters.

Edit: Well, that worked for the other bug I listed above, this one still persists :thinking: I’ll keep working and see if I can figure it out.

Edit2: Ok figured out this one as well, the problematic file for this issue was layout-local.txt which may have something to do with this bug report

The layout-local file that Wow generates now (presumably because of 9.1.5) is blank, the old one has actual data in it

New:

Version: 1

Old:

Version: 1
Frame: PlayerFrame
FrameLevel: 2
Anchor: CENTER
X: -281
Y: -156
W: 232
H: 100
Frame: TargetFrame
FrameLevel: 2
Anchor: CENTER
X: 281
Y: -156
W: 232
H: 100

etc

Getting rid of the one with data in it and letting wow generate the blank one fixes the problem. This is fine for me because I don’t rely on anything from layout-local because I use UI addons that store positions outside of layout-local but for non addon users like the other guys bug report they’ll be running into trouble.

3 Likes