These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

Issues, Workarounds & Localization

 
  • Topic is locked indefinitely.
 

Bug with drones attacking MWD orbiting target?

First post First post
Author
Previous Topic Next Topic
Andaria
Doomheim
#1 - 2017-01-28 15:13:11 UTC  |  Edited by: Andaria
I've seen this happen twice now. I was doing a test and had my Gila with augmented hammerheads attacking another MWD Gila that was orbiting at 7.5km and after about 70 seconds my drones just decided to stop attacking him, and were set to idle. This happened twice in a row.

Anyone know about this or what is causing it? Very much sucks for pvp to have your drones just decide to stop attacking the target.
Arthur Aihaken
Kenshin Academia.
Kenshin Shogunate.
#2 - 2017-01-28 15:17:50 UTC
Just press your drone attack hot key again.

I am currently away, traveling through time and will be returning last week.
Nana Skalski
Taisaanat Kotei
EDENCOM DEFENSIVE INITIATIVE
#3 - 2017-01-28 15:27:57 UTC
Andaria
Doomheim
#4 - 2017-01-28 15:35:34 UTC  |  Edited by: Andaria
Arthur Aihaken wrote:
Just press your drone attack hot key again.


There's no indication this is about to happen, or that it has happened. All you notice is your drones suddenly are idle, that's DPS lost. If you don't notice fast, which is possible because you don't expect this to suddenly happen, or if you are presently target jammed it could easily alter the outcome of the fight.
Arthur Aihaken
Kenshin Academia.
Kenshin Shogunate.
#5 - 2017-01-28 16:06:01 UTC  |  Edited by: Arthur Aihaken
Andaria wrote:
There's no indication this is about to happen, or that it has happened. All you notice is your drones suddenly are idle, that's DPS lost. If you don't notice fast, which is possible because you don't expect this to suddenly happen, or if you are presently target jammed it could easily alter the outcome of the fight.

When your drones turn green instead of red that's usually a good indicator... If you're focused on attacking player(s) I think you'll tend to notice this as you'll most likely be paying very close attention to your drones. Without really knowing the specifics of your example, if the opposing player isn't attacking back you could simply be running into a timer.

I am currently away, traveling through time and will be returning last week.
Rroff
Antagonistic Tendencies
#6 - 2017-01-28 17:39:50 UTC
I've only seen this very rarely - as above mostly when the target isn't attacking back so might be some kind of timer.
ISD Max Trix
ISD Community Communications Liaisons
ISD Alliance
#7 - 2017-01-28 17:42:13 UTC
Moved to Issues and Workarounds.

ISD Max Trix

Lieutenant

Community Communication Liaisons (CCLs)

Interstellar Services Department

I do not respond to EVE mails about forum moderation.
CCP Darwin
C C P
C C P Alliance
#8 - 2017-01-28 18:22:22 UTC
CCP Karkur and CCP Snorlax recently found and fixed a very low-level bug that was causing other weird drone behavior, as well as a number of other problems in other game systems, but extremely rarely. Because of the nature of that fix, it's possible that it will help this issue too. This fix is still being prepared for release.

However, in general the best thing to do is submit an in-game bug report, preferably as soon as possible after the problem occurs. Noting the in-game time that it happened can help us take a look at whether there's anything in the logs, which an in-game bug report will automatically submit.

To do so, press F12 and click "Report Bug," then fill out the form with as much information as you can give us about what happened. That tool also allows you to submit screenshots if you feel they'll be helpful.

CCP Darwin  •  Senior Software Engineer, Art & Graphics, EVE Online  •  @mark_wilkins
Andaria
Doomheim
#9 - 2017-01-29 18:39:28 UTC
Rroff wrote:
I've only seen this very rarely - as above mostly when the target isn't attacking back so might be some kind of timer.


Yes, the target wasn't attacking back both times when this bug happened.