EVE General Discussion

We have recently received a number of reports from pilots that they have been experiencing “rubberbanding” as well as de-synchronization with the Tranquility cluster, notable latency and long session changes when travelling between systems.

We would like to thank everyone who has submitted detailed bug reports, these are proving to be incredibly valuable in tracking down the source of these issues. We now feel that we have enough information from pilots in game to fully investigate the cause of these issues.

Over the course of the last week we have been closely monitoring Tranquility, and will soon be looking to apply a fix once a cause is identified. A number of teams here at CCP are currently working on a resolution to the issue, and our Customer Support team have been able to identify specific scenarios in which this is having an effect on gameplay for our pilots.

We hope to have these issues resolved as soon as possible. If you’d like to discuss these issues, you can do so in this forum thread. We will also use this forum thread to post any necessary updates.

Thank you for finally addressing this.

Thank you for addressing this issue. I thought it was my ISP being bad.

Turns out all those failed target locks were your doing...

YOU OWE ME 4 KILLMARKS CCP!

Seriously though, can't wait for it to get fixed. Thanks guys

dont undock what you cannot afford to lose is the motto of eve.... guess you forgot?

Actually, don't fly what you can't afford to lose. Yes, this is the Eve Motto however, when CCP reimburses ships for other game errors how would an Imp also not apply? I bet if it was your homies Tengu you'd be all "Hey dawg, just petition it to CCP and get it and the SP reimbursed!"
Losing a ship to a game bug or error is completely not a pilots fault. Getting baited or out piloted is one thing. But that is in a fair environment. You have the ability to burn out of range, jump through a gate, dock. But when you are rubber banding it has the same exact effect as the e-warp killing of supercapitals. The pilot in the ship being killed could not do anything since you cannot cancel e-warp. Just like you cannot cancel rubber banding.

If CCP doesnt reimburse EVERY loss to rubber banding, then they may as well take away the Titans and Supers they reimbursed that died to the ascendency implant e-warp bumping. They also need to take away the SP and Ships that died due to DDOS, DCs, Dsyncs and other game-side issues that were of no fault of the players in charge of their ships.

The issue I have is your inability to do the right thing. You provide a faulty service, in which we are paying for. Most of us paying for multiple accounts, and by most I mean the bulk of your active members run 6+ accounts minimum.

You provide a ****** service (which got a lot worse after the Horde cleanse of perimeter). You are having server issues which are at no fault of players, you have reimbursed several T3s that have died due to Rubberbanding/Dsyncing, but you deny an AT ship. Gee, I wonder what the reasoning for that would be. I wonder what bullshit excuse was given to him. "Sorry, our logs dont show anything." Yeah, I bet the logs cant even be found since clearly keeping the server maintained is too hard. God forbid the database where the logs are stored is even online.

TBH this isn't a bittervet thing. Running a game "for >10 years" and fking up its stability after "> 10 years" is a point. Stability over all that's the point of THIS SPECIAL game. A bunch of players actually play this game because of its PVP content. That content - in particular the small scale/solo PVP content - is fked up right now...after "> 10 years". Maybe you're one of those guys watching the market or maybe you're one of the guys waiting for a fleet ping to anchor up but Sir, you're definitly not parcitipating in solo/small scale pvp.

It's cool to see someone who "had to deal with antiquated code with various"...blah. The next step is: Try to deal with actual economics.

I find it disturbing how CCP is declaring the support tickets to be a highly valuable source of information on this relative to all other sources. This indicates they have failed in their obligation to set up adequate systems for monitoring and maintaining their service if they are relying on gibberish sent via support tickets. They should be far more advanced than this.


So am I to believe that the CCP technical team have been sitting about like plonkers (rubberbanding, socket disconnects and session change delays have been going on for months now) and now based on support tickets they are no longer doing nothing but are starting up some monitoring to maybe find the problem and maybe fix it?


It shouldn't take this long if you knew what you was doing.


What a shambles.


I feel you are obliged to reimburse that Imp that was lost due to the failure to provide what he paid for. I also think you should go further and give him compensation.


I lost a total of 8b in assets in December 2016 due to socket disconnects and I was reimbursed everything - but it is still extremely irritating to have the losses on my record.

Admission of fault


I therefore withdraw my support ticket criticism and apologize for making it.


The Imp loss


I suggest Koral submits this 'bug report' immediately to challenge the refusal decision made in Imp reimbursement case. Can I also suggest that CCP Darwin communicates his professional concerns regarding the service blow out Koral likely experienced also in support to challenge the refusal decision on his Imp reimbursement case? It is only fair that he promptly receives his asset back with sincere apologies for the service blowout - the man lost an asset worth 3 or 4 thousand dollars in the real world!


Unfortunately while admitting fault in the above - which I am happy to do - I still maintain the essence of my original point.


The rubber banding, socket disconnects and session change delays have been happening non-stop for months on end now, CCP should have easily been able to get the issue into a highly potent and monitored testing environment using their home gaming computers and/or using VPNs & CCP technical contacts in other continents to also test tranquility connections from afar.

This SHOULD be considered a crisis by the relevant CCP team responsible for service stability, which presumably includes CCP Darwin who as a senior software engineer has stated now that he 'isn't involved', but it is not being considered as such because the problem has now perpetuated for months in the face of massive losses and player reimbursement petitioning. The problem isn't rare - tranquility connections are being plagued by these service stability issues!

I am not going to threaten to unsub from the game, but logically I might have to because I cant play it. I will resub once I can play - I will keep an eye on this blog for any indication of progress.

Ok, got the issue the last days that when changing session (Jumpgate) it took more than 30 seconds to get in the new system. The cloak timer was stuck as well, it didn't update. Also some actions like opening fitting windows took 15 seconds, .... you get the point.

I enabled logging in the client and was spammed with the message:

Someone is trying to load text into Edit which has 0 or less width. This controls visible state under desktop is: False. Edit location: /Desktop/l_main/journal/__maincontainer/main/epicJournal/epicMainContainer/edit_multiline

Well I searched the UI for the Epic Journal Log which was pinned and minimized on my screen, just switched the journal to another tab and the problems and the log messages were gone.

Not sure if it applies here, but just wanted to give you the possibility to test and fix it.