I'm just trying to get the client updated for tomorrow's open beta and as soon as I enter my email and password the client crashes.
A box pops up and says "CrypticError:Oops!" Your Cryptic application has crashed. To help us out, please indicate what was going on at the time of the crash, while we gather Information"
Sorry if this has been answered before but if someone can point me to a possible fix that would be greatly appreciated.
Thanks
Post edited by thoale on
0
Comments
hellsparkMember, Neverwinter Beta Users, Neverwinter Guardian UsersPosts: 0Arc User
same here, the crash happens directly when i press login
EDIT:
Fixed my issue i turned of my teamviever client and now the nw game starts fine.
omg are you serious? I'm at work using teamviewer to connect to my home computer and trying to get it updated lol. I guess i'll wait until I get home tonight and turn off teamviewer
Thanks for the info!
0
herzogMember, Neverwinter Beta Users, Neverwinter Guardian UsersPosts: 1Arc User
edited April 2013
OMG thank you. I thought something was wrong with my login info. I cant believe team viewer being open in the background kept it from logging in.
I'm having the same problem but I do not have Teamviewer, whatever that is.
How can I fix this?
Same. I don't have Teamviewer. More disturbing, it was working fine until today (Hero of the North, so I've been on and of since Thursday). I'm guessing it may be folding under the weight of users - which sucks, because I can't even log in and take advantage of my priority in the queue.
i dont have any other programs runnign .. I had no problem in my 3 day headstart and now today i get the whitebox of death for a launcher.. it sayd loading then disappears and still a white box
0
redfoxxx200Member, Neverwinter Beta UsersPosts: 2Arc User
Same. I don't have Teamviewer. More disturbing, it was working fine until today (Hero of the North, so I've been on and of since Thursday). I'm guessing it may be folding under the weight of users - which sucks, because I can't even log in and take advantage of my priority in the queue.
It is the sudden high user volume, I would have hoped that thay were prepared for the huge amount of people going to enter game !
I don't have teamviewer on, but that is fine. This was most likely going to happen ( Not that I wanted it to ). There are probably around 1-2 million people trying to login.
ravesoja77Member, Neverwinter Beta UsersPosts: 2Arc User
edited May 2013
Game crashes everywhere...char. creation, loading screens, launcher, log-in. You would think that these guys never launched a game before. I guess I will wait till launch and MAYBE the game will be playable. Hope the game isn't dead by then.
So to all you people still crashing at login, you MUST DISABLE all p2p remote clients. I have PhoneMyPC, Splashtop Streamer, and Teamviewer. I tried disabling just teamviewer and no avail. You must disable all remote clients because of their ability to force the display redirect to the mobile client. Obviously this is not going to help all the crashes, but at least we can log in now.
Comments
EDIT:
Fixed my issue i turned of my teamviever client and now the nw game starts fine.
omg are you serious? I'm at work using teamviewer to connect to my home computer and trying to get it updated lol. I guess i'll wait until I get home tonight and turn off teamviewer
Thanks for the info!
Thanks
I'm having the same problem but I do not have Teamviewer, whatever that is.
How can I fix this?
Thank You
Same. I don't have Teamviewer. More disturbing, it was working fine until today (Hero of the North, so I've been on and of since Thursday). I'm guessing it may be folding under the weight of users - which sucks, because I can't even log in and take advantage of my priority in the queue.
It is the sudden high user volume, I would have hoped that thay were prepared for the huge amount of people going to enter game !
would be nice to have someone post from the company to tell us whats up or if they know whats up / how long it will take to fix
It would be nice if that crash reporter at least had the callstack or pointer showing when it sent the report.