EVE Search - Drone Group Bug

All Channels

Test Server Feedback

Drone Group Bug

» Click here to find additional results for this topic using Google

Monitor this thread via RSS [?]

Pages: [1] 2 :: one page
Author	Thread Statistics \| Show CCP posts - 9 post(s)
Rawthorm Gallente The Establishment Establishment	Posted - 2006.12.23 16:28:00 - [1] Ok for a long time now there has been a problem where drone groupings dont stick. This is a huge problem for any ship that uses drones and fighters. It seems that the client only saves your drone groupings when you dock or eject but not when you log off in space. This is obviously a HUGE problem for a mothership so is there any plans to actualy have the client do the breathtaking task of saving your drone groupings when you log off?
Tradesman Mcgee Caldari Derek Knows Us	Posted - 2007.10.08 12:39:00 - [2] bump Fix this please? Too much effort? -------------------------- Research & Trade
Eleana Tomelac Gallente	Posted - 2007.10.08 12:44:00 - [3] necro, necro, necro, bad bad bad... Drones are going to be reviewed... they know of the issue, we can just hope it's on the list, but wasn't that supposed to be fixed? -- Pocket drone carriers (tm) enthousiast ! The Vexor Navy Issue is much more fun than the Myrmidon !
Ina Mina	Posted - 2007.10.08 13:30:00 - [4] Its not bad to necro if the issue is still not fixed..and this one sure as heck isnt.

CCP Casqade	Posted - 2007.10.08 14:04:00 - [5] The forum is still not the right place to post bug reports. Please use the bug report system. 1. Go here: http://oldforums.eveonline.com/?a=topic&threadID=585921 2. Go here: https://bugs.eve-online.com/newbugreport.asp That is the only way you can find out if the bug has been fixed on our internal servers(You'll get a response saying so or "Unable to reproduce"), if it is currently being fixed (Your bug report has been attached to an existing defect), or if a defect has been created from your bug report.

Tonto Auri	Posted - 2007.10.08 14:43:00 - [6] I have about 6 reports marked as fixed/already fixed but only two of 'em actually fixed either on TQ or SiSi. What happened with bugtracking? -- Thanks CCP for cu<end of sig>
Solar Shard	Posted - 2007.10.08 16:54:00 - [7] Originally by: Tonto Auri I have about 6 reports marked as fixed/already fixed but only two of 'em actually fixed either on TQ or SiSi. What happened with bugtracking? The forum is still not the right place to post bug reports about the bug reporting system. Please use the bug report system. 1. Go here: http://oldforums.eveonline.com/?a=topic&threadID=585921 2. Go here: https://bugs.eve-online.com/newbugreport.asp That is the only way you can find out if the bug has been fixed on our internal servers(You'll get a response saying so or "Unable to reproduce"), if it is currently being fixed (Your bug report has been attached to an existing defect), or if a defect has been created from your bug report.
Tonto Auri	Posted - 2007.10.08 16:58:00 - [8] You'll get one and only one of following replies to any given bugreport: 1. Unable to reoproduce 2. Not enough information 3. Already fixed on our internal mysthical servers (but will never came to live server) 4. It's a enchancement, not a bugreport, You should discuss it with players on forum. WTF is that last? Are players writing EVE??? -- Thanks CCP for cu<end of sig>

CCP Casqade	Posted - 2007.10.08 18:13:00 - [9] Developers such as myself are frequently reading the forum, especially constructive threads. The Bug report system is... a bug report system and is connected to a Defect system, not a Feature Request system. This is the reason why suggestions and ideas should not go into Bug Reports. The current Feature request and Ideas system is the "Features and Ideas Discussion" forum on www.eve-online.com where you "Share your game-related features and ideas with the Developers and the rest of the community." The Bug Reports that have been returned to you with "Already fixed on our internal test servers" mean that the problem will hopefully fixed be on Tranquility with next major expansion.

Tonto Auri	Posted - 2007.10.09 17:10:00 - [10] Well, I'll post a bugreport now. Let's see what happened to it. -- Thanks CCP for cu<end of sig>

CCP Tuxford	Posted - 2007.10.09 17:50:00 - [11] We also have a bug report about the bug report system being broken. Ok not really but I have a bug report about groups not being persisted or something of that kind. I'll look into. _______________

Tonto Auri	Posted - 2007.10.09 17:55:00 - [12] At least bug reporting system told me that latest release is 2.2.0... -- Thanks CCP for cu<end of sig>

CCP Casqade	Posted - 2007.10.09 18:08:00 - [13] To bring this back to what this thread is about. 02/10/2007 - There was a Bug report sent about this issue. 03/10/2007 - The Bug report was confirmed by a Bug Hunter and made into a Defect 05/10/2007 - The Defect ended up at QA and my desk 09/10/2007 - The Defect was assigned to Tuxford. This thread was posted: 23/12/2006 If this is not proof enough of that the forum is not the correct place to send bug reports, I don't know what is.

Tonto Auri	Posted - 2007.10.09 18:17:00 - [14] Can You say same about This, this, this, this reports? It all still not fixed. -- Thanks CCP for cu<end of sig>

CCP Atropos	Posted - 2007.10.09 20:12:00 - [15] Some of the main problems with the Bug Reports are the lack of reproduction steps, lack of sufficient substantiating evidence, or just plain invalidity. To expand upon these; reproduction steps are immensely important to the Bug Report. We need them to show that a bug is not just a fluke, or a one off, and that it can be reproduced and studied upon demand. Many Bug Reports that are submitted simply lack this information. A screen shot of the effect a bug has, is helpful, and in many cases a big help, but without exact and explicit steps to reproduce a bug, it can often be a painful, and more importantly time consuming process to track down a bug. In support of the Bug Report is the production of a log, or crash dump. These can be used to ascertain the state the client was in and what was being conducted by the client, at the time a particular problem was occurred. Whilst I understand that not everyone runs the LogServer all the time, when reproducing a bug, it is one of the most important pieces of information that you can provide us with. As a result of this, many of the Bug Reports we get simply do not contain enough information. Vague descriptions saying that something is broken, do not help to clarify or pinpoint the exact nature or a problem, nor what you were doing at the time the problem appeared. Further to what CCP Casqade said, the Bug Reports are not for feature requests. Any feature requests that we find are more than a hindrance in that both the Bug Hunters and the QA team working with them have to spend time filtering the noise to get to useful and complete Bug Reports. These factors all contribute to the current state of the Bug Reports. Whilst we are working on increasing the communication between the Bug Hunters and those filing the Reports, I can not stress the point enough; a complete Bug Report is ray of sunshine. Having solid reproduction steps and helpful data on hand can speed up the process considerably, since those same logs can be filtered and passed to a programmer to work upon. Hopefully this can clarify why several of your Bug Reports haven't been dealt with. Some simply lack valid information, others are feature requests and thus invalid. Others are lacking enough evidence to pinpoint the exact problem. Please do not be dissuaded from filing your reports; every report is helpful to a certain degree, and even though the report may be marked as "trashed" it is often helpful in alerting us to any particular trends in bug reporting.

Valandril Caldari Resurrection R i s e	Posted - 2007.10.09 21:28:00 - [16] Edited by: Valandril on 09/10/2007 21:32:03 It remind me that i got exacly same problem earlier, i fille 2 bugreports exacly describing it, both got filtered. Then i spend 2 weeks (still w/o my drone groups coz i was living in hostiles space in my carrier) on msging with gm, when we came to awesome conclusion that i knew before - drone groups were not saving in space !!!111oneoenoeneeleven Then i filled another bugreport including the fact that i spoken with gm, and then all of sudden voila 42977Dronebay not saving when logging off in space ! Fixed in: Kali 312007.08.22 16:47:54 My point is, issue is not with system, but with ppl who filter bug reports. Funny also is: 02/10/2007 - There was a Bug report sent about this issue. 03/10/2007 - The Bug report was confirmed by a Bug Hunter and made into a Defect 05/10/2007 - The Defect ended up at QA and my desk 09/10/2007 - The Defect was assigned to Tuxford. While i got confirmed bugreport about this almost 2 months earlier :P Something is seriously broken here :D --- Battlecarriers !
Icome4u Caldari Dark and Light inc. D-L	Posted - 2007.10.10 02:18:00 - [17] Step 1: Spawn a Mothership. Step 2: Fill drone bay with fighters/drones. Step 3: Assign groups to different drones/fighters. Step 4: Log Off. Step 5: Log In. Step 6: Open your drone menu. Step 7: Curse since you have a couple hundred drones/fighters all over the place. Step 8: Fix it. I can make it as a PDF also. Just mail me. /End Sarcasm. ______ Originally by: Vyger If I lose connection while walking around a station will my avatar run off in a random direction and go hide in a corner?
Tokenu	Posted - 2007.10.10 09:04:00 - [18] There's a simple solution to this problem: Make bug reports public, just hide the exploits. You'll be amazed how much detail a group of players working on a bug report can provide.
Tonto Auri	Posted - 2007.10.10 09:39:00 - [19] Originally by: CCP Atropos Some of the main problems with the Bug Reports are the lack of reproduction steps, lack of sufficient substantiating evidence, or just plain invalidity. Well, I know that reproduction steps is important (I'm program developer myself). But how strong brain is required to be unable to reproduce this image? They're unable to jump between two systems? Screenshot made 20 min ago. Have clean cache at both clients startup. -- Thanks CCP for cu<end of sig>

CCP Lingorm	Posted - 2007.10.10 10:28:00 - [20] Edited by: CCP Lingorm on 10/10/2007 10:28:21 We are currently designing a rewrite of our bug reporting system. I have been looking at peoples suggestions about features and the features that QA require to do their jobs. This still needs to be finalized and scheduled, but will be soon in the new year (hopefully). CCP Lingorm CCP Quality Assurance QA Engineering Team Leader

Imhothar Xarodit Minmatar Wolverine Solutions Interstellar Alcohol Conglomerate	Posted - 2007.10.10 13:50:00 - [21] Edited by: Imhothar Xarodit on 10/10/2007 13:50:53 Originally by: Valandril My point is, issue is not with system, but with ppl who filter bug reports. I totally second this. Recently I wrote a bug report about wrong buttons on the forum not doing what they should and I got the answer that I should make an in-game petition because it was considered a support request. I mean... wtf? There was not a single question, or the hint of a support issue and it was closed twice with the same response after modyfing it. Can somebody please explain? The report Id is 44380.]
J'Mkarr Soban Amarr Shadows of the Dead Aftermath Alliance	Posted - 2007.10.10 15:31:00 - [22] Originally by: Tokenu There's a simple solution to this problem: Make bug reports public, just hide the exploits. You'll be amazed how much detail a group of players working on a bug report can provide. Yes. Yes yes yes. Yes. There are clear examples of how this works in the Open Source community - and although this game isn't open source, if I have a vague idea of what's causing a bug, and another players does too, we can work together to give a definitive reproducible occasion. It's in our best interest because it gets fixed quicker, and it saves you money. We both win. ----------------------------- "Oh, we're sorry, you had the 'NakedAmarrChicks' bit flagged in your account somehow." "Wait, why was there even a flag for that to begin with?" "..."
Tonto Auri	Posted - 2007.10.10 22:55:00 - [23] Well, two replies at once. Quote: Thank you for your bugreport - ID:44861 Title: Winsock error in IGB Unfortunately, the reproduction steps in your bugreport did not replicate the problem on our clients. Could you please file another bugreport with an improved set of reproduction steps. Please review this thread for further information on submitting bugreports. Your bugreport has been closed. The BugHunter Team Report ID: 44861 Title: Winsock error in IGB Description: Starting from build 38060 I can¦t use IGB to browse remote sites. Only one protocol which is working is file:/// protocol. For every URL it gives me Page with text "URL Error" and source contains following code: <html><body> <h1>URL Error</h1> <hr> <urlopen error (2, ´winsock error´)> </body></html> At the same time on live client, IGB working just fine. Reproduction Steps: //Filling in the reproduction steps should help us actually finding this bug you just reported. I tried to access a remote site using the IGB in Build 38309 and I didn¦t have any problems doing so. Please resubmit a bug report where you have proper reproduction steps such as which sites you are trying to access. Read this thread (and especially the "Reproduction Steps:" topic: http://oldforums.eveonline.com/?a=topic&threadID=585921 0 file(s) attached to this report. Please update your bug report: https://bugs.eve-online.com/mybugreports.asp?Action=View&ID=44861 Anyone have ideas what I should add to this bugroport? Me, as developer, have enough info from it. 1. It is working just fine on live build. 2. It is broken in 38060 or shortly before it. 3. It is Winsock error indicating problem in netwok layer. 4. Well, we made something wrong and not 100% supported in 38060 or before, let's look what may cause such proble so client is unable to request a page. But BH team is not a programmers, they're kind of robots. They see that there's lack of one field and answering with standard template. But did they rally know WHAT I CAN IN THE LOVE OF GOD ADD TO THAT FIELD? STACKTRACE? -- Thanks CCP for cu<end of sig>
Valandril Caldari Resurrection R i s e	Posted - 2007.10.10 23:03:00 - [24] Maybe you should include fraps movie with nice red-spray poiting at your problem, and prefferably with english voice commentary :D --- Battlecarriers !

CCP Atropos	Posted - 2007.10.10 23:18:00 - [25] Originally by: Tonto Auri Well, two replies at once. Anyone have ideas what I should add to this bugroport? Me, as developer, have enough info from it. 1. It is working just fine on live build. 2. It is broken in 38060 or shortly before it. 3. It is Winsock error indicating problem in netwok layer. 4. Well, we made something wrong and not 100% supported in 38060 or before, let's look what may cause such proble so client is unable to request a page. But BH team is not a programmers, they're kind of robots. They see that there's lack of one field and answering with standard template. But did they rally know WHAT I CAN IN THE LOVE OF GOD ADD TO THAT FIELD? STACKTRACE? As an addendum to your Bug Report it would be helpful for us to know several things in this instance; the site you were connecting to, your network layout (ie: are you on a corporate firewall, have any port forwarding, stuck inside an academic network, etc), whether you have recently started experiencing this, a LogServer of you attempting to connect to the site, as well as say, a screenshot of your ability to connect to that same site in a non EVE related browser. Basically everything that you were doing at the time the error was generated. In these cases, there's often never too much information.

Tonto Auri	Posted - 2007.10.10 23:19:00 - [26] Interesting suggestion... I'll try it with next bugreport. I should have place to practice in spoken English. -- Thanks CCP for cu<end of sig>
Tonto Auri	Posted - 2007.10.10 23:28:00 - [27] Originally by: CCP Atropos As an addendum to your Bug Report it would be helpful for us to know several things in this instance; the site you were connecting to, your network layout (ie: are you on a corporate firewall, have any port forwarding, stuck inside an academic network, etc), whether you have recently started experiencing this, a LogServer of you attempting to connect to the site, as well as say, a screenshot of your ability to connect to that same site in a non EVE related browser. Basically everything that you were doing at the time the error was generated. In these cases, there's often never too much information. 1. Winsock error have nothing to do with network layout. Otherwise it will be something like "unable to connect ot remote host". Beleve me I know. 2. I have this bug after last (looks like major) client update, 38060, as I stated in bugreport. 3. I'll attach logserver but I'm afraid You'll again say that it is "not of any use". But i'll attach. 4. It is EVE news, so I surely can access that site at the same time from live client i.e. In the bottom of this discussion, I'm trying to keep every bugreport as short as possible. It is rather hard to read epic trilogy of trials and errors instead of 4-strings report "What it was, what it now, why it is bad, when it is broken". -- Thanks CCP for cu<end of sig>

CCP Atropos	Posted - 2007.10.11 10:19:00 - [28] Originally by: Tonto Auri I'm trying to keep every bugreport as short as possible. It is rather hard to read epic trilogy of trials and errors instead of 4-strings report "What it was, what it now, why it is bad, when it is broken". But that information is exactly what we need to pinpoint a problem quickly and to see if it's related to any other bug reports. As far as I am aware, you're the only one coming forward and saying that you're suffering from this problem, so it really is important that we get as much information from you as possible. Assuming that we will be able to reproduce it is one of the reasons a lot of Bug Reports are lacking, so please, give us as much information as you can, even if you think it is useless.


CCP Atropos	Posted - 2007.10.11 10:36:00 - [29] I've just looked at the Bug Report you refiled on this same subject and it is exactly what we are looking for, so thank you for refiling it and helping us work towards fixing this problem.

Ina Mina	Posted - 2007.10.11 11:35:00 - [30] Docking your carrier after making the drone groups will force the game to save them, I do not know if another type session change (jumping, joining/leaving gang etc) will work for mothership pilots, worth trying.

Pages: [1] 2 :: one page
First page \| Previous page \| Next page \| Last page

COPYRIGHT NOTICE
EVE Online, the EVE logo, EVE and all associated logos and designs are the intellectual property of CCP hf. All artwork, screenshots, characters, vehicles, storylines, world facts or other recognizable features of the intellectual property relating to these trademarks are likewise the intellectual property of CCP hf. EVE Online and the EVE logo are the registered trademarks of CCP hf. All rights are reserved worldwide. All other trademarks are the property of their respective owners. CCP hf. has granted permission to EVE-Search.com to use EVE Online and all associated logos and designs for promotional and information purposes on its website but does not endorse, and is not in any way affiliated with, EVE-Search.com. CCP is in no way responsible for the content on or functioning of this website, nor can it be liable for any damage arising from the use of this website.