Pages: [1] :: one page |
|
Author |
Thread Statistics | Show CCP posts - 3 post(s) |
Pteranodon
|
Posted - 2008.10.09 12:20:00 -
[1]
You have a Domi with 25 Drones
You have been somewhat careless & some got armor damage to your babies
Why can't we see which ones are damaged when they are docked in the drone bay.
It makes it so much harder to be selective with regard to which drone to deploy next-is it damaged or not-who can tell until you relaunch.
If you can see the damage when they fly surely it is not too much trouble to see the damage when they are docked in the drone bay?-or is it. What about a filter that automatically moves damaged drones to a damaged category when they dock.
If you use drones a lot this little change could be helpful in not launching a badly damaged drone.
|
taekwandokid
hirr Morsus Mihi
|
Posted - 2008.10.09 12:27:00 -
[2]
Features and Ideas Discussion forum is that way
|
Asuka SoryuLangley
|
Posted - 2008.10.09 12:30:00 -
[3]
Edited by: Asuka SoryuLangley on 09/10/2008 12:30:38 I always think about that, and i always wish that something will be done for drones, they need so many fix. But CCP seems to not care, maybe they don't like drones.
|
Pteranodon
|
Posted - 2008.10.09 12:37:00 -
[4]
Originally by: taekwandokid Features and Ideas Discussion forum is that way
Discuss first-then see if I feel the need to move it that way-Okay by you.......?
|
|
CCP Atropos
C C P
|
Posted - 2008.10.09 12:39:00 -
[5]
Originally by: Pteranodon
Originally by: taekwandokid Features and Ideas Discussion forum is that way
Discuss first-then see if I feel the need to move it that way-Okay by you.......?
No.
|
|
Pteranodon
|
Posted - 2008.10.09 12:49:00 -
[6]
Originally by: CCP Atropos
Originally by: Pteranodon
Originally by: taekwandokid Features and Ideas Discussion forum is that way
Discuss first-then see if I feel the need to move it that way-Okay by you.......?
No.
And....your point is?
|
Alexeph Stoekai
Stoekai Corp
|
Posted - 2008.10.09 12:59:00 -
[7]
Perhaps the CCP person's point is that the thread is now where it should be.
|
Pteranodon
|
Posted - 2008.10.09 13:06:00 -
[8]
Originally by: Alexeph Stoekai Perhaps the CCP person's point is that the thread is now where it should be.
Thanks. I could not have worked that out without your help.
|
Burn Mac
Minmatar The Tuskers
|
Posted - 2008.10.09 14:21:00 -
[9]
i have a special group that is labelled "Damaged Drones" were i move drones that have been damaged so i know which drones to launch if i want a fresh batch.
|
Angel Lightbringer
Caldari Dark Evolution Industries
|
Posted - 2008.10.09 14:28:00 -
[10]
I do have a sickbay group where I put those damaged, but I agree seeing the status as in space would be much better.
I'd even add this to drone description, as stats are ajusted anyway when looking at items you own (skills/fittings etc..)
All the ingredients are already there (stored in DB), needs a recipe! :) -Angel |
|
procurement specialist
|
Posted - 2008.10.09 16:24:00 -
[11]
i restack them in station and then they are grouped until i launch them again. only the 5 in one wing ungrouped can possibly be damaged so it doesn't bother me much.
|
Washell Olivaw
|
Posted - 2008.10.09 19:13:00 -
[12]
Originally by: Angel Lightbringer I'd even add this to drone description, as stats are ajusted anyway when looking at items you own (skills/fittings etc..)
All the ingredients are already there (stored in DB), needs a recipe! :)
But that hasn't worked for drones since launch...
Originally by: Signature Everybody has a photographic memory, some people just don't have film.
|
|
CCP Atropos
C C P
|
Posted - 2008.10.10 01:03:00 -
[13]
Part of the problem that I see with changing this, would be for ships with vast numbers of drones in their cargo bays.
For your Dominix, sure, it might be feasible to send state update information on the 20 drones in your bay, in addition to the state information you're already receiving for the 5 in space but, what if you are in a carrier or mothership, with possibly hundreds of drones in your bay. receiving that many more state updates is not only an extra amount of overhead for your client to deal with, but it's also a large amount of data for the server a small fleet fight in your own drone bay.
Consider a fight with carriers; state information is not only being sent on the drones in space, but every single drone in the bays of all the ships on the grid must also be considered by the server and the data sent to the respective owners. Thats a collosal extra amount of overhead. It's something that we can certainly add to the drawing board, but you have to consider the performance implications of this little fix for your problem, in the scope of the larger game
|
|
|
CCP Atropos
C C P
|
Posted - 2008.10.10 01:06:00 -
[14]
Additionally, just so you understand the difference, the reason why drones in space have their health displayed, is because it's data that everyone involved needs. We can't predict what targets people will want to lock next, so the state data pertaining to all relevant targets must be relayed. The opposite is true for the drones in your bay; you're the only one concerned with their state.
|
|
Del Narveux
Dukes of Hazard
|
Posted - 2008.10.10 01:11:00 -
[15]
This is completely random, but somewhat related...perhaps drones in the bay could slowly recharge hull/armor? This I think would address the spirit of OP's idea as well as cutting down on one of the big pain-in-the-ass issues with drones. |
Strill
|
Posted - 2008.10.10 04:39:00 -
[16]
Originally by: CCP Atropos Part of the problem that I see with changing this, would be for ships with vast numbers of drones in their cargo bays.
For your Dominix, sure, it might be feasible to send state update information on the 20 drones in your bay, in addition to the state information you're already receiving for the 5 in space but, what if you are in a carrier or mothership, with possibly hundreds of drones in your bay. receiving that many more state updates is not only an extra amount of overhead for your client to deal with, but it's also a large amount of data for the server a small fleet fight in your own drone bay.
Consider a fight with carriers; state information is not only being sent on the drones in space, but every single drone in the bays of all the ships on the grid must also be considered by the server and the data sent to the respective owners. Thats a collosal extra amount of overhead. It's something that we can certainly add to the drawing board, but you have to consider the performance implications of this little fix for your problem, in the scope of the larger game
Why can't the client just get the information once and keep track of it on its own? |
Elisa Day
Shade.
|
Posted - 2008.10.10 05:27:00 -
[17]
Much like the issue of BPO/BPC coloring, this can be solved with client-side caching:
All drones in your bay would look like they do right now, except for when they have been launched (their damage status is known), and scooped. Their damage status can't possibly change while in the bay, so just having the client remember the health values doesn't seem an insurmountable problem.
|
Nnamuachs
Caldari Kiith Paktu Nex Eternus
|
Posted - 2008.10.10 06:02:00 -
[18]
Originally by: Elisa Day Much like the issue of BPO/BPC coloring, this can be solved with client-side caching:
All drones in your bay would look like they do right now, except for when they have been launched (their damage status is known), and scooped. Their damage status can't possibly change while in the bay, so just having the client remember the health values doesn't seem an insurmountable problem.
except their health status "does" change in the bay, they recharge their shields at the very least. |
Abrazzar
|
Posted - 2008.10.10 10:09:00 -
[19]
Originally by: Nnamuachs
Originally by: Elisa Day Much like the issue of BPO/BPC coloring, this can be solved with client-side caching:
All drones in your bay would look like they do right now, except for when they have been launched (their damage status is known), and scooped. Their damage status can't possibly change while in the bay, so just having the client remember the health values doesn't seem an insurmountable problem.
except their health status "does" change in the bay, they recharge their shields at the very least.
I think the issue is not the recharging of the shield but the real time display of it. The server doesn't need to send information to the client in order to count up the shield on the drone. It's all server side. Now if it had to send this information every few ticks to your client for display, you'd get a lot of lag without a real benefit.
What might work though would be a indicator icon on the drone for damaged armor and hull that gets put on it when docking up in damaged condition. At least then you'll know which of your drones are mint and whether you need some repairs in station or on site. |
Nova Fox
Gallente Novafox Shipyards
|
Posted - 2008.10.10 16:08:00 -
[20]
they just need to add a slow working repair bay for drones
Pre Order your Sisters of Eve ship today!!! |
|
Elisa Day
Shade.
|
Posted - 2008.10.12 17:03:00 -
[21]
Edited by: Elisa Day on 12/10/2008 17:03:34
Originally by: Abrazzar
Originally by: Nnamuachs
Originally by: Elisa Day Much like the issue of BPO/BPC coloring, this can be solved with client-side caching:
All drones in your bay would look like they do right now, except for when they have been launched (their damage status is known), and scooped. Their damage status can't possibly change while in the bay, so just having the client remember the health values doesn't seem an insurmountable problem.
except their health status "does" change in the bay, they recharge their shields at the very least.
I think the issue is not the recharging of the shield but the real time display of it. The server doesn't need to send information to the client in order to count up the shield on the drone. It's all server side. Now if it had to send this information every few ticks to your client for display, you'd get a lot of lag without a real benefit.
What might work though would be a indicator icon on the drone for damaged armor and hull that gets put on it when docking up in damaged condition. At least then you'll know which of your drones are mint and whether you need some repairs in station or on site.
Shield recharge follows a completely non-random formula, the client can just count that as it goes along. Or not, shield damage isn't the damage level we're interested in anyways.
|
Kel Nissa
|
Posted - 2008.10.12 20:42:00 -
[22]
idea 1:
whenever a drone docks, the client caches the last known state for armor and hull the pilot is able to see this armor/hull value inside his bay with the normal bar indicator shield will be unknown, so only 2 indicators instead of 3
idea 2: mark several drones - rightclick - "state info" and voila, the client displays the latest known drone state which is polled after clicking state info
so or so, this problem can be solved its just a question of: is ccp interested into solving it
the "to huge server load" issue is not the problem
|
Jach Wong
|
Posted - 2008.10.13 21:13:00 -
[23]
Originally by: CCP Atropos ...possibly hundreds of drones in your bay. receiving that many more state updates is not only an extra amount of overhead for your client to deal with, but it's also a large amount of data for the server a small fleet fight in your own drone bay.
Would you consider 1000 drones to be more or less the upper limit of a reasonable number of drones in a mothership?
If so, 1000 drones * 3 floats per drone * 4 bytes per float is 12KB of data. And while that might be a hefty load for each update packet, not every drone needs to be updated with every packet (especially considering that at current their health does not change once they are docked).
Thus, you could implement a system whereby 5 drones in the bay are updated every packet, and cycle over the 1000 drones until all of them have had their status reported. After the initial reports, the only updates needed from the server are those for drones being recovered from space (or, if drone repair modules are in the future added, when such a module completes a cycle).
This is a relatively simple solution with a fixed cost to servers. "This is not the boot you're looking for." |
Ashley Thomas
Kiith Paktu Nex Eternus
|
Posted - 2008.10.13 22:42:00 -
[24]
actually, as nnam pointed out, drones slowly recover shields while in bay
|
Daevonar
Minmatar
|
Posted - 2008.10.14 12:20:00 -
[25]
Originally by: Strill
Why can't the client just get the information once and keep track of it on its own?
In fact the client must already have this data before the drone docks, so can't the status of the drone just show this.
Also, if you omit showing the shield data then the data doesn't need tracking and updating until you either repair a drone, or launch it (at which point it has to be updated and tracked anyway)... after all nothing happens to your drones i nthe bay... and its mainly armour and hull that we are concerned with here anyway. D.
|
Jach Wong
|
Posted - 2008.10.15 15:15:00 -
[26]
bump "This is not the boot you're looking for." |
Doxs Roxs
Free Collective Sons of Tangra
|
Posted - 2008.10.15 15:36:00 -
[27]
Originally by: CCP Atropos Part of the problem that I see with changing this, would be for ships with vast numbers of drones in their cargo bays.
For your Dominix, sure, it might be feasible to send state update information on the 20 drones in your bay, in addition to the state information you're already receiving for the 5 in space but, what if you are in a carrier or mothership, with possibly hundreds of drones in your bay. receiving that many more state updates is not only an extra amount of overhead for your client to deal with, but it's also a large amount of data for the server a small fleet fight in your own drone bay.
Consider a fight with carriers; state information is not only being sent on the drones in space, but every single drone in the bays of all the ships on the grid must also be considered by the server and the data sent to the respective owners. Thats a collosal extra amount of overhead. It's something that we can certainly add to the drawing board, but you have to consider the performance implications of this little fix for your problem, in the scope of the larger game
I got to agree, i dont see the problem...
Players are interested in armor and hull status, that wont change once drones are docked, why not let the client show it?
No need to send any status updates, like others have said before me, have the client cache it. Im sure each drone has a unique ID anyway, and Im equally sure the client knows the status of a drone in space since thats sent via status updates.
As soon as the drone docks the client can thus show the last known state for that drones armor and hull. A very useful clientside fix that wont affect network traffic at all.
Regards /Doxs After 9 months of being a "!" face, I now discover that Im butt ugly instead... |
|
|
|
Pages: [1] :: one page |
First page | Previous page | Next page | Last page |