243 replies to this topic

[MavRCK]

Crashing far more often this patch than the last patch:

Most common (once every couple hours): On launch with teammates - straight to desktop.

Also common (once every couple hours: After clicking next after summary screen.

Least common (rare, once a day): in game, sudden crash.

[Qarnage]

Game crash to desktop much more often in this version, no regard to the map (experienced on Forest Colony, River City, Frozen City and Caustic Valley). Happens a lot when looking at / being hit by LRM volleys, but also happens in other situations (shooting lasers only, or being in caldera on Caustic).

I run actually Very High settings but recall crashing with Medium in previous versions. Also noticed that running FRAPS / Dxtory "helps" you to crash more. I recall crashes with these softwares recording, with these softwares just open and without these softwares.

[BlueDragon]

I have not had any crashing problem prior to this patch. In the past 10 games I've CTD in 8 as soon as I engaged in combat.

Then I get to wait around for awhile till my mech releases from the match, mangled usually.

[Rejarial Galatan]

this patch is a beautiful example of them rushing things into the game with out taking the time to fix things that were broken before. it is weakening the infrastructure of the game itself and is making us all lose patience and faith in PGI.

[aKlutz]

A definite increase in in CTD for me.. First times for in game ones... Seems related to heavy incoming fire ??
Also have had black screen drops, another first since patch.

[Nooee]

Just had a CTD with a server connection lost message. Now my Atlas is walking in Forrest Colony on its own. I did however notice that the other Mech's on the team were walking in place.

[KidComrade]

Not so much a crash, as a complete and utter lockdown of my entire PC. It will happen randomly, either during the countdown before match start. or while i'm configuring my loadout in the mechbay. The client will freeze, and my mouse along with it. Forcing me to do a hard reset just to get back to using the PC. After the cataphract patch it was fine. But it was after that little one thanksgiving day after that patch hit my game i can't even get in a match without my PC locking down. suffice to say, I has a sad.

[Tritarian]

CTD alot, I seem to be only able to play one round after a reboot, any match i enter after that seems to be 100% CTD.
After it crashes, it doe snot create a dump file, the omicron log does not even register a dump.
***Copy and paste of last bit of the log***
============================ PrepareLevel forestcolony ============================
Initializing default materials...
[Error] Runaway thread
[Error] Error: CTexMan::ImagePreprocessing: Scaling of 'objects/environments/skyboxes/forestcolony_clouddome_a.dds' compressed texture is dangerous (only single mip) [File=objects/environments/skyboxes/forestcolony_clouddome_a.dds]
[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]
******end of file****
It just simply stops there some of my logs show the level loads in X.X seconds, only two out of 10 and one of those rounds i played, the other was a CTD.

Edit: switched to windowed mode from full screen and i played several rounds in a row without issue. this bug seems to be linked to fullscreen games, at least for me anyway

Edited by Tritarian, 25 November 2012 - 06:53 AM.

[ltwally]

Since the latest patch (1.0.150), MW:O has crashed after clicking the "Launch" button several times. Prior to the patch, this had only happened once or twice. Since, several times. In each instance, when I re-launch the game and my mech eventually returns, I have to pay damages when I never even got so far as to have the map load.

Here is an example of the log after it crashes:

Quote

============================ PrepareLevel rivercity ============================
Initializing default materials...
[Error] Runaway thread
[Error] Error: CTexMan::ImagePreprocessing: Scaling of 'objects/environments/skyboxes/forestcolony_clouddome_a.dds' compressed texture is dangerous (only single mip) [File=objects/environments/skyboxes/forestcolony_clouddome_a.dds]
[Error] Error: CTexMan::ImagePreprocessing: Scaling of 'objects/environments/skyboxes/rivercity_cloud_fulldome.dds' compressed texture is dangerous (only single mip) [File=objects/environments/skyboxes/rivercity_cloud_fulldome.dds]
[Error] Error: CTexMan::ImagePreprocessing: Scaling of 'objects/environments/skyboxes/rivercity_planet_dif.dds' compressed texture is dangerous (only single mip) [File=objects/environments/skyboxes/rivercity_planet_dif.dds]
[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]
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'

Here is an example of when it does NOT crash:

Quote

============================ PrepareLevel rivercity ============================
Initializing default materials...
[Error] Runaway thread
[Error] Error: CTexMan::ImagePreprocessing: Scaling of 'objects/environments/skyboxes/forestcolony_clouddome_a.dds' compressed texture is dangerous (only single mip) [File=objects/environments/skyboxes/forestcolony_clouddome_a.dds]
[Error] Error: CTexMan::ImagePreprocessing: Scaling of 'objects/environments/skyboxes/rivercity_cloud_fulldome.dds' compressed texture is dangerous (only single mip) [File=objects/environments/skyboxes/rivercity_cloud_fulldome.dds]
[Error] Error: CTexMan::ImagePreprocessing: Scaling of 'objects/environments/skyboxes/rivercity_planet_dif.dds' compressed texture is dangerous (only single mip) [File=objects/environments/skyboxes/rivercity_planet_dif.dds]
[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] <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
======== rivercity is loaded in 24.4 sec ========

[-DreadDuck-]

Yep, still getting the exact same issue. Oddly the runaway thread thing does not appear in every Omicron log. But the CTD is quite consistent. I've submitted my logs to support, and they were kind enough to reply that they had everything they needed from me and inform me "Your request (#XXXX) has been deemed solved."

Not that it matters in the grand scheme of things, but I was seriously considering buying MC for the Black Friday deal, but I can hardly justify spending money on a game that I cannot even play.

Color me disappointed.

[Kamatayan]

I have had more crashes to desktop during this weekends with the latest patches than I have had ever since closed beta.

That's a very good indication of how unstable the game has become.

[ltwally]

Happened twice more, today. This has become all to common since the latest patch.

Anyone else experiencing this?

[GrizzlyViking]

ltwally, on 24 November 2012 - 06:06 PM, said:

Happened twice more, today. This has become all to common since the latest patch.

Anyone else experiencing this?

I have had this happen several times since the 11/20 patch. At least 3 times this happened on my first match of the day and I was the group leader. The group and my Mech enters the match and I CTD. The rest of the group makes it into the match. This typically happens once or twice and then I have no CTD issues after that. (This crash does not happen while the map is loading, but immediately after clicking the launch button.)

Edited by GrizzlyViking, 24 November 2012 - 06:24 PM.

[ltwally]

And twice more again. Tired of my mech spending time in battles without me... racking up repair bills in matches that I never actually played in. Ridiculous.

[Utilyan]

today for first time started getting some memory allocation error. got back in said my mech was in match so fixed another one went did it again!, So figure ok reboot, 2 mechs in match fixed a 3rd mech crashed with memory allocation. when stuff still crashes after reboot I know things are going to be a pain.

opened the user.cfg deleted everything in there... starts running, Then I get server discos which i never gotten ever. few hours after now every match or every other match its a straight crash to desktop no messages.

What im gonna try is delete the cache....and if that doesnt work im gonna dnr.

[joker1974]

Kamatayan, on 24 November 2012 - 05:50 PM, said:

I have had more crashes to desktop during this weekends with the latest patches than I have had ever since closed beta.

That's a very good indication of how unstable the game has become.

QFT.

This patch has made the game horribly unstable. I've never crashed pre-patch, and this one makes the client go **** up every 5 matches. Also experiencing more of the other bugs mentioned on these forums (yellow screen). On top of that, the Mech bay is utterly tedious, because you have to save your mech config after each change, because it otherwise don't stick. A lot of Mech bay loose all mechs ****, requiring to log off / log on. More server disconnects, in game CTD, and whatever you can think of.

Seriously, roll back this crap patch, and start over.

[Eisenkrieger]

Game crashes to desktop. Today: 2 from 3 matches. Yesterday: 7 times. Friday: also 7 times. Always appears after the map has loaded and you'd supposed to drop onto the battlefield. The crashes are gettin worse from patch to patch. I already updated my GC drivers without any effect.

[Accused]

I crash on map loading screen. Is there a workaround for this?

[Accused]

Game crashes on loading screen every freaking time. I'm not too bothered since I'm still tinkering with Halo 4. But I'll say this right now, I can not play this game. If it's not solved by next patch, I'm moving on.

[Frustro]

Happens to me to. Never had this problem before the latest patch. I don't understand why you can't just log back into the game and re-join. Jumping back into the mech that's already in-game.

It's really annoying knowing your mech is just standing there with everyone assuming you're afk farming.