A DPS Simulator 2 - SimFF

[Hustensaft]

1277/1145 would have been 1.1152, which is way too big a spread.

Given that my 40 potency dot can go from 58-65 resulting in 1.1206 , and either 64/58 and 65/59 still result in 1.10X, there must other stuff be going on.

Either the game forcefully creates more numbers than needed (for cases where a 1.1 value would result in only one number - level 1 BLM auto-attacking for 1-2) or some stuff happens after creating the damage range (Magic and Mend is applied after creating the damage range - combine that with rounding and you could get there), or you could even have both of these.

Damage ranges are a pretty pointless concept anyway. You'll only ever bother with their existence if they punish you, i.e. you get the bad end of the spectrum and your damage blows because of that. Hopefully going in Heavenswards with a lot of bigger numbers they'll notice that there are no benefits of damage ranges. The only way to counter that is to tune stuff around the worst case, but that would mean that if you get exceptionally lucky, it can seem pretty easy (10% "buff")

[Viridiana]

Given that my 40 potency dot can go from 58-65 resulting in 1.1206 , and either 64/58 and 65/59 still result in 1.10X, there must other stuff be going on.

The target is 21/19=1.1052something. 64.5/58.4 is 1.10445, so that spread makes perfect sense.

[SunnyHirose]

Something I've been looking into but have yet to find an easy way around solving for (lol distractions) is that if you can't trust the X-value of your solve to be error-free, then the slope is actually biased towards zero.

[SunnyHirose]

Well, one thing that I'm pretty sure happens with those damage ranges is that if the rounding is a .51 --> 1 or .49 --> 0 kind of situation, you will need a *lot* of tries to even see it happen. Pretty much why I take a mishmash of potencies (and include crits as x1.5 potency) when I test damage values; yeah, it's making assumptions that that's how it works, but in practice it makes that sort of thing less of a problem.

[Viridiana]

Well, one thing that I'm pretty sure happens with those damage ranges is that if the rounding is a .51 --> 1 or .49 --> 0 kind of situation, you will need a *lot* of tries to even see it happen. Pretty much why I take a mishmash of potencies (and include crits as x1.5 potency) when I test damage values; yeah, it's making assumptions that that's how it works, but in practice it makes that sort of thing less of a problem.

Yeah. The worst is when you're certain that a damage value should be possible, but the game refuses to give it up. Dunno how many times I sat there questioning my own sanity while gathering numbers. . .

Anyway, since I apparently volunteered myself to collect animation delays for some reason, I should probably make sure my methodology isn't gonna be stupid. Record myself doing actions, forcing animation delays, and count fractions of a second using good video editor until the next ability in line triggers a CD. Right? I'm not sleep-deprivation crazy? >_>

Assuming that's right, I have these values so far (based on like, one iteration each, so take with a grain of salt). . .

B4B: .6 seconds
Power Surge: .6 seconds
Life Surge: .7 seconds
Vorpal Thrust: 1.1 seconds
Full Thrust: 1 second
Jump: 1.4 seconds? That seems harsh, but it's what the video shows.

I would probably have more values, but I have a wonderful headache today.

[pandabearcat]

This seems about right. Lower than what I expected, actually.

[Dervy]

If anyone is interested, here's a heck load of Data Points for you lot to play around with. Crit Data is also included. Just to note, the stats used are either listed on the documents file name, or on the 1st page in a table. Ignore the stats listed inside the data points pages. Another thing, nearly all of it is done with 150 potency. The one that's at 100 potency should be listed as such, and I believe there's one datapoint with 180 potency somewhere in the "WD v DMG" sheets.

http://www.filedropper.com/datapoints-fix

I'm working on collecting 0 WD data now, so if you have anything you specifically want me to get for you, I can do that.

[Viridiana]

If anyone is interested, here's a heck load of Data Points for you lot to play around with. Crit Data is also included. Just to note, the stats used are either listed on the documents file name, or on the 1st page in a table. Ignore the stats listed inside the data points pages. Another thing, nearly all of it is done with 150 potency. The one that's at 100 potency should be listed as such, and I believe there's one datapoint with 180 potency somewhere in the "WD v DMG" sheets.

So much info. . .Unfortunately, some of your Disembowel stuff is labeled as 150 potency? I assume that's just a c/p error. Anyway, if you're collecting more info, do you mind taking a few minutes to get some dot tick values? They have a pretty small range usually, and you can have them ticking on multiple dummies at a time, so if it's not a hassle, that would be great.

Edit: Also, are we to trust the file names, the sheet names, or the information in the sheet? @_@

For example, DET VS 573 STR - 150 Potency has a 372 DET sheet, but the info in the sheet says 362 DET, 653 STR. >_>

[Dervy]

Yuuuuuuuuuuuuup. That's all bad copypasta stuff. As I mentioned, the exact stats used are linked in the table on the first page. And sure thing! I'll get DoT damage done for ya. Also, how are you organising your linear regression graph for potency btw? Are you stacking all of the jobs together, or giving them all their own separate tables/graphs? Very interested to see the work you've done on it.

Also, 1.4 for Jump is pretty reasonable. Instinctively, I know that if I have a jump available and I use it more than 1/3 through my GCD, I end up with a GCD clip.

EDIT: Yeah. Whatever is on the first sheet with the table and what the sheet is actually labelled, is what you should trust. The WD/STR/DET info inside sheet is all messed up. I got too lazy fixing it. It's like that for nearly all my datapoints, lmfao. And sunny thinks he's bad... If you want, I can quickly fix it up for you then send you another dl link? hahaha

EDIT 2: I'll send you another download link. I understand my own stuff, even if it's incorrectly labelled, but it'll be annoying for others to decipher what the heck is going on :P

EDIT 3: http://www.filedropper.com/datapoints-fix

Okay, removed all necessary junk and it all should be correctly labelled now. One thing to note, as you might of already noticed, is that I never used the Crit values, as I never achieved a complete min/max on most of them. But it's all there either way.

[Viridiana]

Okay, removed all necessary junk and it all should be correctly labelled now. One thing to note, as you might of already noticed, is that I never used the Crit values, as I never achieved a complete min/max on most of them. But it's all there either way.

Sweet. Totally gonna use your crit numbers, though.