Is parry still being investigated as a performance issue? [Under Investigation]
_noyes
Member Posts: 51 ★
I'm playing on an iPhone 6S with the latest iOS and game version, and I'm still experience a lack of triggering parry frequently. It most commonly happens in AQ and AW. Usually when parry fails to trigger, the game gets a bit laggy and sluggish. Definitely noticing a drop in FPS. So I imagine this dates back to issue on the previous forum when 12.0 was released and it was mentioned that parry wasn't working correctly due to a performance issue, but perhaps that was already addressed. Is there any other info on this? Thanks!
Post edited by Kabam Wolf on
5
Comments
These AI champs are boosted up to make it harder as designed. We shouldn't be fighting the controls too.
It's like we're fighting the Patriots with the referees paid off. How are we supposed to beat that?
Sign Eli Manning obviously.
Separate Issue: in AW and arenas, it's ridiculous that the AI can parry when dashing backwards. Make it available for the player, or take it away from the AI.
The lag and freezing that are still here makes this all much worse. Last night's freezing and lagging was terrible. You are clearly having issues with your servers, given all the "emergency maintenance" this last week. So you're working on it. But what other games have to deal with these kinds of outages and poor performance? I would guess not many. This has been a known issue for a very long time.
Please update the community with what you're doing about this and acknowledge the parry issues.
What happened?
We can be patient and understanding, but ignoring the community is gonna fuel anger to the people who give you money every day.
The new update is very buggy indeed and force us to use resources that we don't have. So, please help us, reassure us. Tell us whats going on
What happened? You get hit with an infraction when you remind them they are not being transparent as promised...
I'm still looking for an update to the issue and have been since 12.0. This was addressed in the 12.0 known bugs as performance issue, then it was silently dropped and not brought up in bug fixes since then. Perhaps some aren't experiencing it, but it sounds like a lot still are. Why is it taking so long to address this issue?
I think it is all these complex mechanics they keep adding to champs with multiple moving parts (like doc oc's breakthroughs). These are all equations the cpu is having to crunch with sloppy coding (as stated in the first 12.0 boycott letter where it was mentioned that the coding was haphazardly written). Despair doesn't even account for 15% HP gain for recovery (which I made a post about 2 months ago with absolutely no response). It seems Kabam comes up with ideas, but doesn't properly test all aspects how it works with the current mechanics.
They simply push content at the sake of quality.
My guess it's due to memory leaks.
Those problems are cumulative. No matter the content no matter the champs, but I've noticed it's hard once you faced champs with sparkles/fire/particles effects and/or you play in the Ultron stage and/or you chance between game arenas (for example you're playing AW then switch to Arenas you'll have Arenas stuttering as hell).
But overall being able to parry works as normal for me
I'm still having some problems with touches not registering or registering late, there's a really clear problem with some champs not dashing back following combos ending on light hits, but it seems a little better
You are one of the few then. Parry is not working as intended, period. It is not a question of being "too late". Most here are pretty good at parry and have been experiencing problems. Mostly, it would be too early. In other posts, Kabam has mentioned that the parry window is a millisec (which seems to be reduced from what it use to be). Many attempts are registering as blocks when you block at right around the same time.
A lot of the timing issues are straight due to lag that happens when the game is calculating what happens... there is substantial frame rate issues when the two champs react... a simple freeze of a millisec could mean a non-parry.
An obvious side effect with the game growing in players and complexity is that there are latency issues. When it comes to parry, intercepts, blocks and dashes, which are finely tuned responses by the player, then latency can be a real problem.
There are ALSO clear coding problems with some specific.champs (nightcrawler!) which can make it worse.
It'll be interesting to see if the extra RAM makes a difference. I suspect not. I think it's a server problem.