| Pages: 1 [2] :: one page |
| Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Azuraito
Caldari
Capital Produce
Free Trade Zone.
   |
Posted - 2008.10.08 15:14:00 -
[31]
Seems to be a desync issue..
I have had similar problems in the past with missions.
I would suggest escalating the petition to a senior GM, first line GM's are most of the time useless and should really be nothing more than tea makers.
I would also suggest not linking this thread in the petition 
|
Andrue
Amarr
|
Posted - 2008.10.08 20:07:00 -
[32]
Edited by: Andrue on 08/10/2008 20:08:13
 Originally by: Azuraito
Seems to be a desync issue..
I'm not convinced about that. I have difficulty understanding how a desync event can be restricted to just one entity when half a dozen entities appear completely unaffected.
That's what is so odd about it. If everything was fubared then sure, desync or lag. Just the way it goes somehow forget it and move on.
But everything wasn't fubared. In my case just one rat out of 7 was failing to lock. Quite clearly my client was communicating just fine with the server and vice versa - it's just that one of the ships was unlockable for nearly a minute. That seems more like a bug to me.
But what the heck. A few of us have bug reported it and we'll just have to wait and see.
--
(Sarcastic mission running veteran, 4+ years)
[Brackley, UK]
My budgie can say "ploppy bottom". You have been warned. |
Shigsy
Heretic Militia
|
Posted - 2008.10.20 21:35:00 -
[33]
It makes for a hilarious bug when you're gatecamping and no one in your gang can lock a target that comes through.
|
The Sol
Minmatar
sol mans wave Corp
|
Posted - 2008.10.21 03:51:00 -
[34]
I have had this problem on a couple of occasions, I found a way around it, it works for me, right click your target and select ( lock target ) from the menu
after the fourth failed attempt at control clicking, I did this, works for me
if this indeed resolves the problem then the programmers should be able to pinpoint the cause
Because the command for control clicking your target and the command for menu targeting is different I would guess
and you need to ask yourself, if the said ship is using modules to block your targeting
but Im sure it is a bug and it should be able to easily trace the problem if again, menu targeting resolves the problem
|
Siu Supjee
|
Posted - 2008.11.05 18:19:00 -
[35]
Edited by: Siu Supjee on 05/11/2008 18:19:07
Saw this bug last night. Relogging fixed it, but it came back once I got jammed then unjammed again. Cost me a ship.
|
| |
|
| Pages: 1 [2] :: one page |
| First page | Previous page | Next page | Last page |