If you download the zip file linked in this and go into the binaries folder, find the tbbmalloc file and put it in C:\Program Files (x86)\Steam\SteamApps\common\Arma 3\Dll folder
start arma3 synch and go to the launcher options. Tick the Malloc box and select tbbmalloc which will add a launch parameter to arma 3.
There might be another step. but bare with me. this is worth it.
Go to start and type run in the search bar… open run and type gpedit.msc
in the window that comes up go to computer configuration / widows settings / security settings / local policies / user rights agreement and then find "Lock pages in memory" by pressing L. Right click on the entry and select properties. Then you need to add your computer username log on to the box that comes up. Apply this, log off of your computer and log back on again. Open arma sync, check that Malloc and tbbmalloc are checked and start arma.
You may now cream yourselves at the smooth framerate.
Wow, I did not expect to see mallocs to be discussed here. That’s awesome! Whilst staying on the topic of ArmA-defined memory allocators, I personally use the original TBB4.2 with my game and (at least for me) get much better results with a different DLL. Link below for those who are interested.
[quote]"reapplying this patch is required with each arma update, DON’T use this patched binary to join BE enabled multiplayer sessions!!!"[/quote](locking pages in memory)
While different malloc may have different results (depends on how arma is using memory arenas), "locking" pages in memory is an old concept to prevent pages from being swapped out - meaning it can have an effect if you have pagefile.sys enabled, but it likely won’t if you don’t.
(Now wait until windows implements hugepages, hehe – imagine it, fragmentation-free textures in memory!)
[quote user_id=“13586136” avatar=“https://assets-cloud.enjin.com/users/13586136/avatar/medium.1479017342.jpeg” name=“Cody”]Wow, I did not expect to see mallocs to be discussed here. That’s awesome! Whilst staying on the topic of ArmA-defined memory allocators, I personally use the original TBB4.2 with my game and (at least for me) get much better results with a different DLL. Link below for those who are interested.
Can you suggest some test cases where tbb4_bi is better than the default? I used my usual first mission of the 2nd campaign chapter (town overview) as a benchmark and FPS as well as general shuttering caused by mis-optimizations (unloading things) seemed to be unaffected.
Where the "default" allocator is tbb3malloc_bi, I have found that with more modern systems I can get a lot more performance and reliability using tbb4malloc_bi over the prior. Since upgrading to an x99 system I have been pushing the game further with every operation, whilst using the tbb3 allocator I would encounter major texture artifacting when on a higher sampling rate. Since switching to tbb4 I have been able to get up to 200% sampling without any issues, with a maximum FPS of ~35 with AA on x8.
I am guessing that allocators are designed for specific system builds, due to the nature of Intel releasing and supporting multiple builds of the same product. Experience may vary, but I have seen an improvement from switching to tbb4.
Edit: Found out that it’s because I only have windows 7 home premium… I’ll find a fix later today[/quote]
Didn’t work for me either (I have win10), but I did have a stable 50 fps in the infantry showcase with high video settings on, while this is usually in between 25-45, so it works
How do I "Then you need to add your computer username log on to the box that comes up."?? What information do I enter where? When I click add User or Group and type in my profile name on windows it says "An object named "F. Alejandro Diaz" cannot be found.". Any help is greatly appreciated!
I’m pretty sure this is the malloc that now effectively murders your PC. If it’s the one I was thinking of then it was slowing PCs fairly progressively until arma crashes.
