This site works best with JavaScript enabled. Please enable JavaScript to get the best experience from this site.
What steps will reproduce the problem?1. Logging on2.3.
What is the expected output? What do you see instead?The expected is to see my character unit frame, what I see is a completely blank unit frame.
What version of the product are you using?Latest Curse Version
Do you have an error log of what happened?Date: 2013-09-11 10:14:49ID: 1Error occured in: GlobalCount: 1Message: ..\AddOns\PitBull4_LuaTexts\LuaTexts.lua line 886: Usage: PitBull4_FontString_6:SetFont("font", fontHeight [, flags])Debug: [C]: SetFont() PitBull4_LuaTexts\LuaTexts.lua:886: PitBull4_LuaTexts\LuaTexts.lua:839 PitBull4_LuaTexts\LuaTexts.lua:1429: AddFontString() ...ddOns\PitBull4\ModuleHandling\TextProviderModule.lua:118: UpdateFrame() PitBull4\ModuleHandling\Module.lua:319: Update() PitBull4\UnitFrame.lua:808: Update() PitBull4\UnitFrame.lua:728: RecheckConfigMode() PitBull4\Options\ConfigMode.lua:58: RecheckConfigMode() PitBull4\Main.lua:1347: OnProfileChanged() PitBull4\Main.lua:1412: PitBull4\Main.lua:1382 (tail call): ? [C]: ? [string "safecall Dispatcher[1]"]:9: [string "safecall Dispatcher[1]"]:5 (tail call): ? Ace3\AceAddon-3.0\AceAddon-3.0.lua:558: EnableAddon() Ace3\AceAddon-3.0\AceAddon-3.0.lua:651: Ace3\AceAddon-3.0\AceAddon-3.0.lua:636 [C]: LoadAddOn() ..\FrameXML\UIParent.lua:303: UIParentLoadAddOn() ..\FrameXML\UIParent.lua:377: TimeManager_LoadUI() ..\FrameXML\UIParent.lua:737: ..\FrameXML\UIParent.lua:702Locals:None
Please provide any additional information below.
<p>Blank Player Unit Frame</p>
<p>Requested Attachement</p>
<p>Errored LuaTexts file</p>
<p>Error is with Player not Target</p>
<p>After selecting "Party" from config mode drop-down.</p>
<p>Segoe UI (Name/Class) Player, Segoe UI Bold (Name/Class) Target</p>
I also have this same issue as the OP. Same lua error and same UI result with no text on the player panel. Can upload mine also if you need np.
So far nobody has uploaded the config file which may be helpful in tracking this down.
Config file is in WTF/Account/$ACCOUNTID/SavedVariables/PitBull4.lua
If someone can attach it to this ticket that would be very helpful. Please specify which profile you're using on the character(s) that are having the issue.
Added requested file(s)
This error is not affecting all characters or it seems to have fixed itself when I chose "Party" from the config mode drop-down. This error is affecting Gotswaggle - Moon Guard and Smallybigs - Moon Guard.
Getting FrameXML\Unitframe.lua Error on Fuzzybum - Azuremyst and Aloriele - Azuremyst
Also noted when updating to the latest SharedMediaAdditionalFonts it broke Pitbull completely
Thanks
Text not loading properly on player frame on any character. Requires a /reload followed by a manual disabling/re-enabling of LUA:class in Pitbull's text drop-down menu.
Using default profile.
EDIT: This is a beta build downloaded from wowace (47.1 if I'm not mistaken), not the version currently uploaded to curse.
EDIT 2: Can confirm like the other poster that all texts will ultimately load properly if you enable PitBull's "Party" configuration mode and disable it.
Heya, I have exactly the same problem from time to time, blank player frame, no text, no power bar, no background panel.
Difference is: I use DogTags.
Pitbull version is the latest download here, Beta47-2. A single /rl or afromentioned use of Config Mode are reliable ways to get rid of the problem.
I can provide error logs / config files if necessary.
Thanks for your hard work!
Shefki,
Hey there and thanks for the update. Sadly though, I seem to have the same issue with 47.3 as I did with 47.1/47.2. Most of my frame loads as shown in the screenshots below, but the texts seem to be hit or miss. Sometimes the name, health, and mana texts will load, but never LUA: class on my initial load-in on any character. I either have to disable/re-enable that particular text manually, or simply do the party configuration workaround.
Let me know if I can provide anything aside from these two posts to help you track down the issue.
Thanks again.
OK so I have figured out the problem on my own, it has to do with SharedMediaAdditionalFonts and a custom Windows font that I'm using. The error I'm having has something to do with "font height" yet these fonts were being used prior to 5.4 without error.
These are the strings I'm using in SharedMediaAdditionalFonts:
SharedMediaAdditionalFonts:Register("font", "Segoe UI", [[Interface\Addons\SharedMediaAdditionalFonts\fonts\segoeui.ttf]]) SharedMediaAdditionalFonts:Register("font", "Segoe UI Bold", [[Interface\Addons\SharedMediaAdditionalFonts\fonts\segoeuib.ttf]]) SharedMediaAdditionalFonts:Register("font", "Segoe Print", [[Interface\Addons\SharedMediaAdditionalFonts\fonts\segoepr.ttf]]) SharedMediaAdditionalFonts:Register("font", "Segoe Print Bold", [[Interface\Addons\SharedMediaAdditionalFonts\fonts\segoeprb.ttf]]) SharedMediaAdditionalFonts:Register("font", "Segoe Script", [[Interface\Addons\SharedMediaAdditionalFonts\fonts\segoesc.ttf]]) SharedMediaAdditionalFonts:Register("font", "Segoe Script Bold", [[Interface\Addons\SharedMediaAdditionalFonts\fonts\segoescb.ttf]]) SharedMediaAdditionalFonts:Register("font", "MV Boli", [[Interface\Addons\SharedMediaAdditionalFonts\fonts\mvboli.ttf]])
Fonts that I'm using in Pitbull Unit Frames 4.0 Segoe UI Segoe UI Bold
Those fonts are standard Windows 7/8 Fonts, so maybe I should put in a ticket with that addon?
I've tried to reproduce this and can't. However, the latest alpha has some code that should prevent this sort of error from breaking the frames (you may still have missing text but the frame will still show).
I suspect (and this has happened in the past) that Blizzard has broken something with respect to font rendering. The configuration file that's been uploaded was using Segoe UI and Segoe UI Bold. I set those fonts up but still wasn't able to reproduce the issue. However, I'm on a Mac and so I'm using the OpenGL rendering engine rather than the DirectX engine. So the bug could be specific to when that engine is being used.
The changes I made in the latest alpha should also help determining which layouts/texts are causing problems. You'll get an error message that mentions the layout and the text name that triggered the error. I'd of course be interested in seeing these errors. But I suspect that if you chose a different font for those layouts the problem will just go away.
If the problem goes away when you change the font then there's really nothing I can do about it.
@BillieJackFu: Go
All the SharedMedia addons do is provide a way to know where fonts are located since you just provide the game the path to them. So if a font isn't working correctly then it's a problem on Blizzard's end. This has happened before, Blizzard doesn't test against fonts other than what they include.
<<reply 1777575>>
Yes, what I did to resolve the issue was removing my modified SharedMediaAdditionalFonts then installing the latest.
When using the latest with the standard fonts, there are no errors produced. So do I need to contact Blizzard in regards to getting Segoe UI to work again, because Arial doesn't look right.
I would make a post on the UI & Macros forum. But to be honest it might get fixed but it's not likely to be fixed until the next major patch and even then there's no guarantees. Blizzard often ends up with these sorts of issue persisting for years.
@Shefki
The only issue I see is that I'm not receiving errors for using the font in Prat 3.0, Bazooka Bars, or SCT.
I just loaded the latest and it shows which texts are throwing errors and I have figured out the issue.
The issue in Pitbull 4 only is Segoe UI Bold for Lua_Name, Lua_Class I switched them to Segoe UI and no errors.
However Segoe UI Bold is still being used for Target Lua_Name, Lua_Class and not throwing any errors for those, the text is still being rendered fine. Curious.
<<reply 1777590="">>
Added a new screenshot showing Segoe UI on Player frame and Segoe UI Bold on Target frame, no errors.
Why would the player frame throw errors and the target frame not?
Post the errors with the new alpha. It'll be interesting to see what sorts of arguments to SetFont are triggering that error. But I couldn't reproduce the issue with Segoe UI Bold on the Mac and using your configuration. The fact that only a small number of people are having the issue, I can't reproduce it and that the error really doesn't make any sense leads me to think this isn't my bug.
<<reply 1777612>>
Error but it's just with the Lua_Name / Lua_Class on Player only:
Date: 2013-09-15 19:32:34 ID: 1 Error occured in: Global Count: 1 Message: PitBull4_LuaTexts:Player:Lua:Name caused the following error when calling SetFont(nil,0,nil): Usage: PitBull4_FontString_3:SetFont("font", fontHeight [, flags]) Debug: PitBull4_LuaTexts\LuaTexts.lua:902 PitBull4_LuaTexts\LuaTexts.lua:856 PitBull4_LuaTexts\LuaTexts.lua:1445 AddFontString() ...ddOns\PitBull4\ModuleHandling\TextProviderModule.lua:118 UpdateFrame() PitBull4\ModuleHandling\Module.lua:319 Update() PitBull4\UnitFrame.lua:808 Update() PitBull4\UnitFrame.lua:728 RecheckConfigMode() PitBull4\Options\ConfigMode.lua:58 RecheckConfigMode() PitBull4\Main.lua:1347 OnProfileChanged() PitBull4\Main.lua:1412 PitBull4\Main.lua:1382 (tail call): ? [C]: ? [string "safecall Dispatcher[1]"]:9: [string "safecall Dispatcher[1]"]:5 (tail call): ? Ace3\AceAddon-3.0\AceAddon-3.0.lua:558 EnableAddon() Ace3\AceAddon-3.0\AceAddon-3.0.lua:651 Ace3\AceAddon-3.0\AceAddon-3.0.lua:636 [C]: LoadAddOn() ..\FrameXML\UIParent.lua:303 UIParentLoadAddOn() ..\FrameXML\UIParent.lua:377 TimeManager_LoadUI() ..\FrameXML\UIParent.lua:737 ..\FrameXML\UIParent.lua:702 Locals: None AddOns: Swatter, v5.18.5433 (PassionatePhascogale) Ace3, v ACP, v3.4.4 Align, v Altoholic, v5.4.001 AraBrokerGuildFriends, vr62 AraBrokerReputations, vr15 Atlas, v1.26.01 AtlasBattlegrounds, v1.26.00 AtlasBurningCrusade, v1.26.00 AtlasCataclysm, v1.26.00 AtlasClassicWoW, v1.26.00 AtlasDungeonLocs, v1.26.00 AtlasOutdoorRaids, v1.26.00 AtlasScenarios, v1.26.00 AtlasTransportation, v1.26.00 AtlasWrathoftheLichKing, v1.26.00 AtlasLootLoader, vv7.07.00 AucAdvanced, v5.18.5433 (PassionatePhascogale) AucFilterBasic, v5.18.5433 (PassionatePhascogale) AucFilterOutlier, v5.18.5433.5347(5.18/embedded) AucMatchUndercut, v5.18.5433.5364(5.18/embedded) AucStatHistogram, v5.18.5433 (PassionatePhascogale) AucStatiLevel, v5.18.5433 (PassionatePhascogale) AucStatPurchased, v5.18.5433 (PassionatePhascogale) AucStatSales, v5.18.5433.5376(5.18/embedded) AucStatSimple, v5.18.5433 (PassionatePhascogale) AucStatStdDev, v5.18.5433 (PassionatePhascogale) AucStatWOWEcon, v5.18.5433.5323(5.18/embedded) AucUtilAHWindowControl, v5.18.5433.5347(5.18/embedded) AucUtilAppraiser, v5.18.5433.5427(5.18/embedded) AucUtilAskPrice, v5.18.5433.5347(5.18/embedded) AucUtilAutoMagic, v5.18.5433.5415(5.18/embedded) AucUtilCompactUI, v5.18.5433.5427(5.18/embedded) AucUtilEasyBuyout, v5.18.5433.5427(5.18/embedded) AucUtilFixAH, v5.18.5433 (PassionatePhascogale) AucUtilItemSuggest, v5.18.5433.5417(5.18/embedded) AucUtilPriceLevel, v5.18.5433.5427(5.18/embedded) AucUtilScanButton, v5.18.5433.5403(5.18/embedded) AucUtilScanFinish, v5.18.5433.5347(5.18/embedded) AucUtilScanProgress, v5.18.5433.4979(5.18/embedded) AucUtilScanStart, v5.18.5433.5347(5.18/embedded) AucUtilSearchUI, v5.18.5433.5373(5.18/embedded) AucUtilSimpleAuction, v5.18.5433.5415(5.18/embedded) AucUtilVendMarkup, v5.18.5433.4828(5.18/embedded) Aurora, v4.7a Babylonian, v5.1.DEV.332(/embedded) BagBrother, v Bagnon, v5.4.2 Bartender4, v4.5.13 BasicMinimap, v2.13 Bazooka, vv2.2.5 BeanCounter, v5.18.5433 (PassionatePhascogale) BrokerBagFu, v50400-1 BrokerCurrencyflow, vv1.4-1 BrokerDurabilityInfo, v1.17 BrokerExit, v3.0.4-release BrokerGotMail, v1.01a BrokerGroup, v BrokerVolume, v1.3.1 Carbonite, v5.4.0 alpha 1r1 CarboniteInfo, v1.0 CarboniteNodes, v1.02 CarboniteNotes, v1.1 CarboniteNotesSample, v1.0 CarboniteQuests, v1.0 CarboniteSocial, v1.0 CarboniteTransfer, v1.01 CarboniteWarehouse, v1.0 CarboniteWeekly, v1.0 Configator, v5.1.DEV.344(/embedded) CTCore, v5.0002 CTMailMod, v5.0002 cursorcastbar, v DataStore, v5.4.001 DataStoreAchievements, v5.4.001 DataStoreAgenda, v5.4.001 DataStoreAuctions, v5.4.001 DataStoreCharacters, v5.4.001 DataStoreContainers, v5.4.001 DataStoreCrafts, v5.4.001 DataStoreCurrencies, v5.4.001 DataStoreInventory, v5.4.001 DataStoreMails, v5.4.001 DataStorePets, v5.4.001 DataStoreQuests, v5.4.001 DataStoreReputations, v5.4.001 DataStoreSpells, v5.4.001 DataStoreStats, v5.4.001 DataStoreTalents, v5.4.001 DBMCore, v DBMLDB, v DebugLib, v5.1.DEV.337(/embedded) DungeonHelper, vv2.3.6 Enchantrix, v5.18.5433 (PassionatePhascogale) EnchantrixBarker, v5.18.5433 (PassionatePhascogale) Examiner, v13.05.22 fontain, v GnomishVendorShrinker, v5.0.1.15 GrayBGone, v GuildRosterButtons, v3.8 HealBot, v5.4.0.1 IgnoreMore, v1.1.1-40300 LibExtraTip, v5.12.DEV.355(/embedded) LibMapData10, v1.0.0.30-release LibPeriodicTable31, vv3.3.0.423 Masque, v5.0.387 MasqueDiabloIII, v1.5 Misspelled, v1.5.19 MoveAnything, v13.6.1 Multishot, v3.1.1 Omen, v3.1.8 Outfitter, v5.9.2 PitBull4, vv4.0.0-beta47-5-g54eda46 PitBull4Aggro, vv4.0.0-beta47-5-g54eda46 PitBull4AltPowerBar, vv4.0.0-beta47-5-g54eda46 PitBull4Aura, vv4.0.0-beta47-5-g54eda46 PitBull4Background, vv4.0.0-beta47-5-g54eda46 PitBull4BattlePet, vv4.0.0-beta47-5-g54eda46 PitBull4BlankSpace, vv4.0.0-beta47-5-g54eda46 PitBull4Border, vv4.0.0-beta47-5-g54eda46 PitBull4CastBar, vv4.0.0-beta47-5-g54eda46 PitBull4CastBarLatency, vv4.0.0-beta47-5-g54eda46 PitBull4CombatFader, vv4.0.0-beta47-5-g54eda46 PitBull4CombatIcon, vv4.0.0-beta47-5-g54eda46 PitBull4CombatText, vv4.0.0-beta47-5-g54eda46 PitBull4ComboPoints, vv4.0.0-beta47-5-g54eda46 PitBull4ExperienceBar, vv4.0.0-beta47-5-g54eda46 PitBull4HealthBar, vv4.0.0-beta47-5-g54eda46 PitBull4HideBlizzard, vv4.0.0-beta47-5-g54eda46 PitBull4HostilityFader, vv4.0.0-beta47-5-g54eda46 PitBull4LeaderIcon, vv4.0.0-beta47-5-g54eda46 PitBull4LuaTexts, vv4.0.0-beta47-5-g54eda46 PitBull4MasterLooterIcon, vv4.0.0-beta47-5-g54eda46 PitBull4PhaseIcon, vv4.0.0-beta47-5-g54eda46 PitBull4Portrait, vv4.0.0-beta47-5-g54eda46 PitBull4PowerBar, vv4.0.0-beta47-5-g54eda46 PitBull4PvPIcon, vv4.0.0-beta47-5-g54eda46 PitBull4RaidTargetIcon, vv4.0.0-beta47-5-g54eda46 PitBull4RangeFader, vv4.0.0-beta47-5-g54eda46 PitBull4ReadyCheckIcon, vv4.0.0-beta47-5-g54eda46 PitBull4ReputationBar, vv4.0.0-beta47-5-g54eda46 PitBull4RestIcon, vv4.0.0-beta47-5-g54eda46 PitBull4RoleIcon, vv4.0.0-beta47-5-g54eda46 PitBull4Sounds, vv4.0.0-beta47-5-g54eda46 PitBull4ThreatBar, vv4.0.0-beta47-5-g54eda46 PitBull4VisualHeal, vv4.0.0-beta47-5-g54eda46 Prat30, v3.5.7 Prat30HighCPUUsageModules, v Prat30Libraries, v Raven, v Recount, v ReforgeLite, v1.33 sct, v6.65 sctd, v6.65 SharedMediaClassicalFonts, vRelease 1.0.4 SharedMediaAdditionalFonts, v1.0.16 SharedMediaAdditionalSounds, v1.1 SlideBar, v5.18.5433 (PassionatePhascogale) Stubby, v5.18.5433 (PassionatePhascogale) SunnArt, v3.68 SunnArtPack3, v1.14 TidyPlates, v6.12.3 TidyPlatesGraphite, v TidyPlatesGrey, v TidyPlatesNeon, v TidyPlatesQuatre, v TidyPlatesThreatPlates, v6.008 TidyPlatesHub, v TidyPlatesWidgets, v TipHelper, v5.12.DEV.351(/embedded) TipTac, v13.05.22 TipTacItemRef, v13.05.22 TipTacTalents, v13.04.17 TravelAgent, v5.3.0-1.1.3 WIM, v3.6.10 WIMRaspberyl, v WIMRaspberylCurse, v zzInfoclock, v BlizRuntimeLib_enUS v5.4.0.50400 <us> (ck=17e0)
I've installed the 47.5 beta and in doing so I've encountered 13 LUA errors upon initial login. This is error #1 of 13
Message: PitBull4_LuaTexts:Normal:Lua:Name caused the following error when calling SetFont(nil,0,nil): Usage: PitBull4_FontString_2:SetFont("font", fontHeight [, flags]) Time: 09/15/13 19:45:04 Count: 1 Stack: Interface\AddOns\PitBull4_LuaTexts\LuaTexts.lua:902 in function <Interface\AddOns\PitBull4_LuaTexts\LuaTexts.lua:856 Interface\AddOns\PitBull4_LuaTexts\LuaTexts.lua:1445 in function `AddFontString' ...ddOns\PitBull4\ModuleHandling\TextProviderModule.lua:118 in function `UpdateFrame' Interface\AddOns\PitBull4\ModuleHandling\Module.lua:319 in function `Update' Interface\AddOns\PitBull4\UnitFrame.lua:808 in function `Update' Interface\AddOns\PitBull4\UnitFrame.lua:728 in function `RecheckConfigMode' Interface\AddOns\PitBull4\Options\ConfigMode.lua:58 in function `RecheckConfigMode' Interface\AddOns\PitBull4\Main.lua:1347 in function `OnProfileChanged' Interface\AddOns\PitBull4\Main.lua:1412 in function <Interface\AddOns\PitBull4\Main.lua:1382 (tail call): ? [C]: ? [string "safecall Dispatcher[1]"]:9: in function <[string "safecall Dispatcher[1]"]:5> (tail call): ? ...AddOns\Bartender4\libs\AceAddon-3.0\AceAddon-3.0.lua:558 in function `EnableAddon' ...AddOns\Bartender4\libs\AceAddon-3.0\AceAddon-3.0.lua:651 in function <...AddOns\Bartender4\libs\AceAddon-3.0\AceAddon-3.0.lua:636 [C]: in function `LoadAddOn' Interface\FrameXML\UIParent.lua:303 in function `UIParentLoadAddOn' Interface\FrameXML\UIParent.lua:326 in function `CombatLog_LoadUI' Interface\FrameXML\UIParent.lua:739 in function <Interface\FrameXML\UIParent.lua:702
I can post any and all other errors if you'd like. Just give me the word.
EDIT: apologies for the formatting. I just wound up copy and pasting the text from the LUA error window in-game. Is there a more preferable way to do this?
EDIT 2: Thank you kindly, Midnightwolf76.
@Crackadamus: Go
I just post the errors in plain text (drop down menu), I also have Swatter grabbing my errors for me, I believe it is included with the Auctioneer suite.
What font are you using in your Unit Frames?
What font are you using for your Unit Frames?
<<reply 1777688>>
@Midnightwolf: Wonder Comic from Shared Media.
EDIT: As well, it should be noted 47.5 has rendered PitBull completely unusable. All that loaded in my player frame was the texture I use for my power/health bars and the texture I've selected to outline the border, and nothing else.
SharedMedia hasn't been updated since last September, I think that font might be your issue. But if you're using that font for target and it's not throwing an error for that. It must be something with the Player and Pet Unit Frames, it's an odd error if you've been following my progress.
<<reply 1777708>>
@Midnightwolf,
I'll remove Shared Media and restart WoW and report back.
<<reply 1777712>>
Well, removing Shared Media didn't change anything, and in fact turned my Chocolate Bar addon from it's normal brown to a greenish color.
EDIT: Not that it means anything, but for what it's worth I was using a font from Shared Media in Prat and it never seemed to have any issues. Pitbull's been borked since 5.4 rolled out, though. Although the version I was using before 47.5 was entirely usable even if one had to use the party config workaround to have everything load properly.
Open your Pitbull config, use the Config Mode dropdown and select party, then select disable and take a screenshot.
Same for me, everything has been working fine with the font I've been using in all my other Ace addons, but for some unknown reason. Lua:Name, Lua:Class for player and pet unit frames are throwing errors. I'm not getting any errors for my Target or Target of Target unit frames with the same font.
<<reply 1777731>>
@Midnightwolf.
I restored Shared Media to my addons folder and did the party config workaround. Apparently I spoke too soon with my last post as that restored my frames to how I've customized them and everything appeared fine thereafter.
EDIT: The screenshot shows how my frames appear after the party config workaround.
OK so all this troubleshooting may help Shefki narrow down the issue. Because Lua:Class and Lua:Name work fine with our selected fonts on Target, Target of Target and the like. However Lua:Class and Lua:Name do not work with Player (Normal) or Pet frames.
<<reply 1777745>>
@MW76:
Yeah, I hope so. I've been using Pitbull since its first incarnation, through its "Rock" period and right up until now. It's far and away my favorite unit frame addon and I'll do whatever I can to help restore its error-free functionality.
Okay I have an idea what's going on now.
Can you guys update to the latest alpha (aka beta47-6), load in and when the problem is occurring run: /dump PitBull4.DEFAULT_FONT and /dump PitBull4.DEFAULT_FONT_SIZE
And tell me what it outputs.
I suspect that for some odd reason the ChatFontNormal isn't available when you load in and your exact font isn't available either. Normally we'd use the ChatFontNormal until the next frame update, but if it isn't available then we'll have no font and thus the problem you're having.
It seems very odd to me that ChatFontNormal isn't available on your load in, but if it isn't perhaps I should just encode a hard coded font/size set for these sorts of situations.
<<reply 1777777>>
I'll do that now, Shefki. Give me a few minutes and I'll report back with the details.
<<reply 1777778>>
Please see the chat box for dump results.
EDIT: Apologies. I didn't get the whole /dump command in for the second query and had to redo it. In any case, the green and purple texts should be what you've asked for.
Default_Font [1]="Fonts\\ARIALN.TTF"
Default_Font_Size [1]=13.999999046326
<<reply 1777786>>
@MW76
We're a match!
Well that's not what I expected.
Can you guys try one other thing for me and see if it helps.
Exit the game. Edit the file in Interface/AddOns/PitBull4/PitBull4.toc and add whatever addon is loading your SharedMedia font, e.g. SharedMediaAdditionalFonts to the list of OptionalDeps.
Load the game up and see if the issue continues.
With Matching Errors; which I'm assuming that's the reason only a few people are suffering from this error. I'm sure Shefki figured this as well.
No the result is actually a normal result. It's what I'd expect if your frames were working normally.
@Shefki: Go
Edited TOC and.....
Zero errors!!!
So push an update to include SharedMedia, SharedMediaAdditionalFonts, SharedMediaClassicalFonts to TOC file?
The whole point of the way things are designed is so that isn't necessary. It's impossible to include all the modules that add fonts in the OptionalDeps. I actually get my fonts from SharedMedia_MyMedia and other independent mods can provide fonts. So there's got to be another answer to this issue.
One other thought. Did both of you complete exit the game after you updated the addon to the latest alpha? A lot of people have been saying this only happens on the first load in.
<<reply 1777800>>
Hmm, I'm relatively sure I put in the correct parameters in the .toc but I'm getting the same errors. mw76, could you please paste your .toc here so I can try it in my game?
I was just thinking it could be a temporary fix to push until you find the real culprit. I realize adding modules would be tedious. I use an old addon called Fontain to adjust all my other fonts, just keep updating the TOC because the project seems to be dead.
<<reply 1777810>>
Yeah, I'd always be out of game whenever I update an addon.
FYI toc files are only read when the game starts, if you change it while it's running you'll have to exit before any of the changes will take effect.
@Crackadamus: Go @Shefki: Go
This is another reason for the request for the modules to be added to the TOC as a hotfix, for testing.
EDIT: Well scratch that, I just loaded another character and got an error on Lua:Experience of the same type.
<<reply 1777816>>
I edited the .toc with Notepad++ when WoW wasn't running. I just saved the file and re-launched WoW.
<<reply 1777818>>
Here's the contents of my edited .toc. Anything look incorrect to you two?
<snip>
EDIT: Ah, ok mw76. I just saw your edit.
So the reason the protection code I added a few pushes ago wasn't working was that Blizzard's error handler apparently throws an error itself when called so early in the loading process.
I think if you guys try now you'll have some initial errors on load in but everything should work normally besides that.
<<reply 1777855>>
Yeah, I got a LUA error on initial load-in, but after a /reload everything appears to be normal.
[off topic]
As well, Shefki, I know this isn't the appropriate place and for that you have my apologies, but if it's all the same to you I was wondering if I can make a small request about the monk class.
Like the druid, the mana bar will disappear and reappear when you change stances. But, when the Monk is in his healing stance, he can still do melee attacks but the power bar is no longer visible. Would it be at all possible to make Pitbull show the Monk's power bar while in healing stance?
Thanks for all the work you've done with Pitbull, by the way. As I've already mentioned this has been my favorite unit frame addon for as long as I can remember.
Lastly, regarding the above if you wanted me to make a ticket of some kind for the request, by all means please let me know.[/off topic]
Thanks again!
My only issue is why is it only throwing errors on Player Unit Frame and Pet Unit Frame, if it was an error handler it would throw errors on Target / Target of Target Unit Frames too.
Probably because those frames are created and updated on load, other frames don't have anything to display until after you load in.
The latest alpha should work right from the start (you'll just see some errors if you have Lua Errors turned on), at least it does for me when I deliberately create the error.
The Monk thing should be a new ticket.
<<reply 1777879>>
Understood. Thanks again for all the uploads today.
Hi
Latest alpha is showing frame properly now and is populating a lua error also as you predicted.
A /reload straight after initial load is completely fine for me then (I know this works for some people).
1x PitBull4_LuaTexts:Normal:Lua:Power caused the following error when calling SetFont(nil,2.6031158770146e-030,nil): Usage: PitBull4_FontString_7:SetFont("font", fontHeight [, flags]) PitBull4_LuaTexts-v4.0.0-beta47-7-g82a3dda\LuaTexts.lua:843: in function <PitBull4_LuaTexts\LuaTexts.lua:838> PitBull4_LuaTexts-v4.0.0-beta47-7-g82a3dda\LuaTexts.lua:902: in function <PitBull4_LuaTexts\LuaTexts.lua:856> PitBull4_LuaTexts-v4.0.0-beta47-7-g82a3dda\LuaTexts.lua:1445: in function "AddFontString" PitBull4-v4.0.0-beta47-7-g82a3dda\ModuleHandling\TextProviderModule.lua:118: in function "UpdateFrame" PitBull4-v4.0.0-beta47-7-g82a3dda\ModuleHandling\Module.lua:319: in function "Update" PitBull4-v4.0.0-beta47-7-g82a3dda\UnitFrame.lua:810: in function "Update" PitBull4-v4.0.0-beta47-7-g82a3dda\UnitFrame.lua:728: in function "RecheckConfigMode" PitBull4-v4.0.0-beta47-7-g82a3dda\Options\ConfigMode.lua:58: in function "RecheckConfigMode" PitBull4-v4.0.0-beta47-7-g82a3dda\Main.lua:1347: in function "OnProfileChanged" PitBull4-v4.0.0-beta47-7-g82a3dda\Main.lua:1412: in function <PitBull4\Main.lua:1382> (tail call): ? <in C code> <string>:"safecall Dispatcher[1]":9: in function <string>:"safecall Dispatcher[1]":5 (tail call): ? AffDots-v1.3.3\Libs\AceAddon-3.0\AceAddon-3.0-12.lua:558: in function "EnableAddon" AffDots-v1.3.3\Libs\AceAddon-3.0\AceAddon-3.0-12.lua:651: in function <AffDots\Libs\AceAddon-3.0\AceAddon-3.0.lua:636> <in C code> FrameXML\UIParent.lua:303: in function "UIParentLoadAddOn" FrameXML\UIParent.lua:326: in function "CombatLog_LoadUI" FrameXML\UIParent.lua:739: in function <FrameXML\UIParent.lua:702> Locals: nil
Give beta47-9 a try. I have a theory about what's going on and that has a very specific workaround for the issue. If it works then it should solve the problem for LuaTexts and DogTagTexts.
Just to update.
I haven't installed the latest Alpha, but the issue doesn't present itself on load for me anymore. I'm actually thinking that another Ace module was the culprit, but can't narrow it down as I have been clearing my error logs.
The only error I'm receiving is when I join a party or raid and someone in the party/raid is flagged for PvP, I get an error on Lua.Text:PvPTimer but it goes away on its own.
Thanks for all your work on resolving the issue Shefki.
I believe the most recent push should fix the problem for everyone. Someone opened ticket 1055 with a reproduction recipe that worked for me. As I suspected it is a race condition (font provided by another addon is not available as far as the game engine is concerned but is available according to SharedMedia). When we set that font on the FontStrings it accepts it with no error, but when we later try to ask what the font is on the font string it gives us nil, which we then try to pass off to the SetFont. We use this GetFont() to preserve the font and size when we're only changing the 3rd parameter (the flags, e.g. outline, thick outline).
My fix resolves this by caching the font and size and using them instead when the font provided by GetFont is nil.
For what it's worth I've had fairly rare complaints about this problem for years. But could never replicate it. I'd guess this behavior of GetFont has always existed, but it simply didn't happen very often because WoW was almost always seeing the font as loaded before SharedMedia registered it. Something in 5.4 changed that, possibly some optimization that tries to make things load faster. Since the game only looks for files in the Interface folders the first time it loads, the problem doesn't reoccur on reloads or subsequent logins.
To post a comment, please login or register a new account.