Nipos

You can set any shortcut/executable to be run as Administrator. Just right click the OA Beta executable --> Properties --> Compatibility tab --> Tick the bottom box "Run this program as Administrator" and it will always run in Administrator mode. I think you need to re-take these steps every time you install a new Beta version, though.

This photo was found some months ago, approximately one mile South-West of the radio tower hill. From the looks of it, it seems that it was taken by a camera that was triggered when it touched the ground. The maker of the photo is still unknown up until this very day.

Hatchets? I'm not surprised. Nothing special? I'm not so sure about that...

Don't go there during nights when there's a full moon. Especially not when it's about to turn 12:05 AM, at which point you DON'T want to look East while standing at the main entrance with your back towards the... tower...

Nice troll post you got there.

Yeah, it's probably something pretty random, just as I encountered myself as well. Not really something you can find a direct cause for.

Remove 94945, install 94876 and you should be fine.

Weird, man. I don't know what to say... Have you tried underclocking your GPU a tiny bit? Just go into AMD Vision Control Centre --> Performance --> Graphics Overdrive and turn the clocks one or two nodges down (both top and bottom slider). You may have to enable Graphics Overdrive first under the AMD Overdrive tab, found under the same Performance tab at the bottom (if you've never enabled it before).

Also handy to know: that offer will be there until July the 23rd, BUT it's also possible to see ArmA II (CO/OA/DLCs) in one of the daily deals as well, with a much higher discount. ArmA II is well worth its money either way, but for the people with less money to spend, the advise is to wait at least until the 23rd. If ArmA II hasn't been in any of the daily deals by then, you can still pick it up for the normal 20% discount.

Alpha.

The one file failing to validate is nothing to be worried about, that happens with pretty much everyone. It's just an install script being newer than the default script that Steam's trying to validate and is just a small glitch in Steam's validating system. Just Google for "arma 2 failed to validate" and you'll see tons of threads and questions about this. It's not related to your problem. :)

Well, that has been a debate going on for years. Some say it's best to remove a previous driver (with the uninstalling program that comes with it, and using a program like Driversweeper in Windows Safe Mode after that). Others say it doesn't matter, and you can install newer drivers "over" older ones. I personally never remove older drivers first, unless there's something really borked.

Hmm, it seems that the OA Beta can be ruled out as a cause of these crashes. There are a couple of things you can do: 1) Update your DirectX, so you're sure you're using the latest version (http://www.microsoft...aylang=en&id=35) 2) Fiddle around with the Video Memory settings within ArmA II. I've got mine set at Default, using the the full memory available on my GPU that way. 3) Try installing older AMD drivers. I'd recommend starting with 12.3 or 12.4. I'm currently using 12.4, and whilst having had the same issue with this driver about one and a half week ago, it only showed up about three times. Game has been running properly after that (with still keeping 12.4). Go to http://downloads.guru3d.com/search.php and do a search for "Catalyst". It will bring up a list of pretty much all previous Catalyst driver versions.

Do these problems also show up when you're not actually wearing a Ghilli suit, but just have it in your inventory (the package you can unpack)? I found a Ghilli suit package the other day and had read about the problems people were having with wearing it, so I decided to not wear it and leave the packaged suit in my inventory.

I don't know, actually. I've always avoided the use Six Launcher (mainly because of stuff you're encountering now). I've been updating DayZ and the OA Beta manually ever since I started playing DayZ to have full control over installing/uninstalling stuff, without some program forcing updates etc. Also, make sure you've got the Beta set up properly (I don't know to which extent Six Launcher does this for you already): 1) Go to the Arma 2: Operation Arrowhead directory and right-click -> edit on the .cmd file "_runA2CO_beta.cmd". 2) Search for ":run" near the end of the file. Add ";@dayz" without quotes to "-mod=%_ARMA2PATH%;EXPANSION;ca" if it's not there already. It should say "-mod=%_ARMA2PATH%;EXPANSION;ca;@dayz".

Alright, try installing an older OA Beta version (94364 or 94444) and see how that works out for you. This way we have a chance of ruling out the OA Beta as the cause. You can get those here: http://www.arma2.com/beta-patch.php Delete the "beta" folder in your "arma 2 operation arrowhead\Expansion" folder first before installing a different beta version! That's the only proper (manual) way to uninstall OA Beta.

Have you been updating your OA Beta versions regularly (in other words; did your game crash/AMD Driver stop responding using earlier OA Beta versions)?

Which OA Beta version are you running? I had the same issue about a week and a half ago, but it magically disappeared after not changing anything but the OA Beta versions. During the time of getting the "AMD Driver has stopped working" errors, I was using OA Beta versions 94209 and 94364 (maybe even the version before 94209, can't remember). After updating to 94444, DayZ/ArmA II has been working perfectly, and the issue seems to have gone away. Here's what I posted in another thread that was addressing this problem: Like I said in the post, after some Googling, I found that ArmA II has been plagued by this issue before, so it's very likely - also looking at the thread where I made that post - that it's an ArmA II bug of some sorts. I'm still using the same AMD Driver version when I had this problem, by the way (12.4).

It also struck me that when you connect to a server extremely fast (after "Receiving Mission") you already know you're going to be stuck on the loading screen. Normally, connecting to a server and actually being able to walk around in the game takes about 30 seconds (not counting the first time you connect to a server when having just started the mod, it usually takes longer the first time). Now, I connect within literally 5-10 seconds after pressing OK in the server pool-menu where you can see the active players, but it results in getting stuck on the loading screen.

Same here. ArmA II OA (CO) on Steam, OA Beta 94444.

It's not hard to predict the outcome of this; the TOP-BR admin posting in this thread looks like one of the most incompetent admins out there. Can't wait for the vid!

Sorry for necroing this thread, but I've been having the same issues in 1.7.1.5. I've been monitoring my graphics card, because at first I thought it might be a temperature-related issue, but I'm fairly sure that's not it; temperature is sticking around 60-65 degrees Celcius when playing DayZ (idle/non-gaming temperature is between 44-48 degrees). I can run games like Battlefield 3 and Skyrim on high settings for hours without any problems. After some searching, I found that this issue was present in earlier builds of ArmA 2, but was supposed to be resolved. Maybe it came back due to DayZ-specific content/code? System specs: -AMD Phenom II X4 955 Black Edition @ 3.2 Ghz (no overclock) -HD5850 Toxic 1GB @ 820/1165 (slightly overclocked, standard clock is 765/1125) -8GB DDR3 SDRAM -2 x Samsung Spinpoint F3 1TB 7200 RPM -Be Quiet! 520 Watt PSU -Windows 7 Home Premium 64bit, SP1 (all latest updates present) Software versions: -DayZ: 1.7.1.5 (didn't notice these issues with previous DayZ builds) -Operation Arrowhead Beta: 94364 (issues were present while using earlier versions too) -AMD Catalyst Driver: 12.4 -Latest DirectX version

Test! (posted at 2:19 forum time, 2:17 on my PC)

Errr...yah. Timezones differ in hours' date=' not minutes, so it's impossible this could be caused by a faulty timezone setting. Obviously, changing my timezone (which was already set to the right one) didn't help a single bit. When I made that post, the forum time was about 20-21 minutes ahead of my time. Now it seems to be about 28 minutes ahead. -edit: here, let me make it more clear to you: [img']http://i45.tinypic.com/2w6x5zs.png In case you don't know, the time/date is generated by PHP, thus it is most likely an incorrect PHP configuration or something else in the server configuration. The only thing MyBB does is use PHP functionalities to have the time and date displayed correctly based on your timezone. In case you don't believe me, here it is: http://stackoverflow.com/questions/9593684/php-date-function-gets-wrong-minutes-why @Griff If you need any help, just let me know and I'll see what I can do. In short: forum time is messed up.