EVE Search - Locking Delay

All Channels

Warfare & Tactics

Locking Delay - Kinda annoying

» Click here to find additional results for this topic using Google

Monitor this thread via RSS [?]

Pages: [1] :: one page
Author	Thread Statistics \| Show CCP posts - 0 post(s)
Dave Viker Do you even Exist. 55	Posted - 2015.01.08 13:54:42 - [1] - Quote Good Day, I don't know if a similar thread was already posted before, but lately I have stepped on a problem several times: After I successfully lock a target and hyperspam my point, it often just does nothing for ~500ms, just to give me the "Warp interrupts bla bla lock not possible" message and my target's safely cuddling with it's warp bubble. Question is, does EVE really have such a giant Ping? Or am I just doing it wrong? What's the fasted way to lock a target? Manually lock it with CTRL+Click then point, or click point first and then directly on the target? (Auto lock N point) I like missed >that< much kills just because of this "delay". Oh, and another question: After the lock timer ran out, the animation says "Locked" and is blinking like a rabbit for like another 0.5 seconds. Is this intended? Like a fixed 0.5 seconds on top of your locktime? Sorry if my questions were answered somewhere before, but I could not find any thread yet :c
Thanatos Marathon Phoibe Enterprises 384	Posted - 2015.01.08 14:47:20 - [2] - Quote Dave Viker wrote: What's the fasted way to lock a target? Manually lock it with CTRL+Click then point, or click point first and then directly on the target? (Auto lock N point) Activate point first, wait for target, click on target. Note that this will not work on someone who is untargetable.
Dave Viker Do you even Exist. 55	Posted - 2015.01.08 14:53:35 - [3] - Quote Ah thanks, I'll try it that way now. Indie GameDev & Audiophile Checkout my Soundcloud page. Hitech Trance, Chillout, Acoustic Stuff.
Gully Alex Foyle Black Fox Marauders Spaceship Bebop 3314	Posted - 2015.01.08 15:49:06 - [4] - Quote Server ticks are 1 second. I think it can happen that your client counts the lock timer down to zero, assumes you got a lock (and tells you so), but then the server says 'nope, sorry, he warped off already'. That's why most people agree that having an align time under 2 seconds is useless, the way the server works 2 seconds is enoughto aavoid being locked, even if your theoretical lock time is 0.3 seconds. Make space glamorous! Is EVE dying or not? Ask the EVE-O Death-o-meter!
Dave Viker Do you even Exist. 55	Posted - 2015.01.08 15:54:48 - [5] - Quote Gully Alex Foyle wrote: Server ticks are 1 second. I think it can happen that your client counts the lock timer down to zero, assumes you got a lock (and tells you so), but then the server says 'nope, sorry, he warped off already'. That's why most people agree that having an align time under 2 seconds is useless, the way the server works 2 seconds is enoughto aavoid being locked, even if your theoretical lock time is 0.3 seconds. Well this is interesting. Does the server compute in one-second ticks or communicate in that interval? This must also be the reason for i.e. the Movement Speed of Vessels only updating every Second. But thanks for that info, that clears up a lot! Indie GameDev & Audiophile Checkout my Soundcloud page. Hitech Trance, Chillout, Acoustic Stuff.
Gully Alex Foyle Black Fox Marauders Spaceship Bebop 3315	Posted - 2015.01.08 16:19:21 - [6] - Quote Dave Viker wrote: Gully Alex Foyle wrote: Server ticks are 1 second. I think it can happen that your client counts the lock timer down to zero, assumes you got a lock (and tells you so), but then the server says 'nope, sorry, he warped off already'. That's why most people agree that having an align time under 2 seconds is useless, the way the server works 2 seconds is enoughto aavoid being locked, even if your theoretical lock time is 0.3 seconds. Well this is interesting. Does the server compute in one-second ticks or communicate in that interval? This must also be the reason for i.e. the Movement Speed of Vessels only updating every Second. But thanks for that info, that clears up a lot! Both. I also believe it can happen that the command you give based on the info the server gave you at T0 will not get back and be processed before T2. That's where Than's advice helps (pre-queueing the 'Point!' command) Make space glamorous! Is EVE dying or not? Ask the EVE-O Death-o-meter!
Andre Vauban Quantum Cats Syndicate 360	Posted - 2015.01.08 17:29:00 - [7] - Quote Dave Viker wrote: Gully Alex Foyle wrote: Server ticks are 1 second. I think it can happen that your client counts the lock timer down to zero, assumes you got a lock (and tells you so), but then the server says 'nope, sorry, he warped off already'. That's why most people agree that having an align time under 2 seconds is useless, the way the server works 2 seconds is enough to aavoid being locked, even if your theoretical lock time is 0.3 seconds. Well this is interesting. Does the server compute in one-second ticks or communicate in that interval? This must also be the reason for i.e. the Movement Speed of Vessels only updating every Second. But thanks for that info, that clears up a lot! The server computes in one second internals, it communicates constantly. This may be wrong/over simplified, but I think the problem boils down server ticks. Assume all the processing happens at integer numbers and commands are sent/received during real numbers. If you request to activate a point on a locked target at time 1.000000001, then that request won't be processed until time 2. If the target is supposed to enter warp at time 1.9999, then the target is gone when the server processes the point command. In essence, the target warps off at the same exact time you try to point him. Somebody did a good write up of Eve server ticks in a PDF document that I remember reading. Try Googling for "Eve server ticks" or something and maybe you can find it. QCATS is recruiting:-á https://forums.eveonline.com/default.aspx?g=posts&m=3896299
Tsukino Stareine Serene Vendetta Brawls Deep 813	Posted - 2015.01.08 18:55:57 - [8] - Quote start locking and then spam module u want to activate while locking. This is the fastest way.
Plato Forko Forko Nanorobotics 113	Posted - 2015.01.08 19:25:23 - [9] - Quote CTRLCTRLCTRLCTRLCTRLCTRLCTRLCTRLCTRCLFUCK!!! repeat There's nothin' like skating away from a fight with the hull on fire, some mods burned out and a cargohold full of loot. See my terribad blog for stories.
Iyokus Patrouette No Vacancies 252	Posted - 2015.01.08 22:45:52 - [10] - Quote Screw points, use bubbles. ---- Advocate for the initiation of purple coloured wormholes----
ShahFluffers Ice Fire Warriors Snuffed Out 7036	Posted - 2015.01.09 04:22:30 - [11] - Quote Gully Alex Foyle wrote: Dave Viker wrote: Gully Alex Foyle wrote: Server ticks are 1 second. Well this is interesting. Does the server compute in one-second ticks or communicate in that interval? This must also be the reason for i.e. the Movement Speed of Vessels only updating every Second. But thanks for that info, that clears up a lot! Both. I also believe it can happen that the command you give based on the info the server gave you at T0 will not get back and be processed before T2. That's where Than's advice helps (pre-queueing the 'Point!' command) ^^ This Every second the server will receive any new (series of) commands, process them, and update your client in the following second. This is why align times (in to warp) that are under 2 seconds are effectively "unlockable" (unless you are living right next to the servers in London). There was a DEV blog about this a LOOOOOOOONG time ago detailing how the server functions and what its Achilles heel* is. In a way, this 1Hz speed is good because it allows for so many people to function at the same time in the same general area without many problems. However it is frustrating when dealing with very fine maneuvers. * EVE's coding architecture can't make use multi-core processors due to its single threaded design (it was built before multi-cores) and time sensitive nature of the information. The former is being worked on as we speak though. The latter can't really be helped. Change isn't bad, but it isn't always good. Sometimes, the oldest and most simple of things can be the most elegant and effective. "How did you veterans start?"
Dave Viker Do you even Exist. 55	Posted - 2015.01.09 08:29:20 - [12] - Quote ShahFluffers wrote: * EVE's coding architecture can't make use multi-core processors due to its single threaded design (it was built before multi-cores) and time sensitive nature of the information. The former is being worked on as we speak though. The latter can't really be helped. This is the exact same problem as Blizzard with World of Warcraft has to deal with. So you're saying that the SERVERS actually run on single-threaded solo processors? That's where tidi comes from then. Indie GameDev & Audiophile** Checkout my Soundcloud page. Hitech Trance, Chillout, Acoustic Stuff.

Pages: [1] :: one page
First page \| Previous page \| Next page \| Last page

COPYRIGHT NOTICE
EVE Online, the EVE logo, EVE and all associated logos and designs are the intellectual property of CCP hf. All artwork, screenshots, characters, vehicles, storylines, world facts or other recognizable features of the intellectual property relating to these trademarks are likewise the intellectual property of CCP hf. EVE Online and the EVE logo are the registered trademarks of CCP hf. All rights are reserved worldwide. All other trademarks are the property of their respective owners. CCP hf. has granted permission to EVE-Search.com to use EVE Online and all associated logos and designs for promotional and information purposes on its website but does not endorse, and is not in any way affiliated with, EVE-Search.com. CCP is in no way responsible for the content on or functioning of this website, nor can it be liable for any damage arising from the use of this website.