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.
 

Not enough CPU/PG messages

Author
Araceli Gabriela
Infinite Density
#1 - 2016-03-10 21:12:52 UTC
Over the last week or so I've been experienced an issue with error messages appearing about my cpu or powergrid. When I switch ships from a SMA, or jump systems, about 90% of the time some random module(s) will give me an error message that I dont have enough CPU/PG.

http://i.imgur.com/1isVffr.png

Sometimes its every single module on the ship, sometimes its just one. Sometimes it says I have 0.00 cpu/pg left, sometimes its some seemingly random and unrelated number. However even though it says my modules are offline - they are online.

Much less frequently my fitting screen will actually show empty module and rig slots - and unrelated to the ones the messages are about too. However they are still fitted on my main screen and I can activate them and the rigs still have their effect even if they aren't shown. So far.

This is beginning to become a serious gameplay issue. For example if I'm trying to jump a wormhole to point something or simply run I'll have to push "Ok" to every single one of these messages before I have access to any part of the UI or game. If that's 17 messages I have to click through 17 separate messages and they dont necessarily load quickly.

The only constant I can see is that whatever modules are affected stay the same throughout the occupation of the ship. Once I switch ships though it can be a totally new set of modules or none at all.

Another issue is sometimes when I switch ships at a SMA it will say I cannot fit certain rigs that were on my previous ship in a similar error message. This is a new error as of yesterday and I'm not sure it's actually related although the same style messages appear.

I've reinstalled the game, cleared cache, and run the error checker but nothing else.

Is this a known issue?