17 replies to this topic

[Primetimex]

I was able to get into MWO the first time after patching today, now on 2nd and 3rd tries it got stuck at "CONNECTING" and hard crashed.

Good job PGI - can anyone help?

*This is the quality of **** that PGI puts out yet they still expect us to support MWO.

[LowKey]

I am having the exact same issue. The launcher loads and after signin the the game hangs and then freezes at the "connecting" after the loading "mechbay" screen.

[Fighting Irish]

Lads,
i didn't pay over a hundred bucks for this craic...

someone know 1) why this is happening and 2) how is it resolved...?

jeez.. who releases patches without Q&A??

Edited by Fighting Irish, 04 February 2014 - 11:10 PM.

[Primetimex]

Fighting Irish, on 04 February 2014 - 11:09 PM, said:

Lads,
i didn't pay over a hundred bucks for this craic...

someone know A) why this is happening and how is it resolved...?

jeez.. who releases patches without Q&A??

Are you new to MWO? This is the way the developer PGI does things, UI 2.0 is just the latest fiasco.

PS: I don't know how to resolve it - I just went away and played other games instead.

[JudgeDeathCZ]

From patch notes.

First - We have a log in issue that can affect a low percentage of users. If you are hit with this issue please be patient as you can restart the client and attempt another log in do this until you succeed. Skipping the video intros with the ESC key also seems to lower the chance.

sometimes it is worth of reading patch notes....however this reminds me red ring of error on xbox 360 xD

[MountainCopper]

I had this problem as well after setting back the options to what they were before the new patch changed them. A frozen game with "connecting" after logging in..

What fixed it for me was deleting the shaders cache at "MechWarrior Online\USER\Shaders\Cache"
So you might give this a try. But I also thought that I got a completely unusable game client...

Edited by GoldenFleece, 05 February 2014 - 01:21 AM.

[Strychninez]

I can't actually restart the client as it freezes and won't actually close the program. Can't bring up task manager to try and close it also, as it retains frontal position and won't allow me to end the task.

Pressing escape on the load up screens worked and it's the ONLY time I've been able to enter the game. All others require me to reboot at this stage.

[CosmicSpeed]

Funny, I have a little played alt, that I have spent no real money on and it logs in just fine. My main, however, cannot get past the "Connecting" page on 2.0

[MountainCopper]

Strychninez, on 05 February 2014 - 02:48 AM, said:

I can't actually restart the client as it freezes and won't actually close the program. Can't bring up task manager to try and close it also, as it retains frontal position and won't allow me to end the task.

Pressing escape on the load up screens worked and it's the ONLY time I've been able to enter the game. All others require me to reboot at this stage.

Don't you use Control+Alt+Delete to bring up the task manager?

[Strychninez]

Certainly did. Only way out of it is to reboot. Running windows 8.1

[GODzillaGSPB]

This is what I get when I try to start MWO (this is after I downloaded the patch yesterday):

[Charon DOC Stock]

If you have 2 active screen:
Try to launch the game with only one active screen.
If you want to play with a second active screen, choose the "full windowed" mode in the graphical settings.

[MountainCopper]

GODzillaGSPB, on 05 February 2014 - 03:58 AM, said:

This is what I get when I try to start MWO (this is after I downloaded the patch yesterday):

MWO can also be started with a shortcut which uses an additional program argument.

"...\MechWarrior Online\Bin32\MWOClient.exe" -nopatch

Mainly used by myself so that I can start the game without the Win7 UAC prompt asking for admin rights, the program thinks it needs for patches (it doesn't since my non-admin users have a "modify" for the game folder), this will make the program not look for new patches every time the program is started.

Edited by GoldenFleece, 05 February 2014 - 04:40 AM.

[TinFoilHat]

Strychninez, on 05 February 2014 - 02:48 AM, said:

I can't actually restart the client as it freezes and won't actually close the program. Can't bring up task manager to try and close it also, as it retains frontal position and won't allow me to end the task.

Pressing escape on the load up screens worked and it's the ONLY time I've been able to enter the game. All others require me to reboot at this stage.

Exact same problems I had last night after patching. Took me four reboots to get into the game, then I got kicked out scanning through the mech lab. I didn't bother logging back in again - might give it a go later, depends if I feel like banging my head against a brick wall or not.

[GODzillaGSPB]

GoldenFleece, on 05 February 2014 - 04:35 AM, said:

MWO can also be started with a shortcut which uses an additional program argument.

"...\MechWarrior Online\Bin32\MWOClient.exe" -nopatch

Mainly used by myself so that I can start the game without the Win7 UAC prompt asking for admin rights, the program thinks it need for patches (it doesn't since my non-admin users have a "modify" for the game folder), this will make the program not look for new patches every time the program is started.

Tried that, gives me the same message. Well, the game worked since closed beta, I had my fun, time to move on. lol

[GODzillaGSPB]

The totally broken state of this website and the fact that the launcher works again, but tell me it can't load the RSS feed, tells me this is not on my end and not my firewall. ^^

[Dorado]

GoldenFleece, on 05 February 2014 - 01:20 AM, said:

I had this problem as well after setting back the options to what they were before the new patch changed them. A frozen game with "connecting" after logging in..

What fixed it for me was deleting the shaders cache at "MechWarrior Online\USER\Shaders\Cache"
So you might give this a try. But I also thought that I got a completely unusable game client...

This did not fix it for me.

[MountainCopper]

Dorado, on 05 February 2014 - 07:02 AM, said:

This did not fix it for me.

Sorry to hear. Fixed it twice for me already...