1 thing I didn't like is how the original post intended that the issue is IOS specific only. This is wrong. I am facing the same issue on my android phone and nothing is mentioned in the OG post about android.
Just gonna make a few comments here.1. Very puzzled when you say this is an IOS problem, because from what I've seen its actually Android users who say they are most affected by this.2. The game stutterering, or gamefreeze started for me only after the parry bug patch was released, and its been horrible since. Game freeze up for anywhere between half a second and a second except the other day when it took half apocs special 1 before it actually started moving again.3. Why are there only health potions and revives for aq and aw beeing given out? As far as I'm aware the issue is just as bad in normal quests, and a lot of people saying they wont do any quest exploration these days because of it.So atm you are only actually giving out potions for the part of the game that feels most like a job, and not for the part of the game that people should be enjoying.4. Was doing EQ yesterday on Cav difficulty and all parries were working fine. But when I swapped over to do 100% on UC difficulty only 2 out of the first 8 parries actually stuck. And the fact that you're saying its a IOS issue is something I find strange seeing as im playing on Android, and I'm pretty sure my skills didnt suddenly drop by that much between changing up those two quests.
I appreciate the info though most of it is over my dumb blue collar head but I have two questions:Why is the AQ/AW compensation expiring? I would've thought that the stash/expiry date would be extended if this is what is given to compensate the issues.Where's the solo comp? Is running paths in act 6 for a cav deemed less important than weak war or map2 AQ?
Just gonna make a few comments here.1. Very puzzled when you say this is an IOS problem, because from what I've seen its actually Android users who say they are most affected by this.
“Single player content resources”Hopefully this is a decent amount of revives and potions
iOS only issue my ass..... Are you saying your update made me forget how to play by installing?
Hey Summoners,It’s been a little while since we’ve communicated on the ongoing Control issues, and today we wanted to give you all a different kind of post, where we’ll explore the cause of the issue, what it entails, and the progress we’ve made on our journey so far in addressing the inconsistencies and changes in control timing.We also want to take a moment to better outline what the issue actually is, as we know there’s some confusion surrounding the exact symptoms of this issue. We’ve seen players reporting issues such as framerate drops or lag that are not related to this issue, and are being addressed separately with some fixes coming your way soon.We also want to give you more insight into why this process is taking some time to address, why it’s difficult to address issues based on “feel”, and introduce you to a new member of our team!You can read the post here, and then come back to this thread to discuss! Hello I just want to point out that I am an android user and I definitely have an issue with parry and dex. It's not consistent, it's not each and every fight, but it is there. It may come once every 100 fights (I grind the arena daily) or it can also come twice in a row as I enter aq. I don't understand a single thing about coding and game engine, I'm just saying you should take a better look into android interactions as well. Because if all you're working on is fixing the timing for apple devices, then I may never be able to rely on parry and dex as well as before. I mean... as far as arena goes, if I fail 2 parries in a row and get hit by 2-3 combos, I still survive and I have a way to come back. But when it comes to endgame content or even more importantly aw... I mean what am I supposed to do exactly? If I get comboes 2-3 times I may just die without being able to do anything. And same goes with dex issue. I fail to dex a special, I just die. This is an important issue to address. It's not just ios, it's android too. I can safely say that when the issue first popped out all my alliance mates playing on ios were affected while android users (myself included) weren't noticing any issues. I mean the difference was clear: ios players were saying the game was unplayable while us android players were fine. Ever since the first patch to fix the issue, I started noticing that sometimes my parry window was off. And the same goes for other android users. I believe that maybe the fix that was pushed through had an effect on all devices. I can't see another possible explanation. I play the game several hours a day and I can safely say that I can go on for hours without failing a parry but then again I know that at some point I will touch the screen to parry with the same timing as ever, as I do countless times everyday, and the parry will indeed fail. Knowing this, I've tried to adapt my gameplay to rely less heavily on parry and more on intercepting, but that too proves risky and doesn't necessarily pay off as much as I'd like to. Also, there are abilities and node interactions that pretty much force you to parry (i.e. playing against evade or miss champions without a proper counter, nodes such as icarus and flux dispersal...). As for dexing, the timing is occasionally off. This summer I had my first run in the abyss. I remember the howard the duck fight was long and I can't dex his sp2. So I was just always dexing his sp1, pushing him to sp1 and baiting. Always. I baited and dexed dunno how many of his sp1. But sometimes I would just stand there as if I wasn't dexing. And get hit in the face. This with howard the duck sp1 also happened a few times in aq or eq. I mean it's really easy to dodge but sometimes I swipe and I just stand there and get hit. Also something else I want to report is that from my testing in the last months since the issue appeared I find that most of the failed parries are on the opponent's medium dash. I somehow have less troubles to parry a light attack when I'm close to the opponent. This is because the moment he moves I just tap to parry and it works. On medium dashes, sometimes my input is late and sometimes it's early. So I either get caught off guard and take a combo, or I get hit on the block. Either way fighting champs that require to parry their medium has proved more troublesome. On my old phone I had a lag in my inputs and the issue was different. In fact I couldn't parry a light, since my input wouldn't come in time and I'd get hit. Instead, I'd be able to parry a medium dash by anticipating it. This was a matter of lag in my control inputs. When I bought a new phone I had no troubles anymore. For example I couldn't properly use captain marvel movie on my old device... doing 12-13 parries to charge her was a nightmare. With the new phone I used her a lot and I came to love her. Now, since the issue came out, I have her sitting on the bench. I ranked up other champs that rely less on parry for the sake of my items stash and my units stash.All this to say that android users are also suffering an issue with parry and dex. It may be less frequent than with ios, I don't know... but I don't want to think that Kabam will only work towards fixing ios version of the game. All this time I've been hopeful that the next update the issue would be resolved. And now I'm reading that you're not even convinced there's an issue on android to begin with? That's really horrible to find out... Basically I'll have to spend more than others to do endgame content and I won't be reliable in aq/aw because anytime I could just miss a parry and die? And what about an alliance then? Should there be a purge of android users if you want to push? Because only ios users will be able to rely on their inputs? This is not good for the health of the community and the game They don't care about android issues because they're harder to solve & smaller community. Funny how every other game can optimise for both, but mcoc can't. We moan for years about the issues- nothing.. iOS has an issue it's the end of humanity.
Hey Summoners,It’s been a little while since we’ve communicated on the ongoing Control issues, and today we wanted to give you all a different kind of post, where we’ll explore the cause of the issue, what it entails, and the progress we’ve made on our journey so far in addressing the inconsistencies and changes in control timing.We also want to take a moment to better outline what the issue actually is, as we know there’s some confusion surrounding the exact symptoms of this issue. We’ve seen players reporting issues such as framerate drops or lag that are not related to this issue, and are being addressed separately with some fixes coming your way soon.We also want to give you more insight into why this process is taking some time to address, why it’s difficult to address issues based on “feel”, and introduce you to a new member of our team!You can read the post here, and then come back to this thread to discuss! Hello I just want to point out that I am an android user and I definitely have an issue with parry and dex. It's not consistent, it's not each and every fight, but it is there. It may come once every 100 fights (I grind the arena daily) or it can also come twice in a row as I enter aq. I don't understand a single thing about coding and game engine, I'm just saying you should take a better look into android interactions as well. Because if all you're working on is fixing the timing for apple devices, then I may never be able to rely on parry and dex as well as before. I mean... as far as arena goes, if I fail 2 parries in a row and get hit by 2-3 combos, I still survive and I have a way to come back. But when it comes to endgame content or even more importantly aw... I mean what am I supposed to do exactly? If I get comboes 2-3 times I may just die without being able to do anything. And same goes with dex issue. I fail to dex a special, I just die. This is an important issue to address. It's not just ios, it's android too. I can safely say that when the issue first popped out all my alliance mates playing on ios were affected while android users (myself included) weren't noticing any issues. I mean the difference was clear: ios players were saying the game was unplayable while us android players were fine. Ever since the first patch to fix the issue, I started noticing that sometimes my parry window was off. And the same goes for other android users. I believe that maybe the fix that was pushed through had an effect on all devices. I can't see another possible explanation. I play the game several hours a day and I can safely say that I can go on for hours without failing a parry but then again I know that at some point I will touch the screen to parry with the same timing as ever, as I do countless times everyday, and the parry will indeed fail. Knowing this, I've tried to adapt my gameplay to rely less heavily on parry and more on intercepting, but that too proves risky and doesn't necessarily pay off as much as I'd like to. Also, there are abilities and node interactions that pretty much force you to parry (i.e. playing against evade or miss champions without a proper counter, nodes such as icarus and flux dispersal...). As for dexing, the timing is occasionally off. This summer I had my first run in the abyss. I remember the howard the duck fight was long and I can't dex his sp2. So I was just always dexing his sp1, pushing him to sp1 and baiting. Always. I baited and dexed dunno how many of his sp1. But sometimes I would just stand there as if I wasn't dexing. And get hit in the face. This with howard the duck sp1 also happened a few times in aq or eq. I mean it's really easy to dodge but sometimes I swipe and I just stand there and get hit. Also something else I want to report is that from my testing in the last months since the issue appeared I find that most of the failed parries are on the opponent's medium dash. I somehow have less troubles to parry a light attack when I'm close to the opponent. This is because the moment he moves I just tap to parry and it works. On medium dashes, sometimes my input is late and sometimes it's early. So I either get caught off guard and take a combo, or I get hit on the block. Either way fighting champs that require to parry their medium has proved more troublesome. On my old phone I had a lag in my inputs and the issue was different. In fact I couldn't parry a light, since my input wouldn't come in time and I'd get hit. Instead, I'd be able to parry a medium dash by anticipating it. This was a matter of lag in my control inputs. When I bought a new phone I had no troubles anymore. For example I couldn't properly use captain marvel movie on my old device... doing 12-13 parries to charge her was a nightmare. With the new phone I used her a lot and I came to love her. Now, since the issue came out, I have her sitting on the bench. I ranked up other champs that rely less on parry for the sake of my items stash and my units stash.All this to say that android users are also suffering an issue with parry and dex. It may be less frequent than with ios, I don't know... but I don't want to think that Kabam will only work towards fixing ios version of the game. All this time I've been hopeful that the next update the issue would be resolved. And now I'm reading that you're not even convinced there's an issue on android to begin with? That's really horrible to find out... Basically I'll have to spend more than others to do endgame content and I won't be reliable in aq/aw because anytime I could just miss a parry and die? And what about an alliance then? Should there be a purge of android users if you want to push? Because only ios users will be able to rely on their inputs? This is not good for the health of the community and the game
Hey Summoners,It’s been a little while since we’ve communicated on the ongoing Control issues, and today we wanted to give you all a different kind of post, where we’ll explore the cause of the issue, what it entails, and the progress we’ve made on our journey so far in addressing the inconsistencies and changes in control timing.We also want to take a moment to better outline what the issue actually is, as we know there’s some confusion surrounding the exact symptoms of this issue. We’ve seen players reporting issues such as framerate drops or lag that are not related to this issue, and are being addressed separately with some fixes coming your way soon.We also want to give you more insight into why this process is taking some time to address, why it’s difficult to address issues based on “feel”, and introduce you to a new member of our team!You can read the post here, and then come back to this thread to discuss!
Sry, but my English is not so good, so I can’t understand few things. I’m iOS user, so can someone tell me, will they fix the lag and stuttering issue? I’m using iPhone XR, and FPS and stuttering is the top issue for me right now, because game unplayable for me. If they fix this, can I ask when? I found some issues will fix October and November update, and other in 2022. Tnx
I have a bit of trouble digesting this whole “feel” thing .. if i can consistently produce the “bug”, how is it just a feel thing?
@rockykoston to continue our conversation here, I’m not saying the unity engine only updated for IOS. I’m saying that update only caused the parry dex issue for IOS and not Android. I’d encourage you to read the entire post again, because I’m afraid you’ve misunderstood that aspect. I don’t mean that in a patronising way, just that if you think Kabam are saying Android players don’t have an issue with parry or dex, then you haven’t read the whole thing. Please read it again, but I’ll direct you to this part which explains the IOS issues. “ When we refer to the “Parry and Dex issue”, we’re not actually talking about an issue with Parry or Dex, but a framerate and control input issue exclusive to iOS devices that is most noticeable when trying to Parry or Dex, since these are two mechanics players rely on quite often.Marvel Contest of Champions is built on a 3rd Party Game Engine built by our partners at Unity, which has an input system built-in. We’ve relied on Unity's input system since the game was built, and have regularly updated the Engine as they have released updates. With the most recent update to the Engine, a bug was fixed where iOS devices had been operating at the device’s own frame rate, instead of being capped to 30fps as it was set to. This meant that iOS devices had a slightly different input window than Android devices, but this was never identified.Since this is how iOS devices had always worked with our game since launch, we had built game interactions around that input window. Now, because this bug in the engine has been fixed, it changed the input window of inputs for all iOS devices and pushed back the input window by mere milliseconds, but that is enough that it is noticeable when playing the game.This is the issue that we are working to address, and our fix for it is to integrate an entirely new control input system from our partners at Unity. But this is not a quick or easy task.”Only the IOS input window was pushed back, therefore it cannot be the cause of the Android issues.
@rockykoston to continue our conversation here, I’m not saying the unity engine only updated for IOS. I’m saying that update only caused the parry dex issue for IOS and not Android. I’d encourage you to read the entire post again, because I’m afraid you’ve misunderstood that aspect. I don’t mean that in a patronising way, just that if you think Kabam are saying Android players don’t have an issue with parry or dex, then you haven’t read the whole thing. Please read it again, but I’ll direct you to this part which explains the IOS issues. “ When we refer to the “Parry and Dex issue”, we’re not actually talking about an issue with Parry or Dex, but a framerate and control input issue exclusive to iOS devices that is most noticeable when trying to Parry or Dex, since these are two mechanics players rely on quite often.Marvel Contest of Champions is built on a 3rd Party Game Engine built by our partners at Unity, which has an input system built-in. We’ve relied on Unity's input system since the game was built, and have regularly updated the Engine as they have released updates. With the most recent update to the Engine, a bug was fixed where iOS devices had been operating at the device’s own frame rate, instead of being capped to 30fps as it was set to. This meant that iOS devices had a slightly different input window than Android devices, but this was never identified.Since this is how iOS devices had always worked with our game since launch, we had built game interactions around that input window. Now, because this bug in the engine has been fixed, it changed the input window of inputs for all iOS devices and pushed back the input window by mere milliseconds, but that is enough that it is noticeable when playing the game.This is the issue that we are working to address, and our fix for it is to integrate an entirely new control input system from our partners at Unity. But this is not a quick or easy task.”Only the IOS input window was pushed back, therefore it cannot be the cause of the Android issues. @BitterSteel I just don't believe it.Either they've not tested enough or they're afraid to acknowledge that Unity update is affecting android devices.Now you'd ask why would they not accept it, because of the sheer variety of android devices, models, OS etc. They've never really been able to fix the android issue so if this is the same thing then it's nothing new.iOS is clearly much easier to identify and fix because of the small environment.But the fact that they are dismissing android as a generic lag and stutter is what they've been doing forever.The fact that android now has configurable screen refresh rate with phones going UpTo 144hz and no update to make that compatible, tells us everything.
@rockykoston to continue our conversation here, I’m not saying the unity engine only updated for IOS. I’m saying that update only caused the parry dex issue for IOS and not Android. I’d encourage you to read the entire post again, because I’m afraid you’ve misunderstood that aspect. I don’t mean that in a patronising way, just that if you think Kabam are saying Android players don’t have an issue with parry or dex, then you haven’t read the whole thing. Please read it again, but I’ll direct you to this part which explains the IOS issues. “ When we refer to the “Parry and Dex issue”, we’re not actually talking about an issue with Parry or Dex, but a framerate and control input issue exclusive to iOS devices that is most noticeable when trying to Parry or Dex, since these are two mechanics players rely on quite often.Marvel Contest of Champions is built on a 3rd Party Game Engine built by our partners at Unity, which has an input system built-in. We’ve relied on Unity's input system since the game was built, and have regularly updated the Engine as they have released updates. With the most recent update to the Engine, a bug was fixed where iOS devices had been operating at the device’s own frame rate, instead of being capped to 30fps as it was set to. This meant that iOS devices had a slightly different input window than Android devices, but this was never identified.Since this is how iOS devices had always worked with our game since launch, we had built game interactions around that input window. Now, because this bug in the engine has been fixed, it changed the input window of inputs for all iOS devices and pushed back the input window by mere milliseconds, but that is enough that it is noticeable when playing the game.This is the issue that we are working to address, and our fix for it is to integrate an entirely new control input system from our partners at Unity. But this is not a quick or easy task.”Only the IOS input window was pushed back, therefore it cannot be the cause of the Android issues. @BitterSteel I just don't believe it.Either they've not tested enough or they're afraid to acknowledge that Unity update is affecting android devices.Now you'd ask why would they not accept it, because of the sheer variety of android devices, models, OS etc. They've never really been able to fix the android issue so if this is the same thing then it's nothing new.iOS is clearly much easier to identify and fix because of the small environment.But the fact that they are dismissing android as a generic lag and stutter is what they've been doing forever.The fact that android now has configurable screen refresh rate with phones going UpTo 144hz and no update to make that compatible, tells us everything. Ok, well I don’t think spreading conspiracy theories and claiming Kabam is lying is going to help anyone. They’ve said what they’ve said, they have no reason to lie.
