However, using them can delay its occurrence, which doesn't make things actually any better with regard to this particular issue, when not adhering to above restart procedure at the same time.
However, just using those instead of the vanilla, doesn't fix that particular problem at all, that you're having. This also works with any sort of memory allocator and also helps people who need to have even more space for the curator module in the limited amount of addressable RAM that arma3.exe has in 32-bit, than the regular player.īecause it was mentioned: there are a number of different drop in memory allocators available for the game, which are even whitelisted in Battleye (most notably the TBB4 from BIS and the CMA, formerly known as xtbbmalloc from the community, that can also use large pages), so that they can be used on AWE. This is the most effective workaround for this that I've seen, yet, and doesn't involve changing any configuration or runtime parameter of the game whatsoever. It's sufficient to restart arma3.exe only, it's not required to restart Windows as well. The restart of the game client fixes any residual negative effects from memory fragmentation, excessive use of memory due to leaks in the software - it creates a clean slate, that will help to minimize the detrimental effects of memory bugs on your gameplay. and most important: I can play without crashing with that same error in the middle of a mission. Then I can usually play many missions in a row on that same new map without seeing this error at all. This only takes a few minutes and is only really needed after a change of maps. After that I tell my my teammates and especially my TL, my SL or other direct sup, that I will then restart the game client and subsequently slot to the same slot as before then load the prepared loadout to be ready for the mission. Then I load some loadout matching the slot and complete it for the mission ahead and save it. How I'm doin' it: once the map changes on the AWE server, I will pick a slot and go into the game.
I know this error message very well and I think too, that there is no fix available for this and this needs to be dealt with. It is becoming rare to be able to play on EU3 for more than an hour or so. If anybody has had or knows how to fix things like this, please let me know.
0 kommentar(er)
