--------- ADDITIONAL NOTES ---------
a majority of games these days have a way to execute 32 and 64 bit
ArmA is one of few that DO NOT
- SYSTEM (windows in most cases these days) limits the amount of resources and calculations
- backwards compatibility has been resolved years back
BIS needs to optimize for newer tech and software regardless
- per ALL the -maxmem/VRam= Param will roll back to 2047 (or 32bit limit) no matter what you put
- rather 32 or 64 bit... that's the Player's responsibility to upgrade his/her PC
- BIS either needs to stick with smaller maps optimized for 32bit or raise the limits for these redundant benchmark maps
Heres something I just found... which I as a 64bit user also encounter because of the 32bit limitations (out of memory: mem_leak) which I haven't seen in years because BIS has used smaller maps and other games are 64bit
- http://forums.bistudio.com/showthread.php?149636-Beta-Development-branch-changelog/page12 [^]
which is why BIS advertised the following
--- BIS ArmA3*32 Requirements ---
Processor: Dual Core | Quad core
Memory: 2 GB RAM | Memory: 4 GB RAM
- which are *32bit limitations
- 32bit can only effectively use 1-1.5GB of RAM in a process such as ArmA because the rest is either used or cached for Windows which itself only uses 3GB of that RAM due to related background Process caching.
--- EXAMPLE ---
MEM USED BY WINDOWS & A3_PROCESSES
- ArmA3.exe (Altis_DOM) = 2,315,584k (nothing going on)
- ArmA3.exe (Altis_Editor) = 1,792,120k (40 AI)
+++++++++++++++++++++++++++++++++++++++
- SVCHost (windows) = 202mb
- Steam/Steam_Service= 180mb
- DWM (windows) = 80mb
- TaskHost (windows) = 75mb
- Explorer (windows) = 50mb
- SVCHost (windows) = 25mb
- SVCHost (windows) = 20mb
- SrchIndex (windows)= 20mb
- Sidebar (windows) = 20mb
- TOTAL +- = 700mb
Windows + A3_DOM = 3.0GB (minimum)
Windows + A3_Edi = 2.5GB (minimum)
that's IF you are lucky enough not to encounter a (Out_of_mem) (mem_leak) error causing the game to crash during the process
-------------
- we are limited to the 32bit limit therefore the performance issues and errors which make the game unplayable
PER THE BIS_DEV in the link posted (note above)
he/she stated the simple fact
Altis versus 32 bit OS
The default virtual memory limit has been increased to 1.2GB to make sure the game has enough memory to run Altis with proper performance. This limit can be changed with the -maxmem shortcut parameter, but note that virtual memory takes only 3/4 of this number.
Example (sets virtual memory limit to 1.2GB):
Code:
arma3.exe -maxmem=1600
Since processes on a 32bit OS are limited to 2GB of memory, the game might become unstable because of the increased limit. Try decreasing the limit if Altis is running fine but the game is crashing (possibly with an "Out of memory" error). We welcome your feedback to find the ideal sweet spot of this default value (for those running e.g. Vista or Win 7 32 bit - especially with 2GB RAM only).
------------
Gamer sues Sega and Gearbox over Aliens: Colonial Marines quality
http://metro.co.uk/2013/05/01/gamer-sues-sega-and-gearbox-over-aliens-colonial-marines-quality-3708692/ [^]
yes Id say it is VERY LIKELY someone will take this up their chain-of-command if BIS doesn't re-think their strategy
Reality of it
- we should all be reimbursed if they don't implement 64bit because a majority of PCs are 64bit_OS now unfortunately for them but fortunately for us!
... I didn't get all those years of military training and take up gaming PC building years ago as a work-related hobby to have my beloved BIS_OFP/ArmA LIMIT MAX REQUIREMENTS of a $1000+ gaming PC to requirements a $500 PC would meet and STILL NOT BE PLAYABLE REGARDLESS
I understand its BETA_DEV stage and a lot of these issues will be resolved
- but performance limitations and 64bit integration IS STILL NOT one of those!
<JSNFARRELL><JGFARRELL1106>