Vault Frames Do Not Match In-Game Experience
- Dominant language
- JavaScript
- Stars
- 115
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
The simulator is calculating Vault speed as the following:
FRAMES=MAX(CEILING(17.999996/(WeaponAPS*(1+WeaponIAS%)+Item&DualWieldIAS%)).4)
However, D3Planner Data shows Vault has a static Attack Speed of 1 rather than the variable Attacks_Per_Second_Total (compare vs. Dashing Strike); and it has a Walking Speed Multiplier of 1, but MS% does not factor into the above equation at all. It may also be relevant, D3Planner Data shows it has ScaledAnimTiming. I'm not sure what that portion means, however.
The 17.999996 also does not appear to factor in a Velocity (17.999996/velocity), or if that is with Velocity already factored in (base/velocity=17.999996), there would need to be a second component of the animation with its own frames, as the current values are much too fast vs. in-game experience. For example, in the current calculation, if you Dual Wield Hand Crossbows, you have 1.6 WeaponAPS and 15% IAS. This puts you at 10 Frames/Vault or 6 Vaults/second. In game with these settings you are much closer to only 2 Vaults/second. Additionally, in-game you can tell that MS% plays a role, as with Tactical Advantage consecutive Vaults are significantly faster.
So possibly the current formula is correct but only for half of the Vault animation - e.g. the initiation/ending animation, with a second formula needed for the movement portion.
One last thing to note, which may be correct but is unclear based on just D3Planner Data, is where the 4-frame minimum comes from.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.