You fine sir did a fine job being this fast, but you might have done something wrong because im still no whilelisted. Drinking fermented bambojuice while adding people to whitelist might not be the most clever move ;)

-Name Honey Badger -Location Denmark -GUID d694629c8d005f8f918b728e49d64ff2 i place on the whitelist would be much appreciated :D

well for one play on a 1.7.2.4 server, that alone lowers the amount of hackers. if you play in the EU i would suggest the DK6 server. They use the community driven banlist and script detection http://code.google.com/p/dayz-community-banlist/, and the admin goes through the log everyday for illegal script detection. Plus the clan which run the server has rules against combat loging. The times my squard has been engaged with them they died like men and no combat loging or we did ;)

Well sure that works.. we run ran one of the few 100 players server for 2 days. Got nuked and hacked all the time, so we were forced to close it. <_<. What we really would like is to see who killed who, so we can sling the ban hammer right and left. the "x were killed" is just annoying.

True that hackers are a serious problem, and it proberly wont be fixed until the standalone version is released, but many players judge til game as it is right now and you can be sure that if BI studio/rocket fuck up the standalone on release and it turns out there is major hacking loopholes to be exploited, every gameing news site will be on it like vultures on a carcass and getting bad press on major gaming sites would affect the studio and game.

US73 was nuked 18.07.2012 04:27:25 by Mr. T GUID:e1f3d72204a77fe66679f8391c47a20c The hacker was found in our server/hive logs. if someone from the dayz team need them feel free to msg me.

did the exact same thing :P but i had a URAL nearby to started to push it up hill again. unless you got something able to push it up hill or knock down the trees on the hill so it can slide down then you are out of luck

if you got the exact same beta patch version and Dayz patch as the server and still have issue joining try updateing Battleeye: http://www.battleye.com/download.html. If that does not help the server has proberly not updated their own battleeye to the correct version. At which point you are out of luck until they do it.

They have implemented a "fail-safe" feature so if you spawn in the debug zone, you will respawn near the coast with all your previous gear, the next time you join a server.

Here are the full values. Standing targets/Zeds Standard US mildot rangeing system (M24,DMR,M107 all zoomed) - constant = 2, so the formula is 2*1000/mildot height=range (DMR,M105 not zoomed) - constant = 0.65, so the formula is 0.65*1000/mildot height=range AS50 British Mildot system AS50 zoomed - constant = 1.4, so the formula is 1.4*1000/mildot height=range AS50 not zoomed - constant = 0.45, so the formula is 0.45*1000/mildot height=range Crouched Targets/Monkey Zeds Standard US mildot rangeing system (M24,DMR,M107 all zoomed) - constant = 1.2, so the formula is 1.2*1000/mildot height=range (DMR,M105 not zoomed) - constant = 0.4, so the formula is 0.4*1000/mildot height=range AS50 British Mildot system AS50 zoomed - constant = 0.8, so the formula is 0.8*1000/mildot height=range AS50 not zoomed - constant = 0.3, so the formula is 0.3*1000/mildot height=range

i can run them for you. Here some extra info. when useing unzoomed scope the object height is set to 0.65 on DMR, M24, M107 and on the AS50 it is 0.45 so 0.45*1000/mildot height and if you want to be pro you can also take your elevation compared to your targets elevation for a 100% correct shot. useing pythagoras.

I ran some tests and came up with these numbers. The formula is as you said Height*1000/mildot height. Range to target on DMR, M107 and M24 is done useing this Height of object is set to 2m so the math is: 2*1000/mildot height. While the AS50 has the wrong mildot distance in the scope you can still use it.. just change target height value. The correct formula is setting target height to 1.4m (donno why but this compensates) and the math is: 1.4*1000/mildot height these values are all when useing zoomed scope.

Removeing respawn option in a alpha stage = bad. Cause well this is a alpha and there is still bugs breaking peoples legs and getting them stuck all over the map. So a complete removeal of this option is a bad decision. Sure i dont mind running, i like running in this game (even if i got vehicles) because i never know what i might find. But breaking a leg because i accidently walked over a tiny rock miles away from the nearest "natural" death would make me mad, and i would proberly quit playing the game after a few times experianceing this scenario. Just put a timer on the respawn option. or heck even put a forced 5min coma everytime you die if the timer is not programmable, just dont remove it. im all in for the improvement of server performence, but not a the expense of a 1km crawl to the nearest zed infected house. Edit: or make morphine spawn more often and more places :D

yep. had a encounter a hour ago, basicly i see a player in a open field, so i stay like 50 meters inside the forrest outline. 3min later we cross paths again this time he opens fire even after i shouted "DON'T SHOOT IM FRIENDLY" in direct coms. The sad part was he emptied 3 DMR mags into the large tree i was taken cover behind. Only to witness me shoot him in the leg when he was reloading and leaveing him. Guess he found it importent to waste ammo on a tree :D. Another example was me and a buddy getting killed by a AS50 dude while driving our newly acquired jeep. When we finally got back to the spot both our bodies and the car was still there.. i dont get it ? why leave all our items and the car ? :huh: one of us even had NVG.

welcome to the game where all your data is stored on a overloaded Hive server. It proberly missed some packages when it saved your characters state And don't server hop that is a lewd way of playing the game. plus the odds of hive fucking up tenfolds

look at my reply # 13 http://dayzmod.com/forum/index.php?/topic/41136-fucking-bullshit/

There is your problem, been told by our server provider, that them and other hosting companies have been haveing issues with the US hive cluster, and that Bistudio have a repesentive onroute to it. Why they havent made a announcement god only knows. This is what we were told by our Host. The EU hive cluster is also haveing trouble because is has to compensate for the loss of the US one( my theory) . So don't expect progress to be saved properly on EU servers and expect haveing bad Desync/connection issues on US servers. The reason is when you join a server it has to report to the Hive and if the connection is bad you get conneciton failed, and have problems loging in, and even finding loot in buildings because that is also hive controlled. All you can do i wait it out. Try looking at some of the Dayz steams xD they are constantly running around with a yellow chain and you can be 70% sure that all their progress is not saved if they log with a yellow chain.

Are you playing on EU or US servers ?

i will get back to you on that subject when we find the people who took a V3S while we were looking for the parts to repair it :P but my guess would be that it is near or equal to the capacity of the ural.

on a side note. have you activated dayz mod under the expansion menu in ARMA 2 OA main menu ?. Manual install intructions i use: 1. When installing Arma from steam first run both Arma 2 and Arma 2 OA from steam when they are installed, to update them. 2. download the lastest beta patch which is 95208 as of this moment. http://www.arma2.com/beta-patch.php/ 3. install the beta patch. 4. When done go to the folder where your arma 2 OA is located. (eksamble - x:\xxxx\Steam\steamapps\common\arma 2 operation arrowhead ) 5. Backup Arma2OA.exe (application file) 6. go into Steam\steamapps\common\arma 2 operation arrowhead\Expansion\beta and copy the arma2oa.exe, then paste it in the main folder Steam\steamapps\common\arma 2 operation arrowhead and overwrite the exiting file you backed up. 7. create a shortcut to the Arma2oa.exe and right click the shortcut and select Properties. ( might already have been created when you installed the beta patch) 8. in the area Target: type this "X:\XXXXX\Steam\steamapps\common\arma 2 operation arrowhead\Expansion\beta\arma2oa.exe" -beta=Expansion\beta;Expansion\beta\Expansion -nosplash X= your own location. 9. Run arma from the shortcut and make sure you have 1.62.95208 in the lower right corner of the main menu screen, plus check that dayz is activated in expansions menu. 10. open multiplayer and start surviving!

i would say manual, and it is pretty simple to do without getting any errors, if you have problems feel free to PM me.

I suggest you find a medic on one of the forum threads, if you have no luck getting help.

Press P ingame to see your ping.

it is neiither your client or the server you are connection to that is the problem, the problem is HIVE the Dayz backend which store and transmit loot, locations and character locations to the servers you play on. HIVE has been royaly fooked the last 3-4 days. The best bet you got is to stop playing for like 2 days and see if the HIVE backend has become more stable.

Agree. But the main problem is not the beta patches, it is Battleeye which is failing to support the beta patches fast enough.