Pages: [1] :: one page |
|
Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Andrue
Amarr
|
Posted - 2008.09.24 10:51:00 -
[1]
Edited by: Andrue on 24/09/2008 10:52:01 First off - I'm not talking about being target jammed here.
Ever since the last patch I've had cases where a particular individual ship requires many attempts before a lock can be achieved. This happens despite the fact that other ships lock without a problem. Most of the time I just get 'Your attempt to lock XXX failed' appearing on screen. Sometimes though I get that and the lock goes through anyway.
Last night was nearly the final straw. I was fighting Guristas (yeah, ironic I know). I targetted four BS and one BC without problems. But one BC (a Nullifier - told you it was ironic) simply couldn't be targeted at first. It took something like six or seven attempts before I finally got a lock on it.
Aside from clearly being a bug this is incredibly f'ing annoying. Luckily the Nullifier didn't decide to jam me during this time (also suggesting a server issue) but that was the only good thing about it.
CCP - I'm suspicious that this might relate to your new optimised network IO layer. I'd bug report it..except that steps to reproduce is impossible. All I can say is that sometimes it happens. -- (Sarcastic mission running veteran, 4+ years)
[Brackley, UK]
My budgie can say "ploppy bottom". You have been warned. |
Kazuma Saruwatari
Caldari
|
Posted - 2008.09.24 12:48:00 -
[2]
Originally by: Andrue Edited by: Andrue on 24/09/2008 10:52:01 First off - I'm not talking about being target jammed here.
Ever since the last patch I've had cases where a particular individual ship requires many attempts before a lock can be achieved. This happens despite the fact that other ships lock without a problem. Most of the time I just get 'Your attempt to lock XXX failed' appearing on screen. Sometimes though I get that and the lock goes through anyway.
Last night was nearly the final straw. I was fighting Guristas (yeah, ironic I know). I targetted four BS and one BC without problems. But one BC (a Nullifier - told you it was ironic) simply couldn't be targeted at first. It took something like six or seven attempts before I finally got a lock on it.
Aside from clearly being a bug this is incredibly f'ing annoying. Luckily the Nullifier didn't decide to jam me during this time (also suggesting a server issue) but that was the only good thing about it.
CCP - I'm suspicious that this might relate to your new optimised network IO layer. I'd bug report it..except that steps to reproduce is impossible. All I can say is that sometimes it happens.
Bugreport it anyway, link this thread if you have to. -
|
BKnight3
|
Posted - 2008.09.25 14:06:00 -
[3]
Sounds like lag to me.... just my opinion, but some would say some bad things right now
|
Vril Ya
YDdraigGoch
|
Posted - 2008.09.25 16:19:00 -
[4]
I don't think it is lag, everything works without any delay, turning modules on/off is executed without any delay. I also didn't have anny issues during 10vs10 engagement, but when we were ganking 1 guy in group of five ships, me and one other guy - wasn't able to target our victim for about 20 seconds - every atempt ended in 2 seconds with "targeting failed".
|
Andrue
Amarr
|
Posted - 2008.09.25 16:28:00 -
[5]
Originally by: Vril Ya I don't think it is lag, everything works without any delay, turning modules on/off is executed without any delay. I also didn't have anny issues during 10vs10 engagement, but when we were ganking 1 guy in group of five ships, me and one other guy - wasn't able to target our victim for about 20 seconds - every atempt ended in 2 seconds with "targeting failed".
Yup, same here. I carried on fighting what Guristas I could target. Anyway my bug report has requested a log file so I guess we have to try and produce one. -- (Sarcastic mission running veteran, 4+ years)
[Brackley, UK]
My budgie can say "ploppy bottom". You have been warned. |
Tasko Pal
Heron Corporation
|
Posted - 2008.09.25 16:36:00 -
[6]
Originally by: BKnight3 Sounds like lag to me.... just my opinion, but some would say some bad things right now
I agree. This sounds like lag. What happens if you target someone and the server doesn't respond in a few seconds? I bet it's "targeting failed". Else you'd have trouble with retargeting. For example, you're in a laggy fleet battle and suppose you target the maximum number of ships. Your FC tells you to target something else. How do you do that when you're already targeting the max number of targets (say for the past couple of minutes). You'll have to wait for the old targeting to go through, then unlock one, then target. That might require several more minutes of time you don't have.
|
Andrue
Amarr
|
Posted - 2008.09.25 18:54:00 -
[7]
Edited by: Andrue on 25/09/2008 18:57:14 Edited by: Andrue on 25/09/2008 18:56:21
Originally by: Tasko Pal
Originally by: BKnight3 Sounds like lag to me.... just my opinion, but some would say some bad things right now
I agree. This sounds like lag.
Huh? So you think lag can be so specific as to only affect your ability to lock one particular ship while leaving other modules and other ships unnaffected? That's stupid.
I always try to take out the jammers first and it took so long to get a lock on that Nullifier that I managed to lock several other ships in the meantime and even opened fire on one of them when I gave up with the Nullifier.
That isn't lag. -- (Sarcastic mission running veteran, 4+ years)
[Brackley, UK]
My budgie can say "ploppy bottom". You have been warned. |
|
|
|
Pages: [1] :: one page |
First page | Previous page | Next page | Last page |