search

ProjectTako / kparser

Automatically exported from code.google.com/p/kparser
1 stars 3 forks source link

Incorrect calculations @ Performance tab? #57

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Open the attached parse
2. Look @Exp & Perf tabs
3. /stagger lol

What is the expected output? What do you see instead?
Nice thank you for pointing me @ this new tab, i'm still not used to it ^^

ok for your example, then i followed your advice by opening my parse 
war/sam @ Birds Nyzul, to obtain really weird numbers:
- in exp tab, PT total time < total fight time lol
- then, still in exp tab, this:
[code]Mob Listing
Mob                        Base XP   Number   Avg Fight Time
Greater Colibri                ---       12            10.68
Greater Colibri                128      178            26.35
Greater Colibri                144      179            29.52
Wivre                          152        1         13:20.45
[/code]
so 370 Gcolis, np until now you would say, BUT now let's go to perf tab, i 
check option "exclude 0exp mob" as usual (there were ton of Gcolis kills 
from other pt nearby), and i obtain expected numbers (371 mobs, 3hr total 
fight time and DPS values ranging from 23~48). 1st problem arises when i 
select this time "Greater Colibri (128)", KParser finds only 4 o.O, same 
goes for Gcoli144 finds only 7 lol where are others?.
2nd problem is when selecting Gcoli128 or 144 specifically, DPS numbers 
were ranging from 3042~347 o.O. Looks a bit high don't you think XD ?

What version of the product are you using? On what operating system?
Labeled 1.4.5.0 in "About", but it's actually the v1.4.5.1 from here.

Original issue reported on code.google.com by raphael.morineau@gmail.com on 26 Nov 2009 at 9:49

Attachments:

GoogleCodeExporter commented 8 years ago 
Oops forgot to specify this is a reply from your answer to my PM @ BlueGartr 
forum.

Original comment by raphael.morineau@gmail.com on 26 Nov 2009 at 10:00

GoogleCodeExporter commented 8 years ago 
Found the bug.  Was checking for the filter XP (128, for example) vs the XP 
gained in
the fight with the mob rather than the base XP after chain bonus was extracted 
><  So
it missed all the 192 xp/chain 5+, etc versions of said mobs.

Also let me find an issue with Exclude 0XP mobs when 'All' mobs were selected, 
since
that was brought up.  Fixed that too.

Original comment by Kinemati...@gmail.com on 26 Nov 2009 at 1:15

GoogleCodeExporter commented 8 years ago 
Nice happy to have help you, even indirectly :)

Original comment by raphael.morineau@gmail.com on 26 Nov 2009 at 2:56