Nibashe

The OPs sig also means fuck you in finnish....

What did you do about it? You're being as constructive as me after a bottle of whiskey

If you use Nvidia drivers, roll back to the previous version of it. The new driver is causing some players to crash continuously

Let me spell this out for you. Maybe, JUST maybe, you will understand..... A patch is being developed.. People start to play. Now implementations are active in the said patch. Something happens which makes players crash. Also, at the same time, a lot of players are doing absolutely fine with major improvements. In order to figure out WHAT makes this crash happen, you need to collect data from the people being affected. You then look at all the gathered data and see where you can find similarities in hardware or software configuration. Then you crunch this together, compare it to whatever is being developed at this point and try to localize the error. If YOU cant be arsed submitting a bug report in order for them to figure out whats wrong, then also don't expect it for you to work as fast as you want it to... you are part of a process to push this project to beta. With this, it is expected that you throw in your crash report in order to make the game run better. YOUR stubbornness is what's slowing the game down.

You're hiring? :D

Well said.... Nothing to add really.. Just surprised you took the effort of replying to his post.

oops didn't quote

I WANT TO HEAR THE SOUND OF TWO OBESE PEOPLE HAVING SEX! THE HORROR! Seriously though, I would love some eerie music, sound effects... Indeed, the music from the movie insidious is amazing. The sound in a game makes up for more than half of the game. I look forward to see what the game has in store for us.

This.. Also when you talk about "you've made blablala amount of money, fix blablal" you know that whoever is reading this will just go :rolleyes: ... It takes a lot of money to keep up a big team and this project running

Since last week..Are you using an Nvidia video card?

So I've found some other topics about it, however I was wondering if in my situation maybe things are different. It never really happened to me before. Of course, sometimes when I switch to a different server because there is simply not much going on with the server I'm playing on, in very rare cases I've spawned without gear. However, after just logging out and go to a different server this problem was resolved. No problem. Since this week it has been happening a lot more though. I gear up, my friends log in, we decide to go to a full server. So we go into the woods, we log out and go into another server. My friends spawn fully geared, and I end up on the coast as a fresh spawn. Now I've tried the following: Logging out immediately and look for a different regular server Exit steam, reboot the game and look for the same server as I was on in the first place Tried logging in to 4 or 5 servers, only to still be that fresh spawn at the coast. Now, one of my other friends has the exact same issue. It also has been happening to him a lot more since the last week or 2. It just doesn't happen at all to the other people I play with. We don't have similar systems, connections or anything. I've tried every possible solution imaginable, even re-installed the game 3 times, even moved steam to a different SSD, but to no avail. Does anyone of you have any other suggestions I could try? Is anyone else experiencing this issue? I know I should not get attached to gear, and I know it's an alpha, however, when it only seems to affect a specific group of people, maybe it's useful to collect more information on this. I've looked at the bugtracker, and if you have something to add to this, or have a workaround/solution, please let me know. It's much appreciated.

So far I still have my character. I need to figure out if this will be a fix or not. I've deleted my cfg files and let them be replaced by the original ones. I was thinking about this before, but I figured that once you uninstall and reinstall DayZ from steam, it would have also reset those folders, but it doesn't. The folders in your Documents folder will not be removed during an automatic uninstall. I did notice some improvements in my gameplay overall as well which is weird because in the past I've edited those files for fps improvements. Anyway will keep you posted.

What a bunch of BS. Please stop spreading this ungrounded and idiotic statement. Anyway, someone mentioned cars not being in there, and people are already hacking... It's not about vehicles in the game or not.. It's the development of the game. It's still in early development, hence it is more easily accessible by scripts and other exploits. Give it time. I hope they will come with a fix soon, however truth be told, these things can take quite some time.

Thanks for the tip man! I will try this tonight and come back with the results tomorrow.

Yes I did, I think its viewing distance etc. The basic things that were recommended to increase FPS. Can this really be the cause of the issue?

I LIKE BOOBIES

I always try and avoid the private servers. Most of the time its the GB - random number - hosted by multiplay servers (or fragnet or vilayer) with loads of people on them. If it was a private server, I'm sure that the other people of the group would also have lost their gear upon logging into a different server. So that's not it unfortunately. I hope they can find a solution.

Just last night after a long day's work, Ive loaded up the game, 2 of my friends logged in as well and we headed into berenzino. I was looking forward to play a bit with my fully geared character after a shitty day at work. I logged in and explore and gather some food and drinks for another guy who was a newspawn. Suddenly my friend gets shot at. No problem. He ducks for cover and I cross the field from the school building around the barns next to the construction site and I was hiding in some trees and a little stone wall. I was waiting until the guys that were shooting at my friend would come out of the house they were in, so I could pick them off with my Mosin which took some hours to aquire including the LRS. I wait for 5 minutes and all of the sudden I hear footsteps right behind me. I don't hesitate and immediately turn around and I see the person there just disappearing and appearing behind me. Now, this is not the first time I've encountered a teleporthacker, so as soon as he disappeared, I turned around, grabbed my M4 which I had on my back as a secondary, and tried to shoot him. I hit him, however it was not enough. He blinked around me a couple of times until I got killed by his Axe. Very frustrating to lose your gear like that. Been at work an entire day looking forward to gear up a friend so we can play on, just to have it all ruined by some asshole with some teleport script. I hope they can do something about this. For now they say that Battle-eye will sort it out, however, it's only been getting worse, so in my opinion they have ways to stay off the radar when it comes to scripts like this.

Big difference between a motorcycle helmet and Ballistic helmet. Motorcycle helmet wearers are impossible to knock out.

So I've just been replied to by Dean. I was in a terrible mood this morning. No coffee, rounding up my final tasks at the office here in Germany before moving to Brazil in 2 weeks which is very stressful as I need to bring my team here up to speed with procedures and policies before I leave to make sure they keep up the same standards plus some git reared my car whilst talking on his phone.. so I was not too happy.... Anyway, he said the following: Quote from Rocket: "Patches are not and have not been specifically scheduled to certain dates. There has been no announcement with certainty when a patch will deploy to stable. We do announce our server maintenance periods, they occur every Wednesday. When a patch is approved for deployment it will be deployed during a scheduled maintenance period, or in emergency situations an unscheduled deployment may occur. Because deployment of patches outside of scheduled maintenance can occur, we warned everyone that one may occur last Friday. Regardless of negative experiences some people have two things are paramount: We continue to inform people about potential disruptions, i.e. the possibility of patches being deployed. This is because deploying a patch can result in servers being down for extended periods of time. This requires planning with many different people all around the world, such as GSP's who have customers who would bombard them with different questions as to why their server is not online. We will not deploy patches to stable that we know introduce new gameplay breaking bugs. We simply cannot do this. If we know something is broken that breaks gameplay we cannot deploy the patch. It doesn't matter if we have made any "promise" for the update - the purpose of stable is to provide a known level of experience. Each deployment to stable must be a step up in playability. So in conclusion, while I understand your frustration - I am sure you can see that there are reasons why we must warn people of pending patches, and then there are reasons why we might not end up delivering on that warning. That is, quite simply, just the reality of the situation. It will improve as the project becomes less and less risky in terms of it's area's of development. But right now we are dramatically changing the architecture to better support fixing bugs and issues with the engine." Thanks again btw Dean, really appreciate the personal reply.

It's the main reason the helmet always has priority gearwise. Got attacked by a mob of 5 freshspawns once. Didn't go knock out and gave me the time to slice them up one by one :D

Quote from rocket: Anyone who wonders why the patch has not been moved to stable only needs to play on the experimental and you can see the reasons there. If you are disappointed the update is not on stable, simply go play on experimental and you can see these changes. You also quickly see issues as to why it is not out on stable. Believe me: we want this patch out much more than the community. Because continuing like this is a major headache for development as branching and merging becomes an absolute nightmare. This is occurring at the same time as us finishing our planning/roadmap process and starting up our new feature scrums. However, this desire doesn't change the fact that for the patch to be pushed onto stable we must not introduce new serious, game-breaking bugs. Currently we are tracking two new major issues that we see as being blockers: Invisible Characters/Zombies We believe this is caused by them becoming stuck in geometry on client(s) and therefore rejecting new updates. In order to fix this our QA has been going back through different build revisions and checking to see if this occurs so we could isolate the exact point in development it started occurring. That was an extremely labor intensive process and through this we managed to narrow it down to an exact revision that caused the issue. Now that we have found out exactly when that occurred, we start to look into why that happened. Once we fully understand the project we can implement the solution. The problem is that these are not simple issues or bugs, they are complex bugs that can result from a variety of factors. They can be caused by multiple issues, or simply just a symptom of a much wider problem. They are also often very hard to reproduce, and are exceptionally difficult to produce estimates for on fixing. Network pauses roughly every 30 seconds This recently appeared on experimental, and has been noticed by many. What happens is regularly the server stops sending updates for a second or so, which is caused by the server hard-locking for some reason. It lasts only a second before the server starts sending updates again. It looks like desync or rubber-banding for the client. The current most popular theory for this is currently that the Experimental Server Architecture itself is causing the issue. I.e. the Experimental "Hive" central database simply cannot handle the load, and therefore when a players is killed or dies, the updates are delayed and the server is forced to stop and wait for the central server to respond. I've vastly oversimplifying the issue but I am sure you get the point. We're again testing this in detail with our 30 fulltime, onsite, QA staff. It's a huge job and it's been a major effort. source: http://www.reddit.com/r/dayz/comments/207ueh/no_patch_today/

find out he wears motorcycle helmet die

no

Its not desync, its not a bug... just get your heads out of the sand as this is happening. They can do it with any weapon.. M4, mosin, shotgun...Got shot in the face with a full automatic shotgun that kept on blasting. Within a few seconds he gunned down 4 guys. I'm sure it wasn't Robocop guys...