: Oh, that's pretty low. 30 MB for a game that runs an hour is a drop in the bucket compared to a 90 minute video.
The numbers check out. Video is a *lot* of information. Even with good quality modern compression, filling a 1080p screen at 30hz requires far more numbers than the game state of League. If you think about it that way, you can draw a relation between, say, knowing the position of a unit - 3 32-bit numbers, to the color of 12 pixels with 8-bit color channels. That particular comparison isn't fair to video - the compression techniques there are very well developed past the concept of sending individual color information, but the general idea illustrates why the difference is so big.
: > [{quoted}](name=Riot Penrif,realm=NA,application-id=A7LBtoKc,discussion-id=7KgXRu3X,comment-id=00020000,timestamp=2016-10-02T01:50:40.509+0000) > > Oh yes it was quite the voyage of discovery. We had QA-folk trying anything to reproduce it, attacking from any conceivable angle, engineers staring at code trying to make any sense of the evidence and many other Rioters offering any help they could. We were finally able to reproduce it on a development machine late in the night and were eventually able to trace a narrative back to root cause early the next day. > > Teamwork makes the dream work. So was this only reproducible when all of the first 12 clients for secondary synch were NOT one of the 5 members on the enemy team (the 5 players that don't have vision of ASol)?
: Isn't this only an issue with the Ashen Lord skin?
No, it applies to the champion as a whole.
: Interesting to see how the age of the accounts played a factor in this bug. Could we hear more about the process of finding the causes for the bug? I imagine you guys would have been running all sorts of tests before figuring out what it was.
Oh yes it was quite the voyage of discovery. We had QA-folk trying anything to reproduce it, attacking from any conceivable angle, engineers staring at code trying to make any sense of the evidence and many other Rioters offering any help they could. We were finally able to reproduce it on a development machine late in the night and were eventually able to trace a narrative back to root cause early the next day. Teamwork makes the dream work.
ExHentai (NA)
: So, does this workaround mean he is enabled for tomorrow or later?
Yes, Aurelion Sol will be available for play on day 4. https://twitter.com/lolesports/status/782113765932175360
  Rioter Comments
: Are you super sure it shows up enough? I'm looking at this gif and I feel like it blends in with the health bar a little too much. I guess it will be less obvious on a red health bar, but for the self it's a bit... hard to see.
Good point, let me see if I can swap that gif for one with a different bar... edit - boom
George LS (EUW)
: I think op is trying to be a l3gend@ry meme-scoper, he featured jayce's "Can't touch this " dance on the whole invulnerability thing.
https://media.giphy.com/media/XQvhpuryrPGnK/giphy.gif
: I think more along the lines of tryndamere ult
We decided against altering Trynd ult - he's only invuln at very low HP, and he rapidly life-steals out of that state. Disco-invuln-hud wasn't a thing we're interested in inflicting upon the world.
midorii (NA)
: What other abilities were altered to "embrace invulnerability"? I'm guessing something along the lines of Master Yi's Alpha Strike? Will his health bar now go all shiny and yellow when he does that? Can his health bar be visible the whole time he is alpha striking now?
Kindred and Kayle ults were the ones pulled into proper invulnerability.
: Introducing Invulnerability HUD
Due to things, this won't be showing up on PBE 'til Monday, so as y'all know.
  Rioter Comments
Eedat (NA)
: Last question I would like to pose. There are similar reports of Ekko's 'trail' being spotted in places it shouldn't be. Is this going to be fixed on the Worlds patch as well? Ekko is a popular pick and I would hate to see him being disabled for Worlds Thanks for taking the time to answer my questions!
I'll speak with my QA friends on that.
Eedat (NA)
: I've heard (albeit from unconfirmed sources) that it can be reproduced by Aurelion Sol toggling lock/unlock camera while entering fog of war. this is easiest to do in bushes because there is a very clear line. Is this information incorrect?
The status of Aurelion Sol's player camera has no bearing on the communications from the server to other players.
Eedat (NA)
: Can the bug be intentionally reproduced by either team? What circumstances cause it exactly? Why does it happen some times and not others?
I believe it'd be quite hard to intentionally reproduce in a competitive environment. You would need to have the other team lose vision of you at an important position, and remain completely out of vision, only to reveal just your passive to that team some point in the future and a missile might show up at the previous position for a couple frames. It demonstrates infrequently due to many factors. One of which is simply that the position and timing of the effect is complicated and doesn't often arise in an organic environment in a way that's noticeable. There's also a strong timing component to this as well, where the client's framerate and network updates are effectively racing each other. Initially I had a difficult time replicating the issue on my workstation as I had capped my framerate to 30Hz, which allowed the network sync to usually land in time for the issue to not display.
patmax17 (EUW)
: Is this basically the same bug that leaves long trails all over the screen when things like Kindred's Wolf or a champ with DMP exit and enter fog of war?
Similar kind of thing, probably, but neither of those are missiles.
: Who is CLS?
Move along, nothing to see here...
  Rioter Comments

Riot Penrif

Level 54 (NA)
Lifetime Upvotes
Create a Discussion