Page MenuHomeFeedback Tracker

Launcher 1.64 / DEV 1.65 , Names of parameters are mixed.
Closed, ResolvedPublic


Names of parameters are mixed. Change locations of names of parameters.
The mistake seems for all languages.
Restriction of system memory = limit of 2047
Restriction of video of memory = limit 8196
Or the limit for parameters is incorrectly appointed?


Operating System
Windows 10 x64
Operating System Version
Arma3ApexDev 1.65
Steps To Reproduce
  • Launcher.
  • Options. Settings of means of start.
  • Choose language - English.
  • Parameters. To watch the "System of Memory of Limit" and "Memory of Video of Limit" parameter.
  • Try to expose the maximum value of parameters
  • Options. Settings of means of start.
  • Сhoose other language.
  • Parameters. To watch the "System of Memory of Limit" and "Memory of Video of Limit" parameter.

Event Timeline

Lex created this task.Nov 6 2016, 10:10 AM
Lex updated the task description. (Show Details)Nov 6 2016, 10:26 AM
Lex edited Steps To Reproduce. (Show Details)
BISWizard changed the task status from New to Assigned.
BISWizard added a subscriber: BISWizard.

the system memory limit is really 2047 GB. This is the maximum amount of memory Windows can assign to 32 bit process and it is hardcoded in the game. Please note that the game utilize other options and workarounds to keep data in the system memory, but those are not limited by this parameter.

Lex added a comment.EditedNov 7 2016, 7:10 AM

Earlier all Arma3 versions beat with other restrictions - maxVRAM - maxMem.
In a launcher there were other restrictions, it was possible to change values in such limits:

  • maxVRAM = 256 - 2049
  • maxMem = 256 - 16384

It can be seen in reports.
In reports Arma3 to version 1.64:

  • maxVRAM=2049 -maxMem=10241

In reports Arma3 of version 1.64 above:

  • maxmem=2047
  • maxvram=8196

Sizes of parameters have traded places.
It promoted emergence this ticket.

== C:\Program Files (x86)\Arma 3\arma3.exe
== "C:\Program Files (x86)\Arma 3\arma3.exe" -exThreads=7 -cpuCount=8 -maxVRAM=2049 -skipintro -malloc=system -maxMem=10241 -noLogs -nosplash -enableHT -mod=

Original output filename: Arma3Retail_DX11
Exe timestamp: 2016/07/11 10:11:04
Current time:  2016/07/12 19:21:19

Type: Public
Build: Stable
Version: 1.62.137494

Allocator: C:\Program Files (x86)\Arma 3\dll\tbb4malloc_bi.dll
== C:\Program Files (x86)\Arma3\arma3.exe
== "C:\Program Files (x86)\Arma3\arma3.exe" -skipIntro -noSplash -cpuCount=8 -exThreads=7 -malloc=system -maxmem=2047 -maxvram=8196 -noLogs -mod=

Original output filename: Arma3Retail_DX11
Exe timestamp: 2016/10/07 16:49:20
Current time:  2016/11/02 01:07:32

Type: Public
Build: Stable
Version: 1.64.138732

Allocator: Windows

 1:07:32 Entering off-line mode. Callbacks and content list updates will not work.

When in a launcher to switch off the maxVRAM parameters and
maxMem, it doesn't influence a game. A game bypasses restriction in maxMem=2048 and seeks to reach use of the RAM more than 2048. I wrote it in this ticket

BISWizard removed BISWizard as the assignee of this task.Nov 7 2016, 9:29 AM
BISWizard closed this task as Resolved.

the numbers in the logs doesn't matter for the game as they are simply the values passed to the game through the command line. After that the game parses the values, it clamps them within the limits (which is 2047 MB for system memory, and your actual video card memory as reported by DirectX).

The memory limits didn't changed in years, unfortunately when the parameter list for Launcher was created, the designer who created it took the information wrong an incorrect source, so the tooltips and limits in Launcher were incorrect. With the recent update to parameters list, I've taken liberty of revising the parameter values and match it to actual possible values allowed by the engine for them.

The maxmem limit in the launcher was wrong before. 2047 is the correct max as you can see in the post Wizard linked.

BISWizard claimed this task.Nov 7 2016, 9:59 AM
Lex added a comment.EditedNov 7 2016, 10:51 AM

I hope that it is correct. But in the ambassador of the last update, often, completion of work of process of arma3.exe comes to the end with a mistake.
When I press the exit button in the main menu of a game.

The instruction of no anpecy 0x0000000001C7792D has addressed memory of no to the address OxOOOOOOOO7E1CAAC4. Memory can't be written.
Restriction of maxMem=2048 doesn't work. Process easily goes beyond this restriction through 5-10minut after start.

Before updating these mistakes weren't, or it is very rare. Now a game often comes to a desktop without messages on a mistake. Process of arma3.exe can disappear, in 20-30 minutes after start and a game on the server.
These events have drawn my attention to settings in a launcher which I didn't change long ago.

My personal compute:
Intel Core i7-4770K, 4500 MHz (45 x 100)
ASUS Z97-K (BIOS 2902)
2 x G Skill "Sniper" F3-2133C10-8GSR (24,00 х 100) (16GB)
Samsung SSD 850 PRO 128GB
Corsair Force 3 SSD (120 GB)
Chieftec 750W

The 2GB is the user-defined amount you can control yourself. It doesn't mean the game won't use more. And it will, around 3GB is normal.

You could try setting maxmem manually without the launcher limit by adding "-maxmem=10484 -nolauncher" directly to Steam's game properties. But it will not help, because the game will put it back to 2047, just like it has always done.

Lex added a comment.EditedNov 7 2016, 11:22 AM

Why now parameter and a launcher is necessary maxVRAM = 256 - 2049 and maxMem = 256 - 16384 ?
What tasks they carry out, it is more than doubts in their application?
For all that that restriction of maxMem = ~ 1000, about it or less really works.
In a launcher any restriction less than admissible works.

Lex removed a subscriber: Lex.Jan 23 2017, 1:19 PM