Pages: [1] 2 3 4 :: one page |
|
Author |
Thread Statistics | Show CCP posts - 1 post(s) |

Grunt Futtoks
Zenithal Harvest
|
Posted - 2008.03.20 04:56:00 -
[1]
Edited by: Grunt Futtoks on 20/03/2008 04:57:03 My corp has been having a serious issue attempting to lock targets as they appear from gates.
As soon as the ship uncloaks we target, and the client says "the target is invulnerable" and refuses to allow a lock until the target warps.
This is not just an isolated case of lag, this is consistently happening way too much following the recent 1.1 patch. We know how the game works and feels, and something's messed up. It is happening with fast locking sensor boosted ships and interceptors against targets -we know- that we can lock under normal circumstances.
I'm wondering if anyone else is experiencing this problem? -
"We do not ask sheep to be wolves; we, the wolves, do not ask ourselves to be sheep. Sheep can make such rules as happen to suit them--but it's foolishly naive to expect wolves to obey." |

Jennai
The Greater Goon GoonSwarm
|
Posted - 2008.03.20 04:59:00 -
[2]
yes, noticed this yesterday. some stuff got away that really shouldn't have because everyone was either unable to lock at all, or they had the thing where the lock timer reaches zero but it doesn't lock. the system wasn't lagging in any other way.
|

revilot
the united Sex Panthers
|
Posted - 2008.03.20 07:20:00 -
[3]
I've noticed this as well, especially when jumping through gates after targets. Some corpmates have stated they have the same problem as well, so I know it's not just me.
Since the patch I notice a lot of time I don't actually get a countdown when locking targets. I click to lock and it appears that it's not doing anything, then all of a sudden it locks. It just feels completely broken.
Please, spend less time kicking me in the balls with your incessant nerfing, and more time testing and fine tuning your patches so you don't create more problems than previously existed.
|

Solomunio Kzenig
SPORADIC MOVEMENT HUZZAH FEDERATION
|
Posted - 2008.03.20 07:40:00 -
[4]
Yup, been suffering from this at gate camps quite a bit, very frustrating.
|

Terraform
Synthetic Frontiers Blue Federation
|
Posted - 2008.03.20 08:58:00 -
[5]
Agreed, it's becoming a fairly common problem, it was there before the patch, but now it's there constantly. FIX IT CCP!!
|

Orion Eridanus
Dark Nova Crisis Chain of Chaos
|
Posted - 2008.03.20 09:06:00 -
[6]
No, your not the only one, we had a thread about this 2 weeks ago in C&P I believe
Originally by: Paulo Damarr That is a most Excellent Drake fitting, you are lucky to have survived.
|

Tokena
Federal Navy Academy
|
Posted - 2008.03.20 09:08:00 -
[7]
Has been happening a lot to me as well, not just at gates.
Been at a belt, enemy warps in. I try to target: "Target is invulnerable". Enemy starts flashing yellow (ie. has targeted me): "Target is invulnerable". Enemy starts flashing red (ie. weapons firing): "Target is invulnerable". I start taking damage and am finally able to lock him, maybe 10 seconds later than he could lock me.
Anybody tried bug reporting this yet? I'm too lazy to file a report that will just get filtered out...
|

techzer0
IDLE GUNS
|
Posted - 2008.03.20 09:08:00 -
[8]
Get it all the time... or the target picture appears and modules don't activate. I figure if the locking timer says zero, then I should have lock. Not "oh you have lock... wait 2 more seconds for the picture to load... now activate the module!".
That or you can't lock someone who is aligning... even if you're sitting there bumping them. I tried for four minutes straight to lock a drake that was scrammed by NPCs and got the same "Attempt to target failed" until he killed the last NPC and warped on his happy way. Petitioned it and got a crap response about how my issue should be sent as a bug report, but when I deleted the petition it told me it hadn't even been viewed? Riiiiight.
 ------------
Originally by: CCP Mitnal It's great being a puppetmaster 
|

Disteeler
Segunda Fundacion T e r c i o s
|
Posted - 2008.03.20 09:50:00 -
[9]
I'm getting this constantly since 1.0
Sig by Black Necris |

HellSpreader
Fleeting Moments of Insanity
|
Posted - 2008.03.20 10:15:00 -
[10]
I should imagine this issue is directly related to the period of time it takes for the client computer to "refresh into the new system"
I'm sure if it were the other way around there would be a post saying...
"wtf!!! I jumped into a system and before my screen refreshed I was dead AND podded!!! give me my money back etc etc".
I think it is a good thing that you are invulnerable until you are actually in control of your ship and able to defend yourself from would-be aggressors.
The same thing happens when you exit from a station... until the client computers screen refreshes and you enter your*****pit you are invulnerable. Join -FMI- Now!!! |
|

Venkul Mul
Vikramaditya DO JAJA Alliance
|
Posted - 2008.03.20 10:17:00 -
[11]
Edited by: Venkul Mul on 20/03/2008 10:17:39 If it can make you happy, it happens in PvE too. "Target locking failed" or some similar message.
|

HellSpreader
Fleeting Moments of Insanity
|
Posted - 2008.03.20 10:19:00 -
[12]
Edited by: HellSpreader on 20/03/2008 10:20:06 Yes... in PvE that is because one of the enemies is a tackler. This therefore is a different scenario and THUS the message is "Target Locking Failed" as opposed to "Target is Invulnerable"
I suggest that if you ever get a "Target is Invulnerable" message in PvE.... Warp out of there as quickly as your ship can carry you! Join -FMI- Now!!! |

Grunt Futtoks
Zenithal Harvest
|
Posted - 2008.03.20 10:53:00 -
[13]
Well it seems to be a much more prevalent issue since 1.1. Yes this message did happen before but never so frequently. Today there were several instances when we could not lock cruisers with interceptors. If there was no WTZ this might not be a huge problem but if we can't lock cruisers with inties it greatly affects game dynamics for our corp in a negative way.
HellSpreader: You sound like you're actually defending this issue, which probably should not surprise me. Allow me to point out that it has nothing to do with "refreshing the new system" because you are cloaked until you decide to move (or the 5 minute timer is up). These targets are issuing a warp command, they are not lagging out on system load. They are placing themselves in situations where they should be caught, and escaping because of this issue. -
"We do not ask sheep to be wolves; we, the wolves, do not ask ourselves to be sheep. Sheep can make such rules as happen to suit them--but it's foolishly naive to expect wolves to obey." |

HellSpreader
Fleeting Moments of Insanity
|
Posted - 2008.03.20 11:14:00 -
[14]
I am someone able to concede a point. On the system jump I agree... to a point... with you.
When exiting a station I think it is a very good system as it takes certain users longer to refresh (whilst their ship is floating in space unpiloted) and therefore shouldn't be targeted until they can react to the situation. Join -FMI- Now!!! |

techzer0
IDLE GUNS
|
Posted - 2008.03.20 11:39:00 -
[15]
Originally by: HellSpreader Edited by: HellSpreader on 20/03/2008 10:20:06 Yes... in PvE that is because one of the enemies is a tackler. This therefore is a different scenario and THUS the message is "Target Locking Failed" as opposed to "Target is Invulnerable"
I suggest that if you ever get a "Target is Invulnerable" message in PvE.... Warp out of there as quickly as your ship can carry you!
No. I get "Attempt to target failed" a lot in PVP. I only ever get "Target is Invulnerable" when I'm locking someone who just undocked, or as I'm coming out of warp on top of them and I click too quick.
When you sit on top of a target in a ship and all you get is "Lock failed" and neither of you had just jumped or undocked... then you know there is an issue  ------------
Originally by: CCP Mitnal It's great being a puppetmaster 
|

Venkul Mul
Vikramaditya DO JAJA Alliance
|
Posted - 2008.03.20 11:45:00 -
[16]
Originally by: HellSpreader Edited by: HellSpreader on 20/03/2008 10:20:06 Yes... in PvE that is because one of the enemies is a tackler. This therefore is a different scenario and THUS the message is "Target Locking Failed" as opposed to "Target is Invulnerable"
I suggest that if you ever get a "Target is Invulnerable" message in PvE.... Warp out of there as quickly as your ship can carry you!
I find a bit unclear what you mean with "a tackler" here.
It usually refer to a ship with warp jammer and webbers but that don't make them resistant to target lock.
The behaviour is the same the OP described. The lock fail (while other targets are locked nomally) at the first try and the ship can be locked only after it has attacked.
|

Shintai
Balad Naran Orbital Shipyards
|
Posted - 2008.03.20 11:45:00 -
[17]
I have a feeling this issue will go away soon. Or atleast diminish. But by soon I mean about 3-4 weeks.
It seems to be the interconnect between the nodes are overburden. And the same interconnects are used nomatter where you are basicly. So lets hope when some few million space objects that the client entering a system needs to be aware of before being vulnaable is removed. Then we can see a much more smooth and "locking" EvE Abstraction and Transcendence: Nature, Shintai, and Geometry |

Johncrab
XBeyond
|
Posted - 2008.03.20 12:11:00 -
[18]
Same exact thing here. And not only at gates... belts, planets... |

Omarvelous
Destry's Lounge XIII Legio
|
Posted - 2008.03.20 13:43:00 -
[19]
Thought I was the only one - happens at gates and stations (not the 30-sec invul time either).
Anti-pvp boost?  __________________________________________________ Sup brosef! Destry's Lounge is looking for a few good drunks - contact me in game.
|

Bronson Hughes
Knights of the Wild Visions of Warfare
|
Posted - 2008.03.20 13:53:00 -
[20]
Oh good, I'm not the only one. I was begining to think I was the worst tackler in all of EvE.
I was camping a gate in a sensor boosted Raptor before 1.1 and in the span of 20 minutes no less than three shuttles came through that were 'Invulnerable' until they were warping off. My camp-mates were complaining that I wasn't locking fast enough and I told them that I just couldn't.
I'd be willing to bet that it's some sort of minor desync between the server, the target client, and your client. -------------------- "I am hard pressed on my right; my centre is giving way; situation excellent; I am attacking." - Ferdinand Foch at the Battle of the Marne |
|

MrTripps
Blueprint Haus Intrepid Crossing
|
Posted - 2008.03.20 13:54:00 -
[21]
Yep. Get it all the time. Not only that but at least once I've had a red cov ops come into system, uncloak from the gate jump, then recloak without ever appearing on overview.
"I hate to advocate drugs, alcohol, violence, or insanity to anyone, but they've always worked for me." Hunter S. Thompson. |

Nicholas Barker
MASS Ministry Of Amarrian Secret Service
|
Posted - 2008.03.20 13:54:00 -
[22]
who the hell is HellSpreader and why does he keep posting when he doesn't know what he's talking about?
"Target is Invulnerable" is what you get when you're trying to lock somebody who's Invulnerable due to undocking until they try to do something.
Targeting failed is when the game is just arsing up, I've jumped in to a system to gank something and been the only person who couldn't lock it, so all I can say is it doesn't effect everybody (can't say for 1.1).
It also happens when an npcalt/macro npcer log off mid warp, you can't lock them and they warp off. ---
|

Furious Hawk
I-Omniscient-I
|
Posted - 2008.03.20 14:23:00 -
[23]
Our corp noticed it too.
Yay for targeting nerf?
|

Zenst
Omniscient Order
|
Posted - 2008.03.20 14:36:00 -
[24]
its nothing new, actualy wrote small ditty about it few months back now:
Target invulnerable, Target invulnerable, Target invulnerable, Target invulnerable, Target invulnerable, Target invulnerable Target invulnerable, Target invulnerable, Oh look the designated target is no longer there.
I sit outside the pearly gates, In Jita 4 4 in the congregate, I sit and stand and look around, Awaiting for the agro sound.
I see a target not at gate, I start to lock to seal its fate, Target invulnerable, Goes sound, My lock times all the wrong as it goes around.
Target invulnerable, Target invulnerable, Target invulnerable, Target invulnerable, Target invulnerable, Target invulnerable Target invulnerable, Target invulnerable, Oh look the designated target is no longer there.
|

Kappas.
Galaxy Punks Black Core Alliance
|
Posted - 2008.03.20 16:40:00 -
[25]
I was just scrammed by a frig in a belt, and for just under 4 minutes all I got was "Failed to target XYZ", was just opening a stuck petition when all of a sudden a lock came out of nowhere 
Something is going wrong. __________________
|

Aram Gishno
The Graduates Brutally Clever Empire
|
Posted - 2008.03.20 17:21:00 -
[26]
Edited by: Aram Gishno on 20/03/2008 17:22:31 This was happening to me as well but I thought it was a problem with my system or the way i was locking someone. It also happens to me near gates, planets, and belts. Very frustrating thing especially when you know you should have that person locked down in a fraction of the time it takes for the invulnerable message to eventually go away. Thanks for confirming. I've had other issues that I think warrant someone starting a "since 1.1 was put out" thread.
Edit- Yes, this did exist prior to 1.1 but it is much more of an issue now.
|

El Muerte
The Nine Gates Black Core Alliance
|
Posted - 2008.03.20 17:24:00 -
[27]
Been getting the same thing.
Also, yesterday when trying to jump thru a gate.
Session change in progress. Lost my rapier.
As soon as my ship exploded my pod was in the next system that I was trying to jump to lol.
CCP for the win.
|

Rhaegor Stormborn
Volition Cult The Volition Cult
|
Posted - 2008.03.20 17:25:00 -
[28]
Aye, same problem here.
Volition Cult Recruitment Post |

MaDeX
XxTiggerxX Corp Kraftwerk.
|
Posted - 2008.03.20 17:33:00 -
[29]
Yeah same issue here, also they dont drop faction items - fix also.
|

Uhr Zylex
No Trademark Notoriety Alliance
|
Posted - 2008.03.20 17:34:00 -
[30]
yes. missed out on two carrier kills yesterday because of this.
|
|
|
|
|
Pages: [1] 2 3 4 :: one page |
First page | Previous page | Next page | Last page |