It's possible that these high-demand activities were affected more as a result of the overloading, though.
It's hard to speculate at the moment. I guess we'll find out when Battle.net is fixed.
Didn't people play custom maps over bnet using the Lost Temple patcher? Wasn't the latency fine then? Isn't that already an indicator that patch 13 introduced something new that causes the SAME maps that worked fine before with multiple players to now lag?
So basically it's pointless to have any sort of WASD controls, not even in 1-player maps because those are also online.
Gee. Thanks for that Ghost demo, Blizzard.
Didn't people play custom maps over bnet using the Lost Temple patcher? Wasn't the latency fine then? Isn't that already an indicator that patch 13 introduced something new that causes the SAME maps that worked fine before with multiple players to now lag?
No, because the frequency of those games was low compared to once custom games launched, everyone tried them. In fact, there was a rush of people onto Battle.net.
Also custom maps don't lag now, too. At least most of them don't.
We'll see how patch 14 (or whatever comes next fares), but until then I'll continue working on single-player WASD maps D:
Oookay. But that still says that the maps havent changed, its just that Bnet has gotten laggier at handling their requests and that the map functions, whilst contributing slightly to latency, would not be a problem if Bnet hadn't taken a turn for the worse.
Oookay. But that still says that the maps havent changed, its just that Bnet has gotten laggier at handling their requests and that the map functions, whilst contributing slightly to latency, would not be a problem if Bnet hadn't taken a turn for the worse.
Give them time to fix these things. It's a beta for a reason. If this were after release, I'd be upset, but it's not. It's a beta, and these things are bound to happen. People seem to forget that, and think it's a free trial.
? You seem to have gotten the idea that I'm impatient or even frustrated with Bnet. I'm not, as I've played games with far inferior support in the past, and I think that Blizzard is still leagues ahead of other developers.
I'm only saying that the problem with the lag lies with new bnet patch, and that since the problem is bnet and not the maps, said maps shouldn't need to alter their code to compensate. If your map ran without lag even in multiplayer with the Lost Temple patch, then it should be reasonably expected that the map should run just as well when publishing is reimplemented.
Just (finally) managed to test it. WASD is not viable. There's a 0.5-1 second delay, all the time. This isn't lag because the game runs totally smooth; it just waits that long to process your input.
Blizzard = liars.
In my testing what you just said is generally false. I've had a few Battle.net games where my WASD movement system ran exceptionally.
I've had the same results as BrotherLaz with my WASD. So either the servers have their downs and ups (which might be possible given BNet's state right now) or your system is doing something fundamental different than ours.
Well this is nothing new, this is why even in WC3 Keyboard(Arrow-key) movement fails. Theres a .3-.5 second delay from when you press a key to when the game detects it. Of course in single player it works 100%
But anyways, I would expect it to improve come release date
I use my own, as of yet unreleased system. Basically movement is updated on a separate thread, but movement can begin or be stopped outside of that thread w/o any wait at all.
Yes, so that's exactly what everyone else is doing: triggers for pressing a key and for releasing a key. :P
Yes, but the actual movement events themselves are done differently. I never said my specific implementation magically avoided lag. I only said I had a few moments of "clarity" where Battle.net ran my system extremely smoothly and without issue.
Yea, I'm updating my movement seperately too. Also that wouldn't have anything to do with with the delay.
So you probably just had a lucky day - or you're a Blizzard employee with premium connection to BNet o_0
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
@s3rius: Go
It's possible that these high-demand activities were affected more as a result of the overloading, though.
It's hard to speculate at the moment. I guess we'll find out when Battle.net is fixed.
Didn't people play custom maps over bnet using the Lost Temple patcher? Wasn't the latency fine then? Isn't that already an indicator that patch 13 introduced something new that causes the SAME maps that worked fine before with multiple players to now lag?
So basically it's pointless to have any sort of WASD controls, not even in 1-player maps because those are also online. Gee. Thanks for that Ghost demo, Blizzard.
No, because the frequency of those games was low compared to once custom games launched, everyone tried them. In fact, there was a rush of people onto Battle.net.
Also custom maps don't lag now, too. At least most of them don't.
We'll see how patch 14 (or whatever comes next fares), but until then I'll continue working on single-player WASD maps D:
@MotiveMe: Go
Oookay. But that still says that the maps havent changed, its just that Bnet has gotten laggier at handling their requests and that the map functions, whilst contributing slightly to latency, would not be a problem if Bnet hadn't taken a turn for the worse.
Give them time to fix these things. It's a beta for a reason. If this were after release, I'd be upset, but it's not. It's a beta, and these things are bound to happen. People seem to forget that, and think it's a free trial.
? You seem to have gotten the idea that I'm impatient or even frustrated with Bnet. I'm not, as I've played games with far inferior support in the past, and I think that Blizzard is still leagues ahead of other developers.
I'm only saying that the problem with the lag lies with new bnet patch, and that since the problem is bnet and not the maps, said maps shouldn't need to alter their code to compensate. If your map ran without lag even in multiplayer with the Lost Temple patch, then it should be reasonably expected that the map should run just as well when publishing is reimplemented.
@Centagon: Go
I wasn't referring to you, I used "people" in a general sense. Sorry. :P
Just (finally) managed to test it. WASD is not viable. There's a 0.5-1 second delay, all the time. This isn't lag because the game runs totally smooth; it just waits that long to process your input. Blizzard = liars.
@BrotherLaz: Go
In my testing what you just said is generally false. I've had a few Battle.net games where my WASD movement system ran exceptionally.
I've had the same results as BrotherLaz with my WASD. So either the servers have their downs and ups (which might be possible given BNet's state right now) or your system is doing something fundamental different than ours.
In which case I'd like to know it. Motive...?
Well this is nothing new, this is why even in WC3 Keyboard(Arrow-key) movement fails. Theres a .3-.5 second delay from when you press a key to when the game detects it. Of course in single player it works 100%
But anyways, I would expect it to improve come release date
I use my own, as of yet unreleased system. Basically movement is updated on a separate thread, but movement can begin or be stopped outside of that thread w/o any wait at all.
Yes, so that's exactly what everyone else is doing: triggers for pressing a key and for releasing a key. :P
Yes, but the actual movement events themselves are done differently. I never said my specific implementation magically avoided lag. I only said I had a few moments of "clarity" where Battle.net ran my system extremely smoothly and without issue.
Yea, I'm updating my movement seperately too. Also that wouldn't have anything to do with with the delay.
So you probably just had a lucky day - or you're a Blizzard employee with premium connection to BNet o_0