33 replies to this topic

[-DreadDuck-]

So this isn't my first post about the ridiculous crashes to desktop on launch. And I know I'm not the only one experiencing this. But after having all my support tickets "resolved" (with no resolution) and after two patches have come and gone without addressing the issue, I'm left with limited options.

As things stand right now I cannot play. I crash on most of my launches and my mech just stands there hurting the team. Once in awhile I'll get in, and sometimes I'll even get two games in a row. But three is unheard of. There's no rhyme or reason to it though. Sometimes after a crash I can get right back in and play with no issues. Sometimes I will crash 5 launches in a row (I say five because I'm not dedicated enough to try a 6th after that)

I know I'm not the only one having this issue. I see similar posts every day on these forums. But clearly those of us experiencing this are in the minority as far as PGI is concerned. Because we are either not a priority for them, or they aren't capable of solving the issue. I want to give them more credit than that though, so I'll assume we're just not a priority.

All this means we can either:

A: Not play and just give up on this thing

or

B: Try and find the cause/solution ourselves

I'm dangerously close to A at this point, but I'm willing to give B a try.

I'm running Win7 Ultimate 64-bit on a Core2 Quad Q8200 2.33 Ghz with 6 GB of RAM. A GeForce GTX 560 with the 306.97 drivers.

Old but not ancient and certainly within the defined specifications.

I've tried not running any modules slotted, numerous different mechs, every possible graphics setting as well as windowed, full window, and fullscreen.

I've tried full reinstalls.

And I've tried deleting the user logs and shader files. Deleting he shader files MAY work from time to time..but it's so inconsistent that I'm not convinced that's the issue. There does seem to be a correlation, but it's not reliably reproducible.

So what have y'all tried? Has anything worked? Anyone got any other ideas? I don't want to give up on this thing yet, but PS2 wants my money too and it runs. So..there's that....

Edited by Ron Vandenberg, 11 December 2012 - 06:30 PM.

[Winterdyne]

I also get this. Very similar system spec, except I'm on a Q6600 at 2.4ghz.

[Galvez11]

Same issue here. I ran perfectly right up until the Nov 20 Artemis patch, no crashes, no problems, no complaints at all. Now I crash 25-40% of the time and it always happens right when my 'mech enters the map. Tried everything the ticket repsonses suggested to no avail.

Please Devs, FIX THIS. I want to pay you money for this game, but it's going to have to WORK.

[sycocys]

Have you tried rolling back your vid driver? Bios, wireless/network drivers updated, usb/ps2 drivers updated, forcing the game into 1 core. Just a couple things to try out.

I do believe the constant ctd issue is a minority, though the people with it tend to be louder - they are also still finishing up the move to dx11 among a few other critical parts that should be their final major engine development which will give them more manpower to sort out lingering bugs.

[Fireye]

I've had this issue before, AND I can reliably reproduce it. Sometimes, I'll have a CTD, and when I click "Play" in the patcher/launcher, MWO will open up and close immediately. The workaround, for me, is to close Mumble, and start MWO, and then start Mumble again.

If you're running any software that puts an overlay on top of MWO (ie; fps counter, mumble, etc), try turning it off. I have Mumble set to not do an overlay, but it still causes me issues from time to time.

[BlackAce]

sycocys, on 12 December 2012 - 09:04 AM, said:

Have you tried rolling back your vid driver? Bios, wireless/network drivers updated, usb/ps2 drivers updated, forcing the game into 1 core. Just a couple things to try out.

I do believe the constant ctd issue is a minority, though the people with it tend to be louder - they are also still finishing up the move to dx11 among a few other critical parts that should be their final major engine development which will give them more manpower to sort out lingering bugs.

Nope it's considerably more widespread than that but the threads on it keep being merged into an old non-pinned one, (which was up to 20 pages last I checked,) and this one will probably join it.

Maybe I'm being cynical but I'm starting to feel like this is being swept under the carpet. Certainly when support tickets get tagged as 'resolved' every time there's a new patch even when that patch doesn't even include a fix for it... (The very first attempt at one isn't due till the 18th Dec patch.)

Edited by BlackAce, 12 December 2012 - 03:56 PM.

[Haydon Jurai]

The constant CtDs seem to be most common to those with older dual/quad core Intel processors running Win 7 64 and an Nvidia GTX 500 series video card, and happens more frequently when grouping (and most likely to occur on the first drop; if it doesn't crash on the first drop, I can usually make it about 6 games). I've also got a Q6600, with 8GB RAM and a Galaxy MDT GTX570. Yet, having seen the others post about the same problem, some have ATI, some have newer Intel chips (i5, i7), and some even run Win 7 32-bit.

It leads me to believe it might be some kind of timing issue, that is more likely to occur with older system hardware running a newer video card.

As with most everyone else having the problem, it started with the patch around late Nov, and a clean install doesn't help. Rolling back drivers and BIOS would make sense if it weren't affecting hundreds of people (over 400 had responded to the poll last i saw, before they removed the one for the constant CtDs on launch).

People have told me "well, do a clean windows install", but that's also just a waste of time when so many of us are affected. If there's a file incompatibility or background process causing the problem, hundreds of us are experiencing it, and it started about the same time. Most likely, I'd get everything re-installed and patched up to the same versions, so would have all the same files and background processes in place.

If the game has an incompatibility with something that affects so many people, it needs to be found, and resolved.

Some people tell me I should go out and upgrade my hardware now, instead of waiting. (I was going to wait until community warfare). The hell I will upgrade now, not when I could have the exact same problem, and I don't need better hardware for any other games I'm playing or interested in. Besides, right now the people with new gaming rigs still aren't seeing good performance. I'd rather wait as long as possible, and when it comes time, base my build on user feedback of what seems to be working best for the game.

[RenegadeMaster]

Can you post the last couple lines from your MWO client's omnicron.log file? That should include some errors that may allude to the error causing CTD.

[-DreadDuck-]

From the sound of things the logs I sent to support were largely useless. The successful launches say the same thing as the unsuccessful ones, save for ending abruptly on the unsuccessful ones.

But it's included here:

Spoiler

============================ Loading level mechlab ============================
======== mechlab is loaded in 5.8 sec ========
could not free all buffers from CDevBufferMan!
UnLoadLevel End: 1.1 sec
Game rules class: Assault
============================ PrepareLevel causticvalley ============================
Initializing default materials...
[Error] Runaway thread
[Error] <Flash> Import error: GFxResource 'WeaponIcon' is not exported from movie 'CommonAssets.swf' [Libs/UI/HUD\Common\HUDMain.gfx]
[Error] [UIAction] HUD (0): UIElement does not have object _root.mcMain.mcCurrentLayout.mcSpecHud.SetName
======== causticvalley is loaded in 27.7 sec ========
[Error] CryAnimation: no valid character file-format: EngineAssets/Objects/Default.cgf
[Error] CryAnimation: no valid character file-format: EngineAssets/Objects/Default.cgf
[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.SetCount
[Error] CryAnimation: no valid character file-format: EngineAssets/Objects/Default.cgf
[Error] CryAnimation: no valid character file-format: EngineAssets/Objects/Default.cgf
[Error] CryAnimation: no valid character file-format: EngineAssets/Objects/Default.cgf
[Error] CryAnimation: no valid character file-format: EngineAssets/Objects/Default.cgf
[Error] CryAnimation: no valid character file-format: EngineAssets/Objects/Default.cgf
[Error] CryAnimation: no valid character file-format: EngineAssets/Objects/Default.cgf
[Error] CryAnimation: no valid character file-format: EngineAssets/Objects/Default.cgf
[Error] CryAnimation: no valid character file-format: EngineAssets/Objects/Default.cgf
[Error] CryAnimation: no valid character file-format: EngineAssets/Objects/Default.cgf
[Error] [UIAction] HUD (0): UIElement does not have object _root.mcMain.mcCurrentLayout.mcSpecHud.SetCount
[Error] CryAnimation: no valid character file-format: EngineAssets/Objects/Default.cgf
[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.SetCount
[Error] [UIAction] HUD (0): UIElement does not have object _root.mcMain.mcCurrentLayout.mcSpecHud.SetName
CGameClientChannel::Release
could not free all buffers from CDevBufferMan!
UnLoadLevel End: 1.9 sec
sv_gamerules = mechlab []
============================ Loading level mechlab ============================
Initializing default materials...
======== mechlab is loaded in 8.1 sec ========
could not free all buffers from CDevBufferMan!
UnLoadLevel End: 1.1 sec
Game rules class: Assault
Level causticvalley does not support Assault gamerules.
============================ PrepareLevel causticvalley ============================
Initializing default materials...
[Error] <Flash> Import error: GFxResource 'WeaponIcon' is not exported from movie 'CommonAssets.swf' [Libs/UI/HUD\Common\HUDMain.gfx]
[Error] [UIAction] HUD (0): UIElement does not have object _root.mcMain.mcCurrentLayout.mcSpecHud.SetName
======== causticvalley is loaded in 26.2 sec ========
[Error] CryAnimation: no valid character file-format: EngineAssets/Objects/Default.cgf
[Error] CryAnimation: no valid character file-format: EngineAssets/Objects/Default.cgf
[Error] CryAnimation: no valid character file-format: EngineAssets/Objects/Default.cgf
[Error] CryAnimation: no valid character file-format: EngineAssets/Objects/Default.cgf
[Error] CryAnimation: no valid character file-format: EngineAssets/Objects/Default.cgf
[Error] [UIAction] HUD (0): UIElement does not have object _root.mcMain.mcCurrentLayout.mcSpecHud.SetCount
[Error] CryAnimation: no valid character file-format: EngineAssets/Objects/Default.cgf
[Error] [UIAction] HUD (0): UIElement does not have object _root.mcMain.mcCurrentLayout.mcSpecHud.SetCount
[Error] CryAnimation: no valid character file-format: EngineAssets/Objects/Default.cgf
[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.SetCount
[Error] [UIAction] HUD (0): UIElement does not have object _root.mcMain.mcCurrentLayout.mcSpecHud.SetName
[Error] CryAnimation: no valid character file-format: EngineAssets/Objects/Default.cgf
[Error] CryAnimation: no valid character file-format: EngineAssets/Objects/Default.cgf
[Error] CryAnimation: no valid character file-format: EngineAssets/Objects/Default.cgf
[Error] CryAnimation: no valid character file-format: EngineAssets/Objects/Default.cgf
CGameClientChannel::Release
could not free all buffers from CDevBufferMan!
UnLoadLevel End: 1.8 sec
sv_gamerules = mechlab []
============================ Loading level mechlab ============================
Initializing default materials...
======== mechlab is loaded in 8.8 sec ========
could not free all buffers from CDevBufferMan!
UnLoadLevel End: 1.1 sec
Game rules class: Assault
Level causticvalley does not support Assault gamerules.
============================ PrepareLevel causticvalley ============================
Initializing default materials...
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'

Based on feedback from the player support forums I set MWO to run in Win XP SP3 compatibility mode and as an admin. This did not help. I still crashed on the very first launch. I then deleted my shaders and logs again (because I'm superstitious mostly) and tried again. I got in two successful launches before crashing on the third. Note that all three were on caustic so it's likely not the map. Perhaps it's something relating to the HUD initialization?

[Sietzer]

Hello
I also get this problem constantly. I also get the occasional Fread 128 to 0 error.
I tried support but after a few suggestions that did not work my ticket was closed as 'Solved' when the issue was not. The reason given to me was that they know there some issues and are trying to fix them.

My system:
Intel Core i7-2600 CPU @ 3.40Ghz 3.40GHz
12 GB ram
Windows 7 64-bit
ATI 6950 with latest drivers

The game was totally fine for me up until the Nov. 27 patch then everything started going wrong.
7-zip shows that the Objects.pak is corrupted. Re-downloading is a nightmare, every time I do it I the patcher crashes or has an error and I always get a random selection of corrupted files.

[Gallowglas]

One of my friends has had to stop playing because he has this same problem. He crashes on 75% of his drops. While the system he's playing on isn't brand new, it isn't that old either and has reasonable specs.

[Targaryen X]

I am having this problem also.
Here's the fix they gave me, so far since trying it I have only crashed once after 3 days of playing but... I did crash so ymmv.

Please download the following file: http://patcher.mwome...me/Textures.pak and then paste it in the game's folder (C:\Games\Piranha Games\MechWarrior Online\Game).
Delete the Shaders folder (C:\Games\Piranha Games\MechWarrior Online\USER\Shaders) and then try again


edit: ok nm, apparently my not crashing was purely coincidental.

Edited by Gederix, 13 December 2012 - 11:52 AM.

[-DreadDuck-]

I replaced the textures file, but no improvement.

At this point I'd wave a chicken foot at my hard drive on the full moon if I thought it might help.

[Ryvucz]

Go into-

C:\Games\Piranha Games\MechWarrior Online

attach the Omicron and OmicronOnline files to a composed e-mail

Then go to-

C:\Games\Piranha Games\MechWarrior Online\USER

And also attach the crashdump as well.

To -

support@mwomercs.com

(All at once, in one e-mail)

[-DreadDuck-]

Oh I've given them plenty of logs. They told me to stop sending them in fact. They say the issue has been resolved. (totally not resolved by the way)

[El Penguin]

Either I've gotten unlucky or the problem seems to be worse for me. I crash 90% of the time and always on the first launch now. I gave up trying to play. I hope there will be a fix next patch...

[sycocys]

try setting the process priority of MWO, and your secondary software. It sounds like much of the issue might be how windows is handling it.

Being that I don't use TS or any other such devices and rarely get ctds -your add ons + windows may be more to blame here.

[Lernandir]

Ron Vandenberg, on 11 December 2012 - 06:30 PM, said:

I'm running Win7 Ultimate 64-bit on a Core2 Quad Q8200 2.33 Ghz with 6 GB of RAM. A GeForce GTX 560 with the 306.97 drivers.

Im runing the same, except for the GPU being a 9800GT
Crash every time, and it started to happen from the last patch...
Until then I was runing really good, with an ocasional CtD when playing more than 6 rounds in a row

[Gallowglas]

For what it's worth, my friend is completely stable so long as he's running 8v8's. However, if we're running other matches, he crashes constantly. That may seem like anecdotal and potentially a false correlation, but it's consistent enough that I think there's something to that. I'd be curious to know if the rest of you having the consistent CTD problems experience the same phenomenon.

[Pando]

http://mwomercs.com/...ormance-update/

Take a peek, spread it around to those you know.