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

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

Test Server Feedback

 
  • Topic is locked indefinitely.
 

Solace: Data permeates into wrong client with multiple accounts

Author
Naomi Evotori
Native Freshfood
Minmatar Republic
#1 - 2015-12-05 07:18:49 UTC  |  Edited by: Naomi Evotori
Hi.
I don't know if this issue is related to the new launcher, the brain-in-the-box feature, the solace server setup or the installed version. This is what I did:

- I installed the new beta launcher
- I added 2 of my accounts to the startup list
- Started both accounts
- One character bought a carrier, one bought an interceptor
- Started refitting and storing ships at the carrier
- Did some cyno-jumps


While doing so I had lots and lots of issues... here are some of them:

1) After cyno jump, carrier suddenly deactivated all high slots (Drone Control Units) and the game claimed that I don't have enough CPU to reactivate them. It cut down the CPU calculation value to the same amount as the interceptor while still showing plenty of free CPU (350 of around 750) on the carrier client. I had to eject from the carrier and board it again to be able to activate the modules again.
2) After refitting the interceptor a few times, I tried to activate the 5MN MWD. It gave me a message similar to: "5MN Microwarpdrive II cannot fit Tracking Script, you have to use ." Apparently the slot was somehow mixed up with the Drone Tracking Computer my carrier had fitted.
3) Tried hacking a data site with the interceptor-account, carrier sitting somewhere else in the system. When I activated the module, the hacking-minigame window briefly opened on the carrier-account window. It instantly closed again and the hacking failed.
4) Sometimes the cooldown/activation rings of the modules would not show at all and the modules get stuck in their current activation state without showing a green or red ring. When I tried to deactivate my 5MN MWD it kept saying: "Module already activated."
...
There were numerous other issues all involving data somehow permeating to the wrong client.