2 replies to this topic

[Seductivpancakes]

So I get this error once in a while in CW. Sometimes, Most of the time after it crashes due to this error, I just start the game up again, It doesn't occur again. Other times, it keeps reoccuring every few mins of being in CW.

I don't have the best computer, but the game runs fine on medium settings and, I've crashed during a pug match. I'm using Win7 32bit, and I saw a brief mention when i google the issue that 64bit would solve the issue, but I haven't tried. Is there away to solve the issue or should I just switch to 64 bit?

Edit: I turn the settings to low when I play CW and its less likely to occur, but still does once in a while.

Edited by Princess Danish SweetCream, 24 March 2015 - 04:12 PM.

[9erRed]

Greetings,

Yes, you are correct.
- That issue was solved by upgrading to the Win 64bit version,
- the 64bit game exe and having more RAM available to the system.

Upgrading to the 64bit win version will probably be the best thing you could do for win7. Allowing for full access to many features the 32bit system just couldn't do. RAM being the big one, but also allowing for more updated drivers all around.
Don't worry, any 32bit only programs will still work, but you may find there is a 64bit version now available. Windows update will be a rather long one as many items will need 'updates'. C++ has a 64bit separate version, Dx11 and your video drivers may or will require updates to 64bit drivers versions, sound probably also.

It appears to be 32bit code specific related and MWO's use of it.

9erRed

Edited by 9erRed, 25 March 2015 - 06:52 PM.

[DaangeroussDann]

Only in CW does this memory allocation error occur on my pc, and only since the last patch,, just before CW event. And I do not see having to change to 64 bit as a fix,, its an error in coding that broke the game for 32 bit clients but enables 64 bit optimization . This is not an improvement, its crummy coding. There is also a nifty Cry engine error that keeps popping up , but only in the cw event. Having ran the repair tool over and over again I feel safe in it does not work, in fact there is just as big a chance that it will break the game as fix it.

No I will not dig up a dx log file for pgi, they should have an error reporting system in place by now. I stopped spending money on mwo last year when I realized, they are just milking it, and soon they will move on, nothing will ever be fixed professionally. The game will always be buggy and frustrating until it dies or a new company takes it over. But I thought I'd pipe in that there are tons of disconnects during this battle for this planet Tukeya (or what ever it called), almost never is there a drop where everyone gets in with a full team that does not have a disconnect. Just sad really. I had such high hopes. All that hope is now doubt. Im confident that mwo will fail , ultimately, they just dont seem to know what they are doing , except selling mechs if you'll give them an advance in good faith. So pathetic.