Originally by: Mnengli Noiliffe

---

Edited by: Mnengli Noiliffe on 12/02/2006 17:36:25
Edited by: Mnengli Noiliffe on 12/02/2006 11:17:38
I managed to do pretty "laboratorial" reproduction steps, using the latest SiSi drones.
I have filed the bug report which is named as follows:
"Drones Speed Bug with log, screenshots and simple reproduction steps"
Client Build is RMR/3881 (which really is 2.10.3881).

Here are the reproduction steps:
Two players are acting. First player, P2, and Second player, P2.

Reproduction steps (actual bug report contains more specific info):
----
P1 used a Dominix and 5 Ogre I drones.
P2 used a shuttle with some bookmarks in cargo hold.
P1 stood still with 0 velocity.
P2 orbited P1 at 25 km, its velocity was about 220m/s.
P2 jettisoned a bookmark.
P1 locked a jetcan P2 jettisoned, then he locked P2, and released 5 Ogre I drones.
When P2 was pretty far from his jetcan, P1 ordered his 5 Ogres to attack the jetcan.
After the jetcan was destroyed, P1 ordered his drones to engage P2's shuttle.
After this command, 3 of Ogres did switch their MWDs on, but 2 others didn't, approaching their shuttle target at their orbiting velocity, which is about 220m/s.

This is clearly visible on the screenshots - while 3 first drones has already reached and destroyed their target, 2 other drones, who traveled much slower, were still several kilometers away from where their target was recently.
----

I don't think that these steps will always work to reproduce a bug, but they did at least once for me, and the logs are provided so I hope this will be enough to catch the sneaky bastard..

---

Originally by: lickspittle

---

While I appreciate the effort, please be aware that posting 'bug report' posts to this thread and not submitting them through the bug reporting system is nowhere near as effective.

The reason I say this is that the work I do is based upon the defects assigned to me, in the order that Oveur gives them priority. As it is, because no bug reports have made it to me as defects, these problems do not even register on my radar as work approved to be done.

So, please, submit your reports as bug reports through the system provided for it.

---

Originally by: Tribunal

---

step 2

At this point my drones are idel (very important fact) and orbiting my ship so I order them to kill the target 15km away.

step 3

Before the drones reach the target 15km away I order them to attack the target 35km away, thus changing who they are attacking.

step 4

I have to sit here and watch as a majority of my drones are now stuck in orbit speed. The only way to fix the issue is to either order them back to my ship and wait for them to go idel, or allow them to kill something and they pick out their own target.

---

Originally by: BH Runner

---

Your have appeared to have filed a petition, two in fact, bug reports are to be filed under the bug reporting section of this website, to be found HERE!

Thanks.

---

Originally by: lickspittle

---

The problem you describe above is pretty much identical to what I describe in my newly added edit to Runner's first post to this thread.

So, I believe this is now fixed internally. However, it is unlikely to make it out in the Blood update, because it is too late for it now.

---

Originally by: lickspittle

---

Originally by: Kage Getsu

---

"3. Drone speed
Specific instances of exactly when this happens with logfiles required."

All the time? I don't know what logs are needed to show the messed up speed that happens every time drones select a new target. It's so easy to reproduce and happens without fail.

---

There are too many posts in this thread which make claims like this, which as far as I can tell, are just wild speculation. Unfortunately the bug reports on this and their reproducibility cases have proved equally unhelpful.

If a client-side log were provided with a detailed, clearly written description of exactly what happened and what the player chose to do, and that at given points the drones exhibited the problematic behaviour -- it would be ideal for fixing this bug.

I had a defect with a reproducibility case which pretty much matched the descriptions of the problem given in this thread, the problem is that, looking at the server-side logs, some of the drones used their MWD and the others were already too close to bother. This is the reason it has not been fixed, because I cannot reproduce it, and a better reason has not come along to make it worth my time to look into it again.

If this is to be fixed, I need either of these..

The king of well written reproducibility cases -- one so good that I can just look at it and see that it is believable enough to justify another look, which should include:

1. Proper english sentences, well spelt. Nothing says or has shown to prove defect worthlessness and ambiguity like bad writing.
2. Exact type names. For the ship you are flying, the types of drones that you are using.
3. The type names of the targets, which are likely to be NPCs (or if you can contrive a situation with static objects that don't attack back and do not move, even better)
4. A description of each action taken by the player including the distances of the drones at each step from their targets.
5. At each point in the action description where the drones did not use their MWD, note it and explain how you could tell and why you thought they should.

Or, a client-side log accompanied by a clear description of the actions taken by the player with the drones, including notes on when the drones didn't do what they were supposed to when they should have and why you think you are justified in believing this.

---

Originally by: Kage Getsu

---

I was told that the developers play this game. I don't think that is true. And if they do, they do not use drones. Maybe if you use them you'll have all the logs you need.

Edit: But here's a bug report about my particular problem, which is similar to what my friends have.

Ship: Raven
Drones: Hobgoblin I x5
Each action taken to reproduce problem:

Lock on an NPC frigate.
Order drones to attack target.
Drones fly to the target at MWD speed and attack it.
Target is destroyed.
Immediately order drones to attack another NPC frigate.
Drones really slowly fly over to the next target, no matter what the range is. I guess they're unionized or something, because they think they need to take a break after every job.

The above steps reproduce the problem for me every time. Every time. Out of hundreds of missions I've done. I thought that's how they're supposed to be used, but if you know of a better way to order them that doesn't cause them to break, I would appreciate it.

I can fix the problem by ordering them to return and orbit, then ordering them to attack after they start orbiting me again. That also works every time. I'd prefer it if I didn't have to take that step.

---

Originally by: Linia

---

You now have gotten the 2 most ebil drone mistakes fixed and that is really gonna help the droneusers play normally again.

---

Quote:

---

Thank you for showing me that CCP really do care about drone users

---

Originally by: Kage Getsu

---

Ship: Raven
Drones: Hobgoblin I x5
Each action taken to reproduce problem:

Lock on an NPC frigate.
Order drones to attack target.
Drones fly to the target at MWD speed and attack it.
Target is destroyed.
Immediately order drones to attack another NPC frigate.
Drones really slowly fly over to the next target, no matter what the range is. I guess they're unionized or something, because they think they need to take a break after every job.

The above steps reproduce the problem for me every time. Every time. Out of hundreds of missions I've done. I thought that's how they're supposed to be used, but if you know of a better way to order them that doesn't cause them to break, I would appreciate it.

I can fix the problem by ordering them to return and orbit, then ordering them to attack after they start orbiting me again. That also works every time. I'd prefer it if I didn't have to take that step.

---

Originally by: Kage Getsu

---

Edit: But here's a bug report about my particular problem, which is similar to what my friends have.

---

Originally by: lickspittle

---

Originally by: Kage Getsu

---

Edit: But here's a bug report about my particular problem, which is similar to what my friends have.

---

This sounds pretty much like the same problem that the last fix I posted about addressed. In fact, the fix has gone out to Singularity since I made that post.

Feel free to log on there and confirm that this particular bug is fixed to your satisfaction.

---

Originally by: Mnengli Noiliffe

---

It might be fixed on test, I don't remember this problem when playing there last time.
But maybe I was lucky.

Oh and do people even read what they are replying to I wonder? On teh 1st page of this topic there is the list of known problems. Return to drone bay is among the KNOWN ISSUES which means that it is being fixed. Why post it 10 more times...

---

Originally by: Mnengli Noiliffe

---

DNC doesn't add to orbit speed, but light drones are bugged - they don't switch off their mwd when starting orbiting. That is, sometimes they orbit at mwd speed.

Yes this has most chances to occur with drone nav. comp. So I wanted to reproduce. DNCs are not seeded. I flown to buy them or at least their bpos. On my way I stumbled across the system that is impossible to cross because it loads for 15 minutes without visible progress. OK will go other way. Bah now I am stuck with another system, now I can't even enter game, with usual stuck symptoms .. enough bughunting for today I guess.

---