ETA on broken movement speed, has ZOS even acknowledged it?

AbraXuSeXile · April 2016

ZOS_GinaBruno wrote: »

Yep, we are aware and it's not intended. We're still working on a fix for it, which will likely be included in the next major update.

Rofl i cant believe it, im actually laughing irl

Shader_Shibes · April 2016

ZOS_GinaBruno wrote: »

Yep, we are aware and it's not intended. We're still working on a fix for it, which will likely be included in the next major update.

Dark Brotherhood is when it will be fixed? Really?

515fabfcafa96f5926000091.jpg?w=400

zyk · April 2016

This is why players need to stop defending ZOS. ESO may be a very good game in many ways, but the way this company handles QA, severe bugs and broken functionality is unethical.

@ZOS_MattFiror - you should be ashamed.

Mojmir · April 2016

danielpatrickkeaneub17_ESO wrote: »

[snip]

Complacence, another reason why things don't get fixed

[edited to remove quote]

JadeNaria · April 2016

mb10 wrote: »

Niaver wrote: »

Really? Fixing movement speed for 3 months? Hilarious...

You want them to release a patch for one thing?

Plus havent noticed this at all on pS4 and have friends on xbox who say the same.

[snip]

You're welcome for beta testing ESO for you ppl this long, you're also welcome for all the builds, dungeon, delves, pvp and trials strategies you all watched and copied from us over the years.

[edited to remove quote]

b92303008rwb17_ESO · April 2016

ZOS_GinaBruno wrote: »

Yep, we are aware and it's not intended. We're still working on a fix for it, which will likely be included in the next major update.

Would you please enlighten me on how many people are working on this fix? One or two?

SpAEkus · April 2016

Is this part of the same issue with jumping. We can cliff dive still but we can't jump on or over small rocks?

maboleth · April 2016

Am I right by saying this?

1. You issue the "next major update" with lots and lots of tweaks and fixes + new DLC.
2. You introduce many major bugs that need fixing.
3. You hotfix totally unplayable things rather fast but leave all core and annoying bugs intact.
4. We wait for the "next major update" and hope you will fix old and lingering bugs.
5. We get newly introduced major bugs with the next update - again.

The bug cycle is thus never ending and it means the game can never be polished and fully working as intended.

I'm rather new here, so maybe I'm missing something, but does ZOS issue major patches only when it releases DLC? We need one major patch in-between the DLC cycle.

vyndral13preub18_ESO · April 2016

Maybe it will get the Templar Charge treatment.

Patch notes: Templar charge is fixed!
Players: It still doesnt work.
Zos: oh when we said fixed we meant we had actually made it worse, we will be fixing it in the next major update.

Next patch notes: Templar charge is fixed!
Players: It still doest work.
Zos: Oh when we said fixed we meant we did some stuff that may or may not work, we are working on the true fix for the next major update.

Next patch notes: Templar charge is fixed!
Players: it still doesnt work.
Zos: when we said fixed we meant we had actually wrecked most the charges in the game. we are working on it for the next major update.

This is where Buzz Lightyear runs in and yells to infinity and beyond!

Korah_Eaglecry · April 2016

Ourorboros wrote: »

ZOS_GinaBruno wrote: »

Yep, we are aware and it's not intended. We're still working on a fix for it, which will likely be included in the next major update.

"Next major update" translates to the next DLC release, Dark Brotherhood. Even though this is a major deal for EVERY player, zos is content to let this issue remain until it's convenient for them. Thanks so much. Not only am I noticeably slower, I also don't have my Windrunner CP perk.

This is whats going to eventually drive players away. Theres no way they can keep up with bugs being introduced by the DLCs if theyre only going to address them during the next DLC and maybe one incremental between. Especially since none of the fixes can be confirmed to actually correct the issue on Live since they can only confirm it on their own internal servers. So no matter how many bug fixes they work out between the DLCs. Theyre just spinning their wheels on a lot of issues. This is going to eventually bite them in the *** since the list of bugs will really begin to pile up over the next year or so.

It might seem manageable right now. But theres going to come a point in the development cycle where they cant keep telling themselves that the game can wait til the next DLC. These forums will catch fire like a dry field struck by lightning. Ive seen it happen in other games where the Team either refused to acknowledge the mounting bugs or refused to react to it the way they should have. More focused on pushing out the next shiny to be bought up or the next grindy mechanic that would compound the issues. Only to watch their playerbase dwindle.

It wont kill the game. But theyre going to be facing a stiff decline in player numbers at some point if they keep going this direction and with this business model.

Garldeen · April 2016

No there is money in bug fixes, only in new content (and crown store tat)/ Was always going to happen with the dropping of the sub.

Emma_Overload · April 2016

Before you guys get too mad, consider that the "next major update" might be sooner than you think. Remember how ZOS surprised us with the speed at which they came out with Wrothgar so soon after Imperial City?

sadownik · April 2016

wonkydog wrote: »

No there is money in bug fixes, only in new content (and crown store tat)/ Was always going to happen with the dropping of the sub.

You are very wrong. If bugs will pile up as they are no no new players will stay long enough to leave some money in the game. lets face it buying the game itself right now is very cheap Z. makes money with crown store.

AmakarGranaen · April 2016

ZOS_GinaBruno wrote: »

Yep, we are aware and it's not intended. We're still working on a fix for it, which will likely be included in the next major update.

Bfish22090 · April 2016

Why are we waiting 3 months for a bug fix? This is ridiculous

Lucious90 · April 2016

They fixed the Cake issue pretty fast.....

Why are we waiting 3 months!!! Permaroots and snares, server performance, and more bugs.... The only thing DB patch is going to do is introduce more bugs that make the game unplayable and all we will get are hotfixes that "May or may not work" They need to step outside of their ridiculous patching system and introduce a big patch that addresses a lot of issues. I wouldnt even care if it was 4 gb or more. If they dropped a slue of actual productive fixes I would be happy

runagate · April 2016

This needs to be fixed immediately before anything else is addressed. It's horrendous.

Elsonso · April 2016

Ourorboros wrote: »

ZOS_GinaBruno wrote: »

Yep, we are aware and it's not intended. We're still working on a fix for it, which will likely be included in the next major update.

"Next major update" translates to the next DLC release, Dark Brotherhood. Even though this is a major deal for EVERY player, zos is content to let this issue remain until it's convenient for them. Thanks so much. Not only am I noticeably slower, I also don't have my Windrunner CP perk.

Uh, is it really a "major deal for EVERY player?"

No.

Now, I can't say they should not get right on it. They should get right on all the bugs. However, we are rapidly approaching the point where only the most critical bugs are being pushed out in incremental patches. Dark Brotherhood is right around the corner, and already we see that upcoming bugs are being deferred to that. Dark Brotherhood will probably be on PTS in the next 3 weeks, or so.

themdogesbite · April 2016

NEXT MAJOR UPDATE

Some_Guy · April 2016

Notice how none of the devs are commenting on this anymore...?

nimander99 · April 2016

If you change you F.O.V you can make it seem like you are moving at normal speed until this is fixed...

DaveMoeDee · April 2016

Lucious90 wrote: »

They fixed the Cake issue pretty fast.....

Why are we waiting 3 months!!! Permaroots and snares, server performance, and more bugs.... The only thing DB patch is going to do is introduce more bugs that make the game unplayable and all we will get are hotfixes that "May or may not work" They need to step outside of their ridiculous patching system and introduce a big patch that addresses a lot of issues. I wouldnt even care if it was 4 gb or more. If they dropped a slue of actual productive fixes I would be happy

The root and snare issues seem a lot more complicated than running speed. Server performance is extremely difficult. In general, most things misbehaving in Cyrodiil is likely complex and due to a combination of code, configuration, and hardware. Running speed seems like is should just be a constant somewhere in the code.

Iyas · April 2016

Wait until it's a feature and not a bug anymore.
A typical zos

Elsonso · April 2016

Some_Guy wrote: »

Notice how none of the devs are commenting on this anymore...?

You do realize that this is because they have said what they intend to say, right? They are still working on it and that the fix will likely be in the next major update. I am fairly certain that nothing that has been said in here really changes that answer. All we would get is the same answer, maybe with different words. The comment from Gina was an announcement, not an invite to an active discussion.

I can't say I agree with the "drive by" announcements, but that is the way they do it. Looking on the bright side, at least they made the announcement.

KanedaSyndrome · April 2016

Guess ESO runs on spaghetti code? If a dev changes something in one function/class, he should be able to anticipate the effects throughout the system. Would I be wrong in assuming that there's a manifest that descripes all contact points of each function/class?

The fact that a reduction to major expedition can become a bug that nerfs all movement speed baffles me. I'd love to see the ESO code lol.

Brightxdawn · April 2016

game going down the pooper

vyndral13preub18_ESO · April 2016

KanedaSyndrome wrote: »

Guess ESO runs on spaghetti code? If a dev changes something in one function/class, he should be able to anticipate the effects throughout the system. Would I be wrong in assuming that there's a manifest that descripes all contact points of each function/class?

The fact that a reduction to major expidition can become a bug that nerfs all movement speed baffles me. I'd love to see the ESO code lol.

You could see it. But you wouldnt understand it. Since it seems no one does.

Conquistador · April 2016

ZOS_GinaBruno wrote: »

Yep, we are aware and it's not intended. We're still working on a fix for it, which will likely be included in the next major update.

My question is why does it take a major update for something like this to be fixed? Why are there no small incremental updates that fix these kinds of things? The people at WoW used to fix things like this fast and that game is YEARS OLD.

Pomaikai · April 2016

mb10 wrote: »

Niaver wrote: »

Really? Fixing movement speed for 3 months? Hilarious...

You want them to release a patch for one thing?

Plus havent noticed this at all on pS4 and have friends on xbox who say the same.

[snip]

Yes. Yes we do. That's why they're called PATCHES!

PS... We are righteously ticked off at ZOS the company, and not Gina the messenger. Not one person attacked Gina personally in this thread. People need to learn and understand the difference.

/Start general rant over the state of CS these days.

And, while it has not occurred in anything posted in this thread, employees need to learn the same thing. We as consumers can be hopping mad at the company they work for, but it doesn't mean we're mad at THEM as an individual. Taking that anger personally is a choice they themselves make, and it's a poor one at that.

/End general rant over the state of CS these days.

[edited to remove quote]

L2Pissue · April 2016

ZOS will u fix the bugs that will be included in the next major patch, or we need to wait for the next major patch for it so you can have other bugs in it?