[FIXED] [General] GCD malfunction / Spell Queue / Character trembling

[Granz]

confirm.

[1007]

spuffy wrote:

Bug description: Sometimes I have to press a spell many times before it lands. It triggers the global CD for a very short period of time, then it resets ( many times ). Very frustrating !!! Also trying to cast something when not facing the target triggers some kind of global cooldown and prevents you from using any spell. It works well when out of range although Proof:

https://youtube.com/watch?v=58MEzEZVXqo:


This is the oldest and the worst bug, it persists since Cata(4.3.4) was released on freakz.

[Paul !?]

You dont want to see how impactful it is on hunter , when you cant get your last aimed shot in a vulnerable window

[nelloide]

confirmed

[Ozzydany]

http://wowwiki.wikia.com/wiki/Cooldown

Quote:

The global cooldown is generally 1.5 seconds for all classes except rogues, Cat Form druids, and Death Knights, whose abilities are mostly one second global cooldown(reduced to 0.5 in UP).

I think is a malfunction that doens't let you after a cast/channeling to continue your rotation , clearly sayd you have a global cooldown after your cast is finish (the global cooldown should be finished already in the time of the cast) .
Not every spell have that , i think we should identify every spell with this problem to be able to fix them all .
Rampage is a good example and maybe every problematic spell should have the same fix.


but i dont know about instant spells , i dont have this problem on my monk
https://youtube.com/watch?v=Zx46DZVJuLs:

[Miran]

Confirm

[Jugg]

confirm, happens to me on my rog and its sooo frustrating ! in pvp its worst !!

[Marettak]

confirm, as outlaw rogue in my burst that last couple sec is annoying, also having haste leg ring , with 80%+ haste its annoying , as i should be spamming my abilities but no it wont let me , same issue on DH tank

[Paul !?]

It's that hard to fix ?

[Unrael]

This is really annoying on MM hunter.... They should fix this as fast as possible....

[Garn]

I will move this to confirmed so people stop bumping the report.

Devs are aware of it and will let you know as soon as there is a conclusion to this.


Posting a new BUG REPORT has to follow the template you get when opening a new topic or it can be instantly rejected.

Freakz Lich King 25H

[Quicksand]

Just to begin: Please share this post with everyone you know, this might provide a whole lot better playing experience, let everyone know about this fix!

TL;DR for those who are not interested in technical part:
If you DO NOT want to use spellqueue (highly recommended), do the following:
1. Use ".spellqueue off" to turn off server-side queue
2. Set the following client variables: MaxSpellRecoveryoffset and ReducedLagTolerance. To do this, follow these steps:
Open your Config.wtf, and add these options, then save the file.
SET MaxSpellStartRecoveryoffset 0
SET ReducedLagTolerance 1

OR

If you want to do it via a macro, you can do:

/console MaxSpellStartRecoveryoffset 0
/console ReducedLagTolerance 1

Just enter this into a macro, or directly into chat, you are all set.

In case you do want spellqueue, just simply do ".spellqueue on" and that's all.

For those interested in more details, read further here:

Spoiler:

The issue was never the GCD. GCD calculations are exactly blizzlike, the issue is with the Spell Queue system as some of you suggested.
Just to explain: blizzard ALWAYS uses this spellqueue, but on our server it's disabled by default (and as of now you can't really enable it, since it's rather bugged - both the command and the system itself).
It should function like this: the client lets you cast a spell 400ms sooner than your GCD finishes (there's a 0-400ms window where you can do that, calculated from the end of the GCD). If you try and spam a spell in that time, the client sends the server a request that you want to cast a spell, and at the same time it tells your character to start the cast animation => the request gets to the server, and immediately interrupts the cast because your GCD is not yet finished => your animation is interrupted.

So in that 400ms you can spam the ability, and you will tremble like someone with epilepsy, but your spell won't go off. To fix this issue, you must use the spellqueue system. After the next server restart, everyone will be able to use ".spellqueue on/off/info".
on will turn it on, off will disable it, info will tell you if it's on or not.
Just a preview of what does it look like after my fix (you'll see how much smoother the transition is from 1 cast to another with spellqueue)
https://youtube.com/watch?v=9nhup3EVKmg:



IMPORTANT!!! THE BEST RESULT IN 99% OF THE CASES IS JUST TO TURN OFF COMPLETELY SPELL QUEUING (BOTH CLIENT -> by the following macro AND SERVER SIDE -> by .spellqueue off)! Turning on spellqueue is recommended ONLY if you have latency issues. If you don't have, we strongly recommend doing the following...
You can also turn off the client's request to queue spells. This means it will no longer allow that 400ms to try and cast, instead you will have ABSOLUTE control over your scheduling.
In order to do this, you must do the following:
Open your Config.wtf, and add these options
SET MaxSpellStartRecoveryoffset 0
SET ReducedLagTolerance 1

This will disable the queue timer, and you will never experience that glitching again.
If you want to do it via a macro, you can do:
/console MaxSpellStartRecoveryoffset 0
/console ReducedLagTolerance 1

Don't forget: if you decide to turn it on client side, it is very strongly advised to use .spellqueue off

See the result here:
https://youtube.com/watch?v=9H7wh7Ugukk: