rsuhandy
-
Posts
104 -
Joined
Content Type
Forums
Blogs
Events
Articles
Downloads
Gallery
Store
Posts posted by rsuhandy
-
-
In mine specifically there were other factors that prevented the margin from being shown, namely that nasty fleet lag. It is just meant to give an idea of how clipping effects the overall numbers.
As far as the other parse in question; since it dragged out longer and ENDED with the scatter bombs, it caused the numbers to go waaaaaaaay up. Scatter bombs are quite unique. If you end a parse with them your numbers will be far better then if you end it before them. That is why his numbers are higher in the long run, not because that is the maximum for the spec. If you were to stretch it out just 13 more seconds it would be 3372.83. A loss of ~46 dps from the cropping of 3419 DPS. (For referance sake, here is the parse only showing 5 minutes 3358.31)
Do you see how dangerous cropping logs is? If we want any sort of accurate numbers and thresholds, we need the circumstances as close to the same as we can get them. (That includes time and buffs. The only thing we can not account for is built in executes due to talents and abilities.) An argument can be made that if I want accurate numbers, I should examine the log and crop it to compare with mine.........but that kind of defeats the purpose of having global leader-boards for it, doesn't it? It would be the same is if, they didn't track golf scores on a board for everyone to see and forced whoever wanted to know what the scores were to go check the individual cards of the players..................................
lmfao
I do hear what you are saying but to make a point I will be blunt.
Who are you to say the parse should be 5 minutes exactly?
I can put his parse length to 5 min and 27 seconds and it's about ~3390.
Taking a parse and cutting it at 5 min will just give whoever got lucky RNG at the 5 min mark have the highest parse. I personally don't really care if people clip the start of the parse, but I see a valid argument behind not doing so. But I see no reason to limit the time period to exactly 5 min.
-
The overall point I was trying to make by my post is that there are mitigating factors to why you were able to 2 man up till Kephess then 3 man. Therefore no additional challenge is necessary. Had you done it in full columi grade equipment 2 man I'd be impressed, and pushing the devs to up the difficulty.
To the others who brought up the point it is columi grade I apologize. I WAS thinking of hard mode.
Yes but you come off as dismissing their achievement.
Obviously it wouldn't be possible in Columi with two people.
Don't say it's an easy feat or unimpressive unless you have shown you can do it yourself.
-
His parse is for 3436.56. When you pull it back to the "enter combat" and set the limit to 5 minutes it comes out to 3358.31. A changed of 78.25 dps. In your example You give him an extra minute on the parse. These are just details, however there is a point to it (I am not picking them out just to argue). Saboteur (with scaterbombs) is not necessarily a sustained or "build up" spec. The damage comes strictly from the 20 second CD on HI/CE. It becomes a burst spec with dots that keep some damage going. Cut a log before they go off, the dps falls. Cut a log after it has been used dps rises. The damage the spec does can be manipulated on paper for a desired result.
Different specs require a different amount of set up to do damage. If we are talking about sustained, how about I run a Lethality/Dirty Fighting parse and cut it to only start when the first Cull/Wounding Shots starts (Eliminating the dots in the beginning for set up). This would allow be to get rid of the "ramp up time" and focus more on sustained because Lethality/Dirty Fighting focus's on the proper use of Cull/Wounding Shots. This method is not true to the spec considering what it actually does.
If you analyze a Watchmen Sentinels parse, you would have to cur everything before the 6 stacks of Juyo and 4 stacks of Merciless Slash. So, if I where parsing on my sentinel (by your rules) I would initiate combat --> build focus and centering (saving Master Strike and Zen) until I get my stacks of both buffs --> I would then begin doing damage with all relics and adrenals going with Zen and Inspiration at my. I would then cut my log in the begining to eliminate all of the build up of focus, centering, Juyo and Merc Slash. The log would run for 5 minutes following. This would give me a better idea of what sustained damage I would be doing.
To give a representation of this, I got on my LvL 50 sentinel and went to fleet (yes I had to deal with that nasty lag) and parsed on the LvL 10 training dummy. I had to use that one to ensure I hit with my abilities since the rest are LvL 55 (My gear was a full 63 BiS build from pre 2.0....it included accuarcy stats). Here are my results:
Not Clipped: (2433.68) http://www.torparse.com/a/244058/2/0/Damage+Dealt
End Clipped: (2421.23) http://www.torparse.com/a/244058/time/1369260371/1369260671/0/Damage+Dealt
Beginning and End Clipped: (2477.75) http://www.torparse.com/a/244058/time/1369260426/1369260726/0/Damage+Dealt
Now I ask, which log gives me my sustained damage, my damage threshold and my realistic damage?
The moral of the story here is that importing logs that were created under a different rule set skews the data in favor of trimming the beginning of each log. It sets those logs (unfairly) above the rest for no reason but to measure an e-peen by presenting data in a different fashion.
On the note of measuring fairness and actual thresholds on a global scale, I would put forth the following rule set:
1) Must be combat logged on the level 55 Operations Training Target MK-5.
2) Must be combat logged to a 5 minute duration. (Ending will be clipped 300 seconds after beginning combat)
3) Must include the "Enter Combat" (No clipping the begining)
4) Class buffs/stims/adrenals are permitted.
5) Another player is allowed to assist with 1Bloodthirst/Inspiration and Armour debuff etc during the logging.
6) Nightmare Pilgrim buff is not permitted.
7) No use of Legacy abilities.
8) Only combat logs from http://www.torparse.com/ will be accepted. All claims must be accompanied by a link to their parse.
What this does is set ALL classes on as much of an even playing field as possible considering what they would do within a raid. The only advantages that are left are multiple targets and executes (built in or added ability). Ramp up times stay the same, Inspiration is available to all along with an armor crack.
Let me get right on that for you been trying to get a nice MM parse, but I keep getting thrown out of combat
I have to say I don't really agree with you that the parse has to be cropped at exactly 5 min.
His parse is 3419 even with the enter combat state which is ~18 dps difference so not that much of a change.
I don't think it's fair for you to say that the difference is almost 80dps.
I think the parses should be at least 5 min, after which the parse can be cropped to the highest dps point in time.
This would show the MAXIMUM dps that a spec can attain after at least 5 min of combat.
Watchman does benefit quite a bit from Juyo and Merciless Stacking though and you will see a large increase for that spec.
However looking back at your watchman parse here is a Maximized dps number with the ramp up time.
2473
http://www.torparse.com/a/244058/time/1369260371/1369260827/0/Overview
~ 4dps difference between your beggining and end clip.
-
Coming back to this thread, I just have one other comment.
Surely you can see that a player would be put off by a claim that they were lying about defeating HM S/V, had actually altered logs, screenshots and were actively trying to fool everyone that Styrak was defeated. It's tantamount to saying, "You're not good enough to actually do this, we don't believe you, you're lying"
This is the reason for any less-than-calm response. Everyone was thrilled to have actually accomplished the feat. It was, for us, a moment of celebration. It was met with, "this is a false report and your guild is banned from posting on this thread"
Do you follow?
Now, to reiterate, the simplest solution, which we will be doing, is to do it again this week, take better screenshots, and that should satisfy everyone involved.
Hopefully that should clear this situation up.
I completely agree with you.
Though I would like to add that we haven't actually heard Arashi reply since the "banning".
Perhaps he could elaborate on what evidence he has that would convince him of false reporting.
Based on what has been presented in the thread I don't see anything that would suggest such an infraction,
but perhaps he has information that would say otherwise.
-
You could always screen shot the achievement for each of the group members.
The kill times should be the same for all of the group members.
There are no known bug issues with the Styrak achievement so all group member kill times should be the same.
-
-
If we're being consistent with other servers then taking the best 5 min section would be the way to go.
That being said, this is at most a +/- ~20 dps difference so it really doesn't matter.
The 5 min time period will average initial spikes in dps.
-
-
I wish Tyco and Konstance were still around....I miss those guys.
Two of the best PVE Vanguard dps around.
I'm surprised Shepard hasn't posted here yet.
-
It doesn't really help the thread to make non-concrete accusations.
Remember this is for learning purposes so that people can see rotations.
-
NVM
Problem solved
-
TOR Parse will tell you % overheal
-
-
Updated parse for Miruriya
2110
http://www.torparse.com/a/150610/time/1362290872/1362291189/0/Overview
-
-
Here's a better one.
Orazio
Dead On Arrival
http://www.torparse.com/a/150741/time/1362214323/1362214664/0/Overview
-
-
Yup Torparse is nice, you can even subtract the time it takes to exit combat which is a must
for DOT specs that don't have something like force cloak.
For instance Flint, your parse without the last 10 secs http://www.torparse.com/a/149910/time/1362167606/1362168002/0/Overview
2070
-
Frying time isn't really accurate FYI.
For instance Flint's parse which has a total time of
406.22 seconds with raw damage of 830349 should give a dps of ~2044.
This happens a lot with frying time and a similar problem can be found with Azadeh's parse.
We should all be using the same parser so that we can compare between parses more easily.
-
DPS Leaderboard 2.0+
in Flashpoints, Operations, and Heroic Missions
Posted
You are right dps change is subjective.
I should have said 3-4 fold less of a dps increase than previously suggested.