Also note that if any ships are lost due to this then any petitions are returned as 'Rejected, nothing showing in our logs'.

Not sure if it was a bug...

Did a mission today and suddenly all 5 drones were gone at the same second.
Not sure if the NPC enemies (a lot at this moment) took them out or if this was a bug.

As documented and bug-reported since the release of THE GAME, drones are broken. Specifically they go idle after appearing to obey the command to attack or mine. The long-term drone bug of focus fire not working is also well known.

No acknowledgement from CCP was given on the old forums. I'm posting here to undermine the future "oh we didn't know because that was on the old forums" line that I expect would surface otherwise.

Tell us plainly if this stealth nerf is "functioning as intended" or will be fixed "soon".

Notice the Devs replying and acknowledging other bugs and issues in this section, but never the drone bug.

This stinks!

Hey can someone (or preferably some people) post describing exactly what the problem is, how it manifests and any potential repro steps? Gonna stick a defect on Tuxford once I understand the symptoms properly. (Although as is usually the case, until we can figure out how to consistently reproduce the issue it's really difficult to fix it or indeed to tell whether or not it's actually fixed - the more detail we can collect on the exact circumstances under which this is happening, the better chance we have of reproducing it "in the lab".)

Hey can someone (or preferably some people) post describing exactly what the problem is, how it manifests and any potential repro steps? Gonna stick a defect on Tuxford once I understand the symptoms properly. (Although as is usually the case, until we can figure out how to consistently reproduce the issue it's really difficult to fix it or indeed to tell whether or not it's actually fixed - the more detail we can collect on the exact circumstances under which this is happening, the better chance we have of reproducing it "in the lab".)

Drones specifically sentry drones now do not easily follow from one target to the next. Previously before Incarna I could command my drones to engage the next target as soon as the current target was destroyed and they would all engage. Now some all or none will engage unless I spam the command for them to engage. This is similar to the behavior that drones followed when set to aggressive yet were counter ordered manually. The trouble is that passive drones fail to attack the next target on command without being give the order as many as ten times.

// Thanks for taking the time to fill this out. I-¦m attaching your BR to the relevant defect dealing with focus fire and drone target choosing (or the misbehavior thereof)

BH Exsum
//

Hey can someone (or preferably some people) post describing exactly what the problem is, how it manifests and any potential repro steps? Gonna stick a defect on Tuxford once I understand the symptoms properly. (Although as is usually the case, until we can figure out how to consistently reproduce the issue it's really difficult to fix it or indeed to tell whether or not it's actually fixed - the more detail we can collect on the exact circumstances under which this is happening, the better chance we have of reproducing it "in the lab".)

Look, I've used drone ships in lvl4s for a long time, and yes they are buggy and temperamental, but the issue is fairly minor if u assign your engage drones to a hotkey. Spam that about 100 times and they'll follow your commands. The only drones this wont work for is mining drones.

Hey can someone (or preferably some people) post describing exactly what the problem is, how it manifests and any potential repro steps? Gonna stick a defect on Tuxford once I understand the symptoms properly. (Although as is usually the case, until we can figure out how to consistently reproduce the issue it's really difficult to fix it or indeed to tell whether or not it's actually fixed - the more detail we can collect on the exact circumstances under which this is happening, the better chance we have of reproducing it "in the lab".)

It appears that while doing a mission drones become confused as to what target they are tracking.

For example, if a target is destroyed, or I issue a new attack order on a different target. All five drones will respond and approach the new target to get into firing range. Sometimes between 1 to 5 drones will drop out of attack mode.

What I think is happening is that, some of the drones are still in coldown on their turrets. So when the drone comes out of cool down the turrets are still looking at the old target, even though a new target was specified. The turrets attempt to fire at the old target, which no longer exists. So no target, a stop order is issued by the server and the drones go into a ready state.

So 5 drones are attacking target, 3 have just fired weapons and popped the target, I issue a new attack order, all five drones respond. As drones head into range on new target, 3 come out of turret cool down and realize the target no longer exists. This is interperted as the new target no longer exists, those three go into standby, the other two continue on to attacking new target. Or those three may travel back and attack the old target if it stil exists if I issued a new target while they are in turret cooldown.

That is how it appears to me.

I've been noticing drones misbehaving more than usual lately too.

They seem to loose aggro alot, though I have had them set to agressive.
It also takes for the rats to be within very short distance (10-18 km ish) before the drones even realize I'm under attack.

Yep, that is how it looks to me as well. In addition occasionally (even if the drones are keeping up with the target) drones will forget about a very fast target. I.E. there seems to be some bug with loosing lock on a fast target.

It appears that while doing a mission drones become confused as to what target they are tracking.

For example, if a target is destroyed, or I issue a new attack order on a different target. All five drones will respond and approach the new target to get into firing range. Sometimes between 1 to 5 drones will drop out of attack mode.

What I think is happening is that, some of the drones are still in coldown on their turrets. So when the drone comes out of cool down the turrets are still looking at the old target, even though a new target was specified. The turrets attempt to fire at the old target, which no longer exists. So no target, a stop order is issued by the server and the drones go into a ready state.

So 5 drones are attacking target, 3 have just fired weapons and popped the target, I issue a new attack order, all five drones respond. As drones head into range on new target, 3 come out of turret cool down and realize the target no longer exists. This is interperted as the new target no longer exists, those three go into standby, the other two continue on to attacking new target. Or those three may travel back and attack the old target if it stil exists if I issued a new target while they are in turret cooldown.

That is how it appears to me.

Launch drones, engage target, kill target, immediately on killing said target send the drones after another target. After the time frame it would normally take to pick a new target on their own, they will pick a new target over-riding your orders.

It has nothing to do with the target speed. Drones may unlock veldspar asteroid and I'm sure that it doesn't move anywhere.

This sounds rather good estimation about what is going on. Facts are that drones will not disengage from 1st target they are ordered into. Buggy behauviour starts always when 1st target has died/depleted and drones are commanded to 2nd+++ one.

Still broke...

In addition to the problems already mentioned I'd like to also point out that drones used to act as a solid unit. Somewhere between dominion and incursions, drones stopped functioning as a solid unit. What I mean is that whenever a target was destroyed when drones were set to agressive and focus fire, all the drones would for a split-second become idle, then they would all start microwarping to the next target at the exact same time and once they arrived on target they would all fire in unison on that target. They had a sort of "volley damage" effect that they lack now and it's really made killing elite frigates in missions take quite a bit longer. Now it seems that when a target is destroyed one drone out of the pack will lead the charge while the others at their own pace try to catch up: Drone 1 starts engaging target, up to a whole second later Drones 2 and 3 start to engage, split-second later drones 4 and 5 start to engage. When these drones are finally all on target they have all started firing upon arriving and they are not in any kind of unison, in effect operating much like ungrouped turrets. I'm glad to see a response from a CCP employee on the matter, I thought the day would never come. I can only hope that the issue is tested for more than just a few minutes as it can take some time for the problems to manifest while other times it's right off the bat.


Also, I'd really appreciate it if when I take the time to type out a semi-long post, that when I hit the post button I wasn't immediately brought back to the "Post a reply" page and the whole of my post gone forever without even being posted. Having to copypasta my posts into notepad before hitting the post button just to be safe every time is really getting annoying.

BTW this is post attempt #4

Today we received the second patch to fix invisible Barbies. Another patch day has come and gone without so much as a word from CCP on the drones issue. We did get one Dev to ask for a reiteration of information that was already posted on the forums and already contained within bug reports. Then nothing since. Nothing. It raises the question: Just how useful are bug reports?

Why is it so hard to answer the question in the OP?
Why did CCP choose to break drones? What was the big GÇ£featureGÇ¥ that was added to FiS that caused drones to go idle?
Why does CCP choose to remain silent on the drones issue?

CCP if you think basic FiS mechanics are lower priority than non-alphanumeric characters in file paths causing inviso-Barbie then you demonstrate an out of touch with the player-base mindset.

Today we received the second patch to fix invisible Barbies. Another patch day has come and gone without so much as a word from CCP on the drones issue. We did get one Dev to ask for a reiteration of information that was already posted on the forums and already contained within bug reports. Then nothing since. Nothing. It raises the question: Just how useful are bug reports?

Why is it so hard to answer the question in the OP?
Why did CCP choose to break drones? What was the big GÇ£featureGÇ¥ that was added to FiS that caused drones to go idle?
Why does CCP choose to remain silent on the drones issue?

CCP if you think basic FiS mechanics are lower priority than non-alphanumeric characters in file paths causing inviso-Barbie then you demonstrate an out of touch with the player-base mindset.

[snip]
if we can get dev interest in the problem, we may stand a chance of having them figure it out.

Another OMG...How about actually playing the game and see? It doesn't take long to see the crap we have endured for years, and even more intensely now since Incarna.

I shouldn't have to keep my finger on my Drones Attack key all the time.

Ok, so the three things I'm seeing repeatedly are:

* Drones picking their own targets/going idle (based on aggressive/passive setting I'm assuming) after a fairly consistent delay once you've issued a command
* Drones failing to focus fire
* Drones catching a fast target, dropping to normal speed and immediately getting left behind

Am I missing something or are those the major problems?



I mainly fly Amarr, we don't usually get a whole lot of drones

What sort of rats is this happening with? Drones shouldn't be selecting targets until you're actually fired upon (red box rather than yellow box).

Ok, so the three things I'm seeing repeatedly are:

* Drones picking their own targets/going idle (based on aggressive/passive setting I'm assuming) after a fairly consistent delay once you've issued a command
* Drones failing to focus fire
* Drones catching a fast target, dropping to normal speed and immediately getting left behind

Am I missing something or are those the major problems?

It appears that while doing a mission drones become confused as to what target they are tracking.

For example, if a target is destroyed, or I issue a new attack order on a different target. All five drones will respond and approach the new target to get into firing range. Sometimes between 1 to 5 drones will drop out of attack mode.

What I think is happening is that, some of the drones are still in coldown on their turrets. So when the drone comes out of cool down the turrets are still looking at the old target, even though a new target was specified. The turrets attempt to fire at the old target, which no longer exists. So no target, a stop order is issued by the server and the drones go into a ready state.

So 5 drones are attacking target, 3 have just fired weapons and popped the target, I issue a new attack order, all five drones respond. As drones head into range on new target, 3 come out of turret cool down and realize the target no longer exists. This is interperted as the new target no longer exists, those three go into standby, the other two continue on to attacking new target. Or those three may travel back and attack the old target if it stil exists if I issued a new target while they are in turret cooldown.

That is how it appears to me.

"We are listening to you, we have heard you, and plans are already in motion." -Arnar Hrafn Gylfason
Senior Producer of EVE Online


I hope this means drones will be restored to their pre-Incarna functionality.

Alot fo very relevant stuff

"We are listening to you, we have heard you, and plans are already in motion." -Arnar Hrafn Gylfason
Senior Producer of EVE Online


I hope this means drones will be restored to their pre-Incarna functionality.

Most/All of the stuff mentioned in this thread were broken pre-Incarna, the only thing that changed is the frequency.

No.

Just spent an hour poking at this and totally failing to get a reproduction for drones switching targets. Tried with Hammerheads, Gardes and Ogres, tried issuing target orders just before, just after, and a second after the target died, and even tried hacking the Ogres to have a10s RoF to see if that'd help. In all cases they're working as advertised (focus fire and aggressive).

Obviously this problem is still happening in the wild, but it doesn't seem to be reproducing on our internal test servers which makes it somewhat difficult to track down. I'll try and give it another poke later in the week and see if I can find anything more, but right now I don't have a whole lot to go on :(

Just spent an hour poking at this and totally failing to get a reproduction for drones switching targets. Tried with Hammerheads, Gardes and Ogres, tried issuing target orders just before, just after, and a second after the target died, and even tried hacking the Ogres to have a10s RoF to see if that'd help. In all cases they're working as advertised (focus fire and aggressive).

Obviously this problem is still happening in the wild, but it doesn't seem to be reproducing on our internal test servers which makes it somewhat difficult to track down. I'll try and give it another poke later in the week and see if I can find anything more, but right now I don't have a whole lot to go on :(

Just spent an hour poking at this and totally failing to get a reproduction for drones switching targets. Tried with Hammerheads, Gardes and Ogres, tried issuing target orders just before, just after, and a second after the target died, and even tried hacking the Ogres to have a10s RoF to see if that'd help. In all cases they're working as advertised (focus fire and aggressive).

Obviously this problem is still happening in the wild, but it doesn't seem to be reproducing on our internal test servers which makes it somewhat difficult to track down. I'll try and give it another poke later in the week and see if I can find anything more, but right now I don't have a whole lot to go on :(

One thing is important though. IT HAS TO BE ON FIXED WINDOW MODE. Both clients.

Try the following:

Have two clients open. Set both to "Fixed window" mode and your native screen resolution (so that they take the full screen).

Another idea for helping track this down... isn't this exactly the type of situation that a structured (or mass) test on singularity might help? I.E. get a bunch of folks together with devs watching and debugging reproducing the error?

I've just lost a drone which went rogue. I tried calling it back but it refused to do anything other than stand Idle.

This happened at the same time, when the distances on my Overview were horrbly wrong and were puting up random values.

The overview in this case said that the enemy npc were chasing me (I was trying to kite them in a drake) at about 60kms and then they suddenly rubber-banded to 200km+. At the same time I was unable to control the drone even though commands were being sent to it.

Just spent an hour poking at this and totally failing to get a reproduction for drones switching targets. Tried with Hammerheads, Gardes and Ogres, tried issuing target orders just before, just after, and a second after the target died, and even tried hacking the Ogres to have a10s RoF to see if that'd help. In all cases they're working as advertised (focus fire and aggressive).

Obviously this problem is still happening in the wild, but it doesn't seem to be reproducing on our internal test servers which makes it somewhat difficult to track down. I'll try and give it another poke later in the week and see if I can find anything more, but right now I don't have a whole lot to go on :(

Just spent an hour poking at this and totally failing to get a reproduction for drones switching targets. Tried with Hammerheads, Gardes and Ogres, tried issuing target orders just before, just after, and a second after the target died, and even tried hacking the Ogres to have a10s RoF to see if that'd help. In all cases they're working as advertised (focus fire and aggressive).

Obviously this problem is still happening in the wild, but it doesn't seem to be reproducing on our internal test servers which makes it somewhat difficult to track down. I'll try and give it another poke later in the week and see if I can find anything more, but right now I don't have a whole lot to go on :(

Message to CCP Greyscale

I use an AC Fit Myrm w/ HH II drones, chain runnin L3 for faction/corp standing increases.

Drone settings as follows: Focus Fire = True; Agressive = True

The lack of focus fire is tied to issue of the drone choosing a target other than the instructed target. Setup for reproduction is this:

w/ multiple hostiles on the field at the same or mixed ranges
1. Launch Drones send after target (mix HH II and Warrior II)
2. Let drones choose next target
3. After several targets instruct drones to engage a specified target **problem begins here**
3.1 - due to flight times and lock/aquire cycle times (happens more often if you mix drone types (HH II and warrior II works well for this bug), the warriors will often aquire and go after a target on their own, the HH with longer lock/aquire cycle will go after the target you've given them.
Notes on 3.1: The lack of focus fire appears to be a result of the issue of target acquisition. Because the warriors are acquiring their targets faster they tend to go after the target they choose where as the HH go after the target i designate. THis causes a split in focus fire. The focus fire issue is a result of the conflicting target designations. After they are split, they tend to take several target changes to re-converge on a single target, as the targets tend to die at different intervals.

"But enough talk from me. We all know that much quoted phrase, GÇ£ItGÇÖs not what you say, itGÇÖs what you do,GÇ¥ that will make the difference here. From now on, CCP will focus on doing what we say and saying what we do. That is the path to restoring trust and moving forward." -Hilmar

Show us that these are not just words.

1. Explain why CCP chose to break drones. What functionality did we gain for what we lost?
2. Examine the drone-breaking code added with Incarna and revert it back to the less broken code before Incarna.
3. At the very least, take the time to read this thread, the threads from the old forums and the bug reports and don't ask us to re-type information already given.
4. Post something. The lack of communication on this issue is unacceptable.

Just spent an hour poking at this and totally failing to get a reproduction for drones switching targets. Tried with Hammerheads, Gardes and Ogres, tried issuing target orders just before, just after, and a second after the target died, and even tried hacking the Ogres to have a10s RoF to see if that'd help. In all cases they're working as advertised (focus fire and aggressive).

Obviously this problem is still happening in the wild, but it doesn't seem to be reproducing on our internal test servers which makes it somewhat difficult to track down. I'll try and give it another poke later in the week and see if I can find anything more, but right now I don't have a whole lot to go on :(

Still alive over there Greyscale?

I am going to look into this further today, I will update this thread with more information as soon as I have it.

Pls watch the fraps and read whole thread all you need to know is in here, you just gotta do the hard bit and try fix it......

I have done already :) We are working on this and I will keep you updated

Cant help but notice the silence....

I suspect both Greyscale and Affinity have "forgotten" ( read ignored ) to actually bother trying to find out :P
Like doing WiS stuff instead...

I am on it... please just understand we have been through a very difficult time.

Team BFF are working on defects for these issues, they are *not* by design and we are investigating the causes.

It might be that the player gives a command to the drones before the drones themselves can realize what just happened, and then their AI kicks in. As if the player gives a new command to the drone before the drone can check to see if its previous target is dead.

@CCP Greyscale without knowing the code (obviously): this all sounds like a concurrency issue where the "receive player order" action isn't processed for all drones in a critical section. A race condition between game mechanics (agress next target) and the player action.

thats a much better way of describing:

:)

I am on it... please just understand we have been through a very difficult time.

Team BFF are working on defects for these issues, they are *not* by design and we are investigating the causes.

I am on it... please just understand we have been through a very difficult time.

Team BFF are working on defects for these issues, they are *not* by design and we are investigating the causes.

Look, I've used drone ships in lvl4s for a long time, and yes they are buggy and temperamental, but the issue is fairly minor if u assign your engage drones to a hotkey. Spam that about 100 times and they'll follow your commands. The only drones this wont work for is mining drones.

Vaako... lets give them little slack now... If drone fix is in the production pipeline now the goal has been reached. The assembly line is long and got many steps before final product hits tranq. If fix comes before xmas, they've done very decent work.

When you know that something is being done, the waiting isn't that bad.

Not exactly. Were it merely a "race", the player action would supercede the game mechanics. As it is, if the player action is made before the game action, it will get ignored.

So basically if you want it to work without a hitch, you need to allow the game mechanics to win the race because you can never win it yourself.

I'll give it some slack once they confirm they have located the issue and will attempt a fix.
As it is atm we know Greyscale attempted once and failed and then nothing...
I am not saying I want a fix right this minute ( which I ofc want :D :D :D ) but I want to see they are trying even if it is "I tested this for 5min today and found nothing", it would show they are doing something other then just sitting there. ( which ofc they can do regardless as we cant confirm it either way :P )

Greyscale is on my team :) We are working on it. The reason for his delayed communication, as he said above, was a conference in a different country. I am currently testing mining drones thoroughly and working with Greyscale and Frellicus to determine what is causing this. I cannot start giving day-by-day diaries of my exact testing but I will, as previously stated, keep this thread updated and keep checking it :)

oh wait, was that a confirmation that you actually encountered the issues?

Yes :)

Yes :)

Yes :)

When you actually discover the problem could you gives us a run down as to why it was happening? I am just curious if my observations are correct or if I was just out in left field somewhere.

Thanks!

I have faith that CCP Affinity is on the case and will solve the issue.

I want to thank everyone who read and posted in this thread and the threads on the old forums. I am especially greatful for the videos and those who took the time to spell out how to reproduce the error and filed bug reports.

As I understand it Affinity has confirmed this is not a stealth nerf functioning as intended and has been reproduced on CCP's end to confirm.

IMO Affinity is delivering on the promise in Hilmar's recent letter.

Thank you all.

Build 304168 to 306979 addresses Patch notes for Incarna 1.1.3

To be released Tuesday, October 25, 2011.

Sadly, the patch notes do not mention drones at all.

http://www.eveonline.com/updates/patchnotes.asp

Sadly, the patch notes do not mention drones at all.

http://www.eveonline.com/updates/patchnotes.asp

I fully expect it to be ignored/forgotten... mostly because I have yet to see CCP deliver on their words... ( and ofc that I am a little negative in general :D, better to expect nothing and be happy when you get something then expect something and never get it )
Its 3 days since CCP's confirmation about these issues and not a single word from Affinity, Greyscale or Frellicus.

And even if they resolv the issues that patch itself will most likely not be released until something else is.
Despite that these fixes should have been out long ago :P
Its "nice" to see them fix the overview issues so fast when the drones issues are just as big but way WAY down the list :P

Sadly, the patch notes do not mention drones at all.

http://www.eveonline.com/updates/patchnotes.asp

I fully expect it to be ignored/forgotten... mostly because I have yet to see CCP deliver on their words... ( and ofc that I am a little negative in general :D, better to expect nothing and be happy when you get something then expect something and never get it )
Its 3 days since CCP's confirmation about these issues and not a single word from Affinity, Greyscale or Frellicus.

And even if they resolv the issues that patch itself will most likely not be released until something else is.
Despite that these fixes should have been out long ago :P
Its "nice" to see them fix the overview issues so fast when the drones issues are just as big but way WAY down the list :P

They are just humans, not robots. 3 days is nothing. I would start getting worried after 3 months. Relax and chill already.

We (BFF) are working on this and we are hoping to get the fix out in the winter expansion. Please note, we cannot 100% guarantee this, but it is our current goal. I will keep you updated when there's any progress or when new discoveries are made.

Come on guys, be nice to Affinity. You're making her bitter and angry! She's just trying to help

Come on guys, be nice to Affinity. You're making her bitter and angry! She's just trying to help

If drones aren't fixed in time for the Winter update then you clearly don't have your priorities in order. Drones have been broke for far too long. They are one of, if not THE most used weapon system in the game and they've been broke for going on 5 months now, heck, it's took you that long to acknowledge there was a problem. The least you can do now that you have recreated and identified the problem is make it one of your top priorities to fix it.

You may aswell hold production on those EWAR drones until this issue is fixed at least. Gonna be a waste of friggin time otherwise!

We are still working on this :) We have uncovered an issue, as I mentioned, it is not by design.. but it's going to take more than 3 days to fix and deploy this :)

Come on guys, be nice to Affinity. You're making her bitter and angry! She's just trying to help

This sounds like a man that tries to preserve the office peace.

My role is simply to serve. Now, let us all be nice to Affinity. She's got a tough job to get done! Without these lovely QA people we'd find ourselves in a bit of a pickle.

I'm glad you have been on this for three days. I'll take your coment as confirmation that CCP Greyscale did nothing what-so-ever as we suspected. (oh he was at a conference for one week out of the 15 weeks that drones have been broken)

"we" being BFF and Greyscale is on BFF and worked on this with me.

"we" being BFF and Greyscale is on BFF and worked on this with me.

Easy tiger... :D :D
I wish you all the best but, as said before, try looking at if from our point of view...
Yes its great you have started but this issue needs to get on double time. its one of the core weapon systems in EVE and its broken... ( has been for a huge amount of time )

Here is me hoping you 3 are spending 100% of your time on this :D :D :D :D

No need to repeat yourself so much. We all get that this is important for you.


Let's show some love for team BFF and CCP Affinity instead:

Great 2 way communication going on here +1

Great incremental information +1

CCP Affinity +1

Keep up the good work guys and fingers crossed to get this into the winter expansion.

*hugs CCP Affinity and applies some duct tape around her ears and eyes to prevent further brain damage this thread would cause*
It is better this way... You may look bit funny but you thank me later. Try not to take those off before Xmas. Everything will be all right .)

Wow that was fast!
Looks like you may have done that a few times before..

Just spent an hour poking at this and totally failing to get a reproduction for drones switching targets. Tried with Hammerheads, Gardes and Ogres, tried issuing target orders just before, just after, and a second after the target died, and even tried hacking the Ogres to have a10s RoF to see if that'd help. In all cases they're working as advertised (focus fire and aggressive).

Obviously this problem is still happening in the wild, but it doesn't seem to be reproducing on our internal test servers which makes it somewhat difficult to track down. I'll try and give it another poke later in the week and see if I can find anything more, but right now I don't have a whole lot to go on :(

bumpie

He is going a little overboard but I kind of understand his frustrations, these bugs have been around in less severe form for years even before I started playing back in late 2009. At least this thread is getting some dev love unlike the bugs reported in the issues threads that have been reported over and over again without even a single dev response. Bugs such as bookmarks in solar system map not showing their range in AU from your ship, being occluded by beacons and other icons and probes losing their labels. There are so many bugs that get reported in the issues thread and seemingly ignored that I sometimes want to rant and cuss at people who are just doing their jobs, so while he is out of line it's understandable.

Also, Affinity only has 30 something likes. THIS MUST BE FIXED!!!!

Everyone like all of her posts :-D

Also, Affinity only has 30 something likes. THIS MUST BE FIXED!!!!

Everyone like all of her posts :-D

Liking is so yesterday... spread some love :)

I think I has to do with firing cycles, but you have to get your drone set firing on different rotations in the case of sentries. Once you do if you kill a target with gun, 3 drones will swap to the assigned target and the other two will shoot at whatever they want (usually something you don't want them shooting at) In race cases I've had the ENTIRE set actually change to the desired target and switch off to whatever random thing got on their to-do list.

Any updates today Affinity?

I've been looking into this for the past few days. Thanks to a great video from Grey Stormshadow, I've managed to get a simple reliable repro for the case where mining drones go idle shortly after a roid pops and they are assigned to a new one. I'm working through a couple of possible solutions, and also trying to figure out how this applies to combat drones.

Just started do some missions again after a few weeks break, and I notice the drones are still acting weird.
First thing I've noticed is that they still can't seem to stick to one target even though they are set to Focus Fire.

You guys still want screenshots and bugreports about this drone stuff?

SOONGäó :(

You need more likes too for your work pushing this(and now its not ALWAYS in my active thread list )

Fear not - When they go on SISI I will let you all know so you can help me test the fixes ;)

Fear not - When they go on SISI I will let you all know so you can help me test the fixes ;)

Off topic: At default picture size, if your portrait would have red hair, it'll be A.L.I.A.S' portrait.
Just noticed.