Oh people like rumours don't they

well here's a video from July 2010 http://youtu.be/39-7YJYKfa0?t=4m49s well before capships

Slime incorrectly calls it lagg however it's affecting everyone in the sector and their ships movements and shots being fired don't seem to be laggy at all, just hits fail.

If you take note off the battle rocket and missile weapons still damage (and that is still the case today) but energy will fail to damage or intermittently damage

Sounds like my experience (which also had no swarm missiles at the time of the bug)

So, we've been working for the last few weeks to build a totally new server for testing this kind of thing, to let us do some really heavy-duty simulations and try and reach a reproducible answer.

However, part of this process is also updating the game to work with newer versions of other programs and libraries and so on, and that has been a bit time consuming.

So, we're still working on this. We can't very well use the production server as a testbed for this right now, as there's a good chance that our logging and debugging would make everything much worse for general gameplay.

Hopefully we'll have it ironed out soon.

Sounds good! I can't speak for everyone who's encountered this bug (it seems like most people have been putting up with it for a while, and that would certainly be draining!), but just hearing that you guys are taking it so seriously is all I needed.

Go devs! This sure seems like it'll be a nasty bug to find/fix, but we believe in you!!

Great to hear, Inc. Let us know when/if you need people to do testing, I think we're all psyched to kick this bug in the butt.

"If you take note off the battle rocket and missile weapons still damage (and that is still the case today) but energy will fail to damage or intermittently damage"

Um, no, that's not right. Missiles and rockets don't do damage to other people, the splash from missiles and rockets will hurt the user, but not the target, giving the illusion that rocket damage still works when it actually doesn't.

Also I remember having large battles a few years ago and this never happened once. It's a more recent thing.

I've actually seen this happen with no backsplash.

Also I remember having large battles a few years ago and this never happened once. It's a more recent thing.

I remember large battles recently where this didn't happen and ones years ago where it did. It's a sporadic problem.

This as happened to me multiple times when it is just me and one other person in the sector, so it's not just large battles.

Congent co: 1
Vendetta Online: 0

This happened again repeatedly today in conquerable station battles. I was shooting invincible mines even.

It's not even during intense PVP or due to a busy sector. Last night I shot a moth down to about 50% as it warped to an empty sector, no other players were present, nor tridents, nor AI, just me and the moth. I un-warped before him - as my load times tend to be quite fast - and unloaded a full tube of jackhammers right at him and scored a visible hit with each one. 0 damage. He then warped to a station sector, where I was also waiting and as he ran for the dock I zapped him with enough NT2 to kill a 100% prom. He made the docking bay still at 50%ish.

There were no visible signs of lag, apart from not doing any damage. My ping was steady at <>120, and BPS seemed normal. He then undocked in a bus and I could again damage him.

Yikes !

This shit is still happening, and, dare I say, has been worse in the sectors with the special code.

This shit is still happening, and, dare I say, has been worse in the sectors with the special code.

Ray has already replied to your ticket, but since you posted this.. no, the sector was not running the new code.

We're trying to roll the code out to all of grayspace (instead of just the station sectors), and during a transitional test today the "new code" sectors were shut down, but then not started back up using the new-code.

Obviously it was not intended, but is a side effect of our trying to test this code really thoroughly and minimize the risk of it breaking other things in the game.

Ah, well, that makes sense then. I think several of us would probably have made different combat decisions if we had known the old code was running. It really gets to a point where it's just not worth playing.

For six months we made the decision that it was not worth playing and often were we berated by Itan and crew for the choice.

It's amazing the difference the new code made when you consider how quickly the lag bug ruined the fight today in I-8.

I think several of us would probably have made different combat decisions if we had known the old code was running.

This is correct.

"I'm stuck at a dead stop in a turret for over a minute with my shields down, my groupmates shots are doing no damage to my attackers, their shots still do damage to me, and the mines I just deployed aren't even going off. How... convenient."

Ah, well, that makes sense then. I think several of us would probably have made different combat decisions if we had known the old code was running.

We didn't know the old code was running either. We didn't realize it had auto-restarted the old code until you guys raised the issue, since we were focusing on the migration (which happened today).