Loading screen: everyone at 100% but the game is NOT STARTING
-> Bug that's been since forever -> Loading screen stage lasts so much -> FIX!
-> Bug that's been since forever -> Loading screen stage lasts so much -> FIX!
it used to load much faster but somewhere in season 8 the loading time increased by a lot i dont know why.
I have the same issue. League freezes every game in all modes right after everyone reaches 100%. After about 1 minute the game appears at the spawn and freezes for another 10-20 seconds, then all of the sudden everything catches up and the rest of the game is normal. This started happening directly after the latest patch.
I have done the following:
In the logs my game stops directly after these lines:
000054.233| ERROR| Can not open file <SummonerObserver.dds> ********* 000054.233| ERROR| Failed to load SummonerObserver.dds 000054.234| WARN| r3dTexture EX: SummonerObserver.dds - not found. Dummy text
Then resumes from the texture error (I believe the texture error is unrelated):
000054.233| ERROR| Can not open file <SummonerObserver.dds> *********000054.233| ERROR| Failed to load SummonerObserver.dds000054.234| WARN| r3dTexture EX: SummonerObserver.dds - not found. Dummy texture created.000054.324| ALWAYS| FLOW| SEJ-74A6B1FA. 000054.398| ALWAYS| Spawning heroes/minions 000054.398| ALWAYS| CFG| MultiplayerSettings EnableLNP=true Encryption=true Compression=true Logging=false Wireless=false Redundancy=false Threshold=0 Capacity=1000 Resends=20 000054.400| ALWAYS| Finished spawning heroes/minions 000162.187| ALWAYS| ALE-MM44G8Q7 (120.2982182 8.347506 0.051754 0.000009) 000241.293| ALWAYS| ALE-P6S77E01: (0)(0.043)(0.000)(238.141)(246.333)(8.346)(0) 000241.375| ALWAYS| FLOW| Switching Game State from GAMESTATE_SPAWN to GAMESTATE_GAMELOOP for reason Received Game Start Packet. 000242.133| ERROR| >>> BuffHashMap::HashToName - Match not found for hash 0f7c3eb1 000291.534| ALWAYS| GAMESTATE_GAMELOOP Begin 000291.577| ALWAYS| GAMESTATE_GAMELOOP Update World 000297.534| ALWAYS| r3dRenderLayer::RecreateOwnedResources 000299.105| ALWAYS| r3dRenderLayer::RecreateOwnedResources 000300.862| ALWAYS| GAMESTATE_GAMELOOP GUIMenuProcess
I'm running the following hardware:
Operating System: Windows 10 Home 64-bit (10.0, Build 17134) (17134.rs4_release.180410-1804) Language: English (Regional Setting: English) System Manufacturer: ASUSTeK COMPUTER INC. System Model: G551JW BIOS: G551JW.209 (type: UEFI) Processor: Intel(R) Core(TM) i7-4720HQ CPU @ 2.60GHz (8 CPUs), ~2.6GHz Memory: 16384MB RAM Available OS Memory: 16274MB RAM Page File: 5721MB used, 11575MB available Windows Dir: C:\WINDOWS DirectX Version: DirectX 12 DX Setup Parameters: Not found User DPI Setting: 120 DPI (125 percent) System DPI Setting: 120 DPI (125 percent) DWM DPI Scaling: UnKnown Miracast: Available, with HDCPMicrosoft Graphics Hybrid: Supported Card name: Intel(R) HD Graphics 4600 Card name: NVIDIA GeForce GTX 960M (Render only) Core isolation: on
There is something weird that i have noticed in the past few weeks. There is always one person that is at 0% while the others load to 100, and after like a minute or so, that person loads to a 100. I thought that it was just someone having a slow pc or connection but I noticed it happen consistently, every game i played
except the last one where it was 2 people that didnt move from 0. When this happened, one loaded to 60%, then the other went to 60% while the first one stayed at 60, and then the first one completed the load followed by the second.
Weird ass coincidence maybe, but I think something is up with the loading logic....
It is going worst and worst at every patch. :( Got several penalty for afk while I'm looking at my loading screen...
Haven't you considered that the bug is still there because they don't care about fixing bugs but making new skins ?
Just got my second leave buster, because of this nonsense. At least do not penalize players who did not connect to the match. It is absolutely not fair to get your honor level locked as well as being thrown into 20min waiting queues just because due to some bug you cannot successfully connect into the game.