Dragoons: A Rotation Reborn

Quote:

---

Originally Posted by pandabearcat

The problem with the old dps simulator is that the code was really not very polymorphic and couldn't really handle what I had planned for putting in stat weights (it just did pure power conversions, w/o stats and damage). It also didn't have a very robust priority parsing. Also you don't want to see what the event handling was like, there was a lot of spaghetti code. Was originally made for just bards. Monks and dragoons weren't too hard to add, but trying to make it work for casting was a chore, esp once things started taking more/less time than GCD.

If I do go back to it I would likely start over, maybe with a different language, either one that could be hosted online or something faster like C++. I don't think I could ever work with python, indents for braces? No way >.< Python's lamda functions would be useful though.

I should also add that iirc the simulator's primary purpose was to define "optimal" rotations, something which I figured people would have done by now since its been 2 years, but I guess people are still arguing about things? Back then when the game first came out there were a lot of people with terrible playstyles. So the simulator was made to settle those arguments. I couldn't really care less about stat weights, I get little enough gear as is.

---

But we have lamdas in C++11!
http://www.cprogramming.com/c++11/c+...-closures.html

Yes, indent braces sound disgusting...

Quote:

---

Originally Posted by Viridiana

Numbers

---

Awesome! I'll make some Ninja, Warrior and Dragoon sets and try to match your parses.

Quote:

---

Originally Posted by Dervy

Awesome! I'll make some Ninja, Warrior and Dragoon sets and try to match your parses.

---

Yeah, sorry for some of the wonky AP/Det numbers @_@

BRD isn't my main any more, so I'm mostly working with i110 and lower gear. . .

It's fine! :D Low WD is what I need next anyway. Also, SquareEnix were really careful to make sure nothing got Datamined early with the Benchmark... Most of the Database isn't there, a lot of the files are messed up and so far, PV (XIVDB Dataminer) has only been able to get one song out of it, which won't even convert to a half-decent audio file :(. Hopefully Carraway on the BG forums can get something out of it.

Quote:

---

Originally Posted by pandabearcat

If I do go back to it I would likely start over, maybe with a different language, either one that could be hosted online or something faster like C++. I don't think I could ever work with python, indents for braces? No way >.< Python's lamda functions would be useful though.

---

(((((((LISP 4 LYFE)))))))

Quote:

---

Originally Posted by pandabearcat

I should also add that iirc the simulator's primary purpose was to define "optimal" rotations, something which I figured people would have done by now since its been 2 years, but I guess people are still arguing about things?

---

I'm a little surprised that some of this stuff wasn't figured out by the time I started playing seriously (a year ago). I hope I can prepare a summary of FFXIV rotation theorycrafting before HW, including where the details come from and what's not necessarily set in stone.

Dervy: Here's where I was going with that calibration thing. This is what the spreadsheet does: Take the assumption that there is some internal non-integer value for a point of potency and the end result is rounded to the nearest integer. Generate some silly internal value points, multiply them for potency and ±5% values, then round them. Try to estimate the internal value from what you get.

As you can see, the overall accumulated error to estimate that value decreases as you have higher potency, like you should expect (because there's less of that value taken up by that ±0.5 uncertainty, or ±0.333333333 for crits but we're not looking at that here). But if you use multiple measurements of the same internal value, you can alleviate this rounding error somewhat; it can introduce error in some cases, but the overall effect is a serious reduction in the error (see that RSS of 0.146 for 360 potency only vs 0.0554).

I mostly work off the assumption of this internal value based on crits having a higher resolution than non-crits (for a made-up example, you might see 573 for a non-crit, but then the crits might attest both 859 and 860--perhaps not these exact numbers, perhaps not for every value possible, but I have seen crits do things like this from time to time).

Quote:

---

Originally Posted by Dervy

Uhm... Yeah http://sim.ffxivguild.net/ but it's garbage. Your old sim for the bard is much better imo. T0rin and other players also quit. I wish they stayed :( Poor Summoners haven't had a thread for over a year.

---

Well, a meaningful thread anyway.

Dervy wanted me to let you all know that he has been suspended from the forums for two weeks. RIP. He can still be reached via youtube (Dervy Gaming) or reddit (u/iDervyi) if need be.

Was probably too excited about my nonexistent simulator. It turns out I actually lost the source code for it when I swapped computers. Oops.

Update: Possible Dervy perma-ban?! The plot thickens.

When BFB is down, the ideal dragoon rotation becomes HT->PB->CT combo due to a lack of buff snapshotting correct?

3 GCDs of PB DoT ticks> 1 GCD of CT DoT ticks +10% initial hit on PB

Quote:

---

Originally Posted by Outfoxed

When BFB is down, the ideal dragoon rotation becomes HT->PB->CT combo due to a lack of buff snapshotting correct?

3 GCDs of PB DoT ticks> 1 GCD of CT DoT ticks +10% initial hit on PB

---

Don't forget one losing 10% off one GCD of autos, one GCD/auto from the BRD if you have one.