Akilez

Glad it helped mate.

I too seemed to have better performance all around with the 191.03 Betas and before I play next time I intend to go back to the Betas. Glad to know I'm not the only one who noticed that.

Prit I'm pretty convinced this will go away as soon as you disable HT. Your English is fine mate but what I don't understand is how you can play the game but can't get into your BIOS. I saw the speed of your 920 and thought you were running stock which is a really good idea. Just hit 'delete' when it's POSTing and get into the BIOS like you did when you disable the audio. Find the CPU settings and disable 'HyperThreading'...save and exit. The power cycle issue must not be happening all the time or you couldn't play at all or am I missing something? Good Luck Edit: I just re-read those links concerning the power cycling and if that is going on then that definitely needs to be addressed. The disable HT will likely fix your texture issues but a power cycling PC is a sick puppy. This is not the thread for an issue like that but if it runs properly in Safe Mode try going into msconfig and disabling startup items to see if that settles it down. Sounds like h/w to me but who knows. Might need to strip system down to CPU and one RAM stick and go from there. Again best of luck.

That's really a great idea ChiefBoatsRet! I was waiting for the $/GB of those things to come out of the stratosphere but your results have me re-thinking that notion. Cheers ps. You're right about the HDD activity and I've been running Diskeeper for years on Raptors and I get highly playable results.

Prit that is exactly what I was getting prior to killing HyperThreading and running either 191.03 Beta or 191.07 WHQL. It will happen very quickly while in a fast moving vehicle in a built up area. Why can't you disable it in BIOS? I don't understand the power loop reference.

I just updated my drivers to 191.07 WHQL from 191.03 Beta and unless I keep HyperThreading turned OFF in bios I get consistent CTDs in the same place on a test mission. Flying in a Huey into a town the texture issue shows up and it's CTD in 10-15 seconds. Turn OFF HT and alls good in the world. I may actually go back to the 191.03 Beta drivers as they seemed to look and act better in my case. Best of Luck,

I've seen that happen in coop missions that weren't setup properly but never on the initial screen.. . . .

I'm not certain but I don't think ArmA 2 supports that movement (vertical) for TIR. It's a 6DOF arrangement which equates to: -Rotate left/right=2 -Lean left/right=2 -Zoom forward/aft=2 -------------------------- Total = 6 DOF (Degrees Of Freedom) Again I am not 100% certain but this is my understanding. . . .

This driver is available for both 32 and 64 bit versions of XP, VIsta and Win7. You didn't list your OS but here is the link for XP 32. Link If this is not your OS just designate the proper one at nVidia's site and search for 'Beta/Archived' drivers. Good Luck, . .

You keep stating that it hasn't been fixed for 4 patches.....when exactly did you report this?

Everything about that PSU says 'run away'. Using a 'peak' rating is BS. MTBF @ 25C is BS. This is just for starters. If you put in a poorly made PSU you are begging for nothing but trouble from here on. ArmA (2) is a demanding game and will quickly highlight the weaknesses in the build as it has in this case. Best PSU on the market: PC Power & Cooling

Pure Wisdom!

Just wanted to report that after a lot of testing with very repeatable CTDs while in a particular mission that has an insert via AI piloted helo on Chernarus the ONLY thing that has settled this game down for me and allowed me to run uninterrupted is disabling HyperThreading while running the 191.03 Beta drivers from nVidia. No other combination of swtiches, Vid Memory setting, Detail or Config entries was helping. Hope this helps someone enjoy this brilliant sim. Rig: i7 @ 3.2 Ghz X58 (R2E w/1504 and HyperThreading Disabled) 6GB Corsair Dominator DDR3 (3 x 2GB) GTX 295 w/191.03 Beta Drivers

I just did some testing and the ONLY thing that settled things down was the 191.03 drivers plus disabling HyperThreading. No other combination of Video Memory settings, configuration entries or detail levels did any good at all. Rig: i7 920 @ 3.2 Ghz X58 (ASUS R2E w/1504) HyperThreading DISABLED 6 GB Corsair Dominators DDR3 GTX 295 NVidia 191.03 Drivers

There is a theory floating around that can be tested very quickly.. If you are having graphics related CTDs etc try the following: -There are four (5) settings for graphics quality within ArmA 2.. 1) Low (theory is this is for GPUs with 128 MB of VRAM on board) 2) Normal (presumed 256 MB GPU VRAM) 3) High (512 MB VRAM) 4) Very High (1 GB VRAM) 5) Default (ArmA tries to 'auto-detect' CPU VRAM) Try setting ArmA manually (ie do NOT use 'Default) to the appropriate level for you GPU....both exactly (ie High for a 512 MB GPU) or one level down (ie 'Normal' for a 512 MB GPU). Note: If you have a card 'in-between' these parameters (eg 640 MB of VRAM) then set ArmA to one level below or 'Normal' in this case. If this is an improper detection of VRAM issue then this quick test will help prove it. Folks are also reporting the new beta drivers from nVidia is helping with this issue as well (191.03 beta). Please post your results so others can benefit from all of this testing. This is the way ArmA 1 worked so it's worth a quick test. Of course this assumes no other issues are contributing to this problem. Hopefully this gets properly sorted out so the full amount of GPU VRAM is utilized. In the mean time however if this does help at least play is not interrupted while a fix is pending. Traveling in a fast moving helo or fixed wing aircraft while looking outside reportedly will force the crash to occur quicker than most other things. This will help prove/disprove the theory. Best of luck . . . Credit: Bushlurker et al for connecting the dots and opening the dev-heaven ticket.

Oops...misread the post. NM sorry

@MW Have you tried the -maxmem= switch? I don't use the msconfig routine but there's no need to force it above the max value it's allowing as no 32 bit app can use it anyway....even on a x64 OS.

1) D2D usually lags several releases so people aren't forced to a release the server they're on may not be running. You can always patch up but you can't patch down. 2) I think you mean 1.02 and 1.04 3) 4 GB is pretty standard on a 32 bit OS as it depends on things like VRAM and APU RAM plus a lot of other address users to determine how much of the 4 GB is actually usable by the OS. Typically more than 2 GB but less than 3 GB. 4) There are a LOT of posts/threads about the 'normal/high' situation so perhaps you can find the answer by 'searching' through the responses already on the forum. (might also try the latest nVidia drivers which are currently 191.03 beta). Good Luck

It's simply added to the target path in the shortcut: "D:\Program Files\Bohemia Interactive\ArmA 2\arma2.exe" -winxp

Benny while you do have a strong system by most standards these are precisely the rigs that are having fits with ArmA 2. I would recommend going through the saga here in the forums to see what others have tried. To start with: 1) Add -winxp -cpu=4 to the command line of your shortcut 2) 12GB may need to be a)reduced to 6GB or b)setup for less via msconfig 3) Many drivers have been tried by folks here so go through and see what has worked for others (eg 182.50). 4) Possibly edit the config file manually (also all through the forums) This is just a start my friend so I wish you well and hope your journey is shorter and less aggravating than some. . . Cheers, . .

With an i7 920 @ 3.6 and a GTX295 using the latest WHQL drivers (VU64/12GB) I am getting occassional artefacts and CTDs due to grafx driver failure (these latest 190.62 drivers have been best for me by far but still not right). This is my main rig and I've used the -winxp/-cpu=4 switches and set the config manually which has optimized things but there's still issues. I literally just threw ArmA 2 onto an old rig (Q6600 stock/WinXP32/4GB/8800GTS 640 (178.13!)) and can play for hours on end without a single issue (albeit with much lower settings to get the frames up. I did however test at higher settings and could not induce an artefact. I used no command line switches other than a couple of my preferred mods which came later. This sure would seem like something other than a BIS issue to me. I know this is far from a comprehensive test but observationally there is a really big difference between rigs. Does anyone else feel this is issue is more nVidia's than BIS'? Just curious.. . .

First of all a HUGE thank you for the incredible experience ACE has provided us all. You guys don't get near enough credit for all the work you do. With that in mind is there some 'cut off point' of features and content for the initial release of ACE for ArmA 2? Cheers guys!

The smoke is definitely now working properly in terms of billowing and how long it lingers in 1.03.58946. * I thought ArmA and ArmA 2 both dealt with the Beta installations the same. That is, launch the Beta executable with a shortcut to it as the 'target', the 'working directory' as the main ArmA 2 installation (ie one level up from the Beta) and then calling the Beta with -mod-beta. Am I not remembering this correctly? Best of Luck, . .

As mentioned I did see the TIR 'locked full left' issue on a handful of romps through ArmA 2 but in the last week or so it's been behaving perfectly. I simply can't enjoy the game w/o TIR so I'm very glad the problem has not recurred. Brief specs below for reference..Best of Luck! TIR 4 TIR 5 s/w (5.0.300 build 6225) ArmA 2 (1.03.58946 beta) VU 64 w/12 GB DDR3 i7 920 @ 3.6 GTX295 190.62 X-Fi Titanium . .

So far for me personally it's the 190.62. While not yet perfect they perform the best in my situation. Just do a 'safe mode' driver clean out (eg driver sweeper or driver cleaner) and give them a spin. Best of Luck,