Crash & Stability Feedback

#121 bentron

Member

10 posts

Posted 22 February 2013 - 01:01 AM

I've been experiencing similar game freeze/lockup symptoms that others in this thread have been reporting. The game (video and audio) freeze during a match and the process must be manually terminated to close the game. The issue first started happening after the Feb 5th patch and seems to have gotten worse since the Feb 19th patch.

However, the frequency of these freezes for me during normal play is extremely low. I've gone 10-20+ matches without any issues. If I'm recording gameplay, the frequency jumps to once every 2-4 matches. In fact, I've only experienced a single freeze when not recording, and it was after many hours of the game client being open.

Around the time of the Feb 5th patch, I was using XSplit (http://www.xsplit.com) to record gameplay locally. I should also note that prior to the Feb 5th patch, I had no freezing or CTD issues during normal gameplay or when recording. When I made the connection around the 5th, I just stopped recording for a week or so. After that, I decided to try Open Broadcaster Software (http://obsproject.com) to see if the issue was specific to XSplit.

The interesting thing here is, after the Feb 5th patch, but before the Feb 19th patch, I could record over a dozen consecutive matches with OBS without any issues. I believe one play session it finally froze on the 22nd match recorded. It may or may not be relevant, but I took negligible performance hits recording with OBS compared to a significant framerate drop recording with XSplit.

Then Feb 19th rolled around and I started experiencing roughly the same frequency of freezing when recording with OBS as I did recording with XSplit prior to the Feb 19th patch. There has been no additional performance hit when recording with OBS though.

Some people have noted LRMs being a cause of their freezes, but I've seen no such pattern personally. I've had freezes as early as 60 seconds into a match, before a single shot was fired. I've also had freezes more than halfway through a match in isolated parts of the map, with and without mechs in my direct field of view, with and without incoming fire, while firing my own weapons, and simply running around the maps. With the exception of Alpine Peaks (which I've played on maybe 6 times total since it was introduced), I'm pretty sure I've experienced this freezing issue on every map and in several different mechs.

Video Settings:

Spoiler

I hadn't changed anything immediately prior to the issue first occurring (the Feb 5th patch), but I may have since changed some advanced settings to balance visual quality and framerate while recording.

System Specs:

Spoiler

Operating System: Win7 64-bit
Re-installed the game: no
Default installation folder: yes
Solid State Drive: yes

DxDiag:

Spoiler

For the record, I'm aware that PGI probably can't and won't support third party recording software interfacing with MWO, nor do I expect them to. I'm simply sharing my situation in the hopes that it may help narrow down the cause and eventually allow PGI to resolve this issue that clearly isn't specific to my personal edge case.

If there's any other information I can provide or tests I could run, please feel free to contact me. I haven't submitted a support ticket regarding this issue, but I can do that as well if needed.

#122 Silme

Member

The Blade
56 posts

Posted 22 February 2013 - 02:27 AM

Was any error message provided with the crash, if so, which?
CryAnimation: Command Buffer Overflow

Where in the game or menus did the crash occur?
Anytime during a drop, earliest has been about 45 seconds in.
What steps had been taken prior to the crash occurring?
None. Did nothing in mechlab, no option changes. Launch client, invited to group, drop, crash.
Does the crash re-occur for you if repeating those same steps?
Yes
What are your video settings, did you change them since last patch?
1920x1080, full window, vsync off, motion blur off, all Very high, antialiasing on. Tried dropping Object Detail to low. Delayed crashing, but it still occurs.
What are your System specs?

Spoiler

EDIT: I tried lowering Object Detail, downloading a new Objects.pak and a new Animations.pak, none of which fixed my problem. However, I'm currently crash-free after 8-10 games after disabling PostAA and enabling Vsync.

Edited by Silme, 22 February 2013 - 03:47 AM.

#123 Stoomie

Rookie

1 posts

Posted 22 February 2013 - 03:07 AM

My game has been locking up during matches with increasing frequency. I currently end up crashing in an average of every other game or more. I have uninstalled and reinstalled the game from scratch and this has not resolved my issue.

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

Spoiler

Where in the game or menus did the crash occur?

While loaded into a match, any time between during the power up sequence at the beginning of a match, all the way to during the black screen after a match when typically the mech lab would be coming up between matches.

What steps had been taken prior to the crash occurring?

I have not noticed a pattern to when the crashes occur, except it seems to happen every other game or more, and always during a match, never in the menus between matches.

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

The game constantly crashes regardless of what I do, every other game or so.

What are your video settings, did you change them since last patch?

I have not changed my video settings.

Spoiler

What are your System specs?

Spoiler

DxDiag:

Spoiler

Edited by Stoomie, 22 February 2013 - 03:13 AM.

#124 F lan Ker

Member

827 posts

LocationArctic Circle

Posted 22 February 2013 - 06:28 AM

S!

Last night got 2 freezes in a row when starting to play. After that took some 3 matches and again a freeze

Not even considering to join the Hero challenge when you can not be sure if the game will let you play or just freeze on you..

#125 illegalkao

Rookie

3 posts

Posted 22 February 2013 - 07:59 AM

There's something wrong about this game's Vsync setting now, I've noticed that even if I forced the vsync option off in both nvidia driver and ingame menu, my fps is still capped at 120 (I'm using a 120Hz monitor), which never happened month ago. Additionally, I'm also facing this "cryanimation command buffer overflow" crash every 2-3 games these days.

Here's my spec:
I7 3930 4.0G
GTX 680
16G ram
Gigabyte assassin 2
win 7 64bit

sometimes I play this game at lab, the Vsync bug still happened using a 60Hz monitor, but the game never crashed once.

My lab spec:
I7 870
GTX 650 Ti
8G ram
win 7 64bit

#126 Khaze

Member

Overlord
80 posts

Posted 22 February 2013 - 09:49 AM

This latest patch has really killed the game for me. It was bad after the last one, but no it seems I'm crashing even more frequenty, and where before it was mostly total lock-ups, now the game simply drops to desktop with no error message to speak of.

I have also done a full clean re-install of the game, to no avail.

The crashes happen both in mechlab and in-game. Completely abrupt with no lagging or anything before it occurs.

DxDiag:

Spoiler

#127 JamesT Kirk

Member

38 posts

LocationGermany

Posted 22 February 2013 - 10:19 AM

JamesT Kirk, on 20 February 2013 - 11:47 AM, said:

Same 4 me.
I deleted Mechwarrior-Online\MechWarrior Online\Bin32\frontend_version.dll
and launched again.
Some 1800MB later everything works fine now. Did 6-7 matches without any problems.

Ok, after all I can say more:

In the meanwhile I did some 30 battles, and NEVER had any crash anymore!!
The reinstall solved all issues concerning freezing while in battle or mechlab.

The only thing that is still present is a random freeze of the launcher, which I can see
using 12.000KB or so in the taskmanager, but it does not show any entry screen.
Have to kill and restart the launcher and after 3-4 restart I see the Play-Screen.

#128 OriginalCharun

Member

Knight Errant
12 posts

LocationBelgium

Posted 22 February 2013 - 11:43 AM

I realy wonder how they can keep failing at making the patcher work as it should. Nearly each patch leads to me having to reinstall MWO. It's realy starting to annoy the hell out of me.

#129 Gooner

Member

Elite Founder
138 posts

Posted 22 February 2013 - 12:47 PM

Since enabling Vsync I have not crashed in approximately 2.5 hours of play, split across 3 sessions. This seems promising, but I'll continue to monitor over the weekend.

#130 Ragis

Member

Liquid Metal
16 posts

LocationRF

Posted 22 February 2013 - 01:33 PM

StandingCow, on 20 February 2013 - 04:29 AM, said:

I am not actually crashing (no crash dump file is generated) but I often disconnect from matches now and it sends me back to mechlab. This didn't start happening until this latest patch. Happens on all maps as far as I can tell and all different mechs.

Disconnected from my last two matches in a row now... before the game even started.... make that 3.

Same problem.

#131 Ballsmahoney

Rookie

4 posts

Posted 22 February 2013 - 01:50 PM

I have been getting the crash to mechlab since the last patch on the 5th and every time there is no crash dump file. There has been one thing that always shows up in omicron.log and it is

[Error] locomotion-group not found: animations/mechs/stalker/lmg_files/land_to_fwd_fp.lmg
as well as
[Error] Runaway thread

I have reinstalled twice, tried 3 different video card driver revisions(even though I think that has nothing to do with the problem), and just turned off virtual memory to see if it was some sort of address conflict or something.
I have enabled and disabled vsync, changed every slider in the settings, and forced the game to run at a lower frame rate.
I run win7 64bit with no ssd and with the default folder. I will try to reinstall to a different folder now and see if that helps.

edit: First match didnt even make it to the startup sequence before crashing to mechlab. That seems to be when I crash the most, though sometimes I make it to the middle of the match. Also, it seems to happen more on assault than conquest but that could just be my imagination.
Most recent omicron.log

Spoiler

Edited by Ballsmahoney, 22 February 2013 - 02:32 PM.

#132 Scanz

Member

Overlord
786 posts

Posted 22 February 2013 - 04:15 PM

before the patch I updated the driver on 314.07, but after the patch I have periodically crashes the game . just freezes the picture, you have to restart.
sad

msi 5600 ti hawk

#133 PhalKaHn

Rookie

Legendary Founder
6 posts

Posted 22 February 2013 - 04:21 PM

I freeze during combat. It appears to happen EVERY time I fight on the River City Map. I have started bailing out when the map loads due to this freeze and it has not happened on any other map. This has ONLY happened to me with this patch. Guess you could call this the proverbial "Icing". If more than 4 people are not allowed to grpoup for much longer alot of people are looking elsewhere for a game to play. Can't always get 8 on to form an 8 man but we still want to play togehter....so with your new almighty grouping scale....what is wrong with more than 4 man grps?

#134 Meridian

Member

73 posts

Posted 22 February 2013 - 05:44 PM

Oh look, the fread 0 of 128 is back.

Haven't had that one for probably two months. Now it's pretty near every time I try to drop.

You think I'd be surprised, but I'm not.

#135 Valantis

Rookie

4 posts

Posted 22 February 2013 - 05:59 PM

Ok so what did you do thats got me locking up every third or every other match ???????

#136 ShadowDrake05

Member

Knight Errant
25 posts

Posted 22 February 2013 - 06:19 PM

I'm crashing super often and I have been for a little while. I have a sudden CTD with no warning, no error messages.

i5 3570k @ 4.4 GHz
Sapphire Radeon HD 7970 Overclock edition @ stock clock speeds
8 GB DDR 3
Windows 8

I'm using the latest ATI beta driver. I can't finish 70% of my matches because I just drop to desktop with no messages. Happens randomly in matches, nothing in particular seems to trigger it. And no error messages doesn't give me a place to start. I need some help.

Edit: Examining my omicron file reveals:

[Error] Runaway thread
[Error] [UIAction] HUD (0): UIElement does not have object _root.mcMain.mcCurrentLayout.mcSpecHud.SetName

Edited by ShadowDrake05, 22 February 2013 - 06:32 PM.

#137 Maxx Blue

Member

Urban Commando
370 posts

Posted 22 February 2013 - 07:43 PM

I've only been able to play Alpine Peaks twice now, but each time, when the match ends the game crashes to the desktop. This happens after the last player is killed or the base is capped, but before the match summary screen is displayed. I don't get any visible errors, but here is the end of my Omicron.log file:

============================ PrepareLevel alpinepeaks ============================
Initializing default materials...
[Error] Error: CTexMan::ImagePreprocessing: Scaling of 'textures/particles/weapons/laser_beam_1x4_lop0.dds' compressed texture is dangerous (only single mip) [File=textures/particles/weapons/laser_beam_1x4_lop0.dds]
[Error] Error: CTexMan::ImagePreprocessing: Scaling of 'textures/particles/weapons/ppc_beam_b.dds' compressed texture is dangerous (only single mip) [File=textures/particles/weapons/ppc_beam_b.dds]
[Error] [UIAction] HUD (0): UIElement does not have object _root.mcMain.mcCurrentLayout.mcSpecHud.SetName
======== alpinepeaks is loaded in 7.0 sec ========
[Error] locomotion-group not found: animations/mechs/stalker/lmg_files/land_to_fwd_fp.lmg
[Error] Error: CTexMan::ImagePreprocessing: Scaling of 'textures/particles/weapons/laser_beam_1x4_lop1.dds' compressed texture is dangerous (only single mip) [File=textures/particles/weapons/laser_beam_1x4_lop1.dds]
[Error] CryAnimation: no valid character file-format: EngineAssets/Objects/Default.cgf
[Error] CryAnimation: no valid character file-format: EngineAssets/Objects/Default.cgf
WER: Running CryEngine Exception Handler
WER: Creating Crash Dump
WER: Attempting to load DBGHELP.DLL
WER: DBGHELP.DLL Located
WER: Creating Crash Dump File
WER: Crash Dump File Created writing dump data
Saved dump file to 'user\crashdump.dmp'

No idea if that helps or not.

- Bret

Edited by Maxx Blue, 22 February 2013 - 07:44 PM.

#138 Xalafu

Rookie

9 posts

Posted 22 February 2013 - 08:17 PM

I've been having a different issue than others are having. When I get in-game I have no problems at all crash-wise. My problem is with the log-in screen. I enter my user name and password and hit login. It sometimesjust hangs with the connecting message. I will stay like that for as long as I let it. I have to kill it via ctr-alt-del. This gets rid of the desktop window but still have a problem. The apps part will only close if I press end task. The background process, however, stays running and I can not end it via end task button. I just have to wait 5-10 minutes and it usually will shut down. I let it sit for 1/2 hour once and it was still running so had to restart the computer to get rid of it. I will send the dump file for the process in a support ticket. All other programs closed, Norton antivirus and firewall turned off. Will try clean install and edit this with the result.

#139 Graysun

Rookie

Elite Founder
4 posts

LocationCoventry, Lyran Commonwealth

Posted 22 February 2013 - 08:29 PM

Since the Feb 5th patch my client is randomly locking up after launching a game. I've never seen the client do this type of lock up before. Durring most of closed Beta I'd see random CTD but a patch in December or early Jan fixed those for me. It most often occurs either durring the loading phase where it shows the teams assembling. The game just freezes with no error. If i click on the screen a "Program is not responding to Windows" error pops up. I have to close the program and log back in. I've also seen it happen often after the end of a match durring the recap screen. Some times it happens right in the middle of a match and I'll hear a motorboating audio sound till I end the program from the popup.

I've enabled vsysnc and this has helped but it just not happen as often. It does it on any mech I choose to launch with. I've tried limiting my FPS in the user.cfg to 60 but no change. (Vsync enabled does this anyhow).

System:
i7 3.4GHZ
8 GB RAM
GTX 860

#140 Monky

Member

Shredder
3,219 posts

LocationHypothetical Warrior

Posted 22 February 2013 - 09:53 PM

Alright, fresh reinstall of MWO, fresh update of graphics drivers, crashed the first game. Congrats guys.

Crash & Stability Feedback

#121 bentron

#122 Silme

#123 Stoomie

#124 F lan Ker

#125 illegalkao

#126 Khaze

#127 JamesT Kirk

#128 OriginalCharun

#129 Gooner

#130 Ragis

#131 Ballsmahoney

#132 Scanz

#133 PhalKaHn

#134 Meridian

#135 Valantis

#136 ShadowDrake05

#137 Maxx Blue

#138 Xalafu

#139 Graysun

#140 Monky

1 user(s) are reading this topic

HOME

GAME

MEDIA

COMMUNITY

SUPPORT