Jump to content

Two Large Patches Today?


44 replies to this topic

#21 Omnicidal Kitten

    Member

  • Pip
  • Ace Of Spades
  • Ace Of Spades
  • 12 posts
  • LocationOregon

Posted 09 January 2014 - 12:00 AM

Tried everything I could think of. Nuked MWOupdate folder, ran repair tool, even swapped out all the .dll's (namely the frontend_version.dll and the patcher_version.dll) and I still got the same error log in which the patcher didn't recognize the game's version and tried to do a full update. Finally gave up and reinstalled; gonna let it download all its stuff overnight and see what happens come morning.

#22 phulcrum

    Member

  • PipPip
  • Ace Of Spades
  • Ace Of Spades
  • 33 posts

Posted 09 January 2014 - 12:08 AM

I tried reinstalling and had the same patch issues after that still.

#23 Shockblastwave

    Rookie

  • Survivor
  • Survivor
  • 4 posts

Posted 09 January 2014 - 12:10 AM

Well, lots of us seem to have the same issue, patcher is comparing our patch version to PGIs and finding a mismatch. Problem solved, now to wait for the fix.

#24 Broskadamus

    Rookie

  • Overlord
  • Overlord
  • 4 posts

Posted 09 January 2014 - 01:18 AM

View PostShockblastwave, on 09 January 2014 - 12:10 AM, said:

Well, lots of us seem to have the same issue, patcher is comparing our patch version to PGIs and finding a mismatch. Problem solved, now to wait for the fix.


Sadly, that sounds like the issue. I'm in the process of trying out various fixes but judging the situation, this seems to be the most logical. At least until someone comes through and informs us of the situation.

#25 CapnKirk13

    Member

  • PipPip
  • Fire
  • Fire
  • 41 posts

Posted 09 January 2014 - 07:55 AM

PGI needs to get on fixing this as it is potentially costing those affected Premium Time and possibly bandwidth charges for going over allotted amount of data due to the repeated huge downloads.

#26 Valorian

    Rookie

  • 1 posts

Posted 09 January 2014 - 09:00 AM

Same problem here...I've downloaded that 3.7 meg patch 4 times now. Every time I log out it makes me patch again when I start the client.

#27 phulcrum

    Member

  • PipPip
  • Ace Of Spades
  • Ace Of Spades
  • 33 posts

Posted 09 January 2014 - 09:40 AM

Still having the same issue this morning. Waiting for a reply from support.

I'm downloading the patch now. I will try pausing it when it is close to finished then I'll make a copy of my MWOUpate folder. Hopefully every time I need to relaunch I can copy the almost completed patch file back into my MWO folder and it will pick up where it left off at the last few megabytes to limit downtime. I'll report back on this later.

*UPDATE* That didn't work as I thought it would. Looks like I'm stuck having MWO open all day.

Edited by phulcrum, 09 January 2014 - 11:10 AM.


#28 Omnicidal Kitten

    Member

  • Pip
  • Ace Of Spades
  • Ace Of Spades
  • 12 posts
  • LocationOregon

Posted 09 January 2014 - 01:28 PM

Aaaand the last 24 hours of premium time I had expired before I could sit down and play again.

Grand.

#29 Weaselball

    Member

  • PipPipPipPipPipPipPip
  • Ace Of Spades
  • Ace Of Spades
  • 670 posts
  • LocationHell's ********, AKA Fresno.

Posted 09 January 2014 - 02:26 PM

I like how there is absolutely no response from PGI. Not even a "we're looking into this guys," reply.

Stellar customer satisfaction. Keep up the great work PGI technical team.

Also, I got it to work yesterday (did nothing, just launched an hour later after I refused to redownload the patches and it worked). But today same issue. GG.

#30 _____

    Member

  • PipPipPipPipPipPipPip
  • The Cub
  • The Cub
  • 742 posts

Posted 09 January 2014 - 03:33 PM

Has anyone tried this? Delete the MWOUpdate folder. Run the repair tool. Launch mwo. Let the patch download for 10 seconds. Kill the mwo*.exe processes in Windows Explorer. Relaunch the client. Seems to work for me.

#31 Grendel408

    Member

  • PipPipPipPipPipPipPipPipPip
  • Bad Company
  • Bad Company
  • 2,611 posts
  • LocationBay Area, California

Posted 09 January 2014 - 03:47 PM

No word from the Devs yet either? Looks to me like a widespread problem they need to crack down on.

#32 phulcrum

    Member

  • PipPip
  • Ace Of Spades
  • Ace Of Spades
  • 33 posts

Posted 09 January 2014 - 04:13 PM

I still have not gotten a reply from the support ticket I submitted.

View PostBlackhawkSC, on 09 January 2014 - 03:33 PM, said:

Has anyone tried this? Delete the MWOUpdate folder. Run the repair tool. Launch mwo. Let the patch download for 10 seconds. Kill the mwo*.exe processes in Windows Explorer. Relaunch the client. Seems to work for me.


Do you only have to do this once? Or every time you want to run the game?

#33 Weaselball

    Member

  • PipPipPipPipPipPipPip
  • Ace Of Spades
  • Ace Of Spades
  • 670 posts
  • LocationHell's ********, AKA Fresno.

Posted 09 January 2014 - 04:30 PM

Tentative workaround:

I just set my Network Card's DNS manually, configured with Google's public DNS (8.8.8.8, and 8.8.4.4). Now it seems to work. Will post here if it stops working.

Please note: Setting your DNS to Google's public DNS might have averse side-effects on your browsing or other games. Thankfully if any problems arise you can simply set your DNS back to what it was originally (either auto detected, or whatever you had set manually prior to the change)

EDIT: This workaround seems to still be working. I've closed and relaunched MWO multiple times, over the course of an hour or so, and the results are still looking good. Of course this COULD be 100% coincidence, but it might be worth a shot to anyone having difficulty connecting to MWO.

Also, I wouldn't advise changing your DNS if you're not comfortable with doing so, or know how to reverse the change. I mean, editing ones DNS isn't a huge deal (it's not like you're going to brick your machine if you mess it up), but there can be side-effects as mentioned above. So do this at your own discretion.

Edited by Weaselball, 09 January 2014 - 06:23 PM.


#34 phulcrum

    Member

  • PipPip
  • Ace Of Spades
  • Ace Of Spades
  • 33 posts

Posted 09 January 2014 - 04:57 PM

Weaselball, I want to hug you. This works like a charm.

#35 ShinVector

    Liao Mercenary

  • PipPipPipPipPipPipPipPipPip
  • The Hammer
  • The Hammer
  • 3,711 posts

Posted 09 January 2014 - 05:29 PM

View PostWeaselball, on 09 January 2014 - 02:26 PM, said:

I like how there is absolutely no response from PGI. Not even a "we're looking into this guys," reply.
Stellar customer satisfaction. Keep up the great work PGI technical team.


I have been noticing as well, like they have little to no man power left handle these things.
I hope it is not that they don't give a damn and rather have the volunteer mods handle it ?


View PostWeaselball, on 09 January 2014 - 04:30 PM, said:

Tentative workaround:

I just set my Network Card's DNS manually, configured with Google's public DNS (8.8.8.8, and 8.8.4.4). Now it seems to work. Will post here if it stops working.


This just means that PGI changed their patch server IP address or something on the DNS and it taking to long to propagate to all the DNS servers... ? Who knows but PGI...

Edited by ShinVector, 09 January 2014 - 05:31 PM.


#36 Weaselball

    Member

  • PipPipPipPipPipPipPip
  • Ace Of Spades
  • Ace Of Spades
  • 670 posts
  • LocationHell's ********, AKA Fresno.

Posted 09 January 2014 - 05:29 PM

Please note: Setting your DNS to Google's public DNS might have averse side-effects on your browsing or other games. Thankfully if any problems arise you can simply set your DNS back to what it was originally (either auto detected, or whatever you had set manually prior to the change)

#37 ShinVector

    Liao Mercenary

  • PipPipPipPipPipPipPipPipPip
  • The Hammer
  • The Hammer
  • 3,711 posts

Posted 09 January 2014 - 05:35 PM

View PostWeaselball, on 09 January 2014 - 05:29 PM, said:

Please note: Setting your DNS to Google's public DNS might have averse side-effects on your browsing or other games. Thankfully if any problems arise you can simply set your DNS back to what it was originally (either auto detected, or whatever you had set manually prior to the change)


PGI needs to let us know what is the domain name that is causing the problem so, the players can verify with 'nslookup' their respective ISP's DNS servers had been updated with the correct IP.

Anyway you are right about the possible slow down. CDN's like Akamai need you to use your local ISP's DNS servers so, they can redirect you to closest servers whether host windows and anti virus patches, etc...

#38 DodgerH2O

    Member

  • PipPipPipPipPipPip
  • 245 posts

Posted 09 January 2014 - 05:45 PM

Just checked my email, got a response from support and they seem more puzzled than we are. I gave a link to this forum topic along with the requested information, hopefully that will help them. Unfortunately it's probably now after hours for PGI's support team, I know it's after my work hours.

Here's hoping that the issue is resolved soon.

#39 CapnKirk13

    Member

  • PipPip
  • Fire
  • Fire
  • 41 posts

Posted 09 January 2014 - 06:57 PM

Try this: http://mwomercs.com/...-37gb-download/

Edited by CapnKirk13, 09 January 2014 - 09:12 PM.


#40 _____

    Member

  • PipPipPipPipPipPipPip
  • The Cub
  • The Cub
  • 742 posts

Posted 09 January 2014 - 07:58 PM

View Postphulcrum, on 09 January 2014 - 04:13 PM, said:

I still have not gotten a reply from the support ticket I submitted.

Do you only have to do this once? Or every time you want to run the game?


Just once. Actually it seems like you just have to close and re-run MWO. Don't have to do the abort thing.

Edited by BlackhawkSC, 09 January 2014 - 08:02 PM.






1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users