G0lden

Bumping this for justice. I'm having the same exact problem, got 1.2 from the facebook link / passworded .rar as well. Can't get logs or spy to work.

Read on the Battleye FAQ that Arma 3 needs to have administrator privileges and that fixed the issue for me. Things to try: 1. Find the arma 3 exe file and launch it as administrator (or go under compatibility settings and set it there) 2. Go to the official battleye page and go to the download page. Follow the instructions there (replace the client and server dlls in your arma 3 battleye folder)

Could you give an example or description of the call feature? Or perhaps some resources on how to use it? Loving the work so far

I would just like to add that kids with "hacks"/scripts have increased exponentially since release of alpha. Makes it very hard to play when someone picks a game type and runs through every server of it trying to clear all the players out / shut it down. I would say this is the worst problem in all of arma 2 or arma 3 alpha, more damaging than minor bugs for sure, can't wait to see what's in store for anti-cheat software.

Yeah I have had my bad moments with steam but they're always improving and I really have no complaints about it anymore, love it. As far as battleye goes isn't it effective at holding the bans by basing them off of players' guids? I figure as long as script kiddies and hackers are identified you can ban them based off of everything that links them to arma. Whether that be their cd key or IP address, both, or some other method. Let's face it, illegal copies are out there and a determined person will change their ip address/get another copy somehow but it just needs to be made very difficult for them to get through once identified. Detection, Protection, Maintenance, and Removal(of these ill-persons) is the key to all this I think. In arma 2 the biggest problems I've ever had is hackers/scripters and the unoptimized code(network transfer and graphics code) but you know what, it's still my most played game ever and my most favorite because the concept is so unique and awesome. I hope arma 3 is better at keeping people that like to destroy servers away but either way I will be playing it.

So direct communication worked for a long time for me until i had to get rid of my mic. Since then I cannot see or hear direct chat and I do not even see people's mouths' moving when they talk in direct (confirming they are talking in direct with third party VOIN software over a period of many days of attempting to fix the problem). What I have found through my digging is a few solutions. 1) Make sure that arma 2 and arma 2 OA are allowed through your firewall (probably already are but make sure). 2) Verifying steam cache files, for some reason this fixes a whole range of problems, especially after a clean install. (for me it has fixed server connection issues after a clean install) 3) Your beta version should match the server's beta version or you need to run vanilla arma 2 OA(no beta patches). Doing a clean install of arma 2, verifying the cache files, launching arma 2, then clean install of arma 2 OA, verifying the cache files, launching arma 2 OA will get you back to vanilla which should work regardless of the server's beta version. 4) Having a mic plugged in and activated through your operating system (windows sound options). I believe that this will be the ideal solution as I have played arma 2 OA since it came out and up until I had to order a new mic I never had any problems with direct communication. I will be able to confirm this in a few days but hopefully these solutions will work for anyone still struggling with direct communication issues and maybe even other issues.