|
|
Post by aklame on Aug 12, 2008 0:13:12 GMT -5
Anyone else noticed that the percent complete seems off? Sometimes my percent complete after I fail a blueprint will be higher than 100.
|
|
|
|
Post by Jason Citron on Aug 12, 2008 0:50:01 GMT -5
I've heard scattered reports of this. Could someone be ULTRA specific about where the problem occurs? It'll save us time on diagnosing it. I'd like to fix this if we can isolate it.
|
|
|
|
Post by thejuggler on Aug 12, 2008 5:05:43 GMT -5
Jason, I saw the post below yesterday which explains the problem, with pictures .... aurorafeint.proboards100.com/index.cgi?action=display&board=visbug&thread=817&page=1The cases I've seen of this one are exactly as described above where one or more of the elements are over 100%, and the total percentage is over 100% but at least one element has not had enough resources collected. It seems like the algorithm to show completion percentage is based on the sum of each of the elements (including any collected over 100%) however for this to show the correct percentage, a maximum of 100% needs to be applied to each element to prevent the total percentage being greater than 100%, and showing completion when at least one element is not complete. Taking a cut down example ... (and yes I've rounded!) Wind 110/80 = 130% complete Water 79/80 = 99% complete Fire 80/80 = 100 % complete. In total we have 112% completion. This is clearly incorrect as we don't have enough water collected. If we limit this a below then the numbers work out correctly. Wind 110/80 = 100% complete Water 79/80 = 99% complete Fire 80/80 = 100 % complete. Total = 99 % complete. |
|
