[RESOLVED] So, I recorded my first mission....Windows Errors

[SFC (Ret) M. Brewer]

Thought I'd clear up this old post.  These errors were being caused because I disabled my Windows Page File in an attempt to make my system a little faster.  Turns out I didn't really need to do that and Windows freaks out the second it thinks you might not have enough memory even though there are several MB available.  Once I turned the Page File back on the errors stopped and I'm able to record without a problem.

Referencing my earlier post on using NVidia Shadowplay, I recorded my first mission (well part of it) last night.

About 15 minutes into recording, I heard my windows error sound, I got taken out of game and there was an error message on the screen saying that Windows was running low on memory and that I should close some programs.  The program it has listed is Arma...not going to happen obviously.  Also, my recording stopped around that point and I didn't stop it myself.

I continued recording later on and was able to get most of the rest of the mission.  I have 8GB of memory in my system.

On a probably related note, yesterday I added a parameter to my start line of -high -maxmem=7000 supposedly to allow Arma access to 7GB of my 8GB of ram.  By opening that up, does Arma automatically hijack all of that memory or just use what it needs?  Is the -maxmem=7000 much too high? Or do I need to consider bumping my memory to 16GB?

Thanks for input guys.  I really appreciate everyone's knowledge.
-Brewer

[D. Brown]

-maxMem=<number>   
Defines memory allocation limit to number (in MegaBytes).
256 is hard-coded minimum (anything lower falls backs to 256). 2047 is hard-coded maximum (anything higher falls back to 2047).
Engine uses automatic values (512-1536 MB) w/o maxMem parameter.
yet FileCache was always excluded from the virtual address limit, see our developers blog: https://www.bistudio.com/blog/breaking-the-32-bit-barrier


This is directly from the Arma 3 wiki that Bohemia runs. I would recommend dropping it back down to 2gb and seeing if that helps. It "shouldn't" be a reason for the memory issue, but you never really know with Arma. Also, what does -high do? I cannot find it with google when I search Arma parameters, and I can only imagine that if that was another parameter you added before the crash that it is just as likely to have caused the problem since your memory is supposed to limit to 2gb regardless of any parameter set.