John (DayZ)

When I updated to the beta patch, it started giving me this error whenever I tried to play ACE. Now that I've updated to 1.7.1.5, it's giving me this whenever I try to play DayZ. Seriously, why are we using the beta patch? All it does is bug the living shit out of your game while fixing approximately fuck all. At any rate, is there any solution to this that I could take a run at before just deleting the entire game, reinstalling it, and using the buggy, haphazard mess that is SixUpdater?

Thanks for the help, I got it working, though I'm having major framerate issues. Any idea about getting ACE to work? I haven't been able to play it in weeks.

Curious. I can almost never see the sun - seems as though it's perpetually overcast in post-apocalyptia. Regardless, the compass is much faster and more reliable. I don't need one to navigate but I certainly enjoy the benefits of having one.

Come now, Rocket. You just made that up to screw with us.

Correct me if I'm wronger, but aren't you supposed to be able to use one of the machine guns on the crashed helicopter? And I haven't found one since all these updates came out, but I know that throughout 1.7.0 helicopters spawned literally fuck all. Is that fixed?

Okay, so, I assume this section is meant for DayZ troubleshooting, but I really need some help with ACE - and, despite trying my hardest, I can't seem to access their Issue Tracker or their forums. Both just freeze up my browser when I try to navigate to them. Being such a niche mod, this is essentially the only place I can even think of to ask for help! Since I installed the beta, I have been unable to play ACE. I managed to rig DayZ into working with the beta (which was a damned task in and of itself), but no amount of screwing about will get ACE up and running. I run it through the Six Updater (I don't know of any other way to do it), and before installing the most recent beta patch, it worked fine. Now, it crashes every time I try to open it, saying something about a Direct 3D engine failing to initialize, or something. Please help. D:

Uh, no thank you. I understand where you're coming from, and while this isn't a finished product, that doesn't make it any less of a game. I enjoy working my bootay off and getting nice gear to survive with. I don't particularly like the idea of losing everything I have every time Rocket breaks something and has to release six hotfixes in a row. Besides, this would actually send the deathmatching "issue" into overdrive. You know those guys that play just to get a DMR and sit on top of a building in Cherno? Well, that's going to be 90% of the playerbase, when everything we do stops mattering because within a week Rocket will release a new patch that will destroy everybody's work.

If you're running the game through SixUpdater and not SixLauncher (which has never even fucking worked for me anyway), the option on the top left - where it has several choices, like Update Game, Check BIkeys, etc. - should have a setting that just says "Launch Game." That should get you up and running. If not, you'll have to work out how to set the game up through Steam, really. That's how I do it anyway. SixUpdater has always been more of a headache than it is an aid, to me.

I haven't even played since 1.7.1.1 was released. I miss my vaguely stable 1.7.0, but even more so, my gorgeous, perfect 1.6.8. On the bright side the idea of unintentionally spawning five hundred hatchets is hilarious!

I've been playing since something like rev 1.5.8, and I've had two UAZs, two ATVs, a red car that I don't know the name of, three bicycles, and one bus. I'm still waitin' on a Huey.

Yeah, I feel like this was a very negative addition to DayZ overall. As for cars, though, I'd have to disagree - I believe Rocket stated that DayZ is set fairly well off into the future after a massive apocalyptic event. In a third world country, like Chernarus, cars are a status symbol - a lot of the civilians are destitute Eastern European farmers. The majority of the cars that did exist would have been taken, destroyed, or scavenged long ago. Perhaps in a city the size/scope of, and with the same number of residents as, say, New York City, you'd see more cars. In this environment, the current number of cars is even a bit excessive in my opinion - though I don't mind. I really don't use them anyway. Too much hassle!

I've been having the "1.7.0 BUT NOT 1.7.0" issue since 1.7.0 came out. I understand that a lot of people don't like 1.7.0, but it irks me that some server owners would change the name of their server to the version they aren't running. Apparently that's still an issue.

Anybody know why we're being forced to use the beta patch? I had some issues getting it to work at first, but now it's all right - it seems that a startling amount of people have no functionality with the beta at all, though. Before it wasn't a huge issue, but now we're being pigeonholed into using the beta just to run DayZ, and it seems to be having a pretty negative outcome.

Yup. I am confined to DayZ: ACE will not work no matter what I do. It doesn't help that any and all troubleshooting about ArmA II was either written by people that have no idea how to utilize English or are too familiar with their scripting languages to make any sense, either. Glad I updated to the beta patch. So very glad.

Oop. Yeah. Now I'm trying to play ACE and all I get is "Error creating Direct3D 9 Graphical engine." Wee!

Works for me, not without an inexcusable amount of rigging. Completely destroyed my friend's game, despite having installed it in exactly the same way that I did. As for performance increases, I've noticed none; nor did I care about direct chat beforehand.

Much appreciated, managed to get her running just fine - though I have to say the level of jerry-rigging that goes into just getting the mod to run properly, now, is wearisome. This will be a nightmare to explain to any new friends I bring to the game.

I can't seem to figure out how to run Combined Operations with both DayZ and the beta patch on Steam. I installed the beta patch and 1.7.1 properly, but when I run Combined Ops with DayZ it runs it in an outdated, non-beta patch. The only way I can even figure to run the beta is via the Operation Arrowhead folder - and that's only for Arrowhead, not Combined Operations, so not only do I not have my Steam overlay (which is very useful), but I can't get into a DayZ server because I'm running OA instead of CO. Somebody please help. ):

Thank S0N0S. Seems to be working fine for me now that I reinstalled BattleEye, though, naturally, it's dark as hell in-game. Silly moon cycle. At any rate, I'm a bit frustrated at just how much jerry rigging goes into getting this mod functional now - I'm pretty eager for that standalone client deal. I'm also wary of using the SixUpdater, because it's been nothing but a technical headache since the day I started using it for ACE.

Well, luckily, somebody in the main rolling update thread posted this: http://www.neogaf.com/forum/showpost.php?p=38340497&postcount=6612 It seems to get the game running, but now I'm having an issue with BattleEye that I'm trying to resolve. This game is a motherfucking Matryoshka doll with anal sodomy on every new tier.

How in the fuck do I get ArmA II to run on the beta patch in conjunction with DayZ? I keep re-reading the readme, but frankly, somebody at BI has a very poor grasp on the English language.