Page 1 of 3 123 LastLast
Results 1 to 10 of 30

  Click here to go to the first Developer post in this thread.  

Thread: Old and new shortcut switches that make it run better

  1. #1
    Sergeant Skeptic's Avatar
    Join Date
    May 30 2009
    Location
    Kirghudu, Cowjackingstan
    Posts
    131

    Lightbulb Old and new shortcut switches that make it run better

    How to apply:
    1. Right click on Arma2 shortcut
    2. Properties
    3. In target window after the closing quote mark add switch(es) like this:

    Code:
    "C:\Program Files\Bohemia Interactive\ArmA 2\arma2.exe" -nosplash -world=empty -maxmem=2047
    So far:
    -winxp, use it in Vista/W7 to enable multi-GPU support
    -nosplash, skip those splash screens
    -world=empty, doesn't load as much stuff for menu, starts faster
    -maxmem=2047, allows game engine to use more RAM (2047 is hardcoded maximum atm, anything higher falls back to 2047). Make sure you have at least 3-4Gb for this to work.
    -window, windowed mode
    -noCB, turns off multicore drawing, slow down rendering but may resolve visual glitches
    -cpuCount=X, change X to a number equal or less than numbers of available cores. This will override our autodetection.
    Changing affinity on the fly is definitely not good, because worker threads are spawned on the game initialization,
    and by lowering affinity later you cause threads competing for cores.
    The best way to simulate dual core on quad core is to use -cpuCount=2 when you run the game
    and then change the affinity to 2 cores to make sure additional cores can never be used when some overshedulling happens.
    It might be also possible to set the affinity in the OS before you launch the process, that would work as well.

    Non-performance related:
    -mod=XYZ where XYZ is modfolder in "C:\Program Files\Bohemia Interactive\ArmA 2\"
    -profiles=profiles - will store profile info and missions in main C:\Program Files\Bohemia Interactive\Arma 2\profiles folder

    Keep adding new things you discover...
    Last edited by Skeptic; Jun 4 2009 at 14:39. Reason: incorrect info about maxmem maximum

  2. #2
    The old maxmem argument from Arma 1 works too, i.e:
    -maxmem=4096
    seems to stop texture loading lag for me which only started happening after patch 1.01

  3. #3
    Sergeant Skeptic's Avatar
    Join Date
    May 30 2009
    Location
    Kirghudu, Cowjackingstan
    Posts
    131
    Author of the Thread
    Quote Originally Posted by Lee82UK View Post
    The old maxmem argument from Arma 1 works too, i.e:
    -maxmem=4096
    seems to stop texture loading lag for me which only started happening after patch 1.01
    Thanks, Ohara also confirmed. And there are reports from people with 6+ Gb of RAM showing that this helped to improve the game.

  4. #4
    Maybe this should be a sticky!

  5. #5
    Do i have to separate these to add multiple commands, or is it ok like this:

    "C:\Program Files\Bohemia Interactive\ArmA 2\arma2.exe" -nosplash -maxmem=2048

    ?

    (\_/)
    (O.o)copy the bunny into your sig
    ( ><) help him achieve world dominashun

  6. #6
    Quote Originally Posted by ZiiiP View Post
    Do i have to separate these to add multiple commands, or is it ok like this:

    "C:\Program Files\Bohemia Interactive\ArmA 2\arma2.exe" -nosplash -maxmem=2048

    ?
    Afaik you┬┤re right on!

  7. #7

  8.   Click here to go to the next Developer post in this thread.   #8
    BI Developer Suma's Avatar
    Join Date
    Jun 27 2001
    Location
    Czech Republic
    Posts
    3,707
    Maximal allowed value for -maxmem is 2047. Anything above is clamped to 2047. If anyone seems any difference between 2047 and 4096, you fell a victim of wishful thinking.
    Ondrej Spanel, BIS Lead Programmer

  9. #9
    Quote Originally Posted by Suma View Post
    Maximal allowed value for -maxmem is 2047. Anything above is clamped to 2047. If anyone seems any difference between 2047 and 4096, you fell a victim of wishful thinking.

    Will you be fixing this issue in further patches Suma ?

  10.   This is the last Developer post in this thread.   #10
    some more
    -window , windowed mode

    -noCB , turns off multicore drawing, slow down rendering but may resolve visual glitches

    -cpuCount=X. This will override our autodetection.
    Changing affinity on the fly is definitely not good, because worker threads are spawned on the game initialization,
    and by lowering affinity later you cause threads competing for cores.
    The best way to simulate dual core on quad core is to use -cpuCount=2 when you run the game
    and then change the affinity to 2 cores to make sure additional cores can never be used when some overshedulling happens.
    It might be also possible to set the affinity in the OS before you launch the process, that would work as well.

Page 1 of 3 123 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •