Posted 16 October 2014 - 02:47 PM

Hey everyone,



Apologies for the delayed response since the call was put out back in the OP.



Thanks in part to all the players who submitted tickets under the guidelines provided, we've been able to compile a great deal of information on this problem and have been working on potential resolutions for it. We've got a number of fixes in the pipeline that need to go through proper testing before we can start rolling them out, but we hope to have them confirmed and ready to go soon.



Some insight into occurrences of the problem: the performance demands of MWO can fluctuate match-to-match depending on factors such as the map in which a match is taking place; the different models of 'Mechs in play; the loadouts of each 'Mech in play; your specific quality settings; and so forth. These variations in the resource demands are why you might be able to run a match without issue in one session yet experience issues in another with no change in your own configuration or to background applications.



The majority of players being affected by this are running an amount of physical RAM below the 4GB minimum specifications. Furthermore, when a large amount of activity is taking place on-screen under memory-intensive scenarios, machines running with a base level of 4GB physical RAM under a 32-bit OS are also much more prone to receiving the error. A much smaller contingent of players are experiencing similar memory issues under more compatible architecture.

Our fixes are intended to optimize memory handling under these situations.



I'll be responding to all the tickets submitted regarding this issue very soon with similar information, catered more toward specific player configurations, and I'll be keeping this thread updated as more information becomes available.



Apologies again for the frustration. We hope to get everyone back in business soon.

