These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

Science & Industry

 
  • Topic is locked indefinitely.
 

Bugged for 40+ hrs... Can't finish indy jobs container too small.

Author
Previous Topic Next Topic
Mistress Vynia
Of Corsets a Corporation
#1 - 2015-04-13 15:48:19 UTC
I've submitted a ticket, updated it too.

Tried to contact GM asking for support... 24 hrs ago.

No response or fix from CCP.

Anyone know how to get it unstuck? The jobs were set (accidentally) to export to a small container, which was too small to fit the finished job. I've logged in and out. I emptied container. I repackaged container. I put a renamed a large enough container to the original name...

Nada.

My indy builds are stuck.

Anyway, figured I'd post here and see if anyone knew a fix or a way to get some official help with it.

Thanks.
Soldarius
Dreddit
Test Alliance Please Ignore
#2 - 2015-04-13 15:56:10 UTC
You're screwed. Just wait for GM. They may be nice and change the container destination.

btw, how did you even get the interface to set the destination to a container?

CCP should make a check on indy jobs so this can't happen. IF(destination.cargo < output.volume) (no bueno) else (bueno).

http://youtu.be/YVkUvmDQ3HY
Paranoid Loyd
#3 - 2015-04-13 16:26:40 UTC  |  Edited by: Paranoid Loyd
Hmm, usually repackaging the container fixes it. I don't think it looks at the name of the container but the internal ID of the object, did you try completely removing the container from your hanger (Into a ship)?

You can also try clearing your game cache.

"There is only one authority in this game, and that my friend is violence. The supreme authority upon which all other authority is derived." ISD Max Trix

Fix the Prospect!
voetius
Grundrisse
#4 - 2015-04-13 17:48:16 UTC

As Loyd says, either repackage the container or renaming it works as well (so I have been told).

This situation occurs because the Industry UI remembers your last settings so if you "use" a blueprint that is in a can (e.g. just to check the job cost or something) the UI remembers that and when you submit the job it will use the previous defaults.

There is a good argument that this isn't really what you want when the destination can is too small to hold the job output.

However, having the UI remember previous settings is normally so useful it's not really something that most people would want removed.

There is probably a middle ground e.g. having an opt-out warning if the input or output is a container that might save some heartache.
Gully Alex Foyle
The Scope
Gallente Federation
#5 - 2015-04-13 18:27:37 UTC
Paranoid Loyd wrote:
Hmm. usually repackaging the container fixes it. I don't think it looks at the name of the container but the internal ID of the object, did you try completely removing the container from your hanger (Into a ship)?

You can also try clearing your game cache.
+1, worked for me at least (I was very very sad until someone suggested this!).

Make space glamorous! Is EVE dying or not? Ask the EVE-O Death-o-meter!
Elena Thiesant
The Scope
Gallente Federation
#6 - 2015-04-13 21:41:42 UTC
Usually repackaging the container works, also try moving it to a corp hanger if one exists (or a ship if small enough). I've heard someone in a similar predicament solved it by contracting the container to their alt, so give that a try too.
Mistress Vynia
Of Corsets a Corporation
#7 - 2015-04-14 13:00:51 UTC
Soldarius wrote:
You're screwed. Just wait for GM. They may be nice and change the container destination. btw, how did you even get the interface to set the destination to a container? CCP should make a check on indy jobs so this can't happen. IF(destination.cargo < output.volume) (no bueno) else (bueno).


Tnx, I'll re-appeal for a GM again. As to how, I put the BP in a container, so it defaulted to export to that container. I agree 100% - can't be that hard to stop this from happening.

Paranoid Loyd wrote:
Hmm, usually repackaging the container fixes it. I don't think it looks at the name of the container but the internal ID of the object, did you try completely removing the container from your hanger (Into a ship)?


The container is too small. I only keep BPs in it. It is a small standard container (fits only 100m3) - the export job is 150m3. So no matter what happens, the container won't fit the export. I did remove the container and I was able to get it to export to the hanger. Thanks!!!

voetius wrote:
However, having the UI remember previous settings is normally so useful it's not really something that most people would want removed. There is probably a middle ground e.g. having an opt-out warning if the input or output is a container that might save some heartache.


Agreed. Just to have the option in these instances of "It doesn't fit, do you want to export it to the hanger?" would be great IMO.

Elena Thiesant wrote:
Usually repackaging the container works, also try moving it to a corp hanger if one exists (or a ship if small enough). I've heard someone in a similar predicament solved it by contracting the container to their alt, so give that a try too.


Will do.

Thanks everyone for the suggestions! My issue is resolved.
Capsups
Atomic Mangocorp
#8 - 2015-04-15 13:14:18 UTC
I heard another guy with this problem ended up just changing the output destination to another container and then it delivered fine. Is this not possible in this case?
Mistress Vynia
Of Corsets a Corporation
#9 - 2015-04-15 18:32:39 UTC
Capsups wrote:
I heard another guy with this problem ended up just changing the output destination to another container and then it delivered fine. Is this not possible in this case?


It is not possible to change the output destination after the job has been started.

Fortunately, moving the container to a ship so that it wasn't in the hanger allowed the interface to finally stop trying to output it there, and it put it into the hanger.