Issues, Workarounds & Localization

when clearing the field with my noctis after killing everything i encounter huge lag problem looting the wrecks.

detail :
1) after clicking the 'open container' button to display whats in the wreck, there will always be a 2 sec lag and my screen freeze during this lag.
2) clicking the 'loot all' button will cause an even bigger lag, usually lasting 3-4 sec, during which my screen freeze again.
3) after the loot has already gone to my inventory, the loot window will not disappear but instead it changed to my noctis cargo inventory, this is totally not necessary, if i wanted to see whats in my noctis's cargo hold i can click the cargo button. I think the default change from the wreck inventory to my noctis inventory is causing this huge lag.

can someone please help?

hello ccp, any news on this issue?

I am going to be bumping this daily, i know this is annoying to you guys but this is causing alot of distress to me because this happens everytime when i loot each wreck now.

edit:
do you need any data from me to help investigate this? i have asked around and there are alot of ppl having this same loot lag issue.

That is probably a good guess. And then the solution should be aparent as well. Defrag. I do not have this problem.
Also I read somewhere a while back that the market screen can get bogged down after a while and that we should clear the cache every so often to fix that issue. So I wonder if it is all connected to the pricing of items in your loot as well.
Or was that problem corrected already? Unknown...

THis is day 3 now. any update on this issue?

game is becoming unbearable due to this issue.

Many are experiencing the same problems especially those of us who manage large inventories and supply chains. What used to be a great feature with the "loot all" button has now become an unbearable lag wracking wait. as the values load, and it sets up all the hangars and sub containers.

Most pilots do not worry about what items cost when they are trying to loot and scoot quickly in a PvP fight or after winning the field trying to loot the wrecks before reinforcements come.

Salvagers in missions don't care either while looting and salvaging... they are taking everything anyway.

Can they turn off the values of items unless someone requests the value calculations?

What ever the new inventory was intended to make easier, a large enough group have commented in EVE Forums and external forum posts negatively about it. It has slowed down the game, made it more difficult to manage administrative tasks, and made game play considerably less fun.

CCP Please bring back the old inventory, until you solve the lag problem. The good idea fairy didn't help this feature this time around... solving it quickly will be a big deal if the company really means they are player focused.

yeah looting is really a pain if every container needs a 1-2 sec t open and if u loot in a noctis with 4 tractor beams and 4 salvager its absolute only a "lagophonie" :( if they dont resolve the prob i never will loot again, this destroys the fun on the game.

same problem, with single, dual or tri accounts open.
It will only lag out the account that is salvaging/looting rather than the other accounts. It lags when opening a wreck + transfering items from wreck to noctis, or if picking up mission objectives.

Dxdiag

Logserver run for one mission - logserver results uploaded via bug report to 139639

Have passed this on to the programmer to have a look, thank you for the report. If anyone is experiencing the same issue please follow suit.

In addition to this, and I know this is a big ask, videos of this occurring would be much appreciated. I spoke to CCP Optimal about this and he would love to SEE this in action if possible. Thanks everyone again.

Not sure what kind of video is required to see this but been playing my alt en empire space for a few days and noticed a slight delay between accessing wrecks a and the inventory on them showing up as well.

Have to agree its annoying.

Was going to do this but noticed BleedingAngl got to it first... Just replying to confirm I see the exact same behaviour. Also makes no difference if I have only 1 client open.