Pages: [1] :: one page |
|
Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Haniblecter Teg
F.R.E.E. Explorer Elitist Cowards
|
Posted - 2008.09.16 03:31:00 -
[1]
Thought I remember hearing about lock times being capped a few years ago at 1 second, that still true? ----------------- Friends Forever |
Rajere
No Trademark
|
Posted - 2008.09.16 04:45:00 -
[2]
think it's half a second iirc but it doesn't make a bit of difference, with server/client latency you're not going to be able to lock something faster than 1-2 seconds anyway, and even if you did have 0.5 sec lock time you can't stop a cloaker from cloaking by trying to lock him first (this is about the only reason you'd care about precisely how fast your lock time is). Unless you're in a situation with a great deal of module lag (huge fleet fight, etc), by the time the server tells your client that the target has decloaked, the server is already recognizing the command from his client that he hit the cloak button. Ergo, you can't lock him, so stop trying and start burning at him to decloak him instead. it's the only way you will catch him (assuming you have him in a bubble) NOTR How to Fail at Eve
|
Haniblecter Teg
F.R.E.E. Explorer Elitist Cowards
|
Posted - 2008.09.16 06:09:00 -
[3]
Originally by: Rajere think it's half a second iirc but it doesn't make a bit of difference, with server/client latency you're not going to be able to lock something faster than 1-2 seconds anyway, and even if you did have 0.5 sec lock time you can't stop a cloaker from cloaking by trying to lock him first (this is about the only reason you'd care about precisely how fast your lock time is). Unless you're in a situation with a great deal of module lag (huge fleet fight, etc), by the time the server tells your client that the target has decloaked, the server is already recognizing the command from his client that he hit the cloak button. Ergo, you can't lock him, so stop trying and start burning at him to decloak him instead. it's the only way you will catch him (assuming you have him in a bubble)
Upon a jump, I run hot on my guns, web, and two arty's (stilleto) turn on the MWD while sitting still, and wait to click.
I normally get movign in the direction of the guy and miss the lock. One of these days Ill get someone.
But yea, is there a hardcap? ----------------- Friends Forever |
Rajere
No Trademark
|
Posted - 2008.09.16 06:18:00 -
[4]
yeah there is a hardcap, but if they're using a cloak it doesn't matter. Due to latency between client/server/client, your target has activated his cloak and now untargettable on the server before the server has informed your client that he has decloaked and updated your overview to show him on your screen. This is why even if he's appeared on your overview for several seconds you're completely incapable of initiating a lock on him, even if you're lock time is faster than the few seconds he's appeared on your screen. The only things that prevent this is redonkulous server/gridload/module activation lag. Instead of trying to control click what you need to do is activate your mwd, triple click on him as soon as he appears on your overview, then as soon as your ship has aligned in his direction immediately click "move at full speed." If you have drones as you're passing the area he was deploy them. When you click approach and he vanishes off screen, your ship has nothing left to approach so just starts to slow down, giving him enough time to move/escape/warp off. NOTR How to Fail at Eve
|
Kazuma Saruwatari
Caldari
|
Posted - 2008.09.16 06:57:00 -
[5]
probably the main reason why lock times are hardcapped is because not everyone enjoys the double-digit ms ping rates people in Iceland/London enjoy -
|
Rawr Cristina
Caldari Omerta Syndicate
|
Posted - 2008.09.16 07:12:00 -
[6]
Originally by: Kazuma Saruwatari probably the main reason why lock times are hardcapped is because not everyone enjoys the double-digit ms ping rates people in Iceland/London enjoy
module lag is just as bad for most people
still takes me 2s+ for eve to react to anything i do
- Infectious - |
Stork DK
Minmatar Synthetic Frontiers
|
Posted - 2008.09.16 09:09:00 -
[7]
Originally by: Haniblecter Teg Upon a jump, I run hot on my guns, web, and two arty's (stilleto) turn on the MWD while sitting still, and wait to click.
Not doing it right.. Webbing will insta-warp any ship that comes through that gate m8. First get a point on him and then activate the webber.
I think the dual SeBo/Signal Amp stiletto is the fastest local lock speed you can get. (2.5k scan res+) but server lagg will never let you instalock. ----- - Stork DK, Synthetic Frontiers CEO |
Evanade
Rionnag Alba Triumvirate.
|
Posted - 2008.09.16 09:13:00 -
[8]
I dont think there is a hardcap as the formula used to calculate locktime simply doesnt allow you to get it under about .8s with current game mechanics and modules. --------------------------- sok alt - main got banzored |
Haniblecter Teg
F.R.E.E. Explorer Elitist Cowards
|
Posted - 2008.09.16 15:53:00 -
[9]
Originally by: Evanade I dont think there is a hardcap as the formula used to calculate locktime simply doesnt allow you to get it under about .8s with current game mechanics and modules.
Where's this formula?
My top row order is scram, web, gun, gun, so I scram before the web kicks in. I use a single SB too, so Im managing 1800+ scan res. Just seems like it always starts at .5 seconds, no matter the ship class. ----------------- Friends Forever |
Arous Drephius
Perkone
|
Posted - 2008.09.16 17:23:00 -
[10]
Edited by: Arous Drephius on 16/09/2008 17:24:19 Locking Time Formula.
Edit: Not sure where, but someone did an awesome graph showing the effect of higher scan resolution against locking time. As with most things in EVE, you get vastly diminishing returns the more scanres you have, which provides the effective "cap" on locking times.
|
|
Elaron
Jericho Fraction The Star Fraction
|
Posted - 2008.09.16 19:28:00 -
[11]
Originally by: Arous Drephius Locking Time Formula
Is that an approximation, or has it actually changed since TomB first introduced Scan Resolution and Signature Radius here? I ask because I was experimenting with something targeting speed related a couple of months ago and TomB's formula seemed dead on then.
|
Mr Krosis
The humble Crew
|
Posted - 2008.09.17 00:46:00 -
[12]
Originally by: Elaron
Originally by: Arous Drephius Locking Time Formula
Is that an approximation, or has it actually changed since TomB first introduced Scan Resolution and Signature Radius here? I ask because I was experimenting with something targeting speed related a couple of months ago and TomB's formula seemed dead on then.
The formula listed on eve-id.net is the correct one. The original one posted by TomB produces similar results, although squaring the sig radius causes the targeting speed to increase faster as size increases. With targets about the size of a frigate, tomb's original formula is pretty accurate. As target size increases, targeting time is approximately 25% faster at cruiser size, and about 40% faster at battleship size compared to what the original formula predicts.
Connection lag issues aside, there doesn't appear to be a hard cap on the lock time. A 2702mm scanres ship targeting a can (3000m) gets "0.196 seconds" as the first frame of the targeting speed bar. A ship with 1100mm scanres does it in about 0.5 seconds.
-- Mr Krosis The greatest obstacle to discovery is not ignorance; it is the illusion of knowledge. |
Rajere
No Trademark
|
Posted - 2008.09.17 09:10:00 -
[13]
Quote: But that same latency can work to your advantage and delay his cloak by a precious few.
No, not really. The only time there would be latency applying the cloak would be in situations where you have like 900 ppl on grid and there's 20 minute module activation lag or something, so him not cloaking right away is no big deal because even if you had grid loaded and he didn't, it'll take 20 minutes for your warp disruptor to activate.
the issue is simple client-server-client latency, it's nothing to do with what we consider lag. Double click in space and immediately hit f1. Time yourself, how much time passed between those two actions? Less time than the fastest lock achievable in game. Even if you fatfinger it and there is a pause between the two actions, unless that pause is several several seconds you still will not be able to lock a cloaker in time. Your client needs to wait until the server tells it that the target has decloaked before it can begin to display it on your screen, by the time your client is updating your overview the server already knows the target has cloaked and simply won't allow you to complete a target lock. It's the same reason why there is a pause when someone jumps a gate. They're still displayed on your screen for a second or two, but you cannot lock them, because the server already knows the activated the gate and while you're trying to target them the server is telling your client to remove them from your display. NOTR How to Fail at Eve
|
|
|
|
Pages: [1] :: one page |
First page | Previous page | Next page | Last page |