1st thank you for your reports guys. I'll try to answer :
Ifrit.Showmo said:
I believe I found a few small bugs (for ver.5.1.2): Adding "WarCry" under the "JAs used" for Setup 2 seems to mess something up in the formula, causing most of the fields for Setup 2 to display as "#NAME?".
I failed to reproduce that bug on both Excel2003/2007 WinVista32 (works as intended for both setups). Could you save a copy of the sheet with all set up with that bug into a .zip and send it to the google site ("Issues Section") please ? Please specify also which Excel version you used.
Ifrit.Showmo said:
The Store TP formula doesn't seem to include the grip (and maybe weapon also?) in the final "Rounds to WS" result from the "WS SET". My "TP / hit" displays as 16.7, which is correct for my "TP SET". In my WS set, the only Store TP I lose is 1 Store TP from neck piece, which bumps me down to 16.6 TP gain from using WS (Tachi: Gekko btw). 16.7 TP per hit * 5 melee hits = 83.5 TP + 16.6 TP from WS = 100.1 TP gain total, which should bump me to a 6-hit, but it accounts all reported damage (and "Comparison Winner") as a 7-hit.
For the grip, i verified it does get accounted.
Actually i think there is a misunderstanding of the values displayed in Compare tab (maybe you missed the little info bubbles ?).
The TP/hit displayed is indeed the TP you get from each hit, like in game. On other hand, the WS TP return displayed is an AVERAGE that accounts for accuracy and multihits probabilities.
That means when you were expecting a WS TP return of 16.6% (ie 16.7% from TPset -1% from neck changed) it's the "base" tp return, but after accounting for accuracy (even capped there is still 5% misses) and possible DAs/TAs... you actually see in Compare a lower value(15.9%).
Same reasoning is applied for RoundsToWS, TimeToWS and TypicalWSTP.
Also, what i call "X-hits" = WS(1)+ConservedTP+Yhits*TP/hit > MinWSTP => Xhits=Y+1, which means in your example: WS(1)+0+5hits=15.9%+0+5*16.7%=99.4%, so needs another hit to hit more than MinWSTP(100%), ie 15.9%+6*16.7%=116.1% => 7-hits build (with an overflow of 16.1% TP when WSing).
Hope that will clear understandings?
Ifrit.Showmo said:
When I change the "Main Job Level" to 75 (seems to be level 77 and lower), some of the fields for that setup display as the "#NUM!" error. I double checked and confirmed that I was not using any equipment or job abilities that exceeded the level I had inputted. Additional Info: I tested this out with Setup 2, I get a similar error, but when reverting the level back to 90, the error remains until I completely close the Excel file and start over from scratch.
Mmmm... i failed to reproduce thazt also ;; Can you make a copy(s) with those bugs and send them (zipped) to the site please ?
Asura.Arkanethered said:
it is calculating the difference in my aftermath sets between a 5 and 6 hit build to be a draw.
Oh and I don't think it adds Relics(90) +25% damage on relic /ws.
No surprise there: even tough those features seems to be "there", they arenot integrated into the damage calculations yet, hence the draw. Also check the comment on the "DRAW" cell (hover your mouse on the cell) b(^^)
Asura.Arkanethered said:
How accurate from your tests is this? Just wondering
That's the most important question i'm always asking to myself when i code. Unfortunately, especially since i'm alone, rigorous tests are rare. I would go in a limb and say something like barely 30% of FF11 game Mechanics have been thorougly tested (a good chunk of values you see on wikis and forums are most of the time from StudioGobli which doesnot provide the tests that led them to such or such value, or eyeballed loltests on forums...). But despite that i made myself a few tests and coded the adequate formulas to match what KParser showed. The other formulas are base from StudioGobli and the very rare rigorous tests i could find on Allak, FF11AH and mainly BG forums, made by persons like Motentenn CDF Kirchy etc...
That's why i need when possible, besides the bug reports, rigorously parsed tests showing my formulas are wrong. Best way to obtain an "accurate" damage calculator.