49 replies to this topic

[Podex]

Does anyone have Russ's phone number? Heh heh

[Chagatay]

Good to go all works again

Edited by Chagatay, 03 January 2015 - 12:05 PM.

[Thragen]

Podex, on 03 January 2015 - 12:01 PM, said:

Does anyone have Russ's phone number? Heh heh

I don't do Twitter but if you do, I would post there!

[CgMass]

I'm having the same issue. Both of my desktop and my laptop are on the 2nd pass through of downloading install base. I played on the laptop just fine yesterday and haven't experienced this issue before.

[Podex]

I'll do it. What is his Twitter account?

[Kreuger]

Clean Install and patcher still said "patch". Instead I ran repair tool. It found all this ...

MISMATCHED FILES:
G:\MWO\MechWarrior Online\Bin32\CryRenderD3D11.dll-->http://patcher.mwomercs.com/patch/Production/live/Bin32/CryRenderD3D11.dll
G:\MWO\MechWarrior Online\Bin32\CryRenderD3D9.dll-->http://patcher.mwomercs.com/patch/Production/live/Bin32/CryRenderD3D9.dll
G:\MWO\MechWarrior Online\Bin32\frontend_version.dll-->http://patcher.mwomercs.com/patch/Production/live/Bin32/frontend_version.dll
G:\MWO\MechWarrior Online\Bin32\MWOClient.exe-->http://patcher.mwomercs.com/patch/Production/live/Bin32/MWOClient.exe
G:\MWO\MechWarrior Online\Bin64\CryRenderD3D11.dll-->http://patcher.mwomercs.com/patch/Production/live/Bin64/CryRenderD3D11.dll
G:\MWO\MechWarrior Online\Bin64\CryRenderD3D9.dll-->http://patcher.mwomercs.com/patch/Production/live/Bin64/CryRenderD3D9.dll
G:\MWO\MechWarrior Online\Bin64\MWOClient.exe-->http://patcher.mwomercs.com/patch/Production/live/Bin64/MWOClient.exe
G:\MWO\MechWarrior Online\build_info.xml-->http://patcher.mwomercs.com/patch/Production/live/build_info.xml
G:\MWO\MechWarrior Online\Game\ForestColony_ig.pak-->http://patcher.mwomercs.com/patch/Production/live/Game/ForestColony_ig.pak
G:\MWO\MechWarrior Online\Game\GameData.pak-->http://patcher.mwomercs.com/patch/Production/live/Game/GameData.pak
G:\MWO\MechWarrior Online\Game\GameModeAssets.pak-->http://patcher.mwomercs.com/patch/Production/live/Game/GameModeAssets.pak
G:\MWO\MechWarrior Online\Game\Levels\badlands\level.pak-->http://patcher.mwomercs.com/patch/Production/live/Game/Levels/badlands/level.pak
G:\MWO\MechWarrior Online\Game\Levels\frost\level.pak-->http://patcher.mwomercs.com/patch/Production/live/Game/Levels/frost/level.pak

After fixing, it appears to be okay. I am logging in now. <crosses fingers>

Edited by Kreuger, 03 January 2015 - 12:17 PM.

[Thragen]

Podex, on 03 January 2015 - 12:16 PM, said:

I'll do it. What is his Twitter account?

There is a link to his Twitter account in the Developer Tracker link in the General Forum.

Edited by Thragen, 03 January 2015 - 12:20 PM.

[Chagatay]

Well spoke too soon as the please re-run patch box came up on login (crap).

Something is wonky on their end with the patching bootstrap operation. The main issue is the mismatch between the local and remote versioning as discussed earlier in this thread. Earlier logs everything is just fine however that is not the case now.....

Edited by Chagatay, 03 January 2015 - 12:23 PM.

[Chagatay]

Update:
Switching back to 32-bit mode seemed to kick off the game and I got to mechlab. Try it if you haven't.
Either way don't hit the patch button!!!!
Do the repair verify check and re-launch to get it to work.

As a further experiment, I exited the game and relaunched and it wants to patch again!!! So once you get in don't shut it down (unless you really want to verify your files....again arggggg).

Edited by Chagatay, 03 January 2015 - 12:45 PM.

[LordSkippy]

Judging by what people have said in this thread, and what I experienced with starting and stopping the launcher while trying various things, I think the server that tells the patcher what version is what is on the fritz. If you start getting this error, try closing and restarting the launcher a few times.

[Podex]

I sent a tweet to Russ. We'll see what happens.

If anyone autopatches, they are screwed, I guess.

[Thragen]

After a clean install and running the patcher 2 times, I can log in and see everything using the 32 bit option. I then logged out completely, exited the game, and relogged in ( under 32 bit ) without any problems.

I gotta go to a late lunch with my mwo gang. Hopefully, when I get back it will still work.

[Podex]

Is the problem the 64 bit client? I kinda suspected that when it started throwing errors

[LordSkippy]

Podex, on 03 January 2015 - 01:39 PM, said:

Is the problem the 64 bit client? I kinda suspected that when it started throwing errors

No, I'm logged in now with the 64-bit client. Much more likely that the service that tells the launcher what the latest version is is having issues. Besides, it hasn't gotten to the 64-bit part yet, the launcher is still 32-bit.

[MoonUnitBeta]

Y2K15 is upon us!

[Molecule]

This is just superb...

I come back from a 1+ year break, downloaded the installer, start the installer (clicked patch).......waited for 2 mins when the client closes without error message. I start it up again and same story. I also ran the fixing tool which also crashes while downloading one of the .pak files (of course it finds none of the game files in the right place so mostly all content is marked as "mismatch"...)

I really am speechless now because this still feels like a Alpha version and not a released game.

I will "uninstall" (the bit that actually installed I guess) for the Xth time now and try again.

[banjoe]

Happened to me as well. I had to use repair tool 3 times to get MWO up and running

[Molecule]

I think I used the repair tool like 5 times now and this one also crashes each time while downloading "applejak.pak".

"Frustrating" is really an understatement in this case.

[Marshael]

Same problem here, sometimes I can exit out of launcher and then restart and I can get into the game. Other times I get past the intro screens and then it tells me I need to patch. I think the problem is on PGI's end. I hope PGI understands that this error is losing them money, I will not spend one more dime until this is fixed! Come on PGI fix the bugs!

[Podex]

Bugs happen. For all we know, it's just a poorly timed corruption of a file on the server. It's a pain, but at least we have a workaround.

PGI has worked pretty hard on this game and they deserve a vacation. They should be back today, so you may want to put in a support ticket.