CameronMcDonald

IMPORTANT New drivers, 158.18 for Vista, are handling this problem very well if not flawlessly, I advise you to pick them up from Guru3D ASAP.

Drop your settings all to very low and titrate up until you get the problem. Then, just set your settings one notch below problem ville. Make sure you give each setting change a decent test (I use the campaign mission "Sniper Convoy" and the single mission "Battlefields"). Unless of course, you are getting the issue with all settings on "very low?"

At least until the animation tools arrive, and Sanctuary or someone equally as talented gets on it.

...just like our DPUs. It kicks ass not having to shine boots (unless you're wearing dress uniform, but that's a different matter).

Thanks for the feedback, Animal. Have a go running ArmA with -maxmem=1024 rather than 512. My verdict: a godsend. Not one crash to date, and the very very very minor LOD'ing I get is only around Paraiso, and sorts itself out a la XP style. Nice to see NVidia pulling their finger out for BIS. I'm glad I can finally play ArmA the way my computer is designed to - freakin' well.

Loving the Protechs.

ASUS EN8800GTX @ 675/1050 (2100) Very high for everything, 8X AA, 16S AF. Viewdistance 10,000. I love ASUS.

Mave - a nice paltry 1.4V.

I was Chuck Yeager's Air Combat man myself. Good ole bitmap explosions, combined with Chuck's droll comments when you accidentally stack your Phantom II into a B17 => priceless.

Just tentatively - this may be what we needed in Vista-land. I'm still getting a very small amount of residual Playdough, but it seems to be contained to soldier models, and only when wandering around Paraiso. Ran Battlefields with everything maxed (yes, 16xAF/8xAA, 10km viewdistance) and averaged about 40FPS since Bagango isn't too congested. Looks wonderful. I'm going to keep testing in the morning. Good night, yáll. Here's a quick Battlefields pic I took: Battlefields - Maxed Out *** WARNING *** I get instant Playdoughification if I change HDRPrecision in the ArmA config to anything other than 8. So don't touch it.

The -maxmem command is a workaround for the "cannot create system memory texture" CTD bug. It has no effect on the LOD bug, AFAIK - that's a driver problem (hopefully solved by the latest 8800 ones released).

I don't have the US Demo. Good news but, still no LOD issues. Added -maxmem=512 to 1.5 command line, no further CTDs yet. Still going. If you have the US Demo, give it a crack. Hopefully these are what we've been after.

No LOD issues, yet. Copped a "system texture" CTD though. Continuing.

Oh god oh god oh god! Testing!

BIS is certainly upholding their end of the bargain, although there is no official Vista support, I dropped Suma a PM with my concerns. He states: ...which is good news, although: I suppose we'll all know when one enchanted evening we all drop into Guru3D and find something along the lines of "Armed Assault LOD bug firmly and permanently squashed" on the next set of Vista 8800 drivers to show up. Oh, and my settings are as follows: 2500, normal, normal, normal, normal, high, low, very high, low, high.

I like the old system too, but also use the new system in real life when spotting people. Eg, Adsy at 10 moving through 12. Sounds a treat.

Unknown, I haven't got it. ArmA is the only game I haven't straightened out (by that I mean, have got to run on maxed settings, heheheh).

...but would they have killed 30 people?

Do it after or the patch won't work as it will recognise your new modded files as different to those it's looking for, thus requiring you to do a clean install, which is no fun. Always back up the original BIS PBOs and BINs before you do anything with them... this is if you are patching, after all. Godspeed.

Voodoo, are you getting a Playdough-like LOD problem with high or very high texture quality settings? PS. Try setting your page file to 4GB to kill the "system texture" problem. Worked for me, so far.

But, speaking in horrible emotionless black and white - would the body count have been as high if the perp couldn't gain access to a firearm? I think not. Human beings are human beings, and you will always have the occasional bloke who flips out and looks to take it out on others. Having weapons which can deal death easily and efficiently within public reach only means more bystanders will be dead at the end of the day. EDIT - Unless the guy is a ninja.

I've already suggested the -maxmem fix. OK Matt, here's the juice: Either: 1) Run your ArmA with -maxmem=512 in the command line. 2) Disable your pagefile and see what happens. 3) Set your pagefile at 4GB (I did this and haven't had a crash since) and see what happens. 4) Drop your settings, and titrate up until you find something stable (running on high or very high texture detail can cause death). 5) Weep, and help me by submitting the bug at the link in my sig. 3 or 4 times, if you didn't mind, hehehe.

"...my father used to wake us up, half an hour before we went to sleep, give us a handful of cold gravel for breakfast, and when we came home, he would kill us and dance around on our graves singing "hallelujah!" You tell kids these days and they don't believe you!" Couldn't resist, I apologise.

I swear, if this isn't fixed, the bunny will get it.

I've tried the maxmem command in the beta; it made my game crash, but that's Vista for you. I however, have found a little stable niche by setting the page file to 4GB for both of my harddrives. Not a single "cannot create system texture" error yet, though I'm still getting Armed Playdough, damn Vista again.