thebluefish92

Thank god someone has it right. Some hackers are somewhat cool because they can do innovative shit. Script kiddies on the other hand.. Oh wait' date=' just searching for some DayZ hacks shows a couple threads and a shitload of Pastebin posts explaining EXACTLY how people were doing it before the global ban. Holy shit if I wanted I could do that in like 5 minutes?! MAN LET'S START SUPPORTING MY FAVORITE DEVELOPER BY BANNING ALLLLLL THE KEYS. [img']http://cdn.memegenerator.net/instances/400x/22322277.jpg

Set you options all to default (Go to Video settings, set to default, controls, set to default, etc...), and restart. If that doesn't work, try removing the @DayZ folder, redownload the latest DayZ from a torrent (NOT SixLauncher!), and try again. If that doesn't work, then uninstall both ArmA 2 and OA, and install them in the following order: ArmA 2 - run it at least once ArmA 2 1.11 patch (can get off the ArmA 2 website) ArmA 2 OA - run it at least once ArmA 2 OA 1.60 patch (can get off the ArmA 2 website) ArmA 2 OA Beta patch (latest) DayZ (NOT from SixLauncher/SixUpdater, install from latest torrent) Script Restriction errors are odd and mostly undocumented. So if you rule out the possibility of SixLauncher, DayZ, or your own settings, then a full reinstall is in order.

If anyone else is getting issues with the Amazon version, here's what I did to fix it. Even when I followed most steps pretty close, I was getting issues with the beta patch. - I first uninstalled OA, then ArmA2, then both BattleEye installs - Installed ArmA2, played to the menu screen, exited - Installed ArmA2 1.11 patch* - Installed ArmA2 OA, played to the menu screen, exited - Installed ArmA2 1.60 patch* - Installed DayZ, enabled in menu - Installed latest OA beta patch, ran just fine * - I tried this process both with, and without the patches. For some reason if I omitted either one of them, I got the oddest of errors when trying to play the beta, and installing them afterwards didn't seem to actually do anything. This is after probably 4-5 attempts with the install.

I was in NW Airfield barracks on Seattle 13 when I found this glitched ammo box. It contained 20 mags of STANAG and 2 mags of STANAG SD. This is running latest arma 2 beta, DayZ 1.7 on the Seattle 13 server.

Actually, after further review of what kind of hacking is currently being done, it seems that this was a hack-spawned box rather than a glitched one.

I had at one point, an M249 with 3 boxes of ammo. In my backpack I had an mp5sd with 4 mags. I had dropped the M249, and it laid on the ground with all of its ammo perfectly. I then equipped the mp5sd, and everything was dandy. Then the server crashed. I logged back in, and I had the M249 with ammo, and the mp5sd in my bag with the 4 mags. So I tried it again, except this time the M249 and ammo all magically disappeared when I dropped it. Running latest arma 2 beta and dayz 1.7.

Man, I'm running an e8500 dual-core, 4gb ram, and a 9800 GTX+ and I'm breezing at 50+ fps on medium setting with a couple turned to low. Check your GPU utilization, see if Arma 2 is even using all of it. You may want to try restarting your computer. Make sure you're also connecting to a good server, if the server itself is lagging, your framerate will drop miserably as well. I've seen some servers where i'm getting 15-20, and others where I'm maxing 50-60.

It's not a gun that normally spawns in DayZ, so a hacker had to have spawned it in himself.

Ok, so what is it with crashing cars? I have a van, going ~35 and accidentally hit a sign, knocking out my windows. Next thing I know, I'm bleeding, in shock on the ground, and end up dying along with 2 of my friends. Is is really this dangerous?