Issues, Workarounds & Localization

So I reported this problem to the "bughunters" a few months ago... Basicly since Incarna, modules seemed to not activate on same tick as you locked something, (or even slower than it did before)
This mean't that anything that warps in less than 1.9 sec would always be impossible to catch even with a remote seboed dramiel because even if you had lock on the target, the module would take an entire extra second to activate...

Lately when in gangs, I often heard people who were used to pre-incarna call out "point" the second they had locked the target, because thats what normally meant you had the target tackeled... only to see the target warp off split second afterwards

http://www.youtube.com/watch?v=9VtsnhAomJs here is an example... and this is what I want a comment on... do you really think this is working as intended? or even better... will you do something to improve it? specially with the winter expansion?

The bug hunters said there was nothing wrong, but from the video (a problem which I can still reproduce) you can clearly see things aren't optimal...

One solution I see is to make prefired modules server sided or something, so the second you have lock... you also have point
i'm sure you guys can come up with other ways to fix it, just don't tell me nothings wrong, as a bitter vet, I remmeber things being different :3

http://www.youtube.com/user/NicklasRahbek#p/u/7/XPrAk0hXpgI here is another example with a ship that has more than 2-3k scan res... more than interceptors :)

I agree with OP that this is a problem.

As far as responses go, the best response would come as part of the patchnotes!

Moved from "EVE General Discussion".

Wanted to add that we are looking into the matter but CCP Lemur just beat me to it.

In the first video im using a Hurricane with 2 active sensor boosters (with scan res script) and 3 targeting system subcontrollers I, giving it 1050.6 scan res.

The rifter I am trying to catch has fitted 2x Nanofiber I giving it an align time of 2.6 sec

The total lock time of the hurricane vs the rifter is 1.4 sec, giving the rifter 1.2 sec to warp....


Second video is a cynabal with 3 sensor boosters (scan res script) and 3 targeting system subcontrollers, giving it 2711.5 scan res. obviously in the video I didn't target the rifter the second it became visible, but I still had the guy locked before he warped

People who been locked, and warped before the point activates, confirmes that they are indeed yellowboxed. and this is not just a problem with battlecruisers vs frigates, as late as last week, me and my gang were sitting on a gate with a bubble, I was in a dramiel, and a rapier had just jumped into us. I went for him at 8500m/s and got a decloak on him, but he was on the edge of the bubble. I however managed to get a quick lock before he warped and called point the second I saw this... sadly he warped the same second, because of the problem I been describeing, that module activation is "too slow"

Regardless of there having anything being changed, it's definately something that could use improvements :)

Ok, I checked again with your setups and it is the same behaviour on the old builds so it looks as things did not change in Incarna that would make this suddenly appear.

There is a delay between when a ship starts being in the "in warp" state and actually warping off but that has always been the case.

I'll poke some clever code wizard to get his take on it.

Just to make more voices heared on this matter..


i've had the same problem aswell... THe other day i chased a rupture through 3-4 gates, got a lock each time, but he stil warped away...

Even tricked me a few times to call out "point" .. Only to see him warping off.

He said he'll look into it, but is currently occupied with coding things for the winter expansion. When he can squeeze it in he will.

Disclaimer: That is no promise that anything will come out of it, only that he is going to take a look.

The delay between 'in warp' and actually warping isn't the problem, because when this period starts, you actually lose lock on the target at this stage. The problem is that the warp disruptor affect isn't activating immediately upon lock despite being primed. This is evident by the targetted pilot reporting a yellowbox but not a redbox.

CCP Lemur,

Please DON'T fix this bug. It's a welcome nerf to camps of any kind. Camps = blobs, because camps gank.

Fixing this issue would result in a high death toll of soloers, and nothing more.

Or at least, if you fix this, then decrease align time across the board on all ships!

I don't remember it occuring "for years". I've noticed it a few month ago, and I bet on a "locking mechanic fix" or "lag fix" to provoked it.

What we can clearly see in demonstrations vid is :

The lock is client sided, you though you had locked it, but server say no "Target is unvulnerable". You can test it with Cloack also. It's the "lag" between the server state and your client...

Modules (warp disrupt in this case) waits for server status to switch on your client.

Problem might be fixed by coding the locking confirmation as modules works. (Client do not shows the target locked before getting server confirmation)

Anyway, just my 2 cents

PS :Is my very bad english understandable ?!