**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
iphone seems to have the worst bugs that literally ruin aw, aq, and cause more deaths overall in my experience.
with samsung there is a pause in ever fight but it doesnt happen more than once per fight. not sure if thats good or bad lol
It got to the point where I always restarted the game before AW fights.
That problem has gone.
Luckily, the team has been so generous with solo potions I had a ton to fall back on when I experienced those issues…
Dr. Zola
When you have these kinds of issues, can you please be sure to report them to our Support team? We're doing our best to fix these issues but can't do it if we don't know about it. While some bugs might look the same on the outside (eg. Laggy menus or a stutter), the underlying cause is not always the same.
I’m happy to share my experience in a Bugs thread if there’s one that’s appropriate.
Dr. Zola
P.S. most likely I heard about Kabam game engine in forums/YouTube.
Actual fights (as opposed to navigating around the game's menus and maps) require server connectivity to initialize them, and there's some keep alive stuff that gets ping ponged between the game client and the game servers, but a slow connection doesn't usually cause fight lag. A lag or studder *during* a fight is explicitly symptomatic of one simple thing that disguises a lot of complex things: the phone is doing something else. And whatever it is, it causes a noticeable disruption in game play.
The reason why memory leaks *can* (but do not always) cause game lag or stuttering is because when memory gets low or fragmented or both, such as if the game client is leaking memory, you could run into swapping or loading or garbage collection, all of which can noticeably pause game play or cause it to freeze momentarily, sometimes multiple times. Eventually the leak causes free memory to drop to a critical level and the game client crashes. But on its way down, it can sometimes exhibit stuttering or freezing.
Why this is different for different players even running the same device is due to the fact that no two people's memory maps are identical. No two people run the same set of apps, doing the same things, using memory in the same way. And these kinds of problems are not just about how much memory is used and unused. Two devices could both have the exact same amount of free memory but if one of them is experiencing more memory fragmentation they will likely exhibit worse performance.
(For those not aware of the technicalities of memory fragmentation, it is like Tetris. If we're both playing Tetris and you count the white space on my board and your board and find the number to be equal, that doesn't mean we're in the same situation. You could have your white space organized well, while mine could be scattered in a lot of disjoined holes. That would make it harder for me to find space to drop a piece than you. Memory usage is like that: memory is used, then freed, then reused. If you use memory in tiny pockets and randomly free them you could end up with lots of tiny spaces surrounded by used memory. It is now harder to find space for big things.)
Incidentally, memory management is one of the Really Big Things that often causes apps to run better on iOS than Android. It isn't that iOS has a better memory management system, it is that Apple only has to support a couple dozen devices at any moment in time, and app developers only have to test and optimize on a similar number. Android developers have to test and optimize for hundreds of platforms, each one of which has its own set of quirks.
A PC typically contains 16GB or more these days. A PS4 contains 8GB. Most phones contain 2 or 3 GB of RAM. But they are being asked to do similar things. If your app runs out of memory on a PC these days you're probably an idiot. But it takes some effort to squeeze a game into the footprint of a PS4, and it takes extreme effort between the OS vendor, the software development tools, and the app developer, to make a game fit in 2GB. While everything else is running on the phone at the same time. Very tiny platform or device quirks can significantly change how memory starved applications run on a device.
This is not the sort of advice you can just give to anyone, but let's say you're grinding the arena. The way I grind arena is generally to use my champs from top to bottom. I don't scroll around or skip around forming teams, and my sort order allows me to go from top to bottom. But what if you don't do that, and you scroll around a lot? You'll probably crash faster, because all that scrolling around requires the game client to swap into active memory the profile pictures of all the champs you're seeing. In testing I was able to get the client to crash *faster* by doing just that.
That's also why I suggested disabling notifications: every time the phone gets a push notification it has to "wake up" the app it is for, and swap some stuff into active memory to process that notification before going back to sleep. All of that use-memory free-memory use-memory free-memory probably contributes to memory fragmentation, which aggravates the MCOC memory leak. It can also be the straw that breaks the camel's back, if you're trying to process notifications while memory available spirals lower and lower.
Just an example that this memory leak need The highest priority. This kind of lagging really underperformance me in war and in other places.
The pause at the 52 second mark I experienced today. Fight just stopped, dead frozen, for a couple of seconds.
But my lags aren’t nearly as pervasive as yours.
Dr. Zola
You’re welcome.
However, in all fairness I tend to prefer to play on the iPad more often than the phone. (Bigger screen, faster loading times, etc)
Generally it occurs when I have been playing for more than 30 minutes, and especially worse if I switch between game modes (EQ, AQ, AW, arena, etc)
A rule of thumb I have been doing so I would stop losing attack bonuses, and half health in AQ is force close everything, reboot iPad, then go in fresh and immediately go into war or AQ to attack to ensure the game doesnt randomly close on me.
Is your phone running very hot when you're playing? Have you tried playing without a case (which can sometimes exacerbate heating)? Does the game seem to run fine initially, then get progressively worse even after rebooting (rebooting doesn't cool the phone down on its own much, so while reboots generally fix most game client problems temporarily they do nothing for overheating issues).