**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.
Options
Stutter and Hit Boxes
DrZola
Posts: 8,549 ★★★★★
One of the issues I’ve encountered more frequently of late is what has colloquially been called “stutter.”
I’m not a programmer, but the visual experience is something like frames skipping or even jumping ahead during the movement of the champions on screen.
There are moments in a fight when the “feel” is such that I know stutter is coming on—almost as if whatever code loaded in for that particular fight and my device are “straining” to render the visuals of the fight consistently.
“Stutter” occurs frequently for me at what I would call the point of impact—basically, when the two hit boxes of the champs are approaching each other. That is significant, of course, because that’s often the moment when a player is preparing to evade or parry or block. As an example, it’s almost an ironclad law that it will occur on nodes that reflect stuns, and never (that I can recall) to my benefit.
This is (maybe) the memory leak issue. I don’t know, and would appreciate members like @DNA3000 chiming in. What potential causes are there for this? Is this just part of the experience of playing an increasingly complex game on a smartphone? Is there some specific interaction occurring during this specific interval that makes “stutter” more likely? Is this an item that *could* be ameliorated by the ongoing team efforts to repair the game?
Thanks in advance…
Dr. Zola
I’m not a programmer, but the visual experience is something like frames skipping or even jumping ahead during the movement of the champions on screen.
There are moments in a fight when the “feel” is such that I know stutter is coming on—almost as if whatever code loaded in for that particular fight and my device are “straining” to render the visuals of the fight consistently.
“Stutter” occurs frequently for me at what I would call the point of impact—basically, when the two hit boxes of the champs are approaching each other. That is significant, of course, because that’s often the moment when a player is preparing to evade or parry or block. As an example, it’s almost an ironclad law that it will occur on nodes that reflect stuns, and never (that I can recall) to my benefit.
This is (maybe) the memory leak issue. I don’t know, and would appreciate members like @DNA3000 chiming in. What potential causes are there for this? Is this just part of the experience of playing an increasingly complex game on a smartphone? Is there some specific interaction occurring during this specific interval that makes “stutter” more likely? Is this an item that *could* be ameliorated by the ongoing team efforts to repair the game?
Thanks in advance…
Dr. Zola
8
Comments
Good question and I don’t know.
I wonder if there is a connection issue involved. I often get what I call “dead map,” where I cannot move to the next node no matter how many time I tap. There’s no WiFi icon, but it operates like the game is frozen, even though the background and energy clock continue to move.
Is this like the dead special button? It doesn’t seem like it would be, since I recall being told long ago that each “fight” is downloaded when you press the fight button—that is, it doesn’t involve any server communication once the fight begins.
Which is why I would think it’s a “within the fight packet” control issue, not some kind of connection-related issue.
So I think it likely the “memory leak”
issue, but I’m guessing. But I would love to understand both our issues better.
Dr. Zola
But I’d love to have confirmation of that.
Dr. Zola