sgt.mazer

Somebody with a white truck is going to think the server botched the migration... Nah, I stole it with minutes to spare!

Here's the way it needs to work, including a logical explanation of why it works... When you disconnect, your game client shuts down. The server retains a copy of your character for 3 minutes. Any zombies associated with you also stick around, meaning if you lead a group of them into a barn and DC, they are going to eat your sorry ass. This allows you to go to work, do your chores, or peep on the neighbors if an IRL emergency pops up, while the guys you shot at return fire and kill your DCing ass. To prevent you from reconnecting while the old character is still there, the server could issue a temporary 3 minute ban, the hive could refuse to send data for that character for 3 minutes, or whatever technical hack it would take to get this work. Hell, maybe all it takes is the hive storing these characters as "asleep" and not allowing a connection during the asleep phase. This will punish people who exploit, but will not impact legit players except in extremely rare instances. Perhaps someone stumbles on your body during those 3 minutes, you whine? That's equivalent to sleeping for 3 minutes! In the real Zombie Apoc, you would need to sleep for far longer, and be just as vulnerable. This is NOT A PUNISHMENT to legit players. It is simply an implementation to stop people disconnecting in dangerous locations/situations. It also provides another survival goal: finding a safe camp/hiding spot. If you get into a firefight, your choices are to shoot it out, or be vulnerable for 3 minutes. (3 minutes is a compromise. To really reflect the dangers of sleep, your body should stick around far longer: 10 minutes, 30 minutes, an hour even. Except that you can log back in anytime after 3 minutes has passed and "wake up".) If you can't be bothered to hunker down in a secure location before logging out, then you deserve death. Would you go to sleep for 8 hours in a supermarket? What about in the middle of a field? Would you go to sleep in a pine tree during a firefight? I don't think so.

Date/Time: 5/26/12, 5/27/12, 5/28/12 What happened: Frames per second drops from 30-60 on connect to 5-12 after a short time. Where you were: Seems more pronounced near big cities, but happens in woods as well. Sometimes jumps back up in woods after visiting city, sometimes not. What you were doing: Trying to play but failing miserably. *Current installed version: 1.0.6.1 *Server(s) you were on: Many U.S. servers. *Your system specs: Ati 4890 1gb/ C2D E8400@3ghz /4gb ram/Win 7 64bit *Timeline of events before/after error: ̶1̶.̶5̶.̶8̶.̶2̶ ̶r̶a̶n̶ ̶w̶e̶l̶l̶ ̶f̶o̶r̶ ̶m̶e̶.̶ ̶S̶i̶n̶c̶e̶ ̶t̶h̶e̶n̶ ̶e̶a̶c̶h̶ ̶u̶p̶d̶a̶t̶e̶ ̶h̶a̶s̶ ̶h̶a̶d̶ ̶h̶o̶r̶r̶i̶b̶l̶e̶ ̶f̶p̶s̶ ̶p̶e̶r̶f̶o̶r̶m̶a̶n̶c̶e̶.̶ EDIT: After thinking on the issue further, I did experience the lag in 1.5.8.2. It only happened at the end of my play session so I shrugged it off and forgot about it. 1.5.8.2 was my first install of the mod, and I only played it once before the next patch was released. Also... Has anyone experienced this on a 32bit install of windows?

Same fps drop here. Game initially loads in (the woods) at 40-60 fps. Sometimes it will stay there, other times it will drop to 10 fps after a few seconds. Even if it does manage to maintain high fps in the woods, it will ALWAYS drop to ~10 fps when I approach a city. These problems seems to have gotten worse over the past few days. Perhaps a hive or server issue? I should add that no amount of tweaking settings has any results on fps when this bug is happening (which is all the time now). Could it be a hard-coded draw distance? The setting doesn't change draw distance at all, so perhaps it is hard-coded to a level that is too high?