Issues, Workarounds & Localization

Tested both Sisi and TQ: Inferno 1.1.5 by sitting outside Jita 4-4 and looking at a "Jita cam" type view. Sisi: 20 fps, TQ: 30 fps (45 with interval immediate). And on TQ there are ships flying about. So TQ with 1.1.5 is much better than Sisi. That same test gave me 13 fps with Inferno 1.1.3.

Sitting at a POS is also greatly improved, 20 fps vs some painfully low value I did not record with 1.1.3.

Graphics settings: Performance + shader and texture to medium.

OSX10.7.4

Model Name: MacBook Pro
Model Identifier: MacBookPro6,1
Processor Name: Intel Core i7
Processor Speed: 2.66 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache (per core): 256 KB
L3 Cache: 4 MB
Memory: 8 GB

Chipset Model: NVIDIA GeForce GT 330M
Type: GPU
Bus: PCIe
PCIe Lane Width: x16
VRAM (Total): 512 MB

Based on the feedback in this thread, we've discovered another issue where non-cached icon rendering is causing FPS drops on device reset (docking/undocking, jumping, alt-tabbing, resizing and toggling windowed/full screen).

We are working on a fix.

more wanting it to get to tranquility asap :P

Yeah, I've reached my tolerance limit. Not playing with more than 1 client until this gets fixed. I am continually dropping to ~5 FPS now, especially when travelling/jumping. Slows my ENTIRE computer down too, not just the frame rate in-game.

I've even had the clients go non-responsive for about a minute at a time. "Not Responding" Never happened until 1.1 patch.

Dray

I'm also having a lot of problems with the grid sometimes failing to load after jumping through a stargate with lots of others (50+ ships). I have to relog to fix this problem.

Still can't dual box without massive issues. I used to quad box ( dual PvP, dual indy at the same time) before this.

Day 4 of ~5 FPS. Absolutely awful. Slows my whole PC down too. Disappointed that something as serious as this wasn't picked up in testing and is taking so long to isolate. very depressing.

Submitted a bug report, but still haven't seen anything related to compensation for effectively being unable to play.

Just tested again in TQ:
1 Client Docket in Jita
1 Client flying in space.

Both startet frm the same installation dir.
Both have over 60 FPS.

jita char undocket, everthing is peachy.
Jita char docket, BOOOOOM. 5 fps, even non eve stuff like winamp does not work smooth anymore.
The 5 fps stays until i close the jita char.

Interesting, to you happen to also run the client in Fixed Window mode?

OMG. It just hit me!

Can it be that these session changes force the use of the primary display adapter?

Because on some systems and with multiple clients that would be total FPS destroying while on other it wouldn't make a difference at all! If the issue exist(ed) with AA, why not with this particular setting as well?

My own setup is 2 x ATI Radeon HD 6970 (2GB VRAM each), with each card running two clients, running with three monitors. One card handles two monitors and the other one. The monitors are big and I got to push a lot of pixels, even when calculated per card!

Now I remember from when I first tried to make this work, it was important that I select the right graphics card in each client in order to not have to send all screen output over PCI-Express (and main memory?) to the other card in order for it to be displayable.

Before Full screen window mode, even dragging part of one clients output off the screen to be displayed on another would drastically drop frame rates. I wouldn't be surprised at all many of the issues originating in this corner.

Another thing is the unsound resource use when dragging things around, maybe that forces countless redraws or some computation tat chokes stuff, with as a result dropping FPS. Have a look at that too, but I begin to feel thats a separate issue altogether.

Please inform us when you checked this avenue CCP! It is just one more concrete thing to test!

Same thing happens to me either i dock/undock or just jump by a gate i get a drop in fps from 60 fps to 6-7 fps.