I concurZOS_JessicaFolsom wrote: »Slayyer-AUS wrote: »@ZOS_JessicaFolsom Thank you will there be an eta?
Not yet, no, and it wouldn't be fair to you all to speculate. We're still working on it.
Communication is the important thing.
Thanks for the update.
khele23eb17_ESO wrote: »khele23eb17_ESO wrote: »Last night stam nb daggers weave ran new quests plus explore.
Mag blade ran dailies with staff weave.
Mag temp inferno dailies with staff weave.
Have gotten used to new sequencing and things apoear to be fine. If anything content fights go quicker tho might be other reasons.
Definitely not anywhere near "my magicka nb is unusable right now" level of problems.
Ymmv and not sauing there arent issues but it serms like some may be managed by adapting to new sequences instead of hoping they go back to what was favored.
I dont think this is ALL BUG.
You know whats not a bug... when I do a sequence of button presses 3 times and get the same effect all 3 times. If I execute the same sequence of attacks 3 times and the character does it perfectly on the first one, misses an attack on the second one and gets an apoplectic fit on the 3rd one... it certainly isnt working right.
That sounds like a reasonable definition of not a bug and also of not working right.
For me though i am not sering those things since altering my seq/timing?
I can avoid problems connected with my car suddenly stopping at random times by taking the bus. Doesnt make my car any less broken.
khele23eb17_ESO wrote: »khele23eb17_ESO wrote: »Last night stam nb daggers weave ran new quests plus explore.
Mag blade ran dailies with staff weave.
Mag temp inferno dailies with staff weave.
Have gotten used to new sequencing and things apoear to be fine. If anything content fights go quicker tho might be other reasons.
Definitely not anywhere near "my magicka nb is unusable right now" level of problems.
Ymmv and not sauing there arent issues but it serms like some may be managed by adapting to new sequences instead of hoping they go back to what was favored.
I dont think this is ALL BUG.
You know whats not a bug... when I do a sequence of button presses 3 times and get the same effect all 3 times. If I execute the same sequence of attacks 3 times and the character does it perfectly on the first one, misses an attack on the second one and gets an apoplectic fit on the 3rd one... it certainly isnt working right.
That sounds like a reasonable definition of not a bug and also of not working right.
For me though i am not sering those things since altering my seq/timing?
I can avoid problems connected with my car suddenly stopping at random times by taking the bus. Doesnt make my car any less broken.
But, first, i sm not taking the bus. Just hitting a signal ealier. Slso, my car idnt suddenly stopping.
Also, this is an MMO with a major patch aimed at combat changes. Do coming at this from a perspective of "should be working just like it did before" is unfathomable, to me at least.
Ymmv.
They said it was a bug though. And you also said it was fine on the first post too before I posted videos.Last night stam nb daggers weave ran new quests plus explore.
Mag blade ran dailies with staff weave.
Mag temp inferno dailies with staff weave.
Have gotten used to new sequencing and things apoear to be fine. If anything content fights go quicker tho might be other reasons.
Definitely not anywhere near "my magicka nb is unusable right now" level of problems.
Ymmv and not sauing there arent issues but it serms like some may be managed by adapting to new sequences instead of hoping they go back to what was favored.
I dont think this is ALL BUG.
It's clearly not fine.
@ZOS_JessicaFolsom
What about movement speed? We're still stupidly slow compared to pre thieves guild. Any chance that is going to get fixed?
Gilliamtherogue wrote: »@ZOS_JessicaFolsom
What about movement speed? We're still stupidly slow compared to pre thieves guild. Any chance that is going to get fixed?
What instances are you referring to? Mind doing a side to side of pre TG update and post DBH update to show? The momentum loss has finally been fixed with jumping, and move speed seems on par.
Gilliamtherogue wrote: »@ZOS_JessicaFolsom
What about movement speed? We're still stupidly slow compared to pre thieves guild. Any chance that is going to get fixed?
What instances are you referring to? Mind doing a side to side of pre TG update and post DBH update to show? The momentum loss has finally been fixed with jumping, and move speed seems on par.
I believe they said they're still working on it. I switched over to my Imperial that I hadn't played in a while and noticed right away his 'run' speed (not sprint) is noticeably slower than it used to be. And yes, even though I haven't played the character in a while, having spent weeks playing the character I do remember his previous run speed compared to now.
Gilliamtherogue wrote: »@ZOS_JessicaFolsom
What about movement speed? We're still stupidly slow compared to pre thieves guild. Any chance that is going to get fixed?
What instances are you referring to? Mind doing a side to side of pre TG update and post DBH update to show? The momentum loss has finally been fixed with jumping, and move speed seems on par.
ZOS_JessicaFolsom wrote: »Slayyer-AUS wrote: »@ZOS_JessicaFolsom Thank you will there be an eta?
Not yet, no, and it wouldn't be fair to you all to speculate. We're still working on it.
Well for the time being I cancelled my sub until this game feels playable again, like I said before...we all gave feedback during pts saying it was horrible and it still went live. I encourage others to do the same because this is really un acceptable.ZOS_JessicaFolsom wrote: »Slayyer-AUS wrote: »@ZOS_JessicaFolsom Thank you will there be an eta?
Not yet, no, and it wouldn't be fair to you all to speculate. We're still working on it.
relax people, it will probably be fixed by the next DLC patch
khele23eb17_ESO wrote: »So... new patch and still nothing. Not even an acknowledgement the issue existsIs this being looked at or was it decided to aggressively ignore the issue until we stop asking you about it.
Judas Helviaryn wrote: »khele23eb17_ESO wrote: »So... new patch and still nothing. Not even an acknowledgement the issue existsIs this being looked at or was it decided to aggressively ignore the issue until we stop asking you about it.
The issue has been acknowledged by ZOS all over this thread. I'm just glad they said it wasn't intentional, that means a fix IS coming. Try reading.
khele23eb17_ESO wrote: »Judas Helviaryn wrote: »khele23eb17_ESO wrote: »So... new patch and still nothing. Not even an acknowledgement the issue existsIs this being looked at or was it decided to aggressively ignore the issue until we stop asking you about it.
The issue has been acknowledged by ZOS all over this thread. I'm just glad they said it wasn't intentional, that means a fix IS coming. Try reading.
Id would love to see the acknowledgement in the 'known issues' section of the patch notes tho. Yes, I might be jaded and cynical but I have seen things go from 'were working on it' to 'this is now a feature' in the past.
I think it'll most likely be the next major update, it's a big change that I doubt could make it into a small patch. But that's better than nothingkhele23eb17_ESO wrote: »Any news on this?
I think it'll most likely be the next major update, it's a big change that I doubt could make it into a small patch. But that's better than nothingkhele23eb17_ESO wrote: »Any news on this?