Health not accurate at times #768


Closed
  • mizledTV created this issue Nov 21, 2019

    What version of Grid2 are you using?

     r939 (Classic)

     

    What game client version (windows or mac) and language are you using ?

     1.13.2 (Classic) on Windows 

     

    What steps will reproduce the problem?

    I am not able to consistently reproduce the issue but it happens at least 2-3 times per dungeon/raid  


    Did you try having Grid2 as the only enabled addon and everything else disabled?

    No

      

    Was it working in a previous version? If yes, which was the last good one?

    Not sure

      

    Do you have an error log of what happened? If you don't see any errors, make sure that error reporting is enabled (`/console scriptErrors 1`) or install [BugSack](https://mods.curse.com/addons/wow/BugSack).

    No errors that I can see

      

    Please provide any additional information below.

     

    Occasionally Grid2 reports a players health incorrectly. This leads me to healing a target who is already at full HP. See below from my screenshot that the player "Hotburrito" is missing 625 HP according to Grid2 but Shadow Unit Frames is reporting he has full HP (none missing). No buffs/debuffs were recently removed either. Once I heal the target, Grid2 will then update to report the correct HP. I am unsure if this is a misconfiguration of Grid2 on my part or a bug.

     

  • michaelsp posted a comment Nov 22, 2019

    1. Which type of health update configuration are you using ?

    Statuses->Health&heals>Update frequency

    Normal or Instant ?

    Instant option is not always accurate, because is a estimate of future health based on combat log info.

  • mizledTV posted a comment Nov 22, 2019

    I am using instant, I will try with Normal and see if that corrects the issue.


    Edited Nov 22, 2019
  • mizledTV closed issue Nov 24, 2019
  • mizledTV posted a comment Nov 24, 2019

    Setting it to Normal seems to have fixed the issue. If I notice the problem reappear I'll reopen the issue.


To post a comment, please login or register a new account.