datter

As I've said elsewhere, I'm do 3d animation, HD video editing and a lot of photo work and the 8GB is absolutely necessary. The system I do my gaming on is used for more than gaming.

Yes, thanks for the effort Dwarden. Any feedback or help about these issues is very much appreciated. Nothing is working so far, but your contribution here has not gone unnoticed.

Well I just pulled 2gb worth to get me down to 6gb actual. On restart ArmA2 detected my localvram at 207mb. When I limited myself to 6gb through the msconfig trick it thought I had 213mbs. With the full 8gb in place it thinks I have 255mb. I really don't think I have it in me to try again with 4gb. Not for awhile anyway. :P It seems that I'd need 16gb of actual system ram for ArmA2 to find around 512mb of localvram, which makes no sense. All in all, I just hope BIS is listening and fixes this... though at this point they likely won't just to piss me off. ;)

When I limited my 8GB of system ram down to 6GB using the msconfig thing mentioned upthread, localvram was detected as 213mb, as opposed to 255mb when I have the full 8GB in place. I'm almost tempted to physically yank some ram out and run a true 6GB just to see how that affects the localvram detection. You'd think it would be the same as using the msconfig thing, but who knows. There is no way I'll go down to 4GB mind you, and I doubt I'd leave it at 6gb beyond a quick test.

I think the less ArmA2 itself has to do the better.

That is exactly because "very high" gives you 512mb, or half of your video ram, where "default" lets it use all 1gb of it. Try upgrading your system to Win7 and 8GB of ram and see how things work out, it's entirely likely you'll see something like 200mbs of vram detected. :(

100% behind shuurajou on this. Broken in that way for me too, but only since upgrading to Win7 64bit with 8GB.

I've considered dropping back a few driver versions, out of the 190's anyway... just wasn't sure where to settle. Maybe I'll give 182.50 a shot, though as I recall I got a great boost frame rate wise going to 190.38... back before Win7 + 8gb ram that is.

Sir, yes sir.

shuurajou, you're an inspiration as to how to stay positive about this stuff. I've about given up and gotten rather down on things... but at least what you're doing lately is constructive. For me (Win7 64 bit, 8GB ram): Dual 8800GT's, with 190.62 and command line arguments (-winxp) or NO command line arguments... localvram is detected at 213mb with eventual texture issues in game. Same set up, with or without command line and in game texture memory settings set to low, medium, high, very high or default all result in the same thing... 213mb detected, plus eventual texture issues in game as above. Frustrating.

Thanks for all your trouble, I'm definitely following thing. You really shouldn't have to go through all this of course, especially since some of the people who can sort this out once and for all are reading the thread. Makes you wonder.

That was in Halifax harbor actually, not far from my house. :)

Careful, you'll get Placebo over at your house with a baseball bat for comments like that... though he's easy to scare away at least. ;)

We're on our own I'm afraid. Maybe if this was a pay per month type game there would be something in the way of ongoing feedback, but the fact that it isn't is both a blessing and a currse. Hey look at all those other games on my HD. :) .

Mentioned that in the other thread. Tried limiting it to 6GB to no effect, and while restricting things more might help I just don't want to be doing that everytime I feel like playing this damned game. :( Interesting thought, but as you said as no one at BIS seems to give a shit (unless you post negatively about things on your blog), we're left guessing. They're awesome at moving threads around for no fucking reason though.

You'll find a lot of my tips and suggestions <link removed by moderator> <at the link in my sig> though there is one unhappy thread in there, the rest should be helpful. ;)

Me either, which is of course the problem. .

Yes, without -winxp I get the typical blocky texture problem you see with 8GB of ram. The -winxp switch does not help the other issues however nor does the various other suggestions people have been nice enough to send along. A new driver update (190.62) didn't help either, and yes that's after properly uninstalling the older ones. I've run my gas tank dry trouble shooting this game. I freakin' had it too, prior to Win7 and 8GB... then it was back to square one. Real shame as Win7 is absolutely worth the upgrade, and given the work I do the 8GB is not going away either. I just haven't got any more ArmA2 troubleshooting in me right now, which sucks given my history with these games. Looks like it's just going to take up HD space for the time being, and hopefully I'll spot some sort of fix in here or get my energy up to sort this crap out again. Failing that, we'll see what the future holds in the next few months. PS - As to BIS taking the time to explain some things about the game here... Placebo seems to have time to come bitch me out in the comments on my blog if I post something unfavorable so I don't think it's so much a lack of time on their part, as a complete lack of interest. :(

You forgot the "i". :P

Posted elsewhere, but to avoid further chastisement it's now here too... My impressions. I don't hate ArmA2 nor do I hate BIS despite what people seem to think based on my recent blog post. I bought OFP on day one, and enjoyed it and Armed Assault for years and was one of the many people here and elsewhere telling those with problems to stick with it. I would explain that although the road is bumpy, it goes to a place few other games try to so it's worth making the journey. As it happens, despite all my posts along those lines and near fan-boyism that went back to the old days... I'm starting not to believe it myself anymore. Currently I have ArmA2 running acceptably on the rig in my sig... or did anyway until upgrading to Win7 64bit with 8GB of ram. Now there are new problems to sort out, like my local vram not being detected properly, and SLI no longer providing any benefit where it once did etc etc, odd graphic glitches and crashes, an unplayable campaign due to CTD's I no longer want to cope with. Etc. That last line is the thing though, "problems I no longer want to cope with". The years of same-ness with regards to BIS games and problems like these have apparently worn me down, and it's only happened very recently. It seems that where even weeks ago I was willing to spend an evening tweaking my system and ArmA2, then writing a blog or forum post to help people out (like this, this, this, this, this, this, this, this, this, and even this) now, I'd just rather play something I don't have to screw with. Hell, I went back to playing Empire Total War and that's not exactly a bed of roses either. I fear the trend of putting up with the bumps to take a unique journey is about over for me, or very close to it as I haven't touched ArmA2 in a couple of weeks now and that's too bad. If there weren't alternatives on the horizon my sticktoiveness might be a bit stronger, but I find myself wandering in both thought and attention as to where my future milsim free time will be spent.

Fine, I'll reposted mine there if that helps you out in some way.

I don't hate ArmA2 nor do I hate BIS despite what people seem to think based on my recent blog post. I bought OFP on day one, and enjoyed it and Armed Assault for years and was one of the many people here and elsewhere telling those with problems to stick with it. I would explain that although the road is bumpy, it goes to a place few other games try to so it's worth making the journey. As it happens, despite all my posts along those lines and near fan-boyism that went back to the old days... I'm starting not to believe it myself anymore. Currently I have ArmA2 running acceptably on the rig in my sig... or did anyway until upgrading to Win7 64bit with 8GB of ram. Now there are new problems to sort out, like my local vram not being detected properly, and SLI no longer providing any benefit where it once did etc etc, odd graphic glitches and crashes, an unplayable campaign due to CTD's I no longer want to cope with. Etc. That last line is the thing though, "problems I no longer want to cope with". The years of same-ness with regards to BIS games and problems like these have apparently worn me down, and it's only happened very recently. It seems that where even weeks ago I was willing to spend an evening tweaking my system and ArmA2, then writing a blog or forum post to help people out (like this, this, this, this, this, this, this, this, this, and even this) now, I'd just rather play something I don't have to screw with. Hell, I went back to playing Empire Total War and that's not exactly a bed of roses either. I fear the trend of putting up with the bumps to take a unique journey is about over for me, or very close to it as I haven't touched ArmA2 in a couple of weeks now and that's too bad. If there weren't alternatives on the horizon my sticktoiveness might be a bit stronger, but I find myself wandering in both thought and intention as to where my future milsim free time will be spent.

Win 7 64 bit here so I'm good... but still, after someone else. .

No, no I insist. After you! .

I see the 190.62 betas are out (as of a couple days ago), if anyone wants to try them out. .