Test Server Feedback

That worked perfectly, thanks.

The mass test was fun! Quite a few graphical anomalies that appeared during the huge fleet battle:

• When opening the fitting window ships started appearing semi-translucent. By switching ships and randomly undocking and then docking again, I was able to alternate between solid and semi-translucent states. This was present before the mass test with only a few dozen people logged-in and continued until the end of my session.
• Opening the fitting window to swap skins in a large fleet caused a noticeable delay/lag and killed the frame rate to essentially 0 fps while it was opening.
• The Phoenix Wiyrkomi skins started out fine, but later defaulted to primarily white with some green aspects.
• Modules that were active prior to going through a gate incurred a spherical flashing reticle that disappeared once you activated the module, but then returned when you deactivated it.
• Some of the stargates took on a 'rainbow' spherical color shape from a distance and appeared as a coloured beach ball up close.

On the plus side, the Mac client held up. There were quite a few noticeable lags/delays where the screen froze and I thought for sure that was it, but it managed to survive. Audio was active (music set to 0) and the graphics settings were set to maximum where possible (OpenGL enabled and set to interval immediate). FPS was 60 initially, dropped to 45 or so when most of the players and ships started undocking, zoomed up to 80 during fleet warps but generally stayed in the 35-40 range. When we attacked the POS it bottomed out around 1.5 when zoomed in (10 or 11 when zoomed out).

Mac Pro Early 2009 2x2.16 with 16gb ram and ATI Radeon 5870.

First undock after login gives a black screen for 7 or 8 seconds.
By the time you can see, the session change is just about up.
Cutting it very fine for using an instant undock bookmark.

Makes logging out in lowsec rather more of a risk than it should be...

iMac Retina 5k (late 2014) 27"
4GHz Intel Core i7, 16GB DRAM
AMD Radeon R9 M295X 4GB, 256GB Flash Drive
OS X Yosemite 10.10.3

I was running with everything set to high with the exception of the shader (limited to Medium) and anti-aliasing which was disabled. I ran with and without OpenGL enabled (I'm not necessarily convinced that on my system OpenGL gives any benefit). Audio was on with music off, and I ran it windowed @ 2048x1152 resolution. I had Safari and Terminal open in the background, but that was it. Any flash or SSD will make a huge difference, IMHO.

Honestly, when I took a several severe lag hits at various points during the fleet battle I was fully expecting it to bail on me. Call me pleasantly surprised!

Interesting Sidenote: I missed the 'jump through gate' command from CCP Sledgehammer and was trying to figure out where the Moros being primaried was. I ended up with a few stray ships from the opposing fleet who had gone through the gate and I think we were all equally confused as to what was going, on so we ended up in a brief skirmish before figuring out where we were supposed to be.

So, there's one bug that I'm still trying to replicate. It's cosmetic: for some sizes of the probe scanner window, the scan result bars on anomalies (i.e., the ones you don't have to use probes on) aren't all the same length. The right margin gets ragged. I can't reproduce it consistently. Resizing the window fixes it, usually.

Other than that, I am seriously loving the new Mac client. Running full screen, full resolution, with everything cranked up to high and the tactical overlay on, getting 30-50 FPS, with only dips down into the mid-20s after gate jumps (the client used to drop to single digits after gate jumps). Stability has so far not been an issue, although to be fair I haven't stressed it as hard as I could. That's a nice upgrade.

CQ framerate is single digits with medium texture quality. *shrug*

I hope now that Transgaming has announced DX11 support, we aren't going to have to wait too long for the EVE client to adopt that. Obviously, it's not a game-breaking flaw, it's just the last major thing I can think of that the Mac client is missing. Excellent work.

Phew, todays' masstest was rough... It still looks like the cider client is trying to access private VM segments when using a discreet GPU (aka a *good* graphics card), leading to 3 crashes in 10 minutes... -_-'

For me, every time I crossed the 2.1GB RAM usage limit, I crashed.

The new textures/shaders are GORGEOUS, however

the first one isn't actually a big deal, as decompiling cider shows they have a fallback method anyways.

the GPU access disallowed is pretty bad imho, as it seems to indicate cider tries to store the texture in the VRAM (which is fine) in a totally unorthodox manner. Since I have yet to see textureless objects, I assume the fallback is using standard RAM for them, which is considerably slower (hence the low fps), and heavily capped (cider being 32 bits).

It's just a warning that the multicache will go away at some point (because computers have better ways to handle that nowadays). It's even probable that the current implementation does nothing except output that message.