r4z0r49

Not sure whats happening i also use multi-monitors and have no issue. Can you tell me what your interface size is maybe that is why?

Where not sure whats happening on this every test we have done spawns us in the same place when exiting the vehicle. We have asked the arma 2 devs to see if they can shed some light on this.

No idea we do not control release dates. We have to go to other ppl to arrange a release date. Its normal to bring in new bugs with every patch i cant name one game ever released that is perfect. Most of the bugs/issues where already in game the teleport issue and repair/refuel issues are new to the last patch

Just get into the drivers seat before you repair or refuel its a bug.

1 - loot tables needed some love the problem is the last version had some silly values added this will be corrected in the next patch. 2 - Deer stands will also spawn millitary loot not sure why you thought other wise. {"ItemMap","weapon"}, {"ItemFlashlight","generic"}, {"ItemKnife","generic"}, {"ItemMatchbox","generic"}, {"Crossbow_DZ","weapon"}, {"","military"}, {"WeaponHolder_ItemMachete", "object"}, {"huntingrifle","weapon"}, {"","hunter"} 3 - This is a known issue and will be resolved by SA due to arma 2 limits 4 - Downed choppers spawn during the time the server is online75% chance 5 - If nothing was around you then no idea the same scan is used in every script from spawning zeds to spawning loot. 6 - Direct chat is shouting ingame. Thanks

Its because you had one another player close or two you had zeds close by.

Its been fixed already. Just waiting on release

We know about this its a humanity issue. It has been fixed we are just waiting to release.

I'm not 100% sure just now. Once i know more so will you

Long as they don't match that's all i needed to know Thanks

Ill pass this onto the Community team although i'm sure they are reading :-). Everything done is due to them :-) not me i'm just here to help everything along

As i say let me know if the 3 lines of code are taken from you. Ill go from that point then.

http://dayzmod.com/f...t/#entry1207147 Thanks To fix just get in the driver side before you apply each new part until the patch is out.

Stop bringing it up then :-) If you wont access just ask if not no point keep bringing it up. _unit playmove ActsPercMrunSlowWrflDf_TumbleOver or if you need the if also if ((_dmg > 0.3) and (_ammo == "zombie")) then { if ((direction player - direction zed < 1) and (direction player - direction zed > -1)) then { give or take dident have time to lookup the exact numbers but give or take

No one has every stopped you from having access. Just shout as for the animation i'm pretty sure its an arma 2 default one seems there's only a few. http://community.bis...ki/ArmA2:_Moves ActsPercMrunSlowWrflDf_TumbleOver - (Evasive) Running forward, fall onto face, get back up and continue AmovPercMstpSlowWrflDnon_ActsPpneMstpSlowWrflDr_GrenadeEscape - (Evasive) Running to right, then falling heavily on side,

When you have proof of any wrong doing shout ill look into it.

Let me know once you have tried the new system :-)

We said less randomness not removed :-) http://dayzmod.com/forum/index.php?/topic/103845-rolling-changelog-for-community-builds/#entry1255653 * [NEW] - Zeds can now push players to the ground when attacked from behind.

The m107 base weapon was updated by a beta update. This is fixed in our new patch. http://dayzmod.com/forum/index.php?/topic/103845-rolling-changelog-for-community-builds/#entry1255653

Nothing changed in the process of the login not in that section. My guess is this has always been there its just become more noticeable as we added new scripts or fix other systems

Ok so it looks like we may have identified the login process issue thanks to facoptere's log files I'm still unsure to why it happens. Whats happening is when client try's to auth for some reason the login process isn't being called so the monitor just stops and wont carry on this then stops any char data from being got from the db. But as the hole login process is a multiple system the rest of the login process still carry's on not knowing the players authentication still hasn't been run So i'm going to add a retry system to the authentication section and add a stop gap system to make sure the client does not load without authentication. This should stop clients loading as seagulls and will also display a msg if everything fails after 5 retry's. With a little luck this will be on the next patch.

Added issue 11. Login issue - Spawn into seagull before Failed disconnect child 103

Add that to the DayZ Suggestions section :-)

Yea the login issue reported here is a total different issue from the timeout issue. The issue with login is something during the initial login sequence is causing the client to fail unsure what yet. Once i get client side log as it happens ill be able to work out whats going on. Can we get away from this new stuff old stuff rubbish all new content is provided by the community same as the bug fixing is provided by the community. If something is fixed or added its because someone fixed or added it. At any point in time if you feel we are not fixing an issue you wont fixing let us no or better yet fix it :-) and let us know. Until we can recreate not sure how we can fix an issue the info given so far has not helped so far. We need a log of the client as it fails so we can see where its failing so we can then find out why its failing. As you know it works most of the time so why is it failing sometimes. Just as a stupid test can you remove all battleye filters.

With SA drawing every closer we just don't see the point in moving DayZ to A3 alot of the issues we face now with the engine will be the exact same for arma 3 not to mention the arma 3 system is alpha. By the time arma3 hits a real state out of beta/alpha im sure SA will be out :-) But im sure someone at some point will move it over not sure on the legal stuff behind that but yea. Id love to see new projects opened up using the a3 engine not just the same mods moved over.