MavericK96

I can only surmise that this recent burst of rapid-fire betas means a final official patch is coming soon...? :D

Sorry I haven't been around as much, been working and other life-related things. Less time for gaming. :P Anyway, I just tested this versus the last build (78888), and the performance when scoping toward a forest is definitely improved. One issue I am noticing (and maybe this is an old one, it was in the previous beta as well) is that there is this white speckling around the edges of foliage now. I'm thinking maybe it has something to do with this AToC that was added (again, I am sort of behind the times here), but here's a screen of what I'm talking about: http://i263.photobucket.com/albums/ii140/AFireEternal/arma2oaspeckles.jpg > 100kb Is this normal? Or is something messed up in my drivers/settings? PC and settings are in sig.

I can't get -skipintro or -world=empty to work with any of the Steam/CO shortcuts anymore. They worked before I updated/installed PMC.

Have fun trying to play ArmA2 on that console...

Yeah, I've got dual GTX 280s in SLI and my performance is about on par with the single GTX 580 as well. Imagine 2 of those in SLI, though...*drool* :cool:

Gotcha, thanks. :cool: Weird place for that information to be, though. :p ---------- Post added at 03:41 PM ---------- Previous post was at 02:56 PM ---------- Yeah, this kinda sucks. No servers currently (that I can see, anyway) are running the new beta patch, so MP is kinda out for this one so far.

I'm not sure if these were in previous builds (I haven't really been testing lately, sorry :( ), but there seems to be new video options for HDR Quality and VSync. However, the VSync option doesn't seem to work for me (nothing shows up in the pulldown menu. Is this a known issue?

Default works best for me.

Nice, a new beta on my birthday. :cool:

http://www.arma2.com/beta-patch.php Sounds like a good couple of fixes: [72966] Fixed: AI stuck while in combat/stealth mode [72947] New: Explosive shells penetrate bushes; Fixed: FireAtPosition aimpoint [72924] Fixed: Multiplayer on LAN was crashing when GameSpy server was unavailable. [72851] New: GameSpy modhash key contains list of mods hashes and is used to check there are additional mods on server missing on client (yellow icon in UI). Enjoy!

In-game, in the lower right corner, you can see what the build number is. It shows up as x.xx.xxxxx. For instance, the latest build is 1.54.72967.

So it looks like Steam updated 1.54 to this build as being current? I ran OA vanilla (no beta) and it's build 72967.

I guess that makes some level of sense, but as long as you know what the 1.54 build number is (72967 I believe) you can just figure out if the latest betas are newer by the larger build number.

So, a question: How come the BAF DLC shows up as a separate game instead of under the DLC section of OA in Steam? Seems unnecessary.

Also this: http://forums.bistudio.com/showpost.php?p=1663202&postcount=1

Perhaps read the Steam thread in Troubleshooting?

Try reinstalling DirectX 9c, perhaps?

Not all the same tweaks work for the same people, though. It's kind of a trial-and-error situation.

NOT WORKING , DON'T DOWNLOAD :eek: http://www.arma2.com/beta-patch.php [72787] New: Mods contents hashes are compared instead of mods lists when equal mods are required on server. [72716] Fixed: Commandline -mod behavior, active Mods list in UI, ModLauncher UI dialog with better mods detection and handling. Enjoy!

That was actually included in the last beta. I just put the entries that were new to this beta. :cool:

Just did some benchmarking with this beta versus 72418. Honestly, not a lot different in terms of benchmark performance, but here are the results: [b]72418 72716[/b] Benchmark E08: 44 44 ArmAIIMark: 4993.04 5063.93 Cherno _TEST_FPS6: 35, 24, 49, 7 34, 24, 47, 7 (Avg, AvgMin, Max, Min) Notes: -LOD switching seemed faster in 72716. -Weird bug with ArmAIIMark in 72716 where in the first test (Jeep Run), the trailing jeep got stuck on the road, stuttering forward tiny amounts, until finally a bit later driving on. However, the benchmark stopped before the jeep passed into the city, so I think it may have affected framerate a bit (higher framerate than should have been). -Possibly some shadow flickering in 72716 that I didn't notice before. In any case, seems like a good build, though performance did not skyrocket for me like others are stating.

That is odd. I'm guessing it's because ArmA2 does not play nicely with Crossfire?

Or maybe just ArmA2 and OA/CO, since both OA and CO use the same .exe file.

Probably ACE-related. The official missions aren't meant to be played with ACE.

Well, your CPU is not super-fast and your GPU is not super-fast, either. I'd maybe try overclocking your CPU, if possible. You really want 3.0+ GHz for this game. And your GPU is coming up on being 2 generations old.