Page MenuHomeFeedback Tracker

Too much loot stashed in barrels/backpacks/tents in one location cause excessive waiting and "receiving" messages in inventory
Closed, ResolvedPublic

Description

After accumulating a large amount of loot stashed away in barrels, tents, and backpacks. The surrounding vicinity of the stash, approx. 1/2 km is very laggy in terms of handling inventory items. Player movement is not hindered but interaction with the environment is similarly delayed. Up to 30 seconds will elapse when trying to move/use/combine/modify and inventory item. Up to 30 seconds elapsed while right clicking an item in inventory and get "receiving" message after waiting finally get options to, for example, open a barrel, click it and wait another 30 secs and it may or may not open. Walking away from the loot stash approx 1/2 km and the issue does not happen, inventory is able to be manipulated as normal. Also, sometimes when trying to interact with inventory on yourself or in the stash, the wait time becomes more excessive and never happens, and you are eventually kicked from the server with an error.

Details

Legacy ID
2290353734
Severity
None
Resolution
Duplicate
Reproducibility
Sometimes
Category
Inventory
Steps To Reproduce

Accumulate a large amount, approx 2-3 barrels full and approx 5-10 backpacks full of loot and usually after the next server restart, the issue appears to happen.

Additional Information

Discussion on this issue can be found here. Much more user experienced details. https://www.reddit.com/r/dayz/comments/3i7bx7/58_possible_issue_loot_stashes_become/

Event Timeline

PrimeN7 edited Steps To Reproduce. (Show Details)Aug 24 2015, 11:09 PM
PrimeN7 edited Additional Information. (Show Details)
PrimeN7 set Category to Inventory.
PrimeN7 set Reproducibility to Sometimes.
PrimeN7 set Severity to None.
PrimeN7 set Resolution to Duplicate.
PrimeN7 set Legacy ID to 2290353734.May 8 2016, 11:34 PM
Geez added a comment.Aug 25 2015, 2:23 PM

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