[Workaround] Gear/Cog Icon of DOOM

Voir le topic d'origine

AuteurMessage

Deyneth
1. Le 18/10/2010 à 20:11
Hey Guys,

There's tons of threads posted and lots of promising solutions. I have one that I've been testing for three days and have not had as much as lag spike when mousing over cogs. This works if you're willing to disable tooltips when you are anywhere a cog icon might show up.

You will need to create two macros, for "turn off tooltips" and "turn on tooltips".

Turn Off Tooltips 
/script GameTooltip.Temphide = function() GameTooltip:Hide() end;  GameTooltip:SetScript("OnShow", GameTooltip.Temphide);

Turn On Tooltips 
/script GameTooltip:SetScript("OnShow", GameTooltip.Show);


This should get you through until the official fix comes down from Blizzard. Happy hunting!

Ujumqin
2. Le 18/10/2010 à 22:56
Thanks for the tip. Stickied.

Davidba
3. Le 18/10/2010 à 23:39
Curiosity. Has anyone tried turning off Enhanced and Beginner Tooltips as a scriptless workaround?

Main Menu > Interface > Help: Uncheck Enhanced Tooltips; uncheck Beginner Tooltips.


I'd test it myself, but none of the computers around the office has the issue.

Davidba
4. Le 18/10/2010 à 23:43
Q u o t e:
Hey good point, I might try that right now instead of the player fix and see if that works


Thanks, Zev! That would be great. : )

Davidba
5. Le 19/10/2010 à 00:30

Q u o t e:
Negative, still crashes the client.


Shucks. Thanks for trying.

Q u o t e:
A little unsolicited advice from a fellow geek in the software industry: You need a wider variety of computers in your office.


Dev and QA have tons of different configurations; no worries there. I'm not at their location however. : )

Davidba
6. Le 21/10/2010 à 23:37
I just wanted to pop in and confirm that Dev is working on this issue. I understand frustrations over the speed of resolution, but keep in mind that lot of problems simply can't be hotfixed. The worst reaction to a bug is to break five other things while recklessly fixing the first. One of my old favorites was a bugged monster in the barrens. The initial fix for it on the internal server broke the Illidan raid encounter in Outland. That may sound ridiculous from a non programmer's perspective (and it's certainly funny) but that's how code works.

I kept crashing on this same issue on my mage last night and had to use the script from earlier in the thread. Bear in mind that about 80% of us at Blizzard are playing WoW right along with you. We hate game issues from both perspectives, creator and player.

Davidba
7. Le 24/10/2010 à 23:51
UPDATE: We've made good progress on this issue and barring any unfortunate setbacks we should be able to roll out a fix fairly soon. Thanks to all of you who have been patient while we've worked on the problem. Thanks to the rest of you too; you may not be as patient, but your passion for our game is always respected and appreciated. Always.

On a personal note, I'll enjoy not being defeated by the Headless Horseman's pumpkin anymore! : )


Davidba
8. Le 25/10/2010 à 23:02
Q u o t e:
"The Cogwheel of Doom was merely a set-back!" - Davidba

That's how I read this. ^_^


Totally fair interpretation. : )

Q u o t e:
Being former military are you using the Navy sense of the term soon as in "soon-sometime before your enlistment ends" or the civilian version "soon-sometime in the next 15 days"?


Barring weirdness, the civilian version. Unlike a lot of forum issues that seem to be affecting a lot of WoW players but really aren't, this one genuinely is and has been a high-priority issue to resolve.

Q u o t e:
any chance on an explanation of the bug? some of us are interested in how wow ticks and what makes it suddenly stop.


While on the surface this is a great idea, the sheer crunch that the WoW team is under right now probably wouldn't make this feasible. However, if I hear a general explanation more compelling then "it was a UI thing" and I'm allowed to share then I'll definitely be glad to.