I think something like this is happening.

On server start all the loot gets distributed over the map. Building 1 gets it first, then building 2, building 3, building 4, building 5, etc.. All in a chronological order. Building 1 is often right next to building 2 and building 2 is almost always close to building 3, etc.

Everytime an item spawns it deducts that item from the loot table making sure a single item cannot spawn too many times in the world thus making it a real economy where they'd have an actual fixed number of each loot item in the game instead of spawning everything by chance like they have been doing until now.

For example if this was a loot table:

+ Clothes - 100x Wool coat - 100x Grey hoodie - 100x Pink dress - etc.
+ Food - 100x Baked beans - 100x Canned peaches - etc.
+ Weapons - 100x Makarov - 100x M1911 - etc.

The problem now seems to be that instead of randomly picking an item from the loot table to spawn, it picks the one on top that is still available. Resulting in building 1,2,3,4,5,6,7,8,9,10,11,12,13,etc all having the same kind of loot since the items still have spawns left according to the loot table.

Presumably the function that should randomize the picking of the loot either got broken or was forgotten.

@-1PARA-Gramps: Disagree, also if you would have actually read the comments, you'd know one will only get punished if it is not the first time you commit suicide AND you commit suicide within X minutes of being born.

Right now suicide is heavily abused to get a 'better' spawn. Players will keep suiciding untill they get a spawn that better suits their needs, often consisting of being able to quickly get back to the action or the place of death when still geared.

I do not agree that it never is a disadvantage to other players, a lot of times a player is trying to get back to the area he/she was previously killed in. Having been in that area before means he has intel on that area and he can and will use that to his/her advantage. (e.g. knowing where bodies are / loot are / guns are), this to me is a clear disadvantage to other players in that area that might not have that intel or too little time to act upon it.

But all of that doesnt really matter, what matters is that a player can have a clear advantage by killing themselves over and over again untill they are (close to) where they want to be. A big timeout would not only help make people second guess their decision about suicide, but also makes sure other players are better protected against these suiciders.

--

@Sanguine: Did not know that, if true then awesome!

I really think it is a huge problem. It seems however that nowadays people have gotten used to and are okay with just killing themselves in order to get a 'better' spawn. I'm happy to learn not everybody thinks that way. In a game that is supposed to be about survival, killing yourself should never be a viable option and they should work harder on preventing players from doing so.

Agree, there are many ways to properly fight this. My current favorite being incremental timeouts when players die too quick.

If you die within X minutes of being born, you will get a X minute timeout before spawning again. Do it again, you will get a X minute timeout times 2 before spawning again, do it again you will get a X minute timeout times 4 before spawning again. Etc.

Added a screenshot

@HaseDesTodes: It's on the experimental branch that was released just yesterday.

I think that page might be outdated, i just checked my installed software and saw i had all the Microsoft Visual C++ stuff installed all the way up to 2013 (12.0.30501 to be more precise).

http://www.microsoft.com/en-us/download/details.aspx?id=40784 looks like the latest one.

Could be a Microsoft Visual C++ problem. You might want to try reinstalling that.

More: http://www.chiefarchitect.com/support/article/KB-01046/

Okay here is what fixed it for me and the friends i play with.

1.) Right click DayZ on steam
2.) Click on Properties
3.) Click Set launch options
4.) Enter: -malloc=system -maxMem=2047 so it looks like this

http://dayzepoch.nl/images/launch-options.png

Okay here is what fixed it for me and the friends i play with.

1.) Right click DayZ on steam
2.) Click on Properties
3.) Click Set launch options
4.) Enter: -malloc=system -maxMem=2047 so it looks like this

http://dayzepoch.nl/images/launch-options.png

Try -malloc=system -maxMem=2047 (none other, apart from maybe -skipIntro) and make sure your virtual memory is about the same size as your total ram. Did the trick for me.

Hmm might have been lucky, but this has seemed to fix the problem for me "-malloc=system -maxMem=2047". 2047MB is the hardcoded maximum of the arma 2 engine.

Make sure that apart from those two you have no other launch options (except for maybe -skipIntro).

Eugen Hartons reponse to the memory issues:

http://forums.dayzgame.com/index.php?/topic/221332-054-issues/

In short, add -dologs to launch paramaters and provide them with the logs created by that (users/&user&/appdata/local/dayz).

Yep it's annoying as hell. Already reported it when still on experimental.

http://feedback.dayzgame.com/view.php?id=21871

Also make sure Windows does not set some kind of affinity for dayz.exe and update your graphics driver. Had the same thing (4690K / R9 290X / 8GB) first time i played .54, after removing all of the launch option it worked again.

(I also disabled Steam in-game overlay, might be worth the try)

Paper26 your problem might be a different one then. Check your Resource Monitor for extra information when the drop happens (type resmon in start). I think yours might be because of some kind of i/o problem.

Guys really, try these as starting parameters: -malloc=system -maxMem=2047

1.) Right click DayZ on steam
2.) Click on Properties
3.) Click Set launch options
4.) Enter: -malloc=system -maxMem=2047 so it looks like this

http://dayzepoch.nl/images/launch-options.png.

Yeah it's a pain. I did however not encounter any issues since i started using -malloc=system -maxMem=2047 as launch parameters.

So far no issues since I started using "-malloc=system -maxMem=2047".

Some extended RPT info on the crashes (they keep happening)

Exception code: C0000005 ACCESS_VIOLATION at 004A15D7
Allocator: C:\Program Files (x86)\Steam\steamapps\common\DayZ\dll\tbb4malloc_bi.dll
graphics: D3D9, Device: AMD Radeon R9 200 Series, Driver:aticfx32.dll 8.17.10.1333
resolution: 1920x1080x32
Addons:

DZ_Animals_CowV2 in DZ\animals\cow_1406\
DZ_Animals_sus_scrofa in DZ\animals\sus_scrofa\, DZ_Anims_Rtm in DZ\anims\data\
DZ_Buildings in DZ\buildings\

[...]

DZ_Weapons_Optics in DZ\weapons\attachments\optics\

Mods: DZ
Distribution: 0
Version 0.54.126645
Fault address: 004A15D7 01:000A05D7 C:\Program Files (x86)\Steam\steamapps\common\DayZ\DayZ.exe
file: cur_mp (CUR_MP)
world: ChernarusPlus
Prev. code bytes: 89 48 10 83 C0 12 83 FA 04 72 12 8B 0E 83 EA 04
Fault code bytes: 89 08 83 C6 04 83 C0 04 83 FA 04 73 EE 85 D2 74

Registers:
EAX:51224FFD EBX:84FC2E14
ECX:FD0DA90D EDX:000EF735
ESI:84FCE684 EDI:00000100
CS:EIP:0023:004A15D7
SS:ESP:002B:0F3F7EA0 EBP:0F3F7ED8
DS:002B ES:002B FS:0053 GS:002B

Flags:00010206

note: Minidump has been generated into the file C:\Users\f3cuk\AppData\Local\DayZ\DayZ.mdmp