Hello RambiPlays and thank you for the report.
This is an issue we are aware of (#0026903) and it has been scheduled for a fix.
Regards,
Geez

Same, garden plots too on DE 0-2. On NE 0-2 I could place both fire kits and plots then I could do fires again on DE 0-2 5 minutes later but still not garden plots. They just disappear after a few seconds.

Hello jacobguldner.
The issue has been fixed internally and should be fixed on Steam soon.
Regards,
Geez

Hello jacobguldner and thank you for the report.
The issue has been confirmed and scheduled for a fix.
Regards,
Geez

Tents and barrels have been ok so far on Aus/US server 02.

Hello mamersmann and thank you for the report.
This is an issue we are aware of and it has been scheduled for a fix.
Regards,
Geez

Hello mamersmann and thank you for the report.
This is an issue we are aware of (#0023127) and it has been scheduled for a fix.
Regards,
Geez

Hello Reddead,

Sorry to hear about your trouble. If you send me a link to your Steam profile, I can move your character (I get numerous results when searching for the ID you submitted). Example: "http://steamcommunity.com/id/xxxxxxxxxx/"

If you prefer to send your Steam ID url in a private message, you can click the "Make Private" button to the left of your message after you click the button labeled "Add Note".

Thanks,
JStewart

Aus 01 server is working ok for gardening, grops grow and plots are normal 0.58.129052.

[ Update ]

Tried after the rain stopped, but it still disappeared.
Had no trouble planting in greenhouses.

Hello germanpostrigan.
The issue has been fixed internally and should be fixed on Steam soon.
Regards,
Geez

Hello germanpostrigan and thank you for the report.
This is an issue we are aware of and it has been scheduled for a fix.
Regards,
Geez

Hello Stephen Harper.
The issue has been fixed internally and should be fixed on Steam soon.
Regards,
Geez

Hello Stephen Harper and thank you for the report.
This is an issue we are aware of and it has been scheduled for a fix.
Regards,
Geez

Hi glacebondeson,

Good to hear that you managed to get out :)

In case you experience any other problems in the future, please feel free to submit another ticket.

Regards,
JStewart

Got Out! I just ran next to the wall and spammed all the keys.

Same here

If it is a problem, I also get error message upon closing the game in any way.

The crash happens when I close the game in any way - from the main menu or alt-tab and close, sorry I forgot to mention that in the main post. I checked the folder again after the error but there was nothing new there. The game has never actually crashed while playing, performance is pretty good even with the abnormal memory usage!?

Hello,
There are no crash dumps in the latest file, so I suppose the game did not crash with an error message this time? To determine the issue, we are going to need the logs produced upon crash with error message.
Regards,
Geez

Ok, I deleted the whole folder and played for a bit. Same thing is happening. I've attached the files but there's barely anything in the folder after last nights session, not sure if it's meant to be that sparse?

Cheers.

Hello malborojones.
It appears that the files (both the latest and the previous ones) are quite dated. Could you please delete the appdata contents and send us freshly generated ones once you experience the issue again?
Regards,
Geez

Doh! I thought I had removed them a while ago. It didn't help unfortunately, memory is reaching nearly 3GB again in the latest exp. Here's those files again after the latest session - https://www.dropbox.com/s/dx5wc9153p6dqa1/AppData-DayZ.zip?dl=0

Hello malborojones.
According to the files, you are using these startup parameters: -noSplash -noPause -cpuCount=6 -exThreads=5 -maxMem=2048 -maxVram=2048. Please remove all of these parameters, as we do not support the parameters and they cause various issues within the game (memory crashes,low fps and such). Once removed, try playing the latest exp and let me know if the issue still occurs.
Regards,
Geez

https://www.dropbox.com/s/h5vfkvc3ecn882h/AppData-Local-DayZ.zip?dl=0

There you go. I was able to produce this again on the most recent 0.58 build. Memory usage starts at roughly 7GB and then increases gradually as I play, quicker at first.

Cheers!

Hello malborojones.
Please attach contents of your C:\Users\*username*\AppData\Local\DayZ to this ticket. In case the files cannot be uploaded due to size, use some kind of cloud site from which we can easily download the files.
Regards,
Geez

Hi moho,

Thanks for sending in your information. Your problem should now be solved. In case you encounter any further problems, please feel free to submit a new ticket.

Regards,
JStewart

Hello Burlap.
Could you please give me coordinates for the rocks location at http://dayzdb.com/map/chernarusplus ?
Regards,
Geez

can confirm. the rock has no collision and you can run right through it.

Hello peroxo.
The issue has been fixed internally and should be fixed on Steam soon.
Regards,
Geez

Very bad railwork! :P

Same could be said for all other knives, and machette too. They look like they are stabbed into the players back.

Hello peroxo and thank you for the report.
The issue has been confirmed and scheduled for a fix.
Regards,
Geez

Hello HaseDesTodes and thank you for the report.
The issue has been confirmed and scheduled for a fix.
Regards,
Geez

Hello HaseDesTodes and thank you for the report.
This is an issue we are aware of and it has been scheduled for a fix.
Regards,
Geez

Hello peroxo.
The issue has been fixed internally and should be fixed on Steam soon.
Regards,
Geez

ok... i also hit a invisible cow xD thx for info man.

maybe i should mention that when the cow horde has run away I could drive through the invisible border without problems. It should really been the cows i was hitting

Hello peroxo and thank you for the report.
The issue has been confirmed and scheduled for a fix.
Regards,
Geez

I've had the same issue since the latest update.

It can be fixed by changing graphics settings (causing the Please wait screen) unfortunately, this is impossible while in a fight.

Had same issue, got fixed in .58