20 replies to this topic

[Wolfways]

Is there no update or a fix or anything for this yet? Been getting it since we got UI2.0.

I've tried, emptying the shaders folder, adding "r_ShadersAsyncCompiling=0" to my User.cfg as suggest in another thread, ran the repair tool, and turned all graphics down to low.
It happens anywhere from the first to about the fifth match.

Edit: I forgot to mention...I used to get this a long time ago, but found that lowering the Textures option fixed it, but since UI2.0 even putting it on low does nothing.

Edited by Wolfways, 21 June 2014 - 03:44 AM.

[Lyoto Machida]

I get this a lot also. My FPS is fine between 30-50 usually but I'm guessing it has something to do with XP and 4GB of ram only.

[Wolfways]

Lyoto Machida, on 21 June 2014 - 03:32 AM, said:

I get this a lot also. My FPS is fine between 30-50 usually but I'm guessing it has something to do with XP and 4GB of ram only.

Have you tried lowering textures? Might still work for you.

[Ozric]

Aye this memory leak or whatever it is has been back for me for a while now too. Kicks me out at random points in the match with same 'memory allocation error' every time.

The last time this used to happen running the repair tool between patches was all that was needed to avoid it, but now nothing works. Tried re-installing/repair tool/low settings. As this is a known Cryengine error, and Crytec is going bust, does this mean the bug is here to stay?

[Stiennar]

I am having the same issue now. Ever sense the latest update. I thought my cpu what having ram issues so I went through and cleaned it up. I too run windows xp so is this only happening to the window operating systems xp 4GB? I love playing the game but don't like that I can only get one or two games in before the system crashes.... Love everything else about the game!

[Wolfways]

It's not XP. I'm running Win7.

[bripod]

Running Win 8.1 and getting this... Would love to see a fix

[Wolfways]

So are PGI just ignoring this or what?

[shadoxhunter]

I was getting this error all the time, but switching the ram made the problem go away. To clarify, I kept the same ram but i moved the sockets that they sat in.

[Lyoto Machida]

Wolfways, on 21 June 2014 - 03:46 AM, said:

Have you tried lowering textures? Might still work for you.

Low/medium...doesn't matter. High now causes the game to immediately crash, whereas I used to be able to run it on high (closed beta?).

[Maxx Cyborg]

I was having the Memory Allocation Error several times a day. This is how I fixed it on my Xp System.

I went to a 3gig memory allocation, which is an edit to the "Boot.ini" file. (Enabling 3GB switch)

Here is how to do it: http://dwf.blogs.com...dows-vista.html

Then I updated my video card driver --- problem fixed.

[Lyoto Machida]

Maxx Cyborg, on 24 August 2014 - 10:47 AM, said:

I was having the Memory Allocation Error several times a day. This is how I fixed it on my Xp System.

I went to a 3gig memory allocation, which is an edit to the "Boot.ini" file. (Enabling 3GB switch)

Here is how to do it: http://dwf.blogs.com...dows-vista.html

Then I updated my video card driver --- problem fixed.

I've tried the 3GB mem allocation boot.ini thing but then I randomly get blue screens of death so I stopped using it.

[Wolfways]

The error is becoming more regular now, and instead of reload game>play another mech i now get to reload game>rejoin match>float above the map>quit match>rejoin match>watch my team kill the last mech while I'm either dead or just standing up against a tree.

Seriously PGI, get some modders to fix your game for you

[GonaDie]

Yeah... I got this stuff too...But I could live with it until today... Today I got this error during a match for the first time. Normally, this would happen during the beginning of the match( when everybody is waiting for me to press the "READY" button).If PGI won't fix this I won't be able to play this game anymore

Edited by GonaDie, 30 August 2014 - 12:19 AM.

[mikehunter82]

I bet that in my case, cryengine memory error is caused by 32-bit OS running on 5 year old PC, but that is something im NOT gonna change for some time, not until new PC is within my reach... I also like to play some VERY old games time to time, and 64-bit OS just takes this possibility away from me (I guess)... This freakin error CTDs my game EVERY match (right at the start) since the last patch:(. And I definitely wanted a Timberwolf in my Mechbay (but not for real money tbh)... SHAME I am leaving the game just few months before Madcat is released:(. I like games created around Battletech universe a lot and having to leave MWO just as Clans FINALLY arrived SUCKS BIGTIME!!!

[wslpdougout]

Please read my post


http://mwomercs.com/...ost__p__3685988


had odd mem error with cry engine and

shut down of game with no warining or
reason

Now no problems at all

[EekaBlitzer]

Changing the windows Colour settings to 16 bit does appear to have helped, though I am still logging off after 2 games to be safe.
After last patch I was getting mem allocation errors even though on low textures, and in my first game.
Thanks for the advice iro the 16 bit change.

[Suros]

This is getting pretty absurd. All these people are going so far as to modify how Windows manages its memory, lower their detail levels to minimum, and buy new Windows keys just because PGI can't get their game in working order. I'll assume they'll get around to "fixing" this one in 6 months as it's already been happening for over a year.

Should've never come back here...

[mechs-ican]

Ditto. no workaround. Just wanted to say that the last few patches have made the game absolutely unplayable due to this error. When I first started playing mechwarrior online (late september 2013) I never had this problem. I recall being able to run the game for hours with no sign of memory allocation failures.

[ChiefBrowncloud]

Suros, on 19 September 2014 - 11:00 AM, said:

This is getting pretty absurd. All these people are going so far as to modify how Windows manages its memory, lower their detail levels to minimum, and buy new Windows keys just because PGI can't get their game in working order. I'll assume they'll get around to "fixing" this one in 6 months as it's already been happening for over a year.

Should've never come back here...

After spending hours messing with a perfectly fine gaming PC to get this to runn this game (the PC plays everything except this game)...I am showing my support and faith in the devs by uninstalling and telling my friends to do the same...very sad..
There other games that will get my time and effort...they should talk to Russian game devs..they have it together and are making a killing... oh well and goodbye..