Test Server Feedback

What are the changes with Brain in a Box?
(This is mostly a copy-paste from this old forum thread - with a few minor updates)

The changes on Duality include Brain in a Box (BIAB), a rewrite of Dogma attributes and a rewrite of skills.

Disclaimer: We have still a couple of known bugs (and probably even more not known bugs) and we have not decided yet for a release date (the outcome of this mass test might affect this date).

Brain in a Box:
On Tranquility all your skills are recalculated each time you jump to a different system and then the skills are re-applied to your ship. With this change all your skill-effects are being pre-calculated on a different server node and then this pre-calculated brain is applied when needed. This improves the performance of jumping through gates and many other session changes (docking, undocking, switching ships in space, being killed).

Rewrite of Dogma attributes:
Dogma attributes are nearly all of the values on your ships, modules and similar. Many of those you can see in the show info window in the "Attributes" tab or in your HUD (like your current shield). This rewrite changes how these attributes are stored and calculated on the server and the client. This change was done to allow the implementation of Brain in a Box. If you want to know more about this, feel free to watch the recording of our fanfest presentation from this year. As part of this we also rewrote most of how fleet bonuses work internally and we also had to re-implement the system of heat and overloading modules.

Skill rewrite:
Together with BIAB we also moved all skill training to different server nodes. We also changed how trained skills are stored: On TQ all your skills are just inventory items, which are located within your character (=brain). After these changes they are now stored separately as skills.
For this we had to change all related systems like skill training, skill queues, implants, attribute respecs, and similar - everything should behave the same, but the code behind it changed quite a bit. These changes should also fix some old issues with skill training (example: skill queue getting stuck, when the skill completes exactly while jumping between systems)

What shall we test?
Just for the case that you want to help with testing beside the mass test, here some areas:

• Skill training
• Implants
• Boosters (known to be incorrect)
• Fleets
• All various skill effects (on ships, modules, completely different features, ...)
• Ship, ship modules, fitting
• Session changes like jumping, docking, ...

Known issues:

• The Ballistic Control System is causing error spam (and might not work) (should be fixed)
• Boosters will not work correctly (at least after changing ships)
• Learning a skill or changing implants causes modules to go offline (if they need skills for CPU/PG)
• Some audio crashes are reported - it might be good to disable audio as workaround.

good to see the project is progessing

Hrmm. Says offline for me.

Despite the launcher issue, I did get on and position my ship in the test system with /moveme, no issue.

hi I, am new to mass testing what kind of ship should I bring.

Afternoon. For some reason I am not able to log in to Duality.

It will give me the "IP address" message but will not accept my username. I have confirmed the information is correct
as I can log into the normal game with it.

Toon is 1+ years old so that shouldn't be an issue.


Any help would be appreciated as I would really like to start taking a more active
approach to the game.

Having the same issues as the three above me. Saying I'm not subscribed to eve.

Problem with logging in to Duality, i missed the test because -
The authentication token provided by the launcher is of an invalid format. Please try again or contact EVE customer support.

i am a paid client until November, i consider this a bug

p.s. i can log onto Tranquility and Singularity just fine

Tips for mass testing from an admin.

1) If you want to actually have a mass test you actually have to have advanced notice. This means at least 3 days not 24 hours.

2) If you want a mass test you have to make access to the mass test as easy as possible with detailed guides right in your posting for mass test not links to follow.

3) If you want a mass test you do not have mass tests on 2-3 different servers or server clusters. You have them on one server or one server cluster any other testing servers/server cluster would be used for non-mass testing.

4) When you do a mass test you need to listen to the feed back from those involved in the mass test not just view some logs. Then you need to act on that feed back.

5) If you have less than 250 participants and it should really be about 500 your not mass testing anything. Your pretending to mass test.

6) Any serious issues produced by the mass test should be addressed and a second third and more mass testing performed until all serious issues are resolved.

Lately EVEs Tranquility server itself seems to have become the mass testing server.

BTW thanks CCP for rolling forward with updates that you were told would totally hoark with the UI as well as other mechanics that you implemented on SISI and pushed them into Tranquility even after you were informed by several of us that were spending mass ammounts of time on SISI as of late. Now we have people not showing up in systems or on overviews and we have people not showing as redboxed even though they have engaged you with drones. Overviews totally getting hoarked so that they are no longer usable and the list goes on and on and on. Might as well call Tranquility the mass test server at this stage. An the logs well we all know "THE LOGS SHOW NOTHING".

They can and should script more ships into the test. They can even fake the inputs.
Iceland to England.

A lot of disconnecting today, so I guess more testing is needed (I saw a lot of fleet Xs going up there)