Jump to content
Sign in to follow this  
kazenokizu

get arma to use more ram

did it work ?  

1 member has voted

  1. 1. did it work ?



Recommended Posts

i think i found a way to get arma to use more ram or any other 32 bit program. i found this while getting mods for another game and it works on it and i did it on arma and it worked. im not sure if its going to make the game run better. but if any body can use this and find a way to test please do so and post what u get.

http://www.megaupload.com/?d=WT4AYYY7

---------- Post added at 02:28 AM ---------- Previous post was at 02:24 AM ----------

this is part of the read me to explain what this does

Introduction:

I am releasing this application as I have found that it may help with crashing and performance issues with Stalker-COP, particularly when using the larger MOd some like 'Call_of_Pripyat_Complete_v1.0.2 Advanced option' The utility was originally programmed and released by MadBoris, for the game Supreme Commander. I just have simply tweaked the program to work with Stalker-COP(for all versions). Read all about the original utility here: http://forums.gaspowered.com/viewtopic.php?t=2382. .

_______________________________________________________________________________________________________________

Preamble:

It is a good practice to specify large-address-aware for 32-bit applications (such as Stalker-COP), by using the linker flag /LARGEADDRESSAWARE, *even if the application is not intended for a 64-bit platform*, because of the advantages that are gained at no cost. (Info From Microsoft)

Enabling this large-address-aware flag for software allows a 32-bit program to access more memory (with special boot options on a 32-bit OS or on a 64-bit OS- see instructions below)... In general, enabling the /LARGEADDRESSAWARE flag is a good practice, which is not enabled in Stalker-COP.

That is what this utility does; it adds makes Stalker-COP 'large-address-aware'. However. you also need to enable the '3gb switch' (except in Vista or win7 64 bit).

________________________________________________________________________________________________________________

Background info:

Regardless of the amount of physical memory in your system, Windows uses a virtual address space of 4 GB, with 2 GB allocated to user-mode processes (for example, applications) and 2 GB allocated to kernel-mode processes (for example, the operating system and kernel-mode drivers).

On systems that have 1 GB or more of physical memory, these two startup switches (see below), can be used to allocate more memory to applications (3 GB) and less memory to the operating system (1 GB). This additional virtual address space helps reduce the amount of memory fragmentation in the virtual address space of the Exchange information store process.

So, what does this mean? Well...

* Stalker-COP (WITHOUT the 3gb switch and NOT large Address Aware) on 32-bit platforms can address up to only 2 GB.

* Stalker-COP with the /LARGEADDRESSAWARE:YES linker flag on 32-bit Windows XP with the special /3gb * boot option can address up to 3 GB, ie an extra 1GB.(This however, limits the kernel to only 1 GB which may cause some drivers and/or services to fail- but not so much a problem with XP than Vista or win7 32bit).

* Stalker-COP with the /LARGEADDRESSAWARE:YES linker flag on 32-bit versions of Windows Vista or win7, can address memory up to the number specified by the boot configuration data (BCD) element "IncreaseUserVa". IncreaseUserVa can have a value ranging from 2048, the default, to 3072 (which matches the amount of memory configured by the /3gb boot option on Windows XP). I advise using IncreaseUserVa 2900.

(The remainder of 4 GB is allocated to the kernel and can result in failing driver and service configurations. )

* Stalker-COP on 64-bit platforms can address up to 2 GB, or up to 4 GB with the /LARGEADDRESSAWARE:YES linker flag. So, 64-bit processors provide a huge leap in the amount of physical and virtual memory that can be addressed.

Edited by kazenokizu
had to add in link

Share this post


Link to post
Share on other sites

ArmA2 engine doesn't use anything even close to 2 GBs of RAM even during heavy scenarios, why would it need more?

Share this post


Link to post
Share on other sites

hey don't knock it until we can get some test data in here :P

Share this post


Link to post
Share on other sites

and arma 2 already have the large address aware flag checked

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
Sign in to follow this  

×