How to Dragoon Per Second: A DPS Paradigm

What is the main difference between doing IR + BOTD after ID and pot after DIS, and the opposite setup? I've had some weird bufff timings where I'm coming up on a FT and POWERS,LIFES,IR,BOTD, are all coming off CD at the same time. Its kind of awkward.

A quick bug fix of the sim has been released, 0.4.3 : http://forum.square-enix.com/ffxiv/t...ulator-2-SimFF

It also contains documentation and source code for a sample UI in case you want to take a look at that.

I've made delays a bit leaner.

Jump delay is now 1.0 seconds, down from 1.8
GCD delay is now 1.0 seconds, down from 1.2
oGCD delay is now 0.8 seconds, down from 1.0

Custom delays will be added after the 0.5.0 revamp next week.

It should be tight. I double weave BOTD + LIFED so I hit the full thrust, then power surge + IR afterwards.

The micro-management of off-cooldowns is something I'm going to go over in depth, unless someone *cough* thendiel, does it before me.

Has there been any attempts at placing Leg Sweep somewhere in the opener that stops it from coming up at the same time as the GCD all the time? It was possible in 2.x if you did it immediately after Heavy Thrust, and it ended up being a lot of extra damage since you could use it 1.5 seconds earlier when it came off the cooldown.

Quote:

---

Originally Posted by Vandesaan

Has there been any attempts at placing Leg Sweep somewhere in the opener that stops it from coming up at the same time as the GCD all the time? It was possible in 2.x if you did it immediately after Heavy Thrust, and it ended up being a lot of extra damage since you could use it 1.5 seconds earlier when it came off the cooldown.

---

I highly doubt that.

Even if you could use it 1.5 seconds earlier, every single time, it would take you 600 seconds (10 minutes) for it to give you even ONE extra leg sweep.

And 130 potency / 600 seconds is something around a 0.1% dps increase.

one issue i've been having is that on the second use of blood for blood it comes off of cooldown right AFTER CT. i'm not sure if i should wait (30% of 600 is still 180 potency), cast b4b 1 gcd earlier in the opener, cast it immediately or delay it

If you're able to delay/clip your GCD by less than a second and you still have enough duration on BOTD/able to manage GKs, I see no reason why you can't.

I had to do it by paper, but anymore than a 1.5s delay is when you get a potency hit.

Quote:

---

Originally Posted by pandabearcat

A quick bug fix of the sim has been released, 0.4.3 : http://forum.square-enix.com/ffxiv/t...ulator-2-SimFF

It also contains documentation and source code for a sample UI in case you want to take a look at that.

I've made delays a bit leaner.

Jump delay is now 1.0 seconds, down from 1.8
GCD delay is now 1.0 seconds, down from 1.2
oGCD delay is now 0.8 seconds, down from 1.0

Custom delays will be added after the 0.5.0 revamp next week.

---

1.0 + 0.8 + 0.8 (2.6s) means still delays for double oGCD's but no more issues for jump's or regular oGCDs.
Phleb dot's still has a 18 second duration!

Thanks for you work, is the forums and your thread post the best way to keep udpated on simFF?

edit: is it possible to get a option for slightly randomised sim duration (within a set range maybe). This would help to evalulate SkS a bit better since the the weighting of SkS is often determined whether you get another global cooldown during the sim duration.

I think oCDs such as Battle Litany, Internal Release, Blood of the Dragon, Bloodletter and lrgsweep are all at 0.5ish.

Best way to check it really is to record yourself doing CDC -> ocd -> ocd count the frames in video editing software, then divide that number by 30/60 depending on the framerate of the programs timeline to convert to seconds, if I remember correctly

Weird, phlebotomize was 18 sec?

I'll have to look into it, I don't have the code w/ me atm.

Next update will likely be Monday.

I always update the SimFF thread whenever there is a new release. If it is pertinent to the job in question (like DRG) I usually make a post in that job's thread as well.

I will take into consideration the randomized duration.