It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
I have 64 Gigs of DDR4 Ram and even with that the game ran out of memory. Load times between screens got longer and longer until I had to force shut down with Control+Alt+Delete to Task Manager.
Steam user here. For what it is worth, I have been experiencing the same symptoms (Physical RAM fills up, Windows swap file fills up, Windows out of memory warning advising to close Battletech, crash to desktop, log file shows "Access Violation" so definitely memory related).

I've been keeping on eye on the GOG forums to see if this issue is present in both version - and it seems like it is :(

I've already swapping out drivers that could be interacting with the O/S, but no joy...

You can file a bug report with Paradox here:
[url=]forum.paradoxplaza.com/forum/index.php?forums/battletech-bug-reports.998/[/url]

And a support ticket with Paradox here:
[url]support.paradoxplaza.com/hc/en-us/requests/new[/url]


The more people raising this and submitting logs, the better I think..
avatar
peedeeboy: The more people raising this and submitting logs, the better I think..
Agreed! Now if they would also speed up the convoys on escort missions...
They are aware of the memory leak issue. But please continue to submit bug reports anyways.

To work around this issue I suggest exiting the game completely and relaunching it periodically.
Post edited April 25, 2018 by SoheiYamabushi
avatar
SoheiYamabushi: They are aware of the memory leak issue. But please continue to submit bug reports anyways.

To work around this issue I suggest exiting the game completely and relaunching it periodically.
When the memory leak happens, its so severe that one can only get a few minutes of gameplay at most....

I have some potential workarounds here: https://www.gog.com/forum/battletech/constant_crashing_memory_leak_access_violation_resolved_just_not_100_sure_why_yet

Still need to to do some further investigation as to which one actually fixed the issue for me...