Intermittent issue when using Dual Wield

DeathStalker_X

I have been experiencing the occasion issue when using Dual Wield - after a fight I can no longer interact with anything - I switch weapons to bakbar and everything is fine, and when I switch back everything is fine. I may post this issue under BUGS if others are experiencing it.

StormeReigns

DeathStalker_X wrote: »

I have been experiencing the occasion issue when using Dual Wield - after a fight I can no longer interact with anything - I switch weapons to bakbar and everything is fine, and when I switch back everything is fine. I may post this issue under BUGS if others are experiencing it.

It's an on going issue (often cleared by swapping or a rando heavy attack) happens to me on Bows and 2H as well DW

BrokenGameMechanics

As others have said it is not just DW. They pretty much broke basic combat across the board. Historically the forums would be up in arms about this but we are now deep into ZOS fatigue. "Oh the broke basic combat. Ah well ..." People just don't even try any more.

The situation is far worse depending on the skill animation. So Warden's (magica especially) which as a core design principle of the class was to beclunky and sloooow with heavy long animations are almost impossible to play in PVP. Everything either hangs or cancels in mid-cast. It takes 2 or 3 attempts to raise the bear. You can't weave with birds, it double clutches or hangs in mid-throw. Winters revenge literally just stops working. You push the button, you see the icon depress and nothing happens. It will stay broken like that until you weapons swap or try other skills. It will start working again for a bit and then hang again. Like Bird's, Budding Seeds will hang mid-toss, and trying to early activate takes several attempts. I don't even try and more as it will just hang.

I've literally struggled to fine what I can slot that even partially works for my style of play. My Ice Mage is pretty much DOA for PVP. A bread and butter skill sequence for me is Winter's Rev, Blockade of Frost, layer on top Budding Seeds in N vs N combat. It is literally impossible to cast those skills in a row with a single button press for each. They constantly fail mid-animation (assuming like with Winter's Revenge) they are working at all.

For a Sorc with short, fast simple animations things are probably not too bad. So I guess your mileage will vary with the build, class.

GIven ALL multitude of broken fundamental, basic game mechanics that sill persist in this game after years to address them, I just cannot fathom that the Combat Design team sat down and said, "yep the #1 priority is ... (wait for it) ... block canceling". Really REALLY Yep, basic game was broken to another low point but its all good the as the new levels of brokeness were well worth trading for the highly desired by the community block canceling.

DeathStalker_X

I didn't realize it was THAT bad. That seriously sucks. One wonder HOW it could even get through QA/UAT. Oh, that's right, WE'RE their QA/UAT! ZOS should SERIOUSLY start to realize just how much they SUCK at programming. While I'm not a programmer, I am a scrum master, do development, and UAT. This stuff would NEVER get by. And there's no excuse like, oh, they can't test everything - BULL! Yes they bloody well can! This CLEARLY is not a hardware/driver issue, it's an issue with their PROGRAMMING.

I've said it before and I'll say it again - their programmers and product owners are LAZY. I wonder if their product owners even KNOW what they're supposed to be doing. Probably not - they probably don't even have any! But if they'd ever have that B****S, I'd certainly be wiling to discuss the issues on HOW they are doing things with ANY of them.

They have the information on how to contact me, but we all KNOW they won't.

StormeReigns

DeathStalker_X wrote: »

I didn't realize it was THAT bad. That seriously sucks. One wonder HOW it could even get through QA/UAT. Oh, that's right, WE'RE their QA/UAT! ZOS should SERIOUSLY start to realize just how much they SUCK at programming. While I'm not a programmer, I am a scrum master, do development, and UAT. This stuff would NEVER get by. And there's no excuse like, oh, they can't test everything - BULL! Yes they bloody well can! This CLEARLY is not a hardware/driver issue, it's an issue with their PROGRAMMING.

I've said it before and I'll say it again - their programmers and product owners are LAZY. I wonder if their product owners even KNOW what they're supposed to be doing. Probably not - they probably don't even have any! But if they'd ever have that B****S, I'd certainly be wiling to discuss the issues on HOW they are doing things with ANY of them.

They have the information on how to contact me, but we all KNOW they won't.

It's not really that they are lazy. Nor that they don't want to. It is all based on level of priority from the biggest of big wigs.

Taking from my oh so "joyous" experiences as a lowly key studio artist at Supercell San Fran. Studios and IGT (Vegas)... and endless hours, days months to 5 years always passing by the dev offices daily, poor devs. Who we see on streams are the pretty Faces and Smiles on the streams, the ones who will spoon feed us the shiny and the good - the ones taking praise for all the good things that happen, nearly pitch perfect scripture with occasional silly little blunders placed in to provide the "Oh, they are just like us! LOL!" appearances and feeling.

While the real devs. The Faceless Ones as I like to call them; are stuck behind the scenes, being whipped, beaten and hammered to push, push, push the next shiny and if time is given to fix something on that list of issues - but, only approved ones. Always doing someone else's laundry list - never their own. Heads down, pencils up environment, don't speak up or out of place unless it is truly critical.

The real Devs. The faceless ones. Probably, if not almost always want to address the growing issues. Although, Strict dead lines, harsh work hours, and a even harsher, brutal work place makes said things happen in a timely manner - especially, when the looming eyes of department heads and share holders begin to creep in closer and closer.

Seen and heard plenty from my past and with friends slowly retiring from the industry:

"Oh, you want to focus some time on this issue? Great. We'll just have everyone else pick up your slack, and work longer hours to meet dead lines, so sure, by-all-means go on and take this issue as priority." - Normally said by Senior or lead Dev. in front of the entire staff with department manager / director standing by to ensure that an example was made. (Sure, ZoS could be run vastly different from other studios, large or small; or the exact same - just what I seen during that 5 year hell.)

If you want the issue to be addressed, tackle and flood them on all fronts. Don't spam, but gather more attention so more will post about it on the Main Forum, Reddit and Social Media. Grow the attention to it so the higher ups are forced to acknowledge it so time and resources are used to get timely fixes, not whenever a new dlc/chapter happens (and that's if we are lucky to get the critical issues addressed.)

DeathStalker_X

Actually, it's the Product Owner/s who determine what they want, and the priority of EVERYTHING. Believe me, I know - I'm certified in Agile & Scrum. What they have is suck @$$ Product Owners who don't know jack squat except to meet the EXECS' deadlines, programmers be damned. There is, 100% absolutely LAZY coding in this game - but the issue with that is that the Product Owners ALLOWED that! Programmers have NO SAY in anything, except how much work the estimate they can get done in each sprint. This is (part of) what I do for a living - and I have worked both sides, as a dev and as a PO. If you don't know what you're doing, on either side, or you're just lousy/lazy at it, then your end result will ALWAYS be substandard. That is a simple FACT. There ARE occasions where a great dev can overcome a bad PO, but not the other way around.

But honestly, EVERY software development is run Agile/Scrum - every single one of them. How WELL those scrum sessions & sprints are run, is a different matter entirely.

(and yeah, I can tell you EVERY details about running an Agile project with Scrum, and probably every way it can go sideways).

DeathStalker_X

Ok, I reposted things below in case the 1st one gets deleted because I used the "at" sign with $$, just in case it gets auto -deleted for thinking I named someone (which obviously I didn't, lol)

Actually, it's the Product Owner/s who determine what they want, and the priority of EVERYTHING. Believe me, I know - I'm certified in Agile & Scrum. What they have is suck a$$ Product Owners who don't know jack squat except to meet the EXECS' deadlines, programmers be damned. There is, 100% absolutely LAZY coding in this game - but the issue with that is that the Product Owners ALLOWED that! Programmers have NO SAY in anything, except how much work the estimate they can get done in each sprint. This is (part of) what I do for a living - and I have worked both sides, as a dev and as a PO. If you don't know what you're doing, on either side, or you're just lousy/lazy at it, then your end result will ALWAYS be substandard. That is a simple FACT. There ARE occasions where a great dev can overcome a bad PO, but not the other way around.

But honestly, EVERY software development is run Agile/Scrum - every single one of them. How WELL those scrum sessions & sprints are run, is a different matter entirely.

(and yeah, I can tell you EVERY details about running an Agile project with Scrum, and probably every way it can go sideways).

indigorune

yep it's been happening to me lately too. i have only noticed it on my stamblade. if i cast leeching strikes or relentless focus, i can interact with stuff again usually. it's annoying.

ShawnLaRock

Not sure if connected to the same dual-wield issue (I normally run mace / axe) - but I can’t access the nodes in this form, OR if I switch bars to Bow.

But - if I re-slot mace / shield... I can access the node, but I can’t see the mace or shield! Lol.

Brrrrroken.

S.

Kadoin

At least it didn't happen to you as tank in the middle of boss fight in your first trial HM trial attempt and you were doing good until the end...You would not want the aggro from your team members, it sucks. Don't ask me how I know...