399 replies to this topic

[ElCadaver]

probably 10 game crashes or freezes out of 15 games since patch!!!!!

[Hammer RLG]

same. I had freezes before. reported a bug, went through uploading two sets of files at 670MB each for the support team, had the ticket closed with a resolved! no explanation though, just resolved. waited for this last patch (Tue and Fri) and guess what, it is worse now. I even removed my second video card in case it was sli related. I can get out of the game by ctrl-alt-delete, task manager, kill the process. very frustrating, 3 out of 3 games tonight. just shut the pc! no desire to play any more. win 7 x64, gtx680 4GB (could be sli), 16GB ram, rat7 mouse.

[Grimorkin]

I can't even load the game lobby. It teases me with the lobby/mech lab and then disappears completely.

I noticed that it only creates a log file when you try it the next time. The last entries in there state...

Spoiler

============================ Loading level mechlab ============================
[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]

I can't seem to find a "repair" option and I haven't tried a reinstall yet. I'll update my post once I do.


Edit: Just looked back over more of the log files it's created and those errors have been appearing for the last few months (!) so it's not going to be that. Hey ho.

Edit2: Reinstall fixed it and those errors no longer appear in the logs.

Edited by Grimorkin, 06 April 2013 - 11:17 PM.

[Theevenger]

Still getting some CTD in Tourmaline Desert. I just upgraded to 314.xx drivers.

Edit: I had another Tourmaline Desert CTD just now. Match had been going for several minutes. Nothing special happened at the time.

Edited by Theevenger, 06 April 2013 - 11:27 PM.

[Sir Ratburger]

My question is simple - when will you fix these horrendous map bugs. I get them at least 6 out of 10 matches. they are either .....

1 - no map at all - no map and when you press b a cursour appears with no map at all.
2- a bunched up map - all your points are bunched up and your 'direction point' is locked south.
3- fantastically coloured rainbow maps - does not display any info and is pretty much the same as no 2 apart from the fact the mini map is coloured with pretty rainbow colours.

it happens a lot and i hear people complaining about it almost every round.

Sorry if this is in the wrong section but I think it should fall under the stability category.

[Kissamies]

Have started to have increasing amount of random CTD ingame. I'm fighting or just stomping along and suddenly the imagine freezes, sounds going on for a while, and then the game shuts off without any error message. No idea what is causing it. Map doesn't really seem to matter. Log doesn't seem to contain info on the point of the crash. Here's one:

Spoiler

============================ PrepareLevel tourmalinedesert ============================
Initializing default materials...
[Error] ZipDir::Cache::ReadFile mismatch detected for file esert_placeholder: Generated CRC = 0xB2393234, Loaded CRC = 0x14A18A2E
[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/td_rednebula_dif.dds' compressed texture is dangerous (only single mip) [File=objects/environments/skyboxes/td_rednebula_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] 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] [UIAction] HUD (0): UIElement does not have object _root.mcMain.mcCurrentLayout.mcSpecHud.SetName
======== tourmalinedesert is loaded in 21.6 sec ========
[Error] locomotion-group not found: animations/mechs/jagermech/lmg_files/flight_fs_1.lmg
[Error] locomotion-group not found: animations/mechs/jagermech/lmg_files/flight_take_off_ltf.lmg
[Error] locomotion-group not found: animations/mechs/jagermech/lmg_files/flight_fs_1_fp.lmg
[Error] locomotion-group not found: animations/mechs/jagermech/lmg_files/flight_take_off_ltf_fp.lmg
CHAT ALL- Kissamies to No Pilot:
all I do is pug
CHAT TEAM- Kissamies to TEAM:
I'll go find them
CHAT TEAM- Kissamies to TEAM:
not on e5
CHAT TEAM- Kissamies to TEAM:
f5
CHAT TEAM- Kissamies to TEAM:
err f6
CHAT TEAM- Kissamies to TEAM:
5 of them
CHAT ALL- Kissamies to No Pilot:
at, I froze

The last comment was typed at froze screen. I wonder if the other players ever saw it.

Sometimes I have glitchy minimap, but that seems rare compared to others and not connected to crash. One game I got glitchy graphics that looked like perpetual termograph vision, but that didn't crash either.

Edited by Kissamies, 07 April 2013 - 02:08 AM.

[Jeye]

I'm back to getting frequent screen freezes again during games.

[RL Nice]

Ever since this month's patch, I've been getting crashes, which I believe are tied to the graphics card. I've only been able to play a few matches since the patch, what with being a busy film student and all, but in two matches, the screen started flashing random colors after a while. The last time this happened, I was in the game long enough to get the Blue Screen of Death. Don't quite remember what it said, and I'm not willing to risk damaging my computer by trying to get it again.

Also, FPS has taken a drop, though it fortunately hasn't made enough of a drop to be anything worse than slightly annoying. I'm playing on all low settings, except for screen resolution, which I dropped from 1360x768 to 1280x720 to try and help with the aforementioned FPS issues (which it didn't)

And my system specs...

Spoiler

Windows 7 64bit (running via Boot Camp on a MacBook Pro from 2008)
Intel Duo Core 2 CPU 2.40 GHz
2GB RAM
Nvidia GeForce 9600M GT, 256 VRAM

Yes, I know my system specs are below the minimum requirements (I even get the unsupported video card message every time I launch the game), but before the April patch, the game has been pretty playable on low settings. Yes, I had been planning on getting a new rig for some time, but I'd like to be able to play some MWO in the time before then.

[Lightfoot]

I have already posted my specs in this topic a week or two ago. Briefly Nvidia 550 ti, Windows 7 64bit pro, all current drivers.

So I reinstalled the game for the purpose of generating a Crash.dmp file, and new files, but the game still crashes by freezing with looping sounds. Go to Windows Task Manager, it says MWO is still running, but it's just a Black Screen with no sound if you go back to it. Have to use Task Manager to force MWO to shutdown. No Crash.dmp file generated.

I can sometimes get through one game if I reboot MWO each match. Sometimes just a few minutes of a match. In each game I see mechs walking or standing away from the spawn with no pilots. This is because their games have Frozen and crashed. Usually at least two players, sometimes 3. So this bug seems to be widepread, affecting 2-3 out of 16 players, probably two more are struggling with the Bug, but get to the end of the match, so about 25% of MWO players can't get MWO to run by that counting.

The problem started for me with the 2/12/13 patch. No crashes at all before that, no changes in hardware except for driver updates.

[TheGringo]

After last patch, each time I play, the first or second match is going fine, starts to lag then game completely crashes and goes back to windows. Next matches are fine.

[Lightfoot]

Lightfoot, on 07 April 2013 - 07:07 AM, said:

I have already posted my specs in this topic a week or two ago. Briefly Nvidia 550 ti, Windows 7 64bit pro, all current drivers.

So I reinstalled the game for the purpose of generating a Crash.dmp file, and new files, but the game still crashes by freezing with looping sounds. Go to Windows Task Manager, it says MWO is still running, but it's just a Black Screen with no sound if you go back to it. Have to use Task Manager to force MWO to shutdown. No Crash.dmp file generated.

I can sometimes get through one game if I reboot MWO each match. Sometimes just a few minutes of a match. In each game I see mechs walking or standing away from the spawn with no pilots. This is because their games have Frozen and crashed. Usually at least two players, sometimes 3. So this bug seems to be widepread, affecting 2-3 out of 16 players, probably two more are struggling with the Bug, but get to the end of the match, so about 25% of MWO players can't get MWO to run by that counting.

The problem started for me with the 2/12/13 patch. No crashes at all before that, no changes in hardware except for driver updates.

So next game, next Freeze. I just left it Frozen for 20 minutes, then I went to Task Manager and it said MWO was still running, but MWO was now just a black screen. I checked th folder for a Crash.dmp file and there was none, but here is what Task Manager said about the forced shutdown, if that helps.

Spoiler

[color="#0066cc"][color="#0066cc"] Description:[/color][/color]
A problem caused this program to stop interacting with Windows.
[color="#0066cc"][color="#0066cc"]Problem signature:[/color][/color]
Problem Event Name: AppHangB1
Application Name: MWOClient.exe
Application Version: 3.4.1.4418
Application Timestamp: 515de19f
Hang Signature: 9582
Hang Type: 6144
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Hang Signature 1: 9582aa75efdde2848b5b7fc5026b06d2
Additional Hang Signature 2: 4be6
Additional Hang Signature 3: 4be633c5c42175ff52309e2f7df3b761
Additional Hang Signature 4: 9582
Additional Hang Signature 5: 9582aa75efdde2848b5b7fc5026b06d2
Additional Hang Signature 6: 4be6
Additional Hang Signature 7: 4be633c5c42175ff52309e2f7df3b761
[color="#0066cc"][color="#0066cc"]Read our privacy statement online:[/color][/color]

[color="#0066cc"][color="#0066cc"]http://go.microsoft....88&clcid=0x0409[/color][/color]
If the online privacy statement is not available, please read our privacy statement offline:

[color="#0066cc"][color="#0066cc"]C:\Windows\system32\en-US\erofflps.txt[/color][/color]

Edited by Lightfoot, 07 April 2013 - 08:23 AM.

[Pz_DC]

Today game crashes 10 tiems of 15 games. It just shut off w/o any messages, or sometimes, it show up "cry engine error" that closes faster then i can read it. Unplayable game.

Edited by MGA121285, 07 April 2013 - 08:55 AM.

[Manifest Destiny]

Had a couple of issues since last patch: The game crashes me to desktop, happens regular, relogged about 3-4 times tonight in the gaming session, usually happens in combat (annoying after a very long walk on a large map). Regular no radar sometimes as usual, just getting a bit frustrating now of late. I have updated my drivers, running a 9800GT Geoforce, still happening.

[Sgt Zee]

Sir Ratburge, on 06 April 2013 - 11:04 PM, said:

My question is simple - when will you fix these horrendous map bugs. I get them at least 6 out of 10 matches. they are either .....

1 - no map at all - no map and when you press b a cursour appears with no map at all.
2- a bunched up map - all your points are bunched up and your 'direction point' is locked south.
3- fantastically coloured rainbow maps - does not display any info and is pretty much the same as no 2 apart from the fact the mini map is coloured with pretty rainbow colours.

it happens a lot and i hear people complaining about it almost every round.

Sorry if this is in the wrong section but I think it should fall under the stability category.

Same experience here! Would add one more: 1) Arm target reticle (unlocked from torso) pinned completely to the 'left' but in reality the arms are forward

[jay35]

My client is fond of stuffing all sorts of data into the mech name text space in the lower left. I've seen the WWWWWWWWWW bug, I've seen a scrolling coordinate numeral, I've seen nothing there at all, and now I've seen it all: My playername. Apparently I have my own Pretty Baby variant:

[Dirty Old Man]

I dont have crashes, however I have more Frequent Simulation of Fire Control System Failure, Targetting System Failures as well as Radar and Communications System Failure.

I have continueous fired and hired many mech engineers since this patch roll out, blaming them for the damages I am taking due all these failures in the field of battle.

End of Roleplaying



1) My HUD seems to be flickering on and off while playing.... especially in the Desert and Caustic Maps... is this this the new features to simulate Fire Control Systems failures in hottest regions?

2) My mapping is all wierd out either with a blank display or a weird Old School Heat vision color palattees. Simulation of ECM shielding failure? causing Radar and Communications system failure?

3) The Radar also simulates a malfunction where turning the torso of the mech or turning the mech does not translate at all to the Map indicators....

This game is really getting Ultra Realistic ! Now please give me a FPS shooter where I execute my engineers who had failed in their checks on my mech pre mission launches

[No7]

I have struggled with this for a very long time and suffered greatly from it.

What happens is that the game freezes while playing.

I have followed all the suggestions in the workarounds forum, and the only one that actually works for me, is to set the fps to cap out at 50 in the user_cfg file. Higher than that and it will freeze.

If i don't cap it out I have consistent fps of over 100.

7

[Troy Gardenhire]

The game is freezing every now and then. Happend before the patch, but I could reduce it with reducing the ingame resolution from 1900*1200 to 1680*1050. After the patch it crashes more often even with the reduced resolution at any map.

additionally I have the rainbow problem, missing IFF, no HUD at all, not turning minimap, messed up minimap

System:

Intel Core i7-3820
32 GB RAM
NVIDIA GTX 680
Win 7

[BloodyDziq]

my impression is that game is less stable this patch, several times game freezes (alt + Tab seem to fix this problem), also I have some screen flickering after I hit Launch and before the map start loading.

Intel Core i3
nVidia GTX 465
Win 7 - 64bit

[Zambuji]

well.. i'm pretty upset. What a waste of premium time.
SLI 2x Nvidia GTX 680's
core i7 overclocked to 4.0
win 7 - 64 bit
12gig ram.
Why do I randomly disconnect in game?
EVERY DROP i disconnect somewhere between 1sec in to 5 mins or more... very rarely do i see a score screen.
This all started happening after the hotfix patch. I was playing against heavy metals and having no problems... then i download a small patch and it ends my fun. No error, just closes back to client as if the game ended with my mech still stuck in the match. I rerolled my pc back a week ago. updated and patched again... tested without latest drivers for nvidia & with latest drivers... I've dropped my resolution, i've dropped my settings to lowest, i've switched from fullscreen to windowed. Nothing does the trick.

I'm sitting here livid and wondering what more can i do? Patch is a Game breaker for me, and i've noticed the same for several ppl with my same graphics cards. Meanwhile my premium time is ticking off, my stats are dropping for all the disconnects and my friends dont want to play with someone who crashes every match... i dont blame them.... who should i blame? Guess i can ruin pubs days by forcing them to try a 7v8 if i crash before i get to a fight, but even that only lasts a couple drops for me. I'm forced to play other games until something is fixed. And what ****** me off the most was that i had just purchased more premium time to get my cbills up for the upcoming highlander.