These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

EVE New Citizens Q&A

 
  • Topic is locked indefinitely.
 

Target Lock Delay

Author
Miwai Airi
Republic University
Minmatar Republic
#1 - 2017-01-22 16:52:25 UTC  |  Edited by: Miwai Airi
Hi fellow capsuleers,

been noticing something lately that has me a little concerned. I'm not sure if it's an issue or just game machinics.

example:

Today, a known ganker was leaving a station with criminal status, i sit outside waiting, he undocks blinking. I spam lock and nothing happens for like 8-12 secs. I was in my thrasher with high scan res, so once locked takes only 2 secs to fully lock. prob is, i'm having issues activating the actual lock on - takes ages.

Happened again today when i warped in on an astroid belt, the ganker was in the process of killing a retriever, i tried desperately to lock the target but it was taking ages. i'm not talking about the targeting locking speed once locked but the activating the lock.

Question is, why is it taking a long time to get a lock? shouldn't i be able to start a lock instantly or at least wihtin 2 secs on grid?

any ideas?

Only thing i can think of causing this would be lock shortcut on space bar, and i've been tapping it hard while trying to lock. would i need ot hold the space bar / ctrl for more than a second to activate a lock? could that be the issue?
ergherhdfgh
Imperial Academy
Amarr Empire
#2 - 2017-01-22 17:01:59 UTC
When you undock you are imune to being targeted for 30 seconds (iirc) or until you make a piloting control input.

You cannot target while in warp or target something that is still in warp. So the asteroid belt thing has to do with waiting for warp to fully complete. On your own ship you know this happens when your speedometer changes back from AU / sec to KM / sec

Want to talk? Join Cara's channel in game: House Forelli

Miwai Airi
Republic University
Minmatar Republic
#3 - 2017-01-22 17:04:37 UTC  |  Edited by: Miwai Airi
ergherhdfgh wrote:
When you undock you are imune to being targeted for 30 seconds (iirc) or until you make a piloting control input.


i see, that would explain the undock time delay.

ergherhdfgh wrote:
You cannot target while in warp or target something that is still in warp. So the asteroid belt thing has to do with waiting for warp to fully complete. On your own ship you know this happens when your speedometer changes back from AU / sec to KM / sec


Thanks, yes i understand that i can't target something in warp or warping out and the cooldown.

The warping in cooldown could be the reason i had the delay entering the astriod belt. although i'm pretty sure i was out of warp and still had thelong lock delay.

thanks for the information on the station 30 secs station undock timer
ergherhdfgh
Imperial Academy
Amarr Empire
#4 - 2017-01-22 17:30:12 UTC
If you were within range and neither you nor your target was in warp then you should have been able to start the locking sequence.

The only thing that I can think of that would prevent you from beginning the process of target locking is:
-Being out of max targeting range
-You or your target being in warp
-You being ECM jammed.

I left out ECM because that is something which you would be able to see was happening to you and also you had just dropped out of warp into a situation where I did not see a likely source of ECM.

Want to talk? Join Cara's channel in game: House Forelli

Keno Skir
#5 - 2017-01-22 17:45:12 UTC
Slightly long shot here, but try removing your space bar shortcut. Instead hold control down and left click stuff in overview to lock on.

My thinking is that assuming you / target are not exiting warp still, this may be a glitch with the shortcut itself or even you ur keyboard. Potentially you have Space set as both lock and unlock and it's confused etc.

That said it is MOST LIKELY that you are indeed trying to lock targets that are for some mechanical reason invulnerable Pirate
Miwai Airi
Republic University
Minmatar Republic
#6 - 2017-01-22 20:01:47 UTC  |  Edited by: Miwai Airi
Keno Skir wrote:
Slightly long shot here, but try removing your space bar shortcut. Instead hold control down and left click stuff in overview to lock on.

Potentially you have Space set as both lock and unlock and it's confused etc.

This was the issue.

Basically, what i had done was set my space bar to 'toggle lock target' instead of 'Lock target'. So it was locking toggling and then unlocking during my spamming the space bar. Ugh

Explains why i was having issues during the pre-locking phase.

again, thanks for your responses, i've now corrected the shortcut and 'toggle target' shortcut has been set to 'none' as default.

problem solved

thanks again ;)
Keno Skir
#7 - 2017-01-23 14:38:33 UTC
Miwai Airi wrote:
Keno Skir wrote:
Slightly long shot here, but try removing your space bar shortcut. Instead hold control down and left click stuff in overview to lock on.

Potentially you have Space set as both lock and unlock and it's confused etc.

This was the issue.


I'm amazed. Felt stupid for even writing that Pirate
Memphis Baas
#8 - 2017-01-23 15:25:42 UTC
Spacebar can be an issue as a key binding, because you could have chat channel focus and not realize it. You see people type wwwwwwwwwwww in local chat, they're trying to warp; with spacebar you wouldn't even see the spaces being typed.
Dupard Lemmont
KarmaFleet
Goonswarm Federation
#9 - 2017-01-26 07:28:49 UTC  |  Edited by: Dupard Lemmont
People warping off, docking station or jumping a gate will often remain in the overview for several seconds.
But you will be unable to lock them because of the action they are performing.
Also when you land on grid with someone you have to be completely out of warp until you are allowed to lock anything. So you will se what's on grid with you for 3-4 seconds before you actually can activate target lock.

This is completely normal game mechanics.

Does this fit what you are experiencing?
And might this be what is happening to you?

I also got confused by this several times, but I am used to it now.

EDIT: Oh I see this got resolved. Nevermind then.
Maybe this info will help others reading this.