Had to enable legacy client due to champions not appearing in champ select.
Just got my 4th or 5th queue dodge due to this bug. Granted this has been over weeks but I'm tired of it. 30 minutes of my life and 15lp lost due to a client bug.
Just got my 4th or 5th queue dodge due to this bug. Granted this has been over weeks but I'm tired of it. 30 minutes of my life and 15lp lost due to a client bug.
I'm having the same issue. being punished for champs not showing up so i can choose. makes sense
Riot doesn't care about the performance issues normal players are having. They want the game to look better, so streamers with high end pcs make the game look amazing. You're sol if you're on a decent to lower end pc
Actually they do care. The maps (HA, TT, SR) have been optimized to work on lower end machines, the Beta Client is in the process of being optimized.
#Beta Client
Click the cog to the top right corner of the client then click "Initiate Full Repair".
#Legacy Client
Repair the game by clicking the question mark icon to the top right of the patcher. Select "Repair" and let the patcher scan and repair corrupt game files. When the process is completed, you'll see the orange "Launch" button.
Let us know the results.
Click the cog to the top right corner of the client then click "Initiate Full Repair".
Repair the game by clicking the question mark icon to the top right of the patcher. Select "Repair" and let the patcher scan and repair corrupt game files. When the process is completed, you'll see the orange "Launch" button.
Let us know the results.
It doesn't happen every time. Like I said in the original post, this has happened 5 or so time over the course of weeks. I believe it's a connection issue rather than a client issue... like if you don't receive a packet at the right time the champions will never appear for pans/picks leaving you with nothing you can do but accept the forced dodge.
Issue doesn't exist in the Legacy Client, only the beta.
Even if it doesn't happen all of the time, if you're only experiencing it on one client and not the other then it's an issue of corrupted files in the client and not a connection issue.
If this was happening on both clients, a connection issue could have been the cause.