aceace33333

One thing I've noticed in running the YAAB benchmark with 64 instead of 32 is the pagefile usage is a little bit higher (24gigs vs 19-20). But the ram usage is about the same. is that normal/to be expected?

what is the proper -maxmem= parameter for the x64 binaries... is it still 3071 or is it bumped up as well?

Since slightly before the 1.66 update, whenever i start arma (via steam) and the official A3 Launcher opens, it shows my mod preset with an asterisk (*) next to it, denoting that the list of activated mods has changed. However, the list is the same as previous launches, and when I click the dropdown and reselect the mod loadout I want, nothing changes (because the proper mods are already activated) but the asterisk goes away. So basically its like this: I have a mod preset called "v1" When I open arma 3 launcher, all the proper mods (7 to be exact) are activated and 3 are not. This is what my v1 preset looks like. Despite the proper mods activated/deactivated, next to "v1" is an asterisk, which is denoting that the mod setup doesn't match my chosen preset. I re-click "v1", nothing changes with the mods (because like I said, they are all where they should be) but the asterisk goes away. Its a minor, asthetic glitch, to be sure, but was wondering if anyone else had the problem and could offer a fix. Maybe there's a folder somewhere with A3Launcher parameters that I could delete/start fresh?

I'll agree with that. With the new 1.66 I was able to run missions much longer before getting the 3fps bug. I think mine happened aroumd 2:30-3 hours into gameplay. Not solved, but an improvement.

It does actually. I'm not quite sure why that's the case. But like I said, my ram and pagefile reached higher levels before the 3fps bug "triggered."

Didn't work. Got the 3fps bug on both the default malloc and system malloc.... sigh

I noticed*

I left the Malloc files from 1.66 as they were and played for a while last night.. no fps bug for several hours... was really optimistic.. but then it happened after a couple hours in. I always have RivaTuner OSD running, and unnoticed that the ram and pagefile useage had reached a little bit higher before the 3fps bug triggered. So I guess this means the memory isn't as bad now... I'm not quite sure. But nevertheless it still happened, so I think I'm gonna try the system malloc for a bit and see if that fixes it.

The only reason I notice the 5-10fps performance difference is because I run RivaTuner OSD for fps and such, and have tracked the difference between the mallocs. And suprisingly, for me, since deleting the mallocs, they haven't been restored/re-downloaded yet. I've played arma multiple times, turned computer on/off, somewhat anticipating them to eventually re-appear. But they haven't. So that's a good sign i guess for this fix.

Since the 1.66 update todayi haven't been able to load your mission successfully. Game CTDs after choosing the beginning options/parameters and hitting "start your journey" Anyone else having this issue?

quick report back, I too deleted all the mallocs from Arma's DLL folder, and proceeded to run Arma for several hours playing various scenarios, with no "3fps" bug/drop. Out of curiosity, I restored the DLLs (so arma defaulted back to the TBB4 malloc i assume) and ran arma again... just like clockwork, the 3fps drop happened about 50-60 minutes into playing. I think it's safe to say BI still needs to find the memory leak with their DLLs. This was done on the 1.66 RC branch, and actually as i was running these tests is when BI released 1.66 to stable. So haven't replicated these tests yet with the new build, but i assume it will be the same result. Also, its worth noting that running arma with all the mallocs deleted (in which arma chooses presumably chooses the "system" malloc) the performance is notably worse... about a 5-10fps drop on average, versus running the default TBB4 malloc. But at this point, I'd rather have stable gameplay without the fear of "3fps bugging/crashing" than anything else. Hopefully dwarden's profile/performance builds in 1.66 get to the bottom of this.

good to know. I'll still give it a try. But as I said, i still get the 3fps bug with no mods running and no launch parameters. And in case anyone thinks maybe its a really buggy/bad custom scenario, i've been able to produce the bug by just replaying the YAAB (Yet Another Arma Benchmark) over and over again. Its hardly an intensive scenario, literally just a small firefight with scripted camera movements. So if the bug can happen there with just vanilla arma running, I think there's a major engine bug BI needs to address during this "sweep" of theirs.

scimitar, i'm eager to try your suggested fix, as I have been suffering from this glitch/problem for far too long. I too have tried all kinds of malloc/.exe combinations, to no avail. Quick question though... when you say you deleted all the mallocs in the Arma folder, did you then have to set arma to run the system malloc with a launch parameter? or will the game do that automatically. I only ask because I thought I remember reading somewhere that if you delete the mallocs and run the game it will just re-install them. So my basic question is, aside from deleting all of arma folder's mallocs, are there any additional actions that need to be taken? P.S. @CNutter, I think the survey question might be a good idea. And to answer what you had addressed, I've ran Arma 3 with no mods and no start-up parameters, with windows 10 OS (not from upgrade, my rig has had that OS since day 1) and i've still gotten the 3fps bug. I'm not saying those other people haven't solved theirs by doing some of the actions you've mentioned (removing mods/upgrading OS). But I am saying the glitch is deep enough in Arma atm that it occurs when running the most vanilla version of the game as possible.

Ok, I'll try disabling those parameters. As for the string of memory related stuff in the rpt log you mentioned... are you saying that's bad, or that there's an error in there? Because I don't see any. I actually run 2 1080s sli, but run arma 3 in single gpu mode because it actually gets better frames. As for my other specs; I run an i7 6700k oc'd to 4.7, and 16gb ddr4 ram oc'd to 3400. And in case you're wondering about system stability I've run multiple system stress tests (cpuz-id, geekbench, etc) for long periods of time with no errors or crashes. And I play many other games just fine with no errors. So it's a stable overclock setup. And I'm with you, I wouldn't call myself a computer expert but this is a custom build I did myself... actually bought many of these components with the purpose of optimizing for arma (strong single-thread CPU, fast ram, etc) That's why these crashes are so frustrating.

I have (and have always had) windows 10, and i still get many memory-related CTDs in Arma. Glad upgrading worked for your friend, but it isn't a solution for all of us unfortunately :\