WowAce.com

FlightHUD

6 - FightHUD creates client performance problems in 25-man raids

I'm using the latest FlightHUD 0.7.11. Using all the default settings, set to only show while flying and swimming.

I've noticed that having FlightHUD loaded during 25-man raids, it significantly slows down my client while in combat (loss of frame rates, high jitter, etc). Disabling FlightHUD and doing reloadui immediately fixes the performance problem.

I assume that FlightHUD is hooking some UI function that it should not be or in some other way consuming CPU cycles during combat (which I'd prefer it never did). The FlightHUD display is not even visible inside instances, so there's absolutely no reason it should be active;y consuming cycles at all.

Please fix so I can leave this wonderful addon loaded all the time!

User When Change
oscarucb Tue, 30 Jun 2009 02:22:23 Changed status from Waiting to Replied
Barfolomeu Tue, 17 Mar 2009 18:17:10 Changed status from New to Waiting
oscarucb Mon, 09 Mar 2009 05:23:14 Create

You must login to post a comment. Don't have an account? Register to get one!

  • 2 comments
  • Avatar of oscarucb oscarucb Tue, 30 Jun 2009 02:22:23

    Hi Barf - Unfortunately, the problem persists.

    I even tried disabling that function completely by commenting out the line:

    self.DummyFrame:SetScript("OnUpdate", self.DummyOnUpdate)

    and I'm still seeing major drop in frame rates during raid when FlightHUD is loaded (but hidden).

    Something else must be stealing cycles while the window is hidden.

  • Avatar of Barfolomeu Barfolomeu Tue, 17 Mar 2009 18:17:03

    There is in fact a UI hook that is always running which I use to detect swimming, but this only runs once every quarter of a second. I raid all 25 man content every week on 2 characters and have never noticed any appreciable performance degradation.

    Please try this. Open WoW/Interface/AddOns/FlightHUD/FlightHUD.lua in a text editor and change line 830 (in version 0.7.13) from:

    if (DummyOnUpdateElapsed > .25) then

    to

    if (DummyOnUpdateElapsed > 1) then

    (or try numbers greater than 1) and let me know if it makes a difference.

    I admit, I got a bit lazy, and didn't make that timer be configurable via the config, nor did I set it to a variable. I'll fix that in a future release.

    BTW, sorry for not getting back to you sooner. I didn't have wowace notifying me of new tickets, but now I do.

    Barf

  • 2 comments

Facts

Last updated on
30 Jun 2009
Reported on
09 Mar 2009
Status
Replied - Someone has replied after waiting for more information.
Type
Defect - A shortcoming, fault, or imperfection
Priority
Medium - Normal priority.

Reported by

Possible assignees