Troubleshooting Vista – ArmA: Armed Assault

From Bohemia Interactive Community
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
Line 31: Line 31:


=Related Links=
=Related Links=
==Current Forum Discussion Thread==
*[http://www.flashpoint1985.com/cgi-bin/ikonboard311/ikonboard.cgi?act=ST;f=68;t=69307 BIS Forums Vista Troubleshooting thread, the one and only]
==Resources==
==Resources==
*[http://msdn2.microsoft.com/en-us/library/ms791501.aspx Windows XP & Vista Boot parameters explained]
*[http://msdn2.microsoft.com/en-us/library/ms791501.aspx Windows XP & Vista Boot parameters explained]
==Current Forum Discussion Thread==
*[http://www.flashpoint1985.com/cgi-bin/ikonboard311/ikonboard.cgi?act=ST;f=68;t=69307 BIS Forums Vista Troubleshooting thread, the one and only]


==Old Forum Discussion Threads==
==Old Forum Discussion Threads==

Revision as of 15:19, 24 October 2007

Unofficial, unsupported troubleshooting page for Windows Vista 32-bit and Windows Vista 64-bit.

Getting ArmA to run properly on Vista


Known Issues and Resolutions

64-bit Windows with 4GB RAM, black loading screen

  • Until either Bohemia Interactive, Microsoft or the Video Card producers come up with a solution, you can workaround this problem by limiting your System Memory to 3GB by a simple change of settings and a reboot:
    • Press windowskey+R, and run msconfig
    • At the boot tab, pick advanced options and put maximum memory to 3072
    • Reboot
    • You can also revert the setting by above method to get your full 4GB back
  • More methods might be listed soon, together with a method to get a selection screen at system boot up to pick "Normal Operation" and "Limited to 3GB"
  • More info on boot parameters available below, in the section Related Links


D3DX9_30.dll Not Found

  • Check above for the DirectX9/10 redistributable, this resolves this issue.


When shutting down the game, you get a bluescreen "Process has locked Pages"

  • This is a problem confirmed with X-Fi cards and their drivers. Driver Release 2.15.0002 resolves this issue. Or you can add the startup parameter -dsound to ArmA Shortcut but other weird sound problems might arise in that case.


After a shortwhile I get weird textures and models

  • Make sure you have adjusted your startup shortcut to include -maxmem=512, in some cases it might be nececairy to tweak it further back. Try 384.


Related Links

Current Forum Discussion Thread

Resources

Old Forum Discussion Threads


See Also