Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Doesn't show any meters when join new raid #854

Open
GregoryGH opened this issue Nov 3, 2024 · 8 comments
Open

Doesn't show any meters when join new raid #854

GregoryGH opened this issue Nov 3, 2024 · 8 comments

Comments

@GregoryGH
Copy link

WoW SoD
DETAILS! VERSION: VCT 13132 ALPHA 2 1.15.4

Doesnt show anything when join new raid. Reload UI seems fix it.

@Flamanis
Copy link
Contributor

Flamanis commented Nov 3, 2024

As nondescript as possible i see. Thanks for the useless report.

If you want to give some usable information, like what raid, what isnt showing, etc, im all ears

@GregoryGH
Copy link
Author

  1. Join new raid
  2. No any damage bars shown, just an empty details window
  3. After reload ui it work fine

no idea how to be more descriptive

@Tremolo4
Copy link

Tremolo4 commented Nov 7, 2024

At least a few people in my raid including me have the same issue. Maybe everyone. Cataclysm Classic. Also have it in 5 man dungeons. Also had it in a level 50 dungeon on an alt. No errors in BugSack. Doesn't seem to be related to any specific raid or dungeon. Seems to be related to zoning in / loading screen rather than just joining a group.

Some people report healing meters still work when damage doesn't.

@gurka
Copy link

gurka commented Nov 7, 2024

Happened to a few of us in SoD Zul'Gurub too. Reload seem to fix it, but another reload afterwards can break it again. Only damage done is missing, healing done etc still works.

Version 20241107.13188.161.

Now I also get a message like "Details!: seems failed to load, please type /reload to try again" when logging in. I tried /details reinstall but the same message appears.

Edit: nevermind, now no meter work. Only Tiny Threat seem to work.

@lapinsami
Copy link

lapinsami commented Nov 7, 2024

If you enable lua errors you get bad argument #1 to 'pairs' (table expected, got nil) on line 235 in deathrecap.lua

Putting the for key in pairs(tableContents) loop inside an if that checks for nil (so it doesn't execute when tableContents is nil) fixed the problem for me. Not sure if it causes some other problems, I don't know how any of the code works.

Full error message:

Time: Thu Nov  7 22:14:37 2024
Count: 1
Stack: Interface/AddOns/Details/functions/deathrecap.lua:237: bad argument #1 to 'pairs' (table expected, got nil)
[string "=[C]"]: in function `pairs'
[string "@Interface/AddOns/Details/functions/deathrecap.lua"]:237: in function `InitRecap'
[string "@Interface/AddOns/Details/startup.lua"]:109: in function `StartMeUp'
[string "@Interface/AddOns/Details/core/parser.lua"]:6532: in function <Interface/AddOns/Details/core/parser.lua:6531>

Locals: (*temporary) = nil
(*temporary) = "table expected, got nil"```

@mstreurman
Copy link

mstreurman commented Nov 8, 2024

I want to help but I don't know how to get any debug logs and stuff for this. But it happened yesterday (7th nov '24 8pm CET) to me and most of my guild in SoD as well with the then latest version, with the difference that a reload doesn't fix the issue. I noticed when I checked inside the different meters that most damage ones were "greyed out" so to speak.

@GregoryGH
Copy link
Author

seems fixed with
DETAILS! VERSION: VCT 13190 RELEASE 1.15.4

@lapinsami
Copy link

Seems fixed for me as well after updating

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants