Margulus
The Executives
Executive Outcomes
0
   |
Posted - 2011.12.03 03:56:00 -
[1] - Quote
OS version: Win7 Ult SP1
CPU: Intel i7 980X (light overclock)
GPU: AMD 5870 x2 (NOT in SLI/Crossfire, driving multiple monitors)
RAM: 24GB
How many clients were you running at the same time? 4
Graphic setting of the client (low / medium / high): High (GFX Driver AA, client setting is off, but the effects are the same just more efficient). Also, FPS is capped on non-focused clients at 25, focused client is capped at 90, swapping clients dynamically swaps cap. My quoted fps numbers reflect the numbers on the focused client, and were consistent on changing focus.
User Experience
Average FPS during fight at the gate in Poitot, with brackets disabled - Zoomed out: 90
Average FPS - Zoomed in: 60
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): This is easily an 8, a significant improvement.
Did you experience any disconnects or crashes? : Only on the node remap.
Describe your experience, make comments, suggestions, etc.: Time dilation seemed to be much smoother for me this test in that time slowed down nicely, but my fps remained constant and smooth, as opposed to the stuttering I used to get. The node remap seems like a half-solution to the larger fleet fight node crash issues. Expecting both sides to log in rapidly mid-fight, and then instantly reorganize fleets is a bit much (in fact it puts us in quite a similar situation to a regular crash). Client relaunching (as it does on a disconnect) is incredibly balky and slow on some machines, or like in my case, requires re-setting up client monitor positions etc as they all reset to default (unless you have x copies of the 10 gigs of client data, where x is the number of alts you play, which is just silly). Auto fleet reformation would go far in alleviating some of these issues (If that is supposed to happen, it didn't in this test), taking this a step farther and creating a snapshot of the running clients position etc settings and then restoring them on the automatic relaunch would be fantastic; the ultimate would be to have both of those AND the client log itself back in on deliberate remaps. Perhaps in the future a 'state snapshot' feature could be used to avoid relaunching at all, simply have the client pause, and then resume after the remap is complete.
The 'check-boxes' not functioning bug mentioned in the test description seemed to extend beyond the overview, as I was unable to modify the broadcast filters. The check-boxes would manipulate, but the received messages would not reflect the filters properly. I attempted to submit a report describing this, however I'm not sure if the in-game tool sent it.
Finally, an updated mirror would be awesome  |