Analysis of 1.5 s cast problems on Test
by Kaze | 16/10/2007 08:54:59 PROBLEM: New Client-server communication protocol in 2.3 test doesn't allow 1.5 second cast spells to be chained using /stopcasting as on Live, meaning that latency is accumulated for every 1.5 second cast spell. REASON: I'll try to be clear, but I will try to monitor this thread to clarify and discuss. On Test, when I first cast a Flash of Light (1.5s cast), my GCD leads the castbar by a period of time equal to my latency. ~500 ms in my case. On this first cast, I can send a command to the server for my next FoL (Flash of Light) once my GCD is up. Because the GCD leads the castbar for the first cast, this means that my command is sent to the server such that the second FoL starts immediately after the first. However, the second GCD only starts once the second heal has started client side. The GCD no longer leads the castbar. I am unable to start the next heal until the current castbar has finished client side. The result: Every cast of a 1.5 second spell after the second accumulates latency. On Live I can use /stopcasting to prevent all but a small 'window of error' latency build up, essentially making me able to cast as fast as an American. The GCD is the problem. If Blizzard is to implement the client-server spell cast communication currently on test, the GCD must restart when the command for the next spell is sent, not when the server responds and begins the spellcast. This is a huge issue for 1.5 s spellcast classes on Oceanic or equivalent latency. It must be fixed before 2.3 goes live. [ Post edited by Kaze ] In the debate over values, far better that we appeal to our shared humanity rather than encourage behaviours that seek to demonstrate separateness and superiority. |
by Slouken | 17/10/2007 00:58:03 We're looking into this, thanks! |
| by Slouken | 17/10/2007 17:40:46 This is fixed for 2.3 release, thanks! |
| by Slouken | 17/10/2007 18:46:16 Yes, I just verified that it'll be in the test realm update coming next week (not the one coming this week) |
by Slouken | 17/10/2007 18:48:50
Sure. There was code that was starting the cooldown when the cast was started on the server, if the cast was preemptive. We're just removing that code so the start cooldown works normally for preemptive casts. |
News
Spam
Hot: Tharfor comments on trojan alerts on popular database sites
Most Viewed 
Recent Blizzard Announcements
