SpecFour

Your control group is wrong. You need to test your theory on a number of people you have not RUN OVER WITH A BUS...

I think: 1. Why does there need to be another thread like this? and B. You misstate the position. Most of us bitching aren't complaining JUST that we got killed, as shown by prior replies. My latest annoying-as-fuck death is from a sniper I never saw, who doesn't need my dang flashlight. It's just killing for the sake of killing. That makes little sense. Yeah, I'm in a field with fuck-all cover for 75m, but that was the way out of town. My presence doesn't require that you go to Def Con Two and immediately kill me. I have a FLASHLIGHT in my hands, and it is daytime. It will take me 10 seconds to switch to that silenced M16A2 with a latte attachment and can opener that you think I am hiding in my pack. Some of my favorite vids on YouTube are from Acebane. S6 makes no bones about killing other players they encounter, and that's how it works. They don't camp out and snipe, however. His latest vid is him and a buddy taking on four other players. That's cool. Numbers against them, but they have surprise. I got no problem with that. Every time I encounter another player and he has a weapon and I have a weapon, and nobody gets shot, THAT is a "win" for Humanity. And if he blows me away for a Makarov mag, I understand. I like it when we can work things out without Death, but sometimes Death happens. C'est la vie. But if you use your NVG to put a round through the back of my head at 400m, there is something wrong with you. My instinct is that person should be doing homework, or his parents should have sent him off to Space Camp or something. Or they should make him play outside, or even just fucking talk to him twice a day. Something other than just letting him kill people on the Internet.

Download ARMA II Free and see how it runs. I'm not sure DayZ adds much overhead, if any. http://www.arma2.com/free/ I run on an Intel Q9450 (quad at 2.6ghz, but oc'd to 3ghz) with a GTX 260 and 4gig. I run it at whatever graphics options it installed at, and it runs fine. It think yours will run, but some people get funy FPS even with i7 cpus.

Bitches ain't shit but hoes and tricks... - Dr. Dre

Zipper, you are one SERIOUS mofo. Serious as in stern. Not as in "on the scale of MOFOs, you are a serious one." Let's reduce it to this: Many of us are playing to have fun. Our fun doesn't include blasting the beejeezus out of people because they pointed a flashlight at us, or because they are sneaking through a field 200m away and don't even know a sniper is camped out with an AS50 jerking off to zombie porn. Our fun doesn't intrude upon the fun of others. PK'ers - their "fun" is to cause harm to others. There is just something fundamentally wrong with that. If a person doesn't recognize that, they are lacking something in the Humanity department. That is quite a curiosity when revealed by a game that concerns zombies. And stop telling me what I must do when posting. Who made you a moderator? Your attitude blows dead goats.

Zipper foamed at the mouth and said: "What you are proposing is a simplistic hippie driven mindset." 1. I didn't make categorial imperative up, Immanuel Kant did. 2. If you call Immanuel Kant a hippie again, I will track you down and PK you. 3. He wasn't a hippie. He was German. Two totally different things. Categorial imperative (CI) doesn't require that people group up, and I never advocated for that. I'd like to be a part of a group for two reasons: 1) protection; and B- to contribute to something greater that I cannot accomplish, like a car. Other than that, my goal is to use that protection to arm myself and head out to shoot snipers, for the good of other players. My latest character got some loot luck after spawn, but sure enough, some guy sniped me when I was getting out of town. I was not a threat, I was heading away from him. That annoys me because my time has been wasted, and Dildo-PK'er doesn't suffer any consequences. My post isn't any attempt to extrapolate the end-all-be-all of what will happen in a Zombie Apocalypse ™ because that will never happen. The post is directed at WHY PK'ing annoys the fuck out of some of us. Just like some people fuck their cousins, some people PK. The rest of us just wish the cousin-fuckers would find their own little island to go do that on, and leave us out of it. In Basic I had two guys from Kentucky in our room in the barracks. Man, I didn't know there actually was so much cousin-fucking going on in this world. Neither of those guys would have the brains to install a beta-patch, however, but they would both be PK'ers if they could figure this game out. I know it.

Check into Immanuel Kant and his philosophical doctrine of categorical imperative. Man is not a beast. Man is set apart from beasts, and thermostats, by our ability to reason, and free will. Dogs hump your leg because they are driven by desire, not reason. Thermostats turn on, because they are driven by physics, not reason or free will. Man is not so driven, and should get his head out of his ass and act like it. That is, you do not shoot people on site, because using that as your categorical imperative means everyone just kills everyone. That is the rule of the jungle, not man. See also, Queen v Dudley and Stephens [1884] 14 Queen's Bench 273 (The Lifeboat Case, or why you cannot kill and eat the cabin boy.) A more widespread statement of categorical imperative, blasted across every chalkboard I remember as a child, is the Golden Rule - Do unto others as you would have them do unto you. As long as you expect other people to shoot you on site and you aren't going to bitch about it like a little girl, "Shoot on site" works. There are those of us that think Man is made of sterner stuff than a dog humping a stuffed animal, however. But, there are certainly those among us who clearly have nothing else going for them than stuffed animal humping. I had a buddy in high school who was a world class stuffed animal humper, and he is still a POS.

Larkinto: Getting your first period is a special time in your life. It will cause you frustration and anxiety, and you might turn into a little bitch.

To play DayZ you need: - ArmaII (can get latest public patch from their site) - ArmaII:Operation Arrowhead (can get latest public patch from their site) - beta patch for Operation Arrowhead (This is just a patch that isn't made widely known to the public.) - DayZ mod files ArmaII and Operation Arrowhead, slapped together, are called ArmaII: Combined Operations. You can purchase each separately, or as a pack, Combined Ops. $20 to $30 right now, I believe. Beta and the mod files are free. Steam is an online software retailer. You purchase and download through their own software. I believe you MUST have full-time Internet connection, which most people have now, at least in the US. Steam is not required to play this, it is just convenient for a lot of people. I'm runnning on a Intel Q9450 running at 3ghz, GTX 260 with 4meg of memory and have no problems. You should have no problems with that PC's specs.

Furious: I'm having trouble keeping all the different errors straight, but I believe the D3D9 error is either an admin error, or not running the patched OA file. - Make sure Steam runs as admin. - Make sure the patched OA is run.

http://www.arma2.com/beta-patch.php The @dayz means the dayz mod is installed and recognized, at least to some extent. Beta - You have to download and run the executable in the archive. Normally, you then need to rename the arma2oa file in your root ArmaOA directory, and copy the arma2oa application file from \expansion\beta\. A lot of people seem to miss this step. I've been off for a couple days. When I left, 94444 was the latest beta. I think dayz is requiring the latest beta at all times, but I could be wrong. My understanding is that DayZ 7.1.2 is out now, up from 7.1.1.5, I believe.

I would delete everything and start over. - Install ARMA2 and run it as an admin. It sounds like you know how to do the admin thing. - Install OA. Since you are going through Steam, I would suggest setting both the Steam application and the Arma2OA application to run as admin. - Run Combined Ops. Since you have retail Arma2 and Steam OA, I don't know how your system would do this. I have steam for both. When I am at the Steam game menu and double-clock OA, it asks if I want to run OA, or combined ops (or reinstall BattleEye, and one other thing). If both Arma2 and OA already run themselves as admin, this should run as admin also. That's the easy part. six-Launcher: 1.7.1.5 -> I don't use that. 1.7.1.5 is the current DayZ version OA version: 1.60.87580 -> 1.6 is latest version. 87580 is a patch version, and it isn't the latest beta patch ARMA 2 original: 1.06.70710 -> I'm not worrying about this. You can check Arma's site for the latest update. OA patch (from the arma2 website): patch 1.60 -> Steam should automatically hook you up with the latest "public" patch DayZ requires the beta patch for OA. http://www.arma2.com/beta-patch.php That site has been having problems lately... You need to download 94444. When you open the archive, you need to run the executable that is in it. For steam, you then need to make sure the Steam client is running the PATCHED executable. For me: - Go into OA directory under \steamapps\common\ - rename arma2oa application to arma2oa_backup - Navigate from that directory into \Expansion\beta\ - right click arma2oa and copy it - go back to the OA directory and paste this in there In Steam, right click OA in your game library. Select properties. There is a button for SET LAUNCH OPTIONS. There are the user-defined parameters you can pass to the application. Mine says: -mod=%_ARMA2PATH%;EXPANSION;ca;@dayz -beta=Expansion\beta;Expansion\beta\Expansion -nosplash -cpuCount=4 -exThreads=7 -world=empty -maxmem=3096 %1 %2 %3 %4 Collectively, the -mod and -beta parameters pass the Expansion, beta and DayZ mods to the program. Your paths may be different. The %_ARMA2PATH_% means there is a system variable set somewhere for that root directory with respect to the OA program. I don't know which install set that. This works for me, and I'm not messing with it. Now run either OA or Combined Ops and at the main menu you should have a version number of 1.60.94444. At the top right, under the icons, you should have small, bright letters that say Expansion, beta, and DayZ if you have it installed already. I think you are missing the beta patch. It sounds complex, but it is three steps: 1. Install beta patch. 2. Make sure Steam is running the beta executable (the instructions for this are different than in the readme because the readme is for Arma2, NOT for DayZ and Steam...) 3. Make sure the right parameters are passed to your program. -

The checkbox image is OA working properly. Mine pauses with two boxes left, and then eventually gets past that. I don't use Launcher, so can't help you with that problem. Even if you have the beta installed, part two of that is running the executable that comes with the beta patch. If you install the beta patch, but do not run the new executable, that's a problem. Are you using Steam or retail?

Find your Steam executable. It is in your main Steam directory. It is called Steam and its TYPE is Application. Right click it, select Properties. Select Compatibility tab, click the RUN AS ADMIN clickbox. APPLY then OK.

Inventory can be difficult. I'd get on Youtube and look for some vids. Easier to show than describe. If you mouse wheel on something and TAKE it, it tries to put it in your main inventory - NOT in your backback. Your main inventory/gear screen is NOT your backpack. So this is either in your: - MAIN SLOTS - Water, soda, food, flares, lightsticks, cans and bottles, etc. - "BELT" slots - secondary weapon ammo and bandages - TOOLBELT - Map, compass, gps, toolbox, hatchet, etc. I won't even try to describe how you use the backpack. The English language isn't sufficient. Lightsticks - On your regular "running around" screen, press F and you will toggle through some things in the top right corner. THROW is one of the things that comes up. If you have lightsticks, you can throw them by equiping them, then throwing them with the left mouse button. Hold it down a little. Then you can walk up to the stick on the ground and if you mouse over it you can extinguish it, or pick it up. If you pick it up, then you get shot if you run into anybody. Because they can see you. Beng. Fire - ???? First Aid Kit - No such thing. You mean bandage? Only some things are usuable from within your GEAR screen.

I think this is usually a beta issue. Are you running the patched beta for OA? When you get to the main menu, there is a version number in the bottom right corner. It should be 1.60.94444, I believe. Anything else and you will have problems. Also, at the menu screen under the icons in the top right, what expansions are listed there in tiny, bright letters? I have four things listed. What do you got?

Running as admin? The only error I recognize there is "bad serial number" and I think that is an admin error.

- game cache integrity - not running as admin - not running patched executable If running through Steam, did you rename the old OA executable and copy the patched executable from \Expansion\beta\ into the OA folder? I was able to duplicate that error at one point, but now I do not remember how. I'm feeling it might have been the admin thing. If you have a Steam shortcut on your desktop, right click it and go to PROPERTIES. Under SHORTCUT tab there is a button for ADVANCED. In that there is a click box to run as admin. If your system automatically runs Steam then you probably want to find your main Steam application/executable and set it to run as admin.

It isn't working for me either, but it isn't asking for a password like some people say. Just be patient.

START OVER, GUYS... There are five or six steps to getting this all installed right unless you use Six Launcher. That program didn't work for me, so I don't know how many steps there are. 1. Uninstall the programs. 2. Install ARMAII and run it as an admin. If you have a Steam shortcut, you need to make sure it is running as admin. Possibly for both the Steam program, and ArmaII. The admin option is under PROPERTIES, Advanced button. If this runs correctly, go to 2. When you run it, jump into Boot Camp or something and make sure it actually runs. 3. Install OA, and run OA (NOT Combined Ops) as admin. (I have Steam version. When you run OA it gives you an option between OA or Ops. I do not know how the retail versions will do this.) 4. Run Combined Ops. If this is working correction, I believe you will have two icons in the bottom left. ArmaII and OA. Your version number in the bottom right is probably 1.xx.93xxx or something smaller. 5. Download the beta patch and run the executable that is in the archive. The site is: http://www.arma2.com/beta-patch.php. (It isn't asking me for a password, but it isn't working RIGHT NOW. You need the one at the top, which is 94444 unless they issue a new patch in the next couple hourse, which COULD happen...) 6. READ THE README FILE that is in the archive. You need to pass some new parameters to the executable. Specifically, you need -mod=Expansion\beta;Expansion\beta\Expansion *** If you are using Steam, you almost certainly need to go to the directory where OA is installed and rename arma2oa.exe. This is the executable file for OA. Rename it to BACKUP_arma2oa.exe, or whatever you want. The "exe" probably doesn't show up in your directory. If it does not, ignore it. It's old-school vernacular for an application file. *** If you are using Steam, from the install directory for OA, go into the Expansion folder, then into the beta folder. There is another file called arma2oa.exe. Right click and COPY it. Go back to the installation folder for OA and PASTE that in there. When Steam runs OA or Combined Ops, it should now use the patched executable. 7. Run Combined Ops. If all this has worked so far, two magical things will happen: A) At the bottom right, your version should be 94444 or whatever the latest patch is. If it is not, you are probably still running the original executable. Either Steam or a shortcut or Six Launcher are pointing at the wrong executable. (I don't know if that is possible with Launcher...) Nobody on these boards can figure out exactly how you are doing that. FIX THAT. B) At the top right, under the icons, you should have tiny letters in some bright color that say arma2, Expansion, beta. You may or may not have arma2 - I do, so I am guessing you should also. If you do not have Expansion and beta, the -mod parameters are not being passed to your executable properly. FIX THAT. 8. Put the DayZ mod files in your OA directory under \@Dayz\addons\. Add the -mod=@DayZ parameter in Steam or in your shortcut. FINALLY, run Combined Ops again. In addition to A and B above, you should now have tiny, bright letters for @DayZ in the top right. You should, most likely, hopefully, I am praying that you can, be able to connect to a server now. It is very important to remember you are installing two separate programs that could have their own bugs between them. Then you are installing a BETA fucking patch for one of those programs, which requires that you run a different executable AND modify your command line parameters. THEN you are installing an ALPHA mod for a program, half of which is BETA. You CANNOT just throw all this crap together and then post saying "I am invisible and I cannot eat beans" and expect other people to figure this out. Install one step at a time and make sure it is working. Or use Six Launcher and read the instructions. My guess is it works really well if you follow the instructions, or Rocket would not have adopted it to assist the community.

You need: - ArmaII - Operation Arrowhead - beta patch for OA, currently 94444 - DayZ mod files Many/most people are screwing up the beta. You must install the patch now - it used to be optional. After installation, you need to make sure you are running the patched executable and not the original OA executable. You need to make sure the proper parameters are passed to your executable. You no longer start with a Makarov. Bandage, flashlight and painkillers are it, I believe.

http://forums.steampowered.com/forums/showthread.php?t=2754932 Sounds like you might not be running as admin. Right click your steam shortcut, select Properties, Shortcut tab, Advanced button, click "run as admin." Whenever I get an error in steam I google steam and the language of the error. I'm bookmarking your post so I'll check back, and I keep crazy hours... Make sure you have the beta patch installed. Check FOXCONNED's post in the link I gave you. Ultimately, you need: - Steam (run as admin) - ARMAII (run as admin) - OA patched to 94444 (run as admin AND make sure you are running the patched beta executable NOT the original executable) - latest DayZ mod files

That file size doesn't match mine. WHERE/WHEN are you getting this error? - You installed ARMAII and it ran fine? - You installed OA and it installed fine? But would not run? Or is it bailing during the install?

Delete everything. - Install ARMA2, run as admin. - Install OA, run OA as admin. - Run ARMA: Combined OPs, as admin. (I don't KNOW that you must do this, but why the heck not?) - Download and install beta patch: http://www.arma2.com/beta-patch.php - Read the readme file and FOLLOW THOSE INSTRUCTIONS. - Install the mod files under \@DayZ\addons\. You need to add -mod=@dayz, like in the readme file. >no debug monitor/no zombies couldn't go third person, Usually a lack of beta patch. It is required now. >I used Six Updater, Partially fixed it, but i can't talk to people/ >im invisible and the guns don't fire. Invisibility is usually beta issue. Never heard of guns not firing. Did you reload? Is your PC plugged in???

If it is updating but not running through Launcher, and you can run it fine through Steam, I wouldn't muck around with it. Bookmark http://www.arma2.com/beta-patch.php to see when new patches come out, or just run Launcher once a day. Same thing for the mod files. The beta patch includes a new executable, and you MUST use the new executable. For the life of me I cannot imagine how Launcher could update and patch, but then not use the new files, but I reinstalled and got this error today after patching OA, and running the old executable. I THINK it has something to do with the Steam overlay interfacing with the ganm's graphics. Not a programmer, however.