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

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

Issues, Workarounds & Localization

 
  • Topic is locked indefinitely.
 

(BUG) Manufacturing window doesn't list all required materials

Author
Rob Crowley
State War Academy
#1 - 2013-07-06 22:15:14 UTC
Hello,
I found a bug in the manufacturing window today. The BP requires 7 mineral types for manufacturing, however the manufacturing quota window only lists 5 of them, Tritanium and Zydrine are missing for no apparent reason (see first screenshot). I tried if I could actually build a run without any Trit and Zydrine, but then the quota window says that 2 of 7 materials are missing, which is correct but it's still only showing the other 5 materials (see 2nd screenshot).

Screenshots: http://imgur.com/a/DCNQ9
Xeano Estrado
Estrado Empire
#2 - 2013-07-07 14:24:42 UTC  |  Edited by: Xeano Estrado
Just tried this with my rifter BPO, I see all 7 materials when I have to accept the Quote.

This must be a bug in the client. I would suggest you to try and repair if you cannot live with this.

Has this happened to other BP than your rifter BP?
Rob Crowley
State War Academy
#3 - 2013-07-09 21:39:57 UTC  |  Edited by: Rob Crowley
Xeano Estrado wrote:
This must be a bug in the client.
I don't see how you come to this conclusion. I mean it's quite possible but I don't see any clear indication.

Quote:
Has this happened to other BP than your rifter BP?
Good question. I tried it with a couple other BPOs and so far all have been displayed correctly. So it appears to be only the Rifter BPO (30 ML / 20 PL), but it's consistently reproducible with that one.
Rutger Janssen
Chanuur
The Initiative.
#4 - 2013-07-10 10:58:43 UTC
Can you open the quote window with the log server running, see if something pops up there that would halt the process from loading the rest? https://wiki.eveonline.com/en/wiki/Log_Server

When you've done that, clear the cache and see if that fixes it.
Rob Crowley
State War Academy
#5 - 2013-07-10 11:59:48 UTC
Good call. I tried catching it with the log server, but of course it was correct this time after being wrong for 4 days straight. I guess this might indicate a cache issue, though I don't really have a clue what exactly would be cached in this process.