216 replies to this topic

[MustrumRidcully]

I don't remember disconnecting an unusual amount of times myself, but I have the impression there are more players disconnecting overall - more matches where player are dropped at the start of the match or sometimes during the match.

Edited by MustrumRidcully, 27 May 2013 - 06:34 AM.

[Kapre]

Tried twice. Both black screen after pressing launch. My low stats is getting worse. Crashes are collecting losses and deaths.

Edited by Kapre, 27 May 2013 - 07:28 AM.

[Sweet Baby Pirate]

Yeah I can't play at the moment either due to this issue. Sometimes you have to do refactoring and things get worse before they get better, not the end of the world. Hopefully there will be a patch to fix this soon and I can play again.

[Shendrach]

Ok, since the last patch the game crashes to desktop EVERY single match! I had 10 so far and 10 CTDs.

Before the patch everything worked fine. Didnt change anything in the options and after 6 crashes i tried the MWO-Repair-Tool but withouth any change: Game is unplayable by now.

[Audiopulse]

[redacted]
Normally Id look down on such flaming - BUT I CANT HELP MYSELF. RAAARGHLARG.

Okay - I had to get this off my chest after I keep freezing. Its so frustrating! Not just that I lose the game - I know im often ruining it for everyone else in my group, too. Apparently from what Ive read, everyone else is rather crashing to the mechlab, desktop or gets a black screen whereas my screen just freezes in place. A friend ive been playing told me my mech kept walking in a straight line after my screen froze. The only thing I can do after a freeze is terminate the game via Task-manager.

PLEASE! Am I the only one experiencing this? Is that a known issue? I didnt find it myself but maybe what I see as a freeze is nothing else but those crashes ive been reading about. Right now Im having maybe 1 of 3 games crash on me at some point.

I cant say anything about what may cause these - they seem to be completely random. Even closing Programs and freeing Memory before starting MWO didnt do any notable change.



Edit: I just tried the repair-tool ... ill check back and report if anythign changes during the next matches. For now I had enough, though.

Edited by Egomane, 29 May 2013 - 09:20 AM.
quote clean-up

[Ace of Spades]

FuzzyLog1c, on 26 May 2013 - 06:43 PM, said:

I bought 3-day premium time this weekend on sale, and couldn't use it because I was either crashing, or running at one quarter framerate. Asked for a refund. No response from PGI.

I still have my legendary founder's premium package untouched for that very reason. IMHO it is not worth activating that time unless the game runs stable. This is also the very same reason I am not investing any more money/MCs at the moment until the bugs are cleared and the game is running halfway stable, be it beta or not. I also advise anyone else to do the same if asked.
No offense dear devs at PGI, but connection problems like these should have been ironed out in closed beta already.

[Braidedheadman]

Softlock in under 2 seconds while pre-match cockpit tour / mech start up sequence. The Eff is this ****?

[Psychokreep]

Getting multiple disconnects back to client start while playing different maps and mechs. Mech continues to be maneuverable and able to fire weapons but all other players are locked like running in place. Does not matter what I'm using or doing in-game but randomly happens.

[KetchupMustard]

me and my friends are having major blackscreen issues, all mechs all maps, 30% of the time the map loadout wont occur and goes black

[Alekseyev]

Audiopulse, on 27 May 2013 - 03:16 PM, said:

Normally Id look down on such flaming - BUT I CANT HELP MYSELF. RAAARGHLARG.

Okay - I had to get this off my chest after I keep freezing. Its so frustrating! Not just that I lose the game - I know im often ruining it for everyone else in my group, too. Apparently from what Ive read, everyone else is rather crashing to the mechlab, desktop or gets a black screen whereas my screen just freezes in place. A friend ive been playing told me my mech kept walking in a straight line after my screen froze. The only thing I can do after a freeze is terminate the game via Task-manager.

PLEASE! Am I the only one experiencing this? Is that a known issue? I didnt find it myself but maybe what I see as a freeze is nothing else but those crashes ive been reading about. Right now Im having maybe 1 of 3 games crash on me at some point.

I cant say anything about what may cause these - they seem to be completely random. Even closing Programs and freeing Memory before starting MWO didnt do any notable change.



Edit: I just tried the repair-tool ... ill check back and report if anythign changes during the next matches. For now I had enough, though.

I am also experiencing this problem. Very frustrating, i was looking forward to playing more lately.

[Effectz]

Psychokreep, on 27 May 2013 - 08:42 PM, said:

Getting multiple disconnects back to client start while playing different maps and mechs. Mech continues to be maneuverable and able to fire weapons but all other players are locked like running in place. Does not matter what I'm using or doing in-game but randomly happens.

I'm getting this,never happened to me before until patch,even in mechlab I'll get session timed out.

[Aim64C]

So... I just recovered from a spontaneous reboot of my computer, and decided that it was worth reporting any bug that managed to kill my computer so hard that it didn't even go to a dump screen.

I was playing on Alpine, and the level loaded with numerous building textures that couldn't seem to decide whether they were there, or not (and finally decided on not being present). After emptying virtually all eight tons of my LRM ammo into the enemy (for probably 50 damage total with an accuracy rating of 60% or so) - It was me and one other guy left to finish the game via capture (because some other mech was running around out there).

I tabbed into the listing of connections to double-check something... and I get sutter-repeating audio, a frozen screen... and just as I begin to realize that my game crashed - my computer is in the process of rebooting.

This was a new one to me.

Operating System: Windows 7 Ultimate 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.130318-1533)
Processor: AMD FX™-8350 Eight-Core Processor (8 CPUs), ~4.0GHz
Memory: 32768MB RAM
Available OS Memory: 32668MB RAM
Page File: 3439MB used, 29227MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11

Card name: AMD Radeon HD 7800 Series
Manufacturer: Advanced Micro Devices, Inc.
Chip type: AMD Radeon Graphics Processor (0x6818)
DAC type: Internal DAC(400MHz)
Device Key: Enum\PCI\VEN_1002&DEV_6818&SUBSYS_32521682&REV_00
Display Memory: 1699 MB
Dedicated Memory: 2005 MB
Shared Memory: 3790 MB
Current Mode: 1920 x 1080 (32 bit) (60Hz)
Monitor Name: Generic PnP Monitor
Monitor Model: VS278
Monitor Id: ACI27A1
Native Mode: 1920 x 1080(p) (60.000Hz)
Output Type: HD15
Driver Name: aticfx64.dll,aticfx64.dll,aticfx64.dll,aticfx32,aticfx32,aticfx32,atiumd64.dll,atidxx64.dll,atidxx64.dll,atiumdag,atidxx32,atidxx32,atiumdva,atiumd6a.cap,atitmm64.dll
Driver File Version: 8.17.0010.1172 (English)
Driver Version: 9.12.0.0
DDI Version: 11
Driver Model: WDDM 1.1
Driver Attributes: Final Retail
Driver Date/Size: 12/19/2012 15:08:04, 1151488 bytes
WHQL Logo'd: Yes
WHQL Date Stamp:
Device Identifier: {D7B71EE2-2B58-11CF-A671-5812BEC2C535}
Vendor ID: 0x1002
Device ID: 0x6818
SubSys ID: 0x32521682
Revision ID: 0x0000
Driver Strong Name: oem19.inf:ATI.Mfg.NTamd64.6.1:ati2mtag_R575B:9.12.0.0:pci\ven_1002&dev_6818

To also note - while it identifies the page file size - I have the system running without a page file. At least... it should be (and the page file size stacks up to what my RAM is - so that is probably how it figures).

[Krazy Kat]

Crash after a few minute 50-70% of the time lately. Haven't had this problem in a long time. Started again after last patch.

======== forestcolony_snow is loaded in 24.7 sec ========
CGameRules::OnDisconnect: Client has disconnected: cause=eDC_ProtocolError, desc=Remote disconnected: Malformed packet (1486)
CGameClientChannel::Release
could not free all buffers from CDevBufferMan!
UnLoadLevel End: 0.8 sec
sv_gamerules = mechlab []

======== rivercity_night is loaded in 24.9 sec ========
Coolant flush initialized: 1 : 76
Coolant flush post init: 1 : 76
[Error] [UIAction] HUD (0): UIElement does not have object _root.mcMain.mcCurrentLayout.mcSpecHud.SetCount
CGameRules::OnDisconnect: Client has disconnected: cause=eDC_ProtocolError, desc=Remote disconnected: Malformed packet (1400)
CGameClientChannel::Release
could not free all buffers from CDevBufferMan!
UnLoadLevel End: 0.9 sec
sv_gamerules = mechlab []

======== rivercity_night is loaded in 20.2 sec ========
CHAT TEAM- Krazy Kat to TEAM:
upper?
CGameRules::OnDisconnect: Client has disconnected: cause=eDC_ProtocolError, desc=Remote disconnected: Malformed packet (1400)
CGameClientChannel::Release
could not free all buffers from CDevBufferMan!
UnLoadLevel End: 0.9 sec
sv_gamerules = mechlab []

======== tourmalinedesert is loaded in 22.2 sec ========
CGameRules::OnDisconnect: Client has disconnected: cause=eDC_ProtocolError, desc=Remote disconnected: Received an ack for a packet newer than what we've sent (received 2436, at 2435); disconnecting
CGameClientChannel::Release
could not free all buffers from CDevBufferMan!
UnLoadLevel End: 0.9 sec
sv_gamerules = mechlab []

======== frozencity is loaded in 19.7 sec ========
Coolant flush initialized: 1 : 60
Coolant flush post init: 1 : 60
Coolant flush initialized: 1 : 61
Coolant flush post init: 1 : 61
CGameRules::OnDisconnect: Client has disconnected: cause=eDC_ProtocolError, desc=Remote disconnected: Malformed packet (1400)
CGameClientChannel::Release
could not free all buffers from CDevBufferMan!
UnLoadLevel End: 0.8 sec
sv_gamerules = mechlab []

Wow I crashed while dead and observing!

======== rivercity is loaded in 22.0 sec ========
Coolant flush initialized: 1 : 5
Coolant flush post init: 1 : 5
Coolant flush initialized: 1 : 6
Coolant flush post init: 1 : 6
CHAT TEAM- Krazy Kat to TEAM:
upper?
[Error] [UIAction] HUD (0): UIElement does not have object _root.mcMain.mcCurrentLayout.mcSpecHud.SetCount
[Error] [UIAction] HUD (0): UIElement does not have object _root.mcMain.mcCurrentLayout.mcSpecHud.SetName
CGameRules::OnDisconnect: Client has disconnected: cause=eDC_ProtocolError, desc=Remote disconnected: Received an ack for a packet newer than what we've sent (received 67795, at 67794); disconnecting
CGameClientChannel::Release
could not free all buffers from CDevBufferMan!
UnLoadLevel End: 0.9 sec
sv_gamerules = mechlab []

Edited by Krazy Kat, 30 May 2013 - 07:10 PM.

[churchofjt]

Gonna chip in with bad packets.

======== canyonnetwork is loaded in 12.9 sec ========
Coolant flush initialized: 1 : 4
Coolant flush post init: 1 : 4
Coolant flush initialized: 1 : 5
Coolant flush post init: 1 : 5
CHAT ALL- churchofjt to No Pilot:
glhf all
[Error] [UIAction] HUD (0): UIElement does not have object _root.mcMain.mcCurrentLayout.mcSpecHud.SetCount
CHAT TEAM- churchofjt to TEAM:
d4
CGameRules::OnDisconnect: Client has disconnected: cause=eDC_ProtocolError, desc=Remote disconnected: Malformed packet (1486)
CGameClientChannel::Release
could not free all buffers from CDevBufferMan!
UnLoadLevel End: 0.4 sec
sv_gamerules = mechlab []
============================ Loading level mechlab ============================

[Max Jinas]

Just my $.02 on stability since the last patch -

I used to have no d/c issues at all, but since last week's patch, I d/c at least three times over a one hour session. Tonight was particularly bad. Five d/c's in a row. Gave up after the fifth.

The d/c's take me back to the home screen. No errors come up after the d/c.

I'm running a series of pings to google.com (since I don't know the IPs or hostnames of the game servers). I'm seeing a few dropped packets (13 in about 950 requests).

I've also been having incredibly inconsistent frame rates. One night, it's smooth as glass, no issues. The next, it's a slideshow and completely unplayable. I can't detect any rhyme or reason for the slowdown. It seems completely random. When I'm having a bad night, no number of restarts of the game or the PC make any difference.

My system specs:
Windows 7 Home Premium
Intel Core i7-2720QM 2.20 GHz
8 gig RAM
AMD Radeon 6750/1GB

Video settings - everything set to low, with res set to 1440x900 (Native res of the display. Lowering the res doesn't seem to make any fps difference).

Wasn't aware of the f9 to see fps. I'll do that next time I have the game running and will update once I have some numbers.

Edited by Max Jinas, 28 May 2013 - 07:50 PM.

[R 13]

I've been back and forth with support a number of times since ~2-3 major patches ago. I'd been trying 3 games and then stopping for the night so I didn't mess with other's games.

Tonight I just said F-it, and tried to play a dozen or so.....1 went to completion. This is easily the worst it's been.

I REALLY want to play, but the constant crashing is just brutal.

Side note, it never crashed out of testing grounds.

[Aim64C]

I've had roughly the same crash as described before (no obvious texture bugs) multiple times within the past few games.

It's quite frustrating, really.

I have to compare this public beta to another public beta that I've been playing - Path of Exile. You know... there are bugs in that game.... but the difference between the two releases is eye-opening. Compared to Path of Exile - MWO is an empty shell of a game.

I realize the development groups are different and bound by different budgets... and the nature of bugs and other such things for the two games will be different. But when you're starting with the Unreal engine to begin with... I have no idea how a team can construct a game that gets even more unstable with each patch.

I want this game to be awesome... I really do... I'd like to buy up tons of MC as a sort of good-faith investment. I'm glad to see some new content... I'm glad to see some of the competitions... but I have a program that does something I've never encountered on this machine, before. It actually crashes to the point where Windows must reboot.

Granted, I'm not noticing the HUD bugs like I used to. But that's kind of pointless when I find myself hesitant to push the "launch" button because I'm not sure if I'm going to tank my machine and leave my team-mates high and dry in the middle of the battle.

There are so many good ideas and there is so much potential.... but I come back after a couple months and just find myself thinking: "Well, maybe in another couple months...."

It feels more like we're playing a public Alpha than a Beta. Perhaps I'm spoiled... but it's just frustrating.

[Locke Ravenford]

Seriously, these crashes are getting RIDICULOUS. I've blackscreened back to MechLab 8 out of the past 8 games. Cycling client, resetting my computer, stripping processes... nothing helps.

PGI - come on. Seriously. You've had almost a YEAR to figure CryEngine out. Sure, CryEngine was the WORST POSSIBLE choice you could have made to build a game on given the experience level of your dev team - but this is just mind boggling.

[Morang]

Constant hangs in combat, only can be resolved by closing program in Task Manager. MWOClient uses about 1.2 Gb of RAM when I close it - should be that way or is it a leak?

Installation is fresh, reinstalled May 21st (when the patch was released). OS Vista x64. C2Duo E8400@3.6GHz, 4 Gb DDR2, Radeon 4870-1Gb VRAM x 2.

Quote

Description:
A problem caused this program to stop interacting with Windows.

Problem Signature:
Problem Event Name: AppHangB1
Application Name: MWOClient.exe
Application Version: 3.4.1.4418
Application Timestamp: 519d71fb
Hang Signature: 20d7
Hang Type: 6144
OS Version: 6.0.6002.2.2.0.256.1
Locale ID: 1049
Additional Hang Signature 1: 5c110f88a1dfbbbd78288fcf4846d68d
Additional Hang Signature 2: 5359
Additional Hang Signature 3: be9293701551595c3156e4aa12e0f5aa
Additional Hang Signature 4: 20d7
Additional Hang Signature 5: 5c110f88a1dfbbbd78288fcf4846d68d
Additional Hang Signature 6: 5359
Additional Hang Signature 7: be9293701551595c3156e4aa12e0f5aa

[Buckminster]

So, since the last patch it's been crash city. I've tried maybe 2 dozen games, with various mechs, and had a maybe 80% crash to mechbay.


Was any error message provided with the crash, if so, which?
No.

Where in the game or menus did the crash occur?
In match. Sometimes it'd happen during the beginning timer, other times it'd happen mid-match.

What steps had been taken prior to the crash occurring?
I've tried the fixer, updated my drivers and changed between full screen and windowed. I've also tried with and without my user.cfg file.

Does the crash re-occur for you if repeating those same steps?
Yep.

What are your video settings, did you change them since last patch?
Video settings are 1920x1080, set to medium. I swapped between full screen and full windowed, but otherwise these are the same settings pre-patch.

What are your System specs? (You can include them in a spolier

Spoiler

i5 2500, 8gb of ram, nvidia GTX 550 Ti, Win 7 64 bit

Edited by Buckminster, 29 May 2013 - 06:00 AM.