Test Server Feedback

OS version: WIn7 64bit
CPU: Intel 930
GPU: AMD 5870
RAM: 8gigs
Were you running more than one EVE client? How many? 1
Graphic setting of the client (low / medium / high): High, no effects


Average FPS during fight at the gate in FD-MLJ, with brackets disabled - Zoomed out: 50-60, but forgot to turn off effects.
Average FPS - Zoomed in: 40-50, but again, no effects
On a scale of 1-10, how would you compare FPS and performance between this test and TQ? (1=way worse, 5=same, 10=OMG this is awesome) 8. Couple of minor issues, but I'm pretty pleased with the TiDi effects and how it worked. I'm assuming that during the fight the server was automatically calculating the TiDi; as expected, it dropped to about 60, then worked its way up as people loaded onto the grid. 80% was very playable, a slight delay on modules.


Did you experience any disconnects or crashes? No.

Describe your experience, make comments, suggestions, etc.:

The biggest TiDi spike was when we were all instagibbed with yesteryears doomsday. When that hit, TiDi dropped down to about 20%, and then worked its way up as it processed the dead ships. The game screeched to a halt, however, as the server was trying to determine where to settle its dilation. On my end, at least, it took about 10 seconds before I could do anything. At that point it kicked in and I could do everything just fine, but it was slow.

We were kicked at one point and asked to re-login. When I did, my modules were all offline and my guns were unstacked.

Oh dear god it takes a long time to align a titan at 10% dilation.

I think the dilation system needs to be accompanied by a serious ban on exploiting it. Given how long everything takes, one could intentionally dilate an enemy staging system, then make it almost impossible for them to react quickly to a pos rep or something going on in a nearby system.

I'm sure that all the little things, like the typenames of the ships being wrong and wahtnot is just because of the server or the build, not going to list them.

Unrelated to TiDi: The default font size is too large. I know that we can make it smaller in the options, but can't we have the small option by default and make the bigger one an option? Everyone is just going to have to make it smaller.

Machine Info and Settings


OS version: OSX 10.6.8
CPU: 2.66 GHz Intel Core i7
GPU: NVIDIA GeForce GT 330M
RAM: 8 GB
Were you running more than one EVE client? How many? One
Graphic setting of the client (low / medium / high): Low


User Experience


Average FPS during fight at the gate in FD-MLJ, with brackets disabled - Zoomed out: 3
Average FPS - Zoomed in: 1.5
On a scale of 1-10, how would you compare FPS and performance between this test and TQ? (1=way worse, 5=same, 10=OMG this is awesome): 1, see comments.
Did you experience any disconnects or crashes? No
Describe your experience, make comments, suggestions, etc.:

Upon undocking the first time I got black space. Windows and the HUD were there, the UI worked. I docked and got a black CQ with the HUD still showing and no station service window. Relogging did not help, nor clearing the cache, or fiddling with graphics settings. Relogging, then entering the hangar, then undocking worked.

But when I went to hangar view, no ship was visible. On undocking my Dominix did not show. Nor did an NPC in a Domi. Other players said they also could not see Domis. I tried a different ship and it was visible, but went back to my Navy domi for the test.

The test: The jump was fine. The POS bash started to show issues: The client was very laggy. The server seemed to respond just fine, but it was hard to tell when I had actually sent a command, or what was going on. It would take half a minute for stuff to show on the overview or in space if I changed overview or bracket settings.

The fight: It was going OK at first. I could target stuff, shoot, and it all seemed much more responsive despite being in TiDi. (In fact I was surprised at how fast I was targeting. Bug maybe?) Then someone started shooting me and it all went wrong. I decided to warp out. I switched overview tabs to planets and everything locked up for about a minute. No UI response, zero FPS. Eventually I got an overview showing me planets and selected one and warped. The FPS was about 0.1. The speedo got stuck at 23 m/sec, the FPS readout got stuck at 3.28. A minute later and 6 screen updates I was at the planet alive. The fps came up (according to the plot, the number was still stuck) but was extremely choppy and the UI would go from being unresponsive to normal and back every few seconds. I went back to the fight just in time for it to end.

Through the fight it seemed the server was just fine, responding to any command that the client managed to send out. But the client was struggling quite badly.

Suggestion about the cyno effect: I noticed that people cynoing out would show a streak going off in random directions, even though they were all going to the same place. All the streaks should go the same way, and the same way the gate is pointing. Given the idea of the new nebulas: The going from star to star will change the view as though you have moved, means you have the opportunity to actually make space properly laid out. You could let us see stars we are going to when we look in the direction gates point, and so on. Make the stars we see in the background actually be the stars we travel to, in their correct position.

Machine Info and Settings


OS version: Windows 7 x64 SP1
CPU: Q8200@ 2.33GHz
GPU: Radeon HD 6670
RAM: 4GB
Were you running more than one EVE client? How many? only one
Graphic setting of the client (low / medium / high): high


User Experience


Average FPS during fight at the gate in FD-MLJ, with brackets disabled - Zoomed out: ~20
Average FPS - Zoomed in: 7-10
On a scale of 1-10, how would you compare FPS and performance between this test and TQ? (1=way worse, 5=same, 10=OMG this is awesome) 8 really smooth fighting and no major module lag
Did you experience any disconnects or crashes? If the black-screen bug counts, then one
Describe your experience, make comments, suggestions, etc.:
Fight was good and worked fine, only thing I want to mention is that my capacitor was full after jumping with my Dread back to the remapped system. It seems that the server recalled the mass of cap that I had before it got remapped.

If anybody has log-files or crash-dumps from the mass-test to upload: Please do so at https://bugs.eveonline.com. This time we still need your crash-dumps, as the automatic crash-reporter was not (fully) enabled yet in this patch.