Droid Engineer Archive
Thread: Survey Droid Times
Page 2 of 2
Kellisanth
Thu Jul 01, 2004 11:31 am
#14
/thump
Forgot to post my scores
20 - 50m 50s
67 - 29m 24s
69 - 28m 30s
77 - 25m 11s
79 - 24m 8s
84 - 21m 56s
(What's the formula!?)
I've been pricing them at 1k per charge if under 30min, 500c per charge if it takes more than 30min. *shrugs*
And I've noticed, it willtake from top-level inventory first, and not your bags. I made some tools and they were in top level. When I used the droids, I realized that I made tools that I use in my hotkeys, but they (tools in backpack) didn't disappear. *whew*.
Message Edited by Kellisanth on 07-01-2004 01:55 PM
Message Edited by Kellisanth on 07-01-2004 01:59 PM
Gavvot
Fri Jul 02, 2004 5:13 am
#15
Hum.
Reading this, I think we can generalize the formula to something like this :
3600 - 27 * Rate = Time.
The little difference here and there are probably due to the not shown decimal part of the rating.
If you reverse the math and use 3600 as basis, you'll see that the multiplier is always between 27 and 28.
If we could test a droid wit a critical fail on quality experimientation (0% rating) I'm pretty sure it will be 1 hour time.
And a 100% would probably last 15 minutes. (3600 - 2700 = 900 seconds)
If I was a developer doing such kind of droids, that' what I'll do. Set a max time of 1 hour and a min time of 15 minutes. And I think that's what the formula does.
Hope that help.
Reading this, I think we can generalize the formula to something like this :
3600 - 27 * Rate = Time.
The little difference here and there are probably due to the not shown decimal part of the rating.
If you reverse the math and use 3600 as basis, you'll see that the multiplier is always between 27 and 28.
If we could test a droid wit a critical fail on quality experimientation (0% rating) I'm pretty sure it will be 1 hour time.
And a 100% would probably last 15 minutes. (3600 - 2700 = 900 seconds)
If I was a developer doing such kind of droids, that' what I'll do. Set a max time of 1 hour and a min time of 15 minutes. And I think that's what the formula does.
Hope that help.
Kellisanth
Fri Jul 02, 2004 9:13 am
#16
Gavvot wrote:
Reading this, I think we can generalize the formula to something like this :
3600 - 27 * Rate = Time.
The little difference here and there are probably due to the not shown decimal part of the rating.
If you reverse the math and use 3600 as basis, you'll see that the multiplier is always between 27 and 28.
...
Hope that help.
Ahhh, okay... That helps a lot more... Got a lil' confused ... No worries... That's normal for me. 
Wirebiter
Fri Jul 02, 2004 10:47 am
#17
Yeah, I think this formula is about as dead-nutts on as we can get. I calculated a 17min 42sec droid with a 94 rating, and when I sent it out, it told me it would be 17min 36secs. Thats close enough for government work. Thanks for everyone's input on this. Thats one less riddle that we DE's have to worry about!
Gavvot wrote:
Hum.
Reading this, I think we can generalize the formula to something like this :
3600 - 27 * Rate = Time.
The little difference here and there are probably due to the not shown decimal part of the rating.
If you reverse the math and use 3600 as basis, you'll see that the multiplier is always between 27 and 28.
If we could test a droid wit a critical fail on quality experimientation (0% rating) I'm pretty sure it will be 1 hour time.
And a 100% would probably last 15 minutes. (3600 - 2700 = 900 seconds)
If I was a developer doing such kind of droids, that' what I'll do. Set a max time of 1 hour and a min time of 15 minutes. And I think that's what the formula does.
Hope that help.
Gavvot
Fri Jul 02, 2004 11:17 am
#18
I think we can add that margin error is max 27 seconds (1% rate).
There might be a way to be more accurate by calculating the maximum result based on stats of the materials used, but I'm not gonna do that.
I guess the formula is much more simple.
The usual formula for that is something like : Max(Rate/Fixed value, 1).
For droid batteries fixed value is 20 for exemple.
There might be a way to be more accurate by calculating the maximum result based on stats of the materials used, but I'm not gonna do that.
I guess the formula is much more simple.
The usual formula for that is something like : Max(Rate/Fixed value, 1).
For droid batteries fixed value is 20 for exemple.
Kellisanth
Sat Jul 03, 2004 10:50 am
#19
Wirebiter wrote:
Thanks for everyone's input on this. Thats one less riddle that we DE's have to worry about!
We (DE's) shouldn't have to go about and try to decipher our droids. CH's don't puzzle over their animals in their datapads. WS don't when creating their weapons (can you imagine the outcry of folks trying to figure out the CR of their "Uber" T21?) ... I don't think BE's or Chefs either when they make their items. Definitely Artisans don't or Architects. "Whatdoes SC530 translate to?" (Storage Capacity). Don't see that.
Why is it that we DE's have to domore work to decipher our items and explain to people what things do or how they perform?
Are we kinda like the step-children of the DEVs to be tormented?
Wirebiter
Sun Jul 04, 2004 12:36 am
#20
Actually many consider us Red-headed step-children of the crafting community. To be just step-children would be a promotion I think!
Kellisanth wrote:
Are we kinda like the step-children of the DEVs to be tormented?
Parja
Wed Jul 07, 2004 10:20 am
#21
Yup, the 3600-27*R=T is what I figured we were coming to. I compared it to all of the data so far and they're all within 27 seconds except for this one...
Wirebiter wrote:
QUALITY Survey Time
8819min 45+sec
This one is 39 seconds off of what the equation says it should be. Was there a number entered incorrectly on this one by any chance?
Drashk
Wed Jul 07, 2004 10:29 am
#22
I'd say that 45+ might be the key factor here. Looks to be that the time as longer than 45 seconds.
Parja wrote:
Yup, the 3600-27*R=T is what I figured we were coming to. I compared it to all of the data so far and they're all within 27 seconds except for this one...
Wirebiter wrote:
QUALITY Survey Time
8819min 45+sec
This one is 39 seconds off of what the equation says it should be. Was there a number entered incorrectly on this one by any chance?
Wirebiter
Wed Jul 07, 2004 6:02 pm
#23
Parja wrote:
Yup, the 3600-27*R=T is what I figured we were coming to. I compared it to all of the data so far and they're all within 27 seconds except for this one...
Wirebiter wrote:
QUALITY Survey Time
8819min 45+sec
This one is 39 seconds off of what the equation says it should be. Was there a number entered incorrectly on this one by any chance?
Yeah, I listed it as close to what I could remember it being. It probably was a little bit more. I only made one at that value, and have since used it. You could probably throw that one out of the list.
Page 2 of 2