So, Adobe AIR debug launcher crashed while I was in a ranked lobby. Needless to say, I was hit with a 30 minute queue ban for "dodging." I've had this problem before, and I'm sure others have too. This is, for lack of better words, not right.
That being said, I have a couple of questions for you, Riot.
Why am I being punished because your software can't run properly?
Why do you even have a queue ban when you know that things like this can happen and shut players undeserving of this punishment out of the queue?
Why does the time ban count for both queues?
How do you justify dedicating large amounts of resources to developing champions with fishboobs when your game and servers are constantly having technical issues?
Why is there an ELO deduction when there are one or members on any given team AFK?
I'm going to be bumping this until I get some answers, because I feel like these problems need to be addressed. It is unacceptable to be punishing your players for things that are outside of their own control. Not only does it compromise the integrity of the ranking system, it compromises the integrity of a company that should otherwise be fair and balanced in these situations.
I may or may not be adding more questions as I think of them. Good day.
While this is completely unrelated to what he did probably, my client crashes on a weekly basis for what seems like no reason.
Normally if I leave it idle for a while. It likes to take up a lot of resources when you leave it alone and its been running for a long time.
Can you describe a little bit about what's happening just before i crashes? That would enable me to better investigate the issue.
i.e. Does it crash while you're using it after it's been idle for a while, does it usually crash when you're on a specific thing, are you running LoLReplay/LolRecorder, what OS are you on, etc. Any extra detail you can provide makes it a lot easier to get this stuff triaged and corrected.
This happens to me sometimes too. I think downloading and installing the latest Windows Updates then restarting helps a lot, that seems to solve my crashing/constant bugsplat problems.
However...
The overall issue I have with this is that I shouldn't have these kinds of problems so consistently. Why do I need to run Windows Update that often? Does the League of Legends client really depend so much on Windows Updates that I MUST update every two weeks or so, otherwise the client starts failing? I just don't see why that has to be a thing.
Without more information I can't tell you what's going on. I would assume that the Windows Update has no affect and it's the restart that's mattering, but that's just a guess.
I understand how frustrating it is to crash; it sucks, they're our top priority bug fix. If we get a report of a crash bug, we investigate and try to get it locked down and fixed asap.
Unfortunately I can't do a whole lot with a message that says "I crash, then I use windows update and restart, and I think I crash less". I'm not giving you a hard time, but look at it from the perspective of myself or another QA person: how on earth do I figure out what the deal is based on that info?
There is a known stability issue with the Air Client that manifests intermittently When using Windows 8 and LoLRecorder/LoLReplay: it will crash, but only sometimes. And not always in the same way.
That's the only stability issue that we've been able to see as a recurrant behavior. If you guys can help me find more, I'm happy to push as hard as I can to get things handled.
Ok guys, just to clarify, let's split things a little bit.
There are two "chunks" of League. There's the one that happens in Adobe Air, which is everything leading up to Champion Select and that launch sound right before you see the League of Legends logo pop up. This also includes *after* the game ends (Stats screen, etc)
After that is the game client. That's the load screen, the game itself, all that stuff.
It sounds like people are reporting a crash AFTER the league logo, during the loading screen. Does it bugsplat (pop up the message from Bugsplat) or does it just hard crash and windows says "An error has occured"?
Hey Damiya, while you're already here, I wish to inform you about something as a fellow overlord.
While the match is starting, when the PvP.net client closes and then the little ''League of Legends'' logo appears and then the loading screen shows up. Well, while the LoL logo is shown, before the Loading screen appears, if I click anywhere with my mouse or press any button on the keyboard it will bug and stop, preventing the Loading screen from showing up. And to add insult to injury, the PvP.net client states that the game is currently running so I have to turn it off and restart the whole sequence.
It's quite annoying.
This may be related to the quarter window bug that has been plaguing everyone for a while now. I developed a reproduction on that and a Game Engineer is investigating. Once we get that fixed, can we see about recreating your issue?
For me it either crashes completely ('an error has occurred') or it just freezes up. Like it'll be loading normally and then all of a sudden a minute or two will have gone by and no one's loading percentage moved.
When the second scenario happens I realized that the game had already started for everyone else a few minute ago because my pre-made friend asked me where I was. So then I had to hard restart the program (alt, control, delete) and then reboot LOL all over again.
Ok. Game client stuff is way outside my field,so I can't speak to this issue but I will try and flag down a Game Analyst to look into the issues you guys are reporting with the load screen.
For the record, I'm not directly a QA person working on the Air Client/PVP.net so I can't promise I can drive results on this stuff immediately; I have my own very, very full plate. But I work in a roughly related team so I will do the best I can.
Quote:
Originally Posted by TrolImanship
Well, my problem is when I log out and load the client back up, and go to log into a different account the client has about a 50% chance to just completely stop. It won't do anything. The screen is greyed out kind of so I can't click anything in it. I can either let it sit (it won't do anything, I've tried just leaving it for minutes) or close the window.
Then when I load up the client again, it comes up with the error message telling me it's not working, I hit ok, it stops LoL, then it begins loading again, and THEN I can switch accounts, usually
It sounds like you may not be exiting cleanly. When you exit next time, can you hit CTRL-SHIFT-ESCAPE and get a list of the running processes? Specifically looking for: rads_user_kernel, jojodiff, jojopatch, lolclient, league of legends, and so on.
I just realised I don't have a public facing email address without my real name on it, so I won't be able to take logs on this stuff until Monday, but I'll see if I can come up with an alternative.
Does this Game Engineer need more info on systems that this effects? I've had the quarter window bug effect me and I'd be happy to provide system specs if it'll make it die a quick painful death, as I too hate this bug with the passion of a thousand suns...
I came up with a 100% reproduction rate. We know the rough cause (it's a timing issue in certain calls as the DirectX renderer initializes) and a very smart Engineer is taking it in hand.
We should be ok, but I will definitely come request more info if it is necessary.
A few honest questions for you, Riot.
That being said, I have a couple of questions for you, Riot.
Why am I being punished because your software can't run properly?
Why do you even have a queue ban when you know that things like this can happen and shut players undeserving of this punishment out of the queue?
Why does the time ban count for both queues?
How do you justify dedicating large amounts of resources to developing champions with fishboobs when your game and servers are constantly having technical issues?
Why is there an ELO deduction when there are one or members on any given team AFK?
I'm going to be bumping this until I get some answers, because I feel like these problems need to be addressed. It is unacceptable to be punishing your players for things that are outside of their own control. Not only does it compromise the integrity of the ranking system, it compromises the integrity of a company that should otherwise be fair and balanced in these situations.
I may or may not be adding more questions as I think of them. Good day.
You said you were in a ranked lobby; were you running LoLReplay or LolRecorder? Are you on Windows 8?
Normally if I leave it idle for a while. It likes to take up a lot of resources when you leave it alone and its been running for a long time.
i.e. Does it crash while you're using it after it's been idle for a while, does it usually crash when you're on a specific thing, are you running LoLReplay/LolRecorder, what OS are you on, etc. Any extra detail you can provide makes it a lot easier to get this stuff triaged and corrected.
However...
The overall issue I have with this is that I shouldn't have these kinds of problems so consistently. Why do I need to run Windows Update that often? Does the League of Legends client really depend so much on Windows Updates that I MUST update every two weeks or so, otherwise the client starts failing? I just don't see why that has to be a thing.
I understand how frustrating it is to crash; it sucks, they're our top priority bug fix. If we get a report of a crash bug, we investigate and try to get it locked down and fixed asap.
Unfortunately I can't do a whole lot with a message that says "I crash, then I use windows update and restart, and I think I crash less". I'm not giving you a hard time, but look at it from the perspective of myself or another QA person: how on earth do I figure out what the deal is based on that info?
There is a known stability issue with the Air Client that manifests intermittently When using Windows 8 and LoLRecorder/LoLReplay: it will crash, but only sometimes. And not always in the same way.
That's the only stability issue that we've been able to see as a recurrant behavior. If you guys can help me find more, I'm happy to push as hard as I can to get things handled.
There are two "chunks" of League. There's the one that happens in Adobe Air, which is everything leading up to Champion Select and that launch sound right before you see the League of Legends logo pop up. This also includes *after* the game ends (Stats screen, etc)
After that is the game client. That's the load screen, the game itself, all that stuff.
It sounds like people are reporting a crash AFTER the league logo, during the loading screen. Does it bugsplat (pop up the message from Bugsplat) or does it just hard crash and windows says "An error has occured"?
as a fellow overlord.While the match is starting, when the PvP.net client closes and then the little ''League of Legends'' logo appears and then the loading screen shows up. Well, while the LoL logo is shown, before the Loading screen appears, if I click anywhere with my mouse or press any button on the keyboard it will bug and stop, preventing the Loading screen from showing up. And to add insult to injury, the PvP.net client states that the game is currently running so I have to turn it off and restart the whole sequence.
It's quite annoying.
When the second scenario happens I realized that the game had already started for everyone else a few minute ago because my pre-made friend asked me where I was. So then I had to hard restart the program (alt, control, delete) and then reboot LOL all over again.
For the record, I'm not directly a QA person working on the Air Client/PVP.net so I can't promise I can drive results on this stuff immediately; I have my own very, very full plate. But I work in a roughly related team so I will do the best I can.
Then when I load up the client again, it comes up with the error message telling me it's not working, I hit ok, it stops LoL, then it begins loading again, and THEN I can switch accounts, usually
I just realised I don't have a public facing email address without my real name on it, so I won't be able to take logs on this stuff until Monday, but I'll see if I can come up with an alternative.
Unfortunately it's been a pain to reproduce because it only affects certain CPUs and only in a very strange obscure way under specific conditions.
We have an awesome team of Game Engineers, and thankfully there's one of them tackling it now. I can't offer an ETA, but know that it's on the radar.
We should be ok, but I will definitely come request more info if it is necessary.