A DPS Simulator 2 - SimFF

[Kenji1134]

There is a rich selection of i70-i130 gear!

Before HW, I isolated DET at a few levels of AP and at 58 WD. I found it to be pretty dang linear. Many others have said that AP and WD are the same way in isolation but I never got around to trying it out.

By all means if you can run some setups to isolate stat variations then please feel free to do so.

The key things is gathering the data in a controlled manner. So ideally you'd want to use a strong ability to reduce rounding error, and always make sure that the additional effects acting on that ability are the same throughout, even if that means not using any at all.
As far as sample size, I have found that roughly 50-60 non-crit samples under the same conditions is enough to reduce the (standard deviation)/(max damage) to under 3%, which I would say is good enough. About 100 samples with larger damage numbers drives it to just about 2.5%, which I think is the minimum, since there is a natural +-5% swing on damaging abilities which (I assume) follows a Gaussian distribution.
Then the average of that data needs to be divided by the tooltip potency, as well as all passive buffs/traits, again like Heavy Thrust, Deliverance, Maim and Mend, Hot Shot, etc. This allows us to come down to a unified metric, the amount that your stats combined into a single value influence your baseline "potency".

[SunnyHirose]

The key things is gathering the data in a controlled manner. So ideally you'd want to use a strong ability to reduce rounding error, and always make sure that the additional effects acting on that ability are the same throughout, even if that means not using any at all.

I did one better: I tested at multiple potencies (sometimes with buffs) to calibrate around the rounding a little, and the tests were fairly long. A pitifully low number of data points, but they are HQ datapoints so neener neener. Sadly, they changed a few things around for HW and I ran out of retainer space, and won't have the time to do that kind of testing again in the foreseeable future, and excuse excuse excuse so here I am throwing up my hands and working on leveling things all over again instead.

since there is a natural +-5% swing on damaging abilities which (I assume) follows a Gaussian distribution.

It's uniform.

[Dervy]

I'm on Holiday sadly and only have my mobile with me Haha, it'll be like that for three weeks sadly. Actually... on Monday I should be alright as I'll actually have WiFi. "Itsdervy" is my Skype I believe.

I uploaded the solver I used to get my formula anyway. It's nearly a carbon-copy of EMXs old sheet, but changed it up from my liking. I might be able to get a link for it...

[pandabearcat]

It doesn't matter to me really what the accuracy of the formula is (5% or whatever is fine) as long as it works for each class.

Its better to be able to roll them out then tweak later.

Plus, it will be super satisfying to post "dps rankings" and have everyone go crazy, esp if they aren't supposedly accurate yet.

[pandabearcat]

Hallo, just an update on the documentation. I ended up going through and cleaning all of the engine code up. I am -hoping- to get some documentation up by tomorrow, but that depends on my work schedule.

Now there is still going to be a revamp later on needed for Auras and Casting (mostly for BLM, to allow aura stacks and also casting resource cost modifiers). I am also planning to add 2 events, CastEvent (on a spell cast - can be instant or a casted spell) and ResourceEvent (whenever TP or MP changes) for ease of UI monitoring.

Next week there will also be a -huge- revamp to skills, moving from hardcoding to another script system that should allow for easier changes to data values (tp costs, mp costs, etc) without having to rebuild the entire program. However, until someone finds a way to pull spell info (like spell logic) from the client itself (similar to how simcraft does it) I will not make the effort to make skill logic also be scripted.

[HeavensSword]

Ah ok. I commented on the DRG thread before I saw your post here, but like I said over there I have UI almost ready to go. Just need to make the appropriate calls to your code and test/polish.

[pandabearcat]

Hello hello,

0.4.3 has been released.

It contains the DRG jump/ssd fix, as well as a decent code revamp, but most importantly, has documentation!

...for some of it. The core parts that are exposed as public members, at least. If you have any more questions about undocumented aspects of the code let me know.

Also included in the /Samples/ folder is the entire UI (its very small) that I created. It is somewhat commented and should give you a reasonable idea of how to hook your own UI into it.

Note: casting event is currently unused and won't ever fire.

Enjoy!

https://mega.co.nz/#!s89GzAqD!vvX7xw...xshvYCUipH3-to

[Dervy]

Have you tried implementing Heavens UI for your Sim?

EDIT: based Kim dotcom

[pandabearcat]

I would imagine it would be heavensword that would implement his UI for my sim.

Oh uh, for people unfamiliar with programming, the simulator is a set of libraries.

Anyone who wants to can write their own UI, so I don't need to implement his UI, he just needs to call my libraries. Maybe that makes more sense.

They can be developed separately and then used concurrently. As long as the public API does not change all that needs to happen is calling updated libraries if/when they are updated.