10 replies to this topic

[Zensei]

since the last patch and i just tried to uninstall , killed all traces in the registry, reinstalled and patched and same thing, probably 5 of 10 crash during the game if I look at another mech, 2 different machines, windows 7 and 8, both 64 bit, 6970 amd in one. 660ti in the other, and im taking these crashes as deaths.

uncool

zen

Edited by Zensei, 26 May 2013 - 08:26 AM.

[C E Dwyer]

Some reason crashing at the end of each battle now, changed no setting here, and mwo is usually pretty solid

[Radical eliminator]

This game has been unplayable since April, and despite much feedback from players they introduced stability issues, the same error still pops up every 2-3 games and always at the start of a match during drop. Even if its the first drop after a reboot and i never even got to match three without the fread error....how ******* hard is it to get that isolated and fixed?

I don't believe there is real attention to game stability at this moment, all focus seems on features and things that increase income like consumable goods. For someone that played other mech games fanatically for years at end and thus likes to put serious time in a game like this, this is a total let down and a spit in the face.

If it does not get fixed within a month, it might take a year before I will even look at this game again as there is enough out there to play and i can spend my time only once!

Edited by Radical eliminator, 26 May 2013 - 02:24 PM.

[Marvyn Dodgers]

Have any of you tried running the repair tool?

http://mwomercs.com/...public-release/

Good luck with resolution.

[YaoYaoYiffy]

Find your "Omicon.log" file, by default it's found in:

C:\Games\pirahna games\mechwarrior online

Sift through that log and look for 2 things:

Quote

CGameRules::OnDisconnect: Client has disconnected: cause=eDC_ProtocolError, desc=Remote disconnected: Malformed packet

or

Quote

CGameRules::OnDisconnect: Client has disconnected: cause=eDC_ProtocolError, desc=Remote disconnected: Received an ack for a packet newer than what we've sent

If you have either of these entries in your log you can find an existing thread here: http://mwomercs.com/...ng-a-game-drop/ that covers some workarounds that have worked for some players.

Edited by YaoYaoYiffy, 27 May 2013 - 09:24 AM.

[Radical eliminator]

I did ran the repair tool last patch and it did not found anything wrong, will do again shortly:

This is what my log said the last time i started MWO.

Quote

============================ PrepareLevel alpinepeaks ============================
Initializing default materials...
[Error] Runaway thread
Coolant flush initialized: 1 : 1
Coolant flush post init: 1 : 1
======== alpinepeaks is loaded in 12.3 sec ========
[Error] ZipDir::Cache::ReadFile mismatch detected for file ’6|Y: Generated CRC = 0xAA74257E, Loaded CRC = 0xF4EDAEF3
=============================================================================
*ERROR
=============================================================================
FRead did not read expected number of byte from file, only 128 of 0 bytes read
<CrySystem> Last System Error: Cannot create a file when that file already exists.

Windows 7 64 bit SP 1 (build 6.1.7601)
System language: Dutch
Windows Directory: "C:\Windows"
Prerequisites...
* Installation of KB940105 hotfix required: no! (either not needed or already installed)
Local time is 00:10:07 05/27/13, system running for 729 minutes
24568MB physical memory installed, 20066MB available, 4095MB virtual memory installed, 18 percent of memory in use
PageFile usage: 1194MB, Working Set: 1068MB, Peak PageFile usage: 1198MB,
Current display mode is 2560x1600x32, (Unknown graphics card)
IBM enhanced (101/102-key) keyboard and 5+ button mouse installed
--------------------------------------------------------------------------------
CryRenderD3D9.dll Used in module:141204842 Allocations:1412938
FRead did not read expected number of byte from file, only 128 of 0 bytes read
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'

Results of repair tool

Quote

MISMATCHED FILES:
F:\Mechwarrior online\MechWarrior Online\Game\Objects.pak-->http://patcher.mwomercs.com/patch/Production/live/Game/Objects.pak

FOUND LOCAL FILES FOR REMOVAL!

F:\Mechwarrior online\MechWarrior Online\bin32\game_version.dll
F:\Mechwarrior online\MechWarrior Online\game\objects.pak_fresh.6134fcaca366551f1d6ae9dda9ee6411

Fixing as we speak now, that should at least fix the issue i have every time.

Edited by Radical eliminator, 27 May 2013 - 12:08 PM.

[Lightfoot]

Yep, suddenly crashing every one or two matchs since 5/24 hotfix. Before that I was crashing on the third or fourth game. Always a game-freeze-lock requiring a CTRL-ALT-DEL to Windows Task Mananger to escape from the frozen image on the screen. No Crashdump file is produced.

These crashes all started when you added HSR in February, before that no crashes ever at all. No crashes ever on Testing Grounds.

[Lightfoot]

2 out of 10 games don't crash. (about 30-40 games since 5/24) As stated the crash is a game freeze that requires Windows Task Manager to escape from. Happens when weapons are fired by me or at me. No crashDump is produced. Testing Grounds never crashes no matter how many weapons are fired. Seems like HSR bug since there is always a stutter before the crash.

[l33tworks]

I find it amazing that if you just update the game it works better than if you do a fresh install. I never used to have problems with my game since my install from last year and one day I decide to do a fresh install and the game feels funky and acts funky. It installed to a new folder too, program files (x86) instead of c games pirhana.

they should have kept is the same.

Edited by l33tworks, 28 May 2013 - 05:17 AM.

[Opus]

Marvyn Dodgers, on 27 May 2013 - 08:02 AM, said:

Have any of you tried running the repair tool?

http://mwomercs.com/...public-release/

Good luck with resolution.

it wont fix pack malformations, that's server side at PGI

[Tannhauser Gate]

l33tworks, on 28 May 2013 - 05:17 AM, said:

I find it amazing that if you just update the game it works better than if you do a fresh install. I never used to have problems with my game since my install from last year and one day I decide to do a fresh install and the game feels funky and acts funky. It installed to a new folder too, program files (x86) instead of c games pirhana.

they should have kept is the same.

This happened to me a few patches back. I uninstalled and cleaned then reinstalled and had all kinds of issues.. I did the same thing on the next patch and it corrected itself. I dont remember the exact patch or dates otherwise this post would be more useful.