I'm not having this issue, using ghillie suit, 1.7.2.3 and latest beta patch. Tried a couple different servers, progress saved on all of them.

After dying, some people will purpousely respawn several times over to start in a desired location. This places a severe load on the servers, and should be discouraged. Edit: That's not what this thread is about though, this thread is about using the 'shock' mechanic to discourage combat logging, ghosting and the like.

He's not talking about the mechanic that makes you shake if you take damage, he's talking about the mechanic that renders you unconcious the next time you log in if you are in shock when you log out.

I could see this being pretty annyoing/lethal if you were to legitimately lose connection while in a dangerous area, but few other games show too much leniency towards legit disconnects. This is a pretty good idea, IMHO.

I logged in to find that my ghillie had been replaced by the default survivor skin.. The ghillie can't have been removed from the game, as I was keeping a spare in my backpack for a friend, which is still there (though I might "lose" it somehow, if you catch my drift ;D). A bug, I take it? Should I wait before I equip any other ghillies/camo skins? (Also saw the post on gear disappearing when equipping ghillies. Related?) Edit: When I first logged in on the new patch, I think I had some army-style skin. It was a night server without 3rd person camera, but through the NVGs I saw it was short-sleeved with some kind of gloves on. Sleeves were light-colored and appeared to have some form of subtle camo pattern. Desert perhaps. Upon relogging, it was back to plain old vanilla survivor.

IMO one of the biggest problems is the ease of loot hoarding, which renders the intended-to-be-rare weapons common among people who practice server hopping and other loot-farming techniques. I legitimately found NVG's once after 10+ survival attempts over the course of two weeks, I've also found an M107 once, and a ghillie once or twice. Actually finding this stuff legitimately is one of the most thrilling experiences in the game at the moment (or atleast I think it is), and it really makes me value my characters life a lot more. Just nerfing spawnrates or removing the items doesn't fix lootfarming/-hoarding, which IMO is what really breaks these rare items. With that said, I think heli crash sites are too common, and the game could use more civilian weaponry.

I think one of the main problems with doing stuff to bandits was that it's nearly impossible to tell who's a legit bandit and who just got too many murders in self-defence.. I mean, sometimes you have to defend yourself against a player that is trying to become a bandit, but just hasn't gotten there yet... Until that problem is fixed, I doubt it will be viable to "punish" bandits in such a way as you're suggesting. (One could possibly track who fired the first shot? (Yes, that would make Han Solo a bandit)) On the other hand, I really like your hold-up idea, I think something like that would be pretty awesome. You wouldn't need to make it very complex, though, just add an item like duct-tape, rope or those plastic strips some law enforcement use. Then when you walk up to someone, you'd get the option to disable them, making them unable to move or use their hands for like 1-2 minutes, giving you ample time to thoroughly rob them blind (perhaps also making their inventory lootable while disabled). Of course also adding an option to remove said constraints from another player, in case of a rescue or mis-click. This I think could work, because it would let the robbers be certain of a victims inability to suddenly turn on them, thus probably saving a few lives and possibly removing the need many people have to just kill someone to loot them.

Seems like a great idea, and you could merge some of it with the Radio idea if that is implemented as well, like when the helo passes within a set radius of a survivor with an active radio, he would be able to hear the 'Mayday' if the helo was about to go down. (No coordinates or anything, just something to the effect of "Mayday, mayday, Whiskey-Tango-Foxtrot going down!") Also you could just use the existing helo spawn sites as waypoints, to avoid any glitches that might arise from crashing into the middle of forests/buildings/etc. I mean, isn't it only reasonable that the pilot would steer for an open area to increase chances of survival? Still, awesome idea!

Updated original map with termhn's locations plus some me and my group have found over the last few days: https://imgur.com/yHcFP

Let's not stray too far from OT here... Does anyone have an updated version of that map? If not, I'll add a few locations myself a bit later. =)

Lately it seems people have becoming obsessed with putting down wire fences in the most obnoxious places, like blocking off churches completely, or putting it at the bottom of the deer stand ladders (protip: even if you get up, don't climb back down, it will bug out and kill you instantly). Yeah I can acknowledge that wire fences may have their uses, and that they may legitimately add something to the game, but when people keep piling that shit up inside buildings it becomes pretty much impossible to move around! Several times now I've accidentally pulled several Z's and have my attempts to lose them in buildings thwarted by copious amounts of wire fencing inside, leaving me trapped between a rock and a hard place, figuratively. Also inb4 "get a toolkit", most of the time they put it up in such a way that you won't even get the option to take it down. Possible fixes? Lower spawnrate on the fencing kit, limited quantity of fences (or lower quantity, if there already is a set amount), restrictions on placement (might not be doable due to it being part of ArmA?), possibly not requiring a toolkit to take it down, or maybe being able to use a hatchet/hunting knife to remove it? tl;dr: wire fences are cool and all, but don't overdo it, please. IMO it's breaking part of the game.

Hi all, I just thought I'd share my journey to resolve my own performance issues! Part 1 - The Problem: I started playing Day Z just a couple of days ago, and bought the complete ArmA package for the occasion. The game and mod is great, and I love playing it, but I've been having this weird issue where it would quite often (varying from a couple of times per minute to about once every three minutes) experience a sudden and dramatic drop in framerate. It would stay steady at 60 FPS, then suddenly drop to about 5-6 FPS for 3-5 seconds, then revert to normal again. At first I wondered if this was an issue with my own hardware or drivers; and proceeded to install new monitor drivers, GPU drivers, chipset drivers and LAN/WLAN drivers; but none seemed to help. After some rigorous configuration tweaking, the game's performance was improved to the point that my FPS spikes would drop only to about 10-15 fps, making the game at least bearable to play, but in no way optimum condition. At this point I just figured it was a problem with my hardware and ArmA, and let it go. Later I had convinced a couple of my friends to try the mod as well, and when several of them had similar—if not identical—issues as I were, I decided to get a little more thorough in my problem solving. Part 2 - The Fixes: I wrote fixes, because there are several options that people claim have worked for them, so I will list a couple that are likely to work if your problem is anything like the one I was having. Option 1 - Disable Hyperthreading: This one is pretty simple, just reboot your machine and enter the BIOS setup. Once inside, proceed to disable Hyperthreading for your CPU. This will only work if you have a hyperthreading-enabled CPU, such as the Sandy Bridge intel processors (i5, i7). Note also that not all vendors give you the option to disable Hyperthreading in the BIOS setup, and if you are one of the unlucky ones (like myself), I would suggest skipping this step (another option would be to flash your BIOS, but I will not recommend doing that). Sources: http://www.overclockers.com/forums/showpost.php?p=6427871&postcount=18 http://dayzmod.com/forum/showthread.php?tid=17109 (this one contains a series of other nifty performance tweaks as well, nice post sir) Option 2 - Disable Core Parking: Core Parking is a feature in Windows 7 that turns cores in a multicore processor on and off on demand, mostly to save power. This can (and in my case most certainly did) decrease the stability of your CPU's performance, and lead to stuttering, freezing and other issues. The fix is very simple, and described in its entirety in this article. Sources: http://ultimatecomputers.net/forum/viewtopic.php?f=7&t=3644 (the fix) https://blogs.technet.com/b/askperf/archive/2009/10/03/windows-7-windows-server-2008-r2-core-parking-intelligent-timer-tick-timer-coalescing.aspx?Redirected=true Option 3 - Disable Intel Turbo Boost: Again an option only for the Intel crowd (sorry AMD users!), this one will theoretically reduce your performance in office applications and the like, but will most likely only result in less power consumption and lower temperatures when gaming. Most vendors don't let you disable this manually, but there is a nifty workaround, which is described in this post. Sources: http://forum.notebookreview.com/dell-xps-studio-xps/590543-xps-l502x-turbo-boost-2-0-a.html#post7650154 (the fix) Option 4 - Setting Core Affinities If you are unable to turn off Hyperthreading, many people suggest setting core affinities at program startup, or through the task manager while the game is running. This would only help on multicore processors, and is designed to fix the problems Hyperthreading introduces on i5 or i7 processors (or any other CPU with 1 or more logical (non-physical) core). What we want to do is to restrict the game to only use the primary logical core on each physical core (0, 2, 4, 6 on quadcore i7s), and prevent it from using the secondary logical ones (1, 3, 5, 7). There are at least two ways to do this, and they should be identical in effectiveness. The first way is to setup a shortcut to launch ArmA II: OA with a set processor affinity. You do this by making a batch file with the following command: %SYSTEMROOT%\System32\cmd.exe /C start "" /affinity 55 "C:\ExamplePathToArma\Arma2oa.exe" In this example, I set the affinity to 55. This is because the affinity switch requires a hexadecimal conversion of a binary switch which in this case was '01010101'. Every '1' in this binary switch corresponds to a core you want to set affinity to, so '01010101' translates to cores 6, 4, 2 and 0, which is what you want if you have a quadcore CPU. Dualcore CPUs would use the hexadecimal conversion of '00000101' (cores 2 and 0) which for the record is '5'. The second way is to set affinity once the program is running, and the way to do this is described in detail here. Again you would set affinity to only one of the logical cores per physical core, so deselect all of the odd-numbered cores, and you should be golden. Sources: http://www.addictivetips.com/windows-tips/how-to-set-processor-affinity-to-an-application-in-windows/ http://www.gamespot.com/forums/topic/28868679 http://superuser.com/questions/305887/disable-hyperthreading-in-the-windows-7-registry/318799#318799 Part 3 - Conclusion: For me, what worked was option 2 and 3 in unison. What works for you might be different, heck, they might not work at all. But I would—after disawowing all liability—recommend trying them out if you have a problem that seems familiar to mine. Not only did my intermittent spikes disappear completely, my average FPS seems to have increased (when running higher settings) as well. As always, exercise caution, and don't make any changes you aren't comfortable with. (These options should be rather safe, though) Did this work for you? Any other feedback/suggestions? Leave a reply, and let me know!

Same issue here, GPU monitoring shows load never going past 35%, whereas in the previous patch it would fluctuate around 95%...