Akilez

Good to know mate..thanks!

You're probably right dogz thinking back the 2.0 slot showed up with the 7xx series of nVidia chipsets. To be honest I had such a pounding headache after reading 9 posts of rant for every 1 post of meaningful info I seriously mis-spoke. Apologies for the confusion..no excuses. I do stand by the rest of the post though. Cheers, . . Note: I struck through my mistaken reference to 780 in previous post.

+1 for smoke not working properly. Very small cloud and very short duration. 103.xxxx99 i7920@3.6 GTX295 190.62 VU64

i7 920@3.6 GTX295 190.62 12GB DDR3 @ 1440 VU64 TIR4 and current 5.0 s/w No fraps or anything other than A2 and TIR Not much to add here other than I have definitely seen this as well. TIR acts properly in it's s/w but in game it occasionally pegs to one side (left I think) and won't budge. Not at all sure what this is attributable to as it's intermittent for me. I haven't seen it in a few days but prior to that it was occuring constantly for several days forcing me to run w/o TIR. Again I'm not sure what causes this but wanted to mention it in light of this thread. If I find it's something local I'll be sure to post. Cheers,

Amazing how many of these threads so quickly deteriorate..wow! Quick question: How many folks understand that a PCI-E 2.0 card (eg all 2xx) running in a system that only supports PCI-E 1.0 will operate but at a much lower performance rate? As far as I know a P5 mobo does not support PCI-E 2.0 nor do any other 680/780 etc platform. So if folks don't understand this basic interface requirement what else might they not understand? As far as drivers goes this was stated earlier. Yes a driver can significantly impact the performance of one title. I'm a glutton for punishment and use a GTX 295 and previously a 9800GX2 fully understanding that nVidia will address these issues but as any corporation they will work from the highest population down toward the least. Same with 9800GX2 as it took a bit for the drivers to get the attention they needed as they represented a lower population of cards. When the drivers gel these cards are top flight performers but it's necessary to understand where they lie in terms of overall population. In the meantime I'm having a grand time with this game (deaf AI in 1.03 aside) and will calmy wait as the drivers evolve. I'll be playing this game next week, next month and next year as it continues to evolve into the grand milsim that it is. Another quick question: How many folks with driver (or suspected driver) related issues are flaming up the nVidia forums like they are here? Your emotion is not based on facts but only perception and that is twisted to fit into the warmth the near instant feedback this forum provides. Turn it down a notch and try talking some sense as speaking for myself as soon as I see capital letters (wtf? like that's louder or something lmao), chest beating, ultimatums and other flame tactics I'm out. BTW our servers are full every day with people enjoying this game so something is not adding up.. . . This post is not directed toward anyone in particular.. . . . .

Hey cashxx.. I have a system quite similar to yours but my 920 is @ 3.6 Ghz and I'm having a great time with ArmA2. As a test I reset my BIOS to default settings which of course restored my processor's clock rate to 2.67 Ghz. This had an enormous impact on this game making it struggle constantly. I am a huge fan of this genre and I think there's no escaping the fact that this milsim is very, very processor intensive. If you're comfortable with the process you might try clocking that 920 up to say 3.2 Ghz (very modest OC) to see what performance gains this brings you. Best of luck,

Yes it's still free to get a product key but Microsoft is no longer offering downloads of the release candidate. Vista in and of itself will not limit frames. What Vista will do is devour resources as it is the most incredibly bloated OS of all time. If the OS is a concern try minimizing the resources it's using (to start with turn off that SideBar). Good Luck. i7 920 @ 3.6 12 GB DDR3 @ 1440 GTX 295 VU64

I just read through this thread and noticed a very interesting post that didn't seem to even be acknowledged. Could this not in fact be a D3D/Rig situation as noted here?: Link to D3D Article This BIS bashing and chest pounding is counterproductive and the keyboard bravado not in the least bit impressive. Just because your annoying doesn't mean you're right. You might recall that the U.S. and Australian militaries use a superset of this code in the form of VBS for their computer trainers so maybe we should take a breath and see what else this might be attributable to. Just a random thought.. Credit: Link originally posted by Whisper in this thread. . . .

Both ArmA2 and GTA IV are extremely CPU limited.

I just tested this patch in anticipation of upgrading servers and while the sound is very good now with the extended low frequencies the AI have gone completely deaf and more than a little dumb. My final test was engaging a base on Utes (user coop map) and I could fire a DMR at tangos from 300 meters all day long while a patrol less than 10 meters from the ones I was engaging acted like nothing was going on. This is in stark contrast to their behavior before this patch where they would immediately react, seek cover, return fire, flank etc etc making it an excellent fight. But now it's just too easy and very disappointing. I'm concerned that all of this initial complaining by some new to this game has caused BIS to overcompensate and take the challenge completely out for the slightly more experienced players. I had the game set to 'Expert' mode and it was way too easy for me to just stand off a bit with a DMR and knock down targets at will with no concern at all. They just stood there and let me shoot them. Has anyone else noticed a radical change in AI behavior? This is not good. BIS if you'e listening this is not good for anyone so please hotfix this back to the way it was originally. If you stop the dead tangos from reporting in that's fine but making the AI this easy is just not the right approach. . . .

Cheers for that NeMeSiS we will take a look. Very much appreciate you pin pointing the file and the specific code.

That sounds like you're using a terrain modifier (ie low terrain detail) to get rid of the grass perhaps?

After installing the 1.03 patch we immediately noticed a radical decrease in the ability of OPFOR AI to sustain a fight. NeMeSiS in another thread has confirmed a %50 reduction in one setting and a %90 reduction in another relating to AI 'hearing' in the 1.03 patch when compared to 1.02. We feel this is a dramatic move in the wrong direction. Please consider restoring the pre-1.03 values and bringing the tenacious fighting abilities back to the OPFOR AI. Regards, . . .

I'm not a code guy NeMeSiS but it seems that you have verified at the very least a 'significant' change in the hearing capability of AI between 1.02 and 1.03 confirming our observations (90% less in 1.03!!!). This is a huge mistake in my mind (and many others) as dumbing down the AI in this fashion and then relying on people experienced with (and having access to) certain files and their content to make local changes is radically impacting the playability of this game. I have no problem with this being the case at the 'regular' levels but when 'expert' is impacted in such a significant fashion I have to wonder why. Years of development and months of Beta testing brought us the initial settings and then less than 60 days after the U.S. release a massively significant change to the game settings (in the wrong direction) comes through bundled in a patch. Again...why? Can you please be more specific as to exactly what file these changes were made in NeMeSiS? Thank you! I appreciate your feedback very much and I hope BIS sees the error and it is corrected in the next patch. Make it easier at the entry level if you must but leave expert as tough as possible please. . . .

never mind

Vista 64 i7 920 @ 3.6 12 GB DDR3 GTX 295 GPU Driver: 190.62 I've had some sporadic texture problems (I know 295 right lol) primarily at speed when in a vehicle. I managed to get them down to a reasonable level and have been enjoying the game. I just installed the 190.62 64 bit WHQL driver set after a complete Safe Mode driver clean out (driver cleaner) and am really pleased with the results. Not a single anamoly since installation. Sorry I don't have any FPS data but it certainly hasn't degraded the 'feel' of the game. Just thought I'd mention it. . . Oh and regarding the installation of these drivers. I know from past experience that drivers installed over other drivers (eg runnning the driver .exe and letting it do it all) leave a variety of remnants behind. I used driver sweeper (3D Guru) for a long time with decent results before moving to driver cleaner ($10 USD) and I am amazed at the things driver cleaner finds and cleans out. Best ten bucks I've spent in recent memory. Even nVidia doesn't recommend just running the executable and installing drivers over drivers as this will produce a witches brew with unpredicatable results. From nVidia: When an NVIDIA display driver update is performed, the new driver will remove the previous drivers during the installation processor. Sometimes it is not successful in removing the older display drivers which can lead to display issues later on as a result of conflicting drivers. As a basic practice, it is recommended that you first uninstall the older display drivers before updating to a newer version. . . Good Luck . . .

I've seen this occur since at least the original ArmA.

We're listening NeMeSis..:) What have you sorted out? Thanks ps -> - OPFOR AI are not telepathic, they have radios. - Hearing is more directionally accurate than anything second only to an instant sighting - We are set at 'Expert' with all AI at 1.00 and SuperAI enabled. - BIS please help restore the fight.

Thanks Sickboy I'll give this a shot as the stuttering is quite annoying. Other people on the server noticed the same issue but were not running CBA. I'll let you know how this works out. . . .

Hearing is much more accurate than some give it credit for. Go into a pitch black room with someone and see how long it takes to pinpoint their location from sound alone. Also, if hearing was of so little value in determing location why do most of us wear 5.1 or 7.1 headsets?? The AI, in my testing, has gone from a natural response to total oblivion and it is this aspect of the patch with which I take issue. BIS I'm begging you to restore the astute hearing and aggresive behavior which was so refreshingly welcome in the initial release. . . .

Google says: http://www.armaholic.com/page.php?id=5809 ;)

300 meters is a very short distance when it comes to gun shots from unsupressed weapons and explosives. Imagine you were the one at the base with your comrades and gunfire erupted from 300-400 meters...what would be your reaction from that base? And the 'live' AI can radio the info back to base so one way or the other the base is alerted and should immediately react. I'm going to do some more testing and if this is the way it will be then I can only hope for the rapid release of mods like TrueRangeAI to get the AI to step up and fight like more traditional human foes. I think it's a huge mistake to make the AI less astute and agressive but hey that's just me and of course a whole lot of my friends and associates. . . .

Yea Ethne I don't doubt for a second you're experiencing things exactly as you (and others) are describing. I'm on VU64 and just wanted to mention I didn't notice any of the issues which just means it may be an inconsistent, and potentially difficult to isolate, phenomenon. Best of Luck, . . .

Just tested this with a X-Fi Titanium Professional Audio and 6.0.1.1346 drivers on a X58 platform and no distorted sound. The low frequencies have been significantly extended and it actually sounds very good. Directionality is also spot on. The AI have gone stupid but that's for another thread..:rolleyes: . . .

The 285 has 1 GB of VRAM on board right? 1 megabytes = 1,048,576 bytes so multiply that by 1000 for 1GB and the entry for localVRAM in the ARMA2.CFG file would read: localVRAM=1048576000 nonlocalVRAM=(the size of your page file) AFAIK this is the correct setting but double check that nVidia stickie thread to see how they've got it worked out. I don't recall now if it was this that brought the high/very high settings up or not but I believe it was. Good luck and enjoy the game. . . .