SightstoneOfficial / LegendaryClient

LegendaryClient, rebooted
69 stars 59 forks source link

LC saying my LoL is not updated #140

Closed TipicoDev closed 9 years ago

TipicoDev commented 9 years ago

(10/12/2014 20:00) [LOG]: LegendaryClient Has Finished Patching (10/12/2014 20:00) [LOG]: LegendaryClient Started Up Successfully (10/12/2014 20:00) [LOG]: Starting Patcher (10/12/2014 20:00) [LOG]: DataDragon Version: 4.21.5 (10/12/2014 20:00) [LOG]: Current DataDragon Version: 4.21.5 (10/12/2014 20:00) [LOG]: DDragon Version (LOL Version) = 4.21.5 (10/12/2014 20:00) [LOG]: Client Version: 4.21.5 (10/12/2014 20:00) [LOG]: Air Assets Version: 0.0.1.120 (10/12/2014 20:00) [LOG]: Current Air Assets Version: 0.0.1.120 (10/12/2014 20:00) [LOG]: Trying to detect League of Legends GameClient (10/12/2014 20:00) [LOG]: League of Legends is located at: D:\Riot Games\League of Legends\ (10/12/2014 20:00) [LOG]: Latest League of Legends GameClient: 0.0.1.69 (10/12/2014 20:00) [LOG]: Checking if League of Legends is Up-To-Date (10/12/2014 20:00) [LOG]: League of Legends is not Up-To-Date. Please Update League Of Legends (10/12/2014 20:00) [EXCEPTION]: A first chance exception was thrown (10/12/2014 20:00) [EXCEPTION]: O thread de chamada não pode acessar este objeto porque ele pertence a um thread diferente. (10/12/2014 20:00) [EXCEPTION]: em System.Windows.Threading.Dispatcher.VerifyAccess() (10/12/2014 20:00) [UNHANDLEDEXCEPTION]: An unhandled exception was thrown (10/12/2014 20:00) [UNHANDLEDEXCEPTION]: O thread de chamada não pode acessar este objeto porque ele pertence a um thread diferente. (10/12/2014 20:00) [UNHANDLEDEXCEPTION]: em System.Windows.Threading.Dispatcher.VerifyAccess() em System.Windows.DependencyObject.SetValue(DependencyProperty dp, Object value) em System.Windows.UIElement.set_IsEnabled(Boolean value) em LegendaryClient.Windows.PatcherPage.b__0() em System.Threading.ThreadHelper.ThreadStart_Context(Object state) em System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) em System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) em System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) em System.Threading.ThreadHelper.ThreadStart()

after this, LC stop working. My LoL is updated, lol

Dispersia commented 9 years ago

are you using the latest version on the release page? If not, please try that version, if you are, I will look into this.

TipicoDev commented 9 years ago

yes i'm

Dispersia commented 9 years ago

is your league of legends actually located in D:\Riot Games\League of Legends\? in that folder there should be a lol.launcher.exe, and on top of that is that the version you actually use

TipicoDev commented 9 years ago

nope, its here: D:\Program Files\Riot Games\League of Legends

how can I change the league folder in LC?

Dispersia commented 9 years ago

I will make a button in a second that will allow you to change it, give me a minute. I've noticed that is a decently common error so might as well fix it now, if you're using the splash you'll get the update automatically, give me a minute to make ^^ sorry for the inconvenience

TipicoDev commented 9 years ago

splash? I only downloaded the release

Dispersia commented 9 years ago

in the zip file there should be something named LCStartUpSplash, if you are using that to start the client and not running it from the Client folder, it should now update automatically. I can't test it atm as I'm on my phone but it made sense in my head, so tell me if it works ^^ (if you want to update manually simply delete your current folder, go to release page and download 2.2.0.1)

a button should come up when it fails to go on that will let you select the correct folder.

TipicoDev commented 9 years ago

i updated it, but it still crashes when i open: http://prntscr.com/5fgp7z cant even search for the button

Dispersia commented 9 years ago

Redownload 2.2.0.1, I'm not going to push a release from that. simply go to the releases page and redownload, it's still 2.2.0.1

TipicoDev commented 9 years ago

still crashing when i open,

(10/12/2014 23:20) [LOG]: LegendaryClient Started Up Successfully (10/12/2014 23:20) [LOG]: Starting Patcher (10/12/2014 23:20) [EXCEPTION]: A first chance exception was thrown (10/12/2014 23:20) [EXCEPTION]: Não foi possível carregar arquivo ou assembly 'mscorlib.XmlSerializers, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' ou uma de suas dependências. O sistema não pode encontrar o arquivo especificado. (10/12/2014 23:20) [EXCEPTION]: em System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks) em System.Reflection.RuntimeAssembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks) (10/12/2014 23:20) [LOG]: DataDragon Version: 4.21.5 (10/12/2014 23:20) [LOG]: Current DataDragon Version: 4.21.5 (10/12/2014 23:20) [LOG]: DDragon Version (LOL Version) = 4.21.5 (10/12/2014 23:20) [LOG]: Client Version: 4.21.5 (10/12/2014 23:20) [LOG]: Air Assets Version: 0.0.1.120 (10/12/2014 23:20) [LOG]: Current Air Assets Version: 0.0.1.120 (10/12/2014 23:20) [LOG]: Trying to detect League of Legends GameClient (10/12/2014 23:20) [LOG]: League of Legends is located at: D:\Riot Games\League of Legends\ (10/12/2014 23:20) [LOG]: Latest League of Legends GameClient: 0.0.1.69 (10/12/2014 23:20) [LOG]: Checking if League of Legends is Up-To-Date (10/12/2014 23:20) [LOG]: League of Legends is not Up-To-Date. Please Update League Of Legends (10/12/2014 23:20) [EXCEPTION]: A first chance exception was thrown (10/12/2014 23:20) [EXCEPTION]: O thread de chamada não pode acessar este objeto porque ele pertence a um thread diferente. (10/12/2014 23:20) [EXCEPTION]: em System.Windows.Threading.Dispatcher.VerifyAccess() (10/12/2014 23:20) [UNHANDLEDEXCEPTION]: An unhandled exception was thrown (10/12/2014 23:20) [UNHANDLEDEXCEPTION]: O thread de chamada não pode acessar este objeto porque ele pertence a um thread diferente. (10/12/2014 23:20) [UNHANDLEDEXCEPTION]: em System.Windows.Threading.Dispatcher.VerifyAccess() em System.Windows.DependencyObject.SetValue(DependencyProperty dp, Object value) em System.Windows.UIElement.set_IsEnabled(Boolean value) em LegendaryClient.Windows.PatcherPage.b__0() em System.Threading.ThreadHelper.ThreadStart_Context(Object state) em System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) em System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) em System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) em System.Threading.ThreadHelper.ThreadStart()

Dispersia commented 9 years ago

redownload one last time, that was me being stupid. Apologies

TipicoDev commented 9 years ago

happens ¯_(ツ)_/¯ everything seems to be working now, thanks

TipicoDev commented 9 years ago

sorry, but just a few questions: the options like offline in chat, insta-pick and ranked exploit, do I have to compile myself to get them working? also, can you add the ping checker for BR server? thanks for all again

Dispersia commented 9 years ago

offline is a normal feature, insta-pick doesn't need to be recompiled but you have to figure it out (thanks for reminding me that is supposed to not require dev mode anymore), but yes, for exploits such as the ranked exploit you have to compile it as it will not be supported here.

and if you wish to talk feel free to send me an email (its on my github page) and I would be more than happy to talk, however issues aren't the place for conversations ;)