Closed jacobmischka closed 8 years ago
Here is a log taken by the League of Legends patcher when it thinks it's corrupt in case it helps. http://pastebin.com/3ygyXGTV
If I run the game after "repairing" the files and without running the patch again, only a select few icons in the shop are the customary red squares, and I believe they're the same ones that changed with the most recent patch (4.1.14 I think).
Oh and once I actually get the game accepting that nothing is corrupt, everything is fine and all the icons are great.
It seems to be a problem releated to the last patch, so not much we can do I suggest you to patch wine with this patch http://pastebin.com/xSNJjkMY as i said in Wine AppDB
http://appdb.winehq.org/objectManager.php?sClass=version&iId=19141
Oh, I suppose I should have checked there before posting here. I'm actually using an older, patched version of wine for League (the 1.7-LeagueOfLegends binary that I downloaded with POL [didn't actually use POL for anything aside from downloading the binary]), so I'm having no troubles playing the game aside from the "corrupted" thing. Didn't realize this patch caused so many problems. Thanks, I'll be sure to check the appdb page before posting here from now on.
It looks like this may be the culprit:
000092.744| 0.0000kb| 0.0000kb added| WARN| r3dTexture EX: - not found. Dummy texture created. 000100.231| 0.0000kb| 0.0000kb added| ERROR| Riot::RADS::Reader::ProjectListing::ArchiveFile::Open: Mismatch between manifest size and archive size for: DATA/Summoner/SummonerBlockLibraryClient.xml 000100.232| 0.0000kb| 0.0000kb added| ERROR| Riot::RADS::Reader::ProjectListing::Open: RADS failed to open archive file "SummonerBlockLibraryClient.xml". Signaling soft repair. 000100.232| 0.0000kb| 0.0000kb added| ERROR| RadsOpenFile: RADS cannot open file "DATA\Summoner\SummonerBlockLibraryClient.xml". It's in the manifest, but failed to open. 000100.233| 0.0000kb| 0.0000kb added| ERROR| Failed to load Behavior Tree Node Definition file: DATA\Summoner\SummonerBlockLibraryClient.xml!
It's pretty strange, you can check if this file is modified using the repair command btw there are some patches for wine, i suggest using these Take a look on the LoL Wine AppDB page
I know, I even posted one (maybe the less-hacky available out there) http://bugs.winehq.org/show_bug.cgi?id=34480#c12
However they say they will do a major overhaul of the d3d code soon and hopefully tackle this allocation issue so they won't pick it in now.
Since I prefer using wine from the ubuntu ppa instead of compiling my own every time there's a new version I like your utility better, however deleting the SOFT_REPAIR file before opening LoL is just fine for me.. it's just I saw this issue and wanted to throw my 2c in case someone wanted to try to investigate further the issue.
greets
Damn, I've just been repairing and repatching every time I want to open the game, I didn't know you could just delete the SOFT_REPAIR file. Thanks a lot, I'll just add deleting that to my launcher script and now I won't have to worry about it again, as long as the path doesn't change.
It looks like it's not asking for a repair anymore, maybe RIOT read the wine bug :)
Oh really? Guess I can remove the rm command from my launcher now then. Thanks lol
Oh, yes. I was also wondering if Riot touched something specifically because of us wining in WineHQ. This also happened some days after I updated LoL in WineHQ and explained the workaround. I suppose that it is possible that they took us Linux users in consideration. However given recent history it is regretfully not so plausible. They could have changed it for another reason that is not connected to Linux Users. After all - there was initially a purely Linux version of their client and they stopped it. On the other hand - if we can show Riot that the Linux community is big and strong. That we are actively playing, interacting, purchasing and so on. That we really want native support for Linux and that more and more people do play on Linux. They should react in some way, at the very least tell us to go ..... ourselves directly rather than just keeping quiet on the matter.
Really, what do you think on this idea for community-driven pressure? I'd be happy to coordinate it.
Not going to happen. Riot doesn't even fix game-breaking problems with their game, there's no way they're going to make a client for such a small market share.
the only annoying thing atm is the FMOD "hang" when loading a new game...50sec or so
i think they removed this check on purpose, because they know about the texture hack
Ever since the patch a few days ago, League of Legends thinks it's corrupt after running the patch. For some reason, I'm able to "repair" the files, run the patch, then run the game. But after rebooting it thinks it's corrupt again. I'm using the most recent version of LoL-Linux-Tools.