[New Users] Please note that all new users need to be approved before posting. This process can take up to 24 hours. Thank you for your patience.
Check out the v.256 - The Dark Ride: Limbo Patch Notes
here!
Bug Type: Login
World: Login
IGN: Doesn't matter, happens to all of my characters
Date/Time of Occurrence: Repeated instances, especially after the v.180 update
Steps to reproduce: Log into the game using the Game Launcher [see attached video]
VIDEO:
Video description copied here:
Recorded the afternoon of February 8th, 2017, in sequential attempts.
Task manager is open to verify the crashes.
Keep in mind, the nature of these crashes is absolutely random. I just happened to get 4 in a row, and I am not kidding whenever I say that this happened to me 3 more times before I decided to boot up my screen recorder.
However, sometimes, whenever I perform the actions performed in this video (particularly in attempts 3 and 4), I successfully log into the game. These aren't necessarily "I can't log in" glitches. These are "will I log in, or will it crash" problems.
(Obviously, the parts that disclose my account information are trimmed out as seamless as I could get it to be.)
Comments
OS: Win 10 Ver.1511 x64.
It didn't happen at EMS v.117 and below.
I'm afraid that I have reported about these game crashes but nothing was done to better fix it.
It's even worser than how it was!!
New crash type issue by logining in to Luna ch1
imgur.com/a/5q2ef
Client closed for me after entering into a character, too.
Please put attention!!!
Thank you
Other crash issues are due to lack of loading screen when game data is in loading progress.
Need a loading screen like this:
imgur.com/iGd0n3t
However, it's impossible to play without it.
I believe nexon should fix this tool or replace it with another tool such as XignCode (was used by the Europe Service) and there were never client crashes there when the XignCode security tool was used.
This didn't happen to me when people first initially had this issue.
However since the past few patches I eventually came across this issue too, and now I have to use this method.