**Mastery Loadouts**
Due to issues related to the release of Mastery Loadouts, the "free swap" period will be extended.
The new end date will be May 1st.
Due to issues related to the release of Mastery Loadouts, the "free swap" period will be extended.
The new end date will be May 1st.
Comments
Best way to describe it is that the champion you are controlling is wearing a lead suit and they simple don’t want to move. I need to almost drag my thumb completely from one side of the screen to the other before the champ will think about moving back. Performing this in real time during fights is impossible, I’ve simple gone in to some very easy fights with a good champion and practiced at the side while they try to do damage.
The whole left side of the screen mechanic has completely changed. Dex / parry / simply moving back is now a nightmare.
Edit: I’m on iOS, iPad.
Edit x 2: just noticed Kabam have commented and closed another similar thread and redirected to here. Any chance they can update us here if they have time to comment on threads they’re closing? Thanks.
If you watch the characters response time from your inputs it looks like there’s a delay between touching the screen and the character responding, about a quarter of a second.
Running on IOS.
To notice lag when that happens
Timing is way off
I’m been testing it for the last 15 minutes or so in ROL, using my R3 Emma. iPhone SE.
It feels like the issue is occurring when the opponent is dashing at you. It’s not a consistent issue, the parry won’t always fail. It also doesn’t appear to be a case of mistiming the parry, if that were the case I would expect to do it too early, but every single time it’s failed it’s been a hit to the face.
ESF mentioned it earlier but I think it’s either one of three things or a combination of both
1. The frames between the opponent dashing and actually hitting have been the reduced to the point where there aren’t enough frames for your champion to execute a block. This is the explanation I’m leaning toward since it’s only occurring during my testing on dash attacks
2. An input issue where the time between the parry input being registered and it being executed has increased. However, if this was the case I would expect to see it occurring when parrying a variety of attacks
3. The dash back input command is lasting longer than it was previously on our champ, which is causing parries the parry input to execute later than it should. I don’t think this is the case but knowing that most parries against dashing opponents occur altering dashing back, it’s a possibility. It may also explain some of the inconsistency
All of my theories might be wrong, my only computing knowledge is one year in high school. I should mention that so far this hasn’t affected my regular gameplay, it’s been few and far between for me, which doesn’t seem to be the case for a lot of players
In the mean time while this is being investigated, I would suggest players play very aggressive and don’t attempt to parry dashing opponents. If you can reparry or intercept well they seem unaffected. It sucks, I know.
Thank you for pointing that out—initial reports here and from a few other chats I follow indicated the issue was mainly and iOS one.
But your experience indicates it’s broader than just iOS—I appreciate your clarification.
For all users, I hope they get it fixed before the content drops today. I have no interest trying to learn a new timing for all of the game’s basic movements in the middle of SoP.
At a minimum, some form of concession should be in the works, especially if AW/AQ continue under these circumstances.
Dr. Zola
https://youtu.be/c1tXd5pIhJ8
Unplayable, really.
I certainly won’t be playing anymore until this is fixed. It’s like learning a new game which doesn’t work properly.
Regards
2) Block didn't work, got hit in the face into oblivion.
3) Nope
4) First time, didn't try re-parry.
OH man, wish I had check the forum before burning a dozen of revives cos I was too lazy to start all over.