8 replies to this topic

[Ziggycuff]

I have tried reinstalling no dice... Been having this problem since the first time I logged in and out about 8 hours ago.

[Ziggycuff]

bump, really would love an answer to this, i looked just about everywhere for an answer but seems there is nothing..

[Darkwave]

i get the same problem. Failed to sync account on load so manually login in-game and it just sits there "logging in"

edit:
so i had just thought about it and decided to put in a full exception to the entire hawken folder in my anti-virus (kaspersky) and sure enough worked fine after.

Edited by Darkwave, October 26 2012 - 03:18 PM.

[T5ZK]

The same error here too. First login is successful, but the second one after "Loging in, please wait..." is ten out of ten unsuccessful. 100% unplayable.

[h0rus]

Having this problem right now. "Synch : Error!"

[Ziggycuff]

im pretty sure naming your mechs gives you this error. Please fix meteor

[Naelron]

Having this issue as well.  I got logged in once, couldn't connect to any games though, and logged off.  Try to log back on, and no dice.  Oddly enough, what Ziggycuff said may be true, as I did name my mech.  It also seems as though my account partially syncs, as instead of saying Recruit XXX, it instead says my actual callsign, but then proceeds to fail.

[Ziggycuff]

In order for our accounts to be able to log in again, I think our mechs must be named back to default, not sure if the name of them is client side or server side, if its client side there may be a way to fix it without logging into the game, if its server side the administrators must change it manually to fix it. Hopefully everything wipes by the next beta events.

Though then again, i could be wrong about the whole naming mechs thing, but i made 3 accounts to experiment with this, all three lost the connection with the host after one game post mech rename. Then the error started happening in all three accounts.

I'd test this more, but I need more beta keys and emails.

[Dukeleto]

Same prob, and STILL can't log in a 2nd time in game, as the @ key is bound to the console :-p