Diablo III Hotfixes for August 3rd - Rubberbanding
Blizzard has just posted a list of hotfixes for August 3rd. It looks like they are attempting to work on the "rubberbanding" issue a lot of users experience.
Fixed several cases of "rubberbanding" that could sometimes occur while playing under extremely high latency, when a character changed direction or movement speed, or when a character used certain movement-based abilities (like Tempest Rush or Whirlwind)
I seriously belive that. Look at the AH stuff the just talked about and now the rubberbanding. Everything after Kripps vid.
Coincidence? I really do not think so.
It is... They have bee wanting to add those things/ been working on them well before the video =)
I seriously belive that. Look at the AH stuff the just talked about and now the rubberbanding. Everything after Kripps vid.
Coincidence? I really do not think so.
Seriously doubt they even watch or read anything Kripp does. They have their own agenda, as previously mentioned. In the end, all Blizzard cares about is keeping gameplay numbers up so people keep spending money in the RMAH. Should be self-evident in the fact that the first major update to the game was getting the RMAH working--not fixing botters, spammers, or exploiters; OR fixing end-game inferno grinding. The rubberbanding has been a serious issue for a Monk friend of mine, and also a very bad issue for my wizard, who has literally rubberbanded halfway across a zone after teleporting.
Seriously doubt they even watch or read anything Kripp does. They have their own agenda, as previously mentioned. In the end, all Blizzard cares about is keeping gameplay numbers up so people keep spending money in the RMAH. Should be self-evident in the fact that the first major update to the game was getting the RMAH working--not fixing botters, spammers, or exploiters; OR fixing end-game inferno grinding. The rubberbanding has been a serious issue for a Monk friend of mine, and also a very bad issue for my wizard, who has literally rubberbanded halfway across a zone after teleporting.
I think you are wrong about that. Popular streamers as Kripp make a huge impact on the community's opinion so Blizzard has to keep an eye on what they are saying. When Kripp posted the "Jay Wilson exploit" video about the 1 month old exploit Blizzard fixed it instantly.
I can imagine that the rubberbanding optimization has been made because of Kripp's video. The AH improvements are surely under development for some time, but they posted the details now because they had to react to minimize the damage, to let people know that they are fixing the problems Kripp mentioned.
none of this has anything to do with his video. They cant make a hotfix that fixes such a key issue that fast.
Rubberbanding has been on their list for a while. They have been actively attempting to fix it for some time.
edit: however to the other comment. Blizzard does watch his videos, we even have a blue post on it from awhile back =P
in Eu servers rubberbanding occurs often, still not fixed (tempest rush monk), my average latency is 50-60. The servers are overpopulated there is no latency issue in my opinon, blizz's servers can't handle this amount of data I/O and creates packet losses which leads to rubberbanding.
the hotfix hasnt been added to the EU yet according to Lylirra
I seriously belive that. Look at the AH stuff the just talked about and now the rubberbanding. Everything after Kripps vid.
Coincidence? I really do not think so.
It is... They have bee wanting to add those things/ been working on them well before the video =)
This^
I just logged in just to say that, Kripp's good but this is something that has been in the works.
Hopefully this will resolve a good deal of the rubber banding that happens. Hopefully.
Me too.. but they said rubber banding for high latency.. not rubber banding for awesome connections :/
Fixed several cases of "rubberbanding" that could sometimes occur while playing under extremely high latency, when a character changed direction or movement speed, or when a character used certain movement-based abilities (like Tempest Rush or Whirlwind)
This is what I see:
Fixed cases of rubberbanding when:
playing under extremely high latency
when a character changed direction or movement speed
when a character used certain movement-based abilities
I seriously belive that. Look at the AH stuff the just talked about and now the rubberbanding. Everything after Kripps vid.
Coincidence? I really do not think so.
He just so happened to mention things that were obviously needed... very obvious.
I seriously belive that. Look at the AH stuff the just talked about and now the rubberbanding. Everything after Kripps vid.
Coincidence? I really do not think so.
He just so happened to mention things that were obviously needed... very obvious.
Exactly. People were posting about that stuff during the first week.
I seriously belive that. Look at the AH stuff the just talked about and now the rubberbanding. Everything after Kripps vid.
Coincidence? I really do not think so.
It is... They have bee wanting to add those things/ been working on them well before the video =)
Yeah they have been working on it long before Krips, even tho his video is very good...Its been in the works long before. People need to relax with Krip shit and relize he is only another player to Blizz. No offense Krip! a good one at that too.
in Eu servers rubberbanding occurs often, still not fixed (tempest rush monk), my average latency is 50-60. The servers are overpopulated there is no latency issue in my opinon, blizz's servers can't handle this amount of data I/O and creates packet losses which leads to rubberbanding.
That's what I thought when I read that... "did they...?"
Besides, the servers are in no way overpopulated at this point. Most of players abandoned the game or was banned for botting. I uninstalled the game even.
What's ruining the movement of characters is the excessive use of bandwidth and processing of the Auction House. Too much useless searches because of the limit of 3 characteristics, and it's programmed as higher priority than the game, as showed when they had to take down the AH on US servers to allow people to play under 400ms.
Some of these statements really show just how ignorant people are about programming. It's pretty simple ... there is one big list ... everything goes on the list. The list gets is categorized by "group" (graphics, engine, logic, etc). Time estimates (guesses) are attached to each item. A "Severity" type flag is place on each item (how badly does it affect the game and how many users does it affect negatively). Finally they come up with some sort of "value" number and that determines the order in which things happen.
Public opinion might move one of the data points slightly, but doesn't send Blizzard into a tail spin in the list.
Even if it did, once a bug gets assigned to a team, the work has to begin. I can't guess how many man hours the problem took to solve, or how many real days it took cause I don't know the man hours or the size of the team that worked on it. Even then, it's got to go through internal developer testing, then has to be turned over to the QA guys to test (which could be days of testing) ... then the code has to be merged into patch payload and deployed to a test cluster and re-tested to make sure the merge didn't break anything before it can be deployed live.
That process didn't start, and consequently complete, due to that video. Guaranteed.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Blizzard has just posted a list of hotfixes for August 3rd. It looks like they are attempting to work on the "rubberbanding" issue a lot of users experience.
Originally Posted by Blizzard (Blue Tracker / Official Forums)
Bug Fixes
Smoke Screen, Run, Smoke Screen, *Rubber Band*, Run, Smoke Screen, *Kicked from game*
And may the odds be ever in your favour.
Emmo#2406
It is... They have bee wanting to add those things/ been working on them well before the video =)
waiting for multiplayer incentives to confim.
It's called Return of Jediablo. Turns out Leah has a twin bother Luke, who Adria was raising.
Me too.. but they said rubber banding for high latency.. not rubber banding for awesome connections :/
none of this has anything to do with his video. They cant make a hotfix that fixes such a key issue that fast.
Rubberbanding has been on their list for a while. They have been actively attempting to fix it for some time.
edit: however to the other comment. Blizzard does watch his videos, we even have a blue post on it from awhile back =P
the hotfix hasnt been added to the EU yet according to Lylirra
Blizzard has linked a video of Kripp clearing inferno. I think it was the budget barb build.
This^
I just logged in just to say that, Kripp's good but this is something that has been in the works.
This is what I see:
Fixed cases of rubberbanding when:
He just so happened to mention things that were obviously needed... very obvious.
Exactly. People were posting about that stuff during the first week.
Yeah they have been working on it long before Krips, even tho his video is very good...Its been in the works long before. People need to relax with Krip shit and relize he is only another player to Blizz. No offense Krip! a good one at that too.
Besides, the servers are in no way overpopulated at this point. Most of players abandoned the game or was banned for botting. I uninstalled the game even.
What's ruining the movement of characters is the excessive use of bandwidth and processing of the Auction House. Too much useless searches because of the limit of 3 characteristics, and it's programmed as higher priority than the game, as showed when they had to take down the AH on US servers to allow people to play under 400ms.
Some of these statements really show just how ignorant people are about programming. It's pretty simple ... there is one big list ... everything goes on the list. The list gets is categorized by "group" (graphics, engine, logic, etc). Time estimates (guesses) are attached to each item. A "Severity" type flag is place on each item (how badly does it affect the game and how many users does it affect negatively). Finally they come up with some sort of "value" number and that determines the order in which things happen.
Public opinion might move one of the data points slightly, but doesn't send Blizzard into a tail spin in the list.
Even if it did, once a bug gets assigned to a team, the work has to begin. I can't guess how many man hours the problem took to solve, or how many real days it took cause I don't know the man hours or the size of the team that worked on it. Even then, it's got to go through internal developer testing, then has to be turned over to the QA guys to test (which could be days of testing) ... then the code has to be merged into patch payload and deployed to a test cluster and re-tested to make sure the merge didn't break anything before it can be deployed live.
That process didn't start, and consequently complete, due to that video. Guaranteed.