107 replies to this topic

[SpaniardAE]

try the older password , as this is a copy of the actual account sometime ago

[Calliss]

41 min unlocking and saving and modifying and saving, at last entering first match.

[NRP]

Not sure where else to post this, but it takes a loooooooong time to save changes go a mech's loadout.

[SpaniardAE]

ive actually made a new hairstyle with my hands.... messing around with my hair waiting for the loadout to save

[Kampfer]

WARNING! DANGER!
Do not change mech load out!

[Mechteric]

Stonefalcon, on 15 June 2014 - 10:36 AM, said:

Took about 5 minutes to save a weapons loadout, about halfway through I remembered modules...

Seems better now, at first it was taking more than 30 seconds per unlocked skill, but then went down to 10 or 5 just a few minutes ago. Also now saving a mech config is quick. The server must have finally caught up to demands.

[HoggerOne]

Nikolai,

Thanks for the update

[Beaker Meeps]

I'm able to get through and log in but none the pre-ordered mechs are available. :-/

[SpaniardAE]

what about the stuck on loadout... still waiting been like 20 mins

[Flatfoot]

well ive tried every password ive used... Still a no go invalid password for me.

[Nurgle256]

all working fine for me at present, as if in the normal client

[HoggerOne]

Same here all working great

[GentlemanBryan]

The only issue I have at this time is it is taking a long time to save... I will continue to update...

[MilesTeg1982]

well, now trying for 80 minutes (!) to get past the "connecting" ...

[RupeyUK]

Flatfoot, on 15 June 2014 - 11:03 AM, said:

well ive tried every password ive used... Still a no go invalid password for me.

hey, last time there was an issue with a "funny" character in some ones password. I think it didn't compute in the PTS. No way to change it for this test if this is the case as the data was taken from a snapshot earlier and I guess won't be refreshed.

[ei8ht]

Anyways, seems pretty stable now. Finding matches now seems to be rather quick too. If you're still having trouble, close the client and retry.
'

[GentlemanBryan]

Would you please look at the SRMs.....they don't appear to be causing damage or maybe they are causing some damage and we or not noticing... please advise.

[Argent Usher]

Login error:

There is an update available. Please shutdown and run the patcher.


Repairtool: no error.
Patcher: autopatch

bootstrap_patcher_log

15.06.2014 21:34:45 - main - Config file: C:\Program Files (x86)\Piranha Games\MechWarrior Online\Bin32\PatchBot.cfg
15.06.2014 21:34:45 - main - Setting null proxy to False
15.06.2014 21:34:45 - main - Local patcher version: 24
15.06.2014 21:34:45 - main - Checking patch inventory.
15.06.2014 21:34:45 - main - Connecting for maintenance check.
15.06.2014 21:34:48 - main - Fetching patch inventory data..
15.06.2014 21:34:48 - main - Remote patcher version: 24
15.06.2014 21:34:48 - main - Already up-to-date

frontend_patcher_log

15.06.2014 21:34:52 - main - Config file: C:\Program Files (x86)\Piranha Games\MechWarrior Online\Bin32\PatchBot.cfg
15.06.2014 21:34:52 - main - Setting null proxy to False
15.06.2014 21:34:52 - main - Local frontend version: 159
15.06.2014 21:34:52 - main - Checking patch inventory.
15.06.2014 21:34:52 - main - Connecting for maintenance check.
15.06.2014 21:34:52 - main - Fetching patch inventory data..
15.06.2014 21:34:52 - main - Remote frontend version: 159
15.06.2014 21:34:54 - patch - Complete!
15.06.2014 21:34:54 - main - Complete!
15.06.2014 21:34:56 - main - User closing the patcher...

[Jorill]

I am getting that md5 error when updating the public test install. I've tried the standard reinstall/etc people have suggested for the normal version, anyone have other ideas or anything specific that works for the public test version?

I've also run the repair tool, but do I need to do anything different (or is there another utility) to have it specifically look at the test install folder?

[KuroNyra]

the 17th june. It's gonna rock.