to add thoughts for smarter people to play with, are these the cells that were referenced in change stating that SND uptime assume 100% before cycles applied in the version change notes?

or perhaps a slight difference in energy regen procs calculated now that the sheets are streamlined instead of feeding back and forth (or whatever they did before).

Hopefully my inane comments will cause others better suited to expound helpfully =)

This is from the notes he posted in the thread when he updated the version. It states "always assumes targets are poisoned".

I hope that clears it up for people that keep asking.

Well, the reason I'm asking is because I once questioned myself what poisons I should run with while doing dailies (or in some 10-man when there is no one who can apply a posion to the target) with WD/WD and eviscerate mutilate build. I managed to find the answer by removing the assumption of the target being always poisoned in the previous version of the spreadsheet (just putting back the originial string but chaning 0.5 to 0.2). So I wondered how this could be achieved in the new version too.

Version 0.4.6 is available via the download link in the first post. Changes in this version:

- Expertise is no longer truncated (i.e. each point of expertise rating provides equal effect).
- Bloodlust modeling streamlined slightly.
- Slightly changed the calculation path for Slice and Dice uptime, preventing the drop-off that previously occurred on DPS Calc 2.
- Hyperspeed Accelerators cooldown reduced to 60 seconds, duration increased to 10 seconds.
- Added some logic to automatically activate the Master Poisoner or Savage Combat debuffs if those talents are taken.
- Added an option to assume that the target is always being poisoned by someone (for Mutilate).
- Skinning now properly provides 32 crit rating.
- The damage breakdown header on data entry sheets no longer displays values adding up to less than 100% of your DPS.
- Cooldown-based haste effects now properly affect Instant Poison and Wound Poison DPS.
- Fixed a naming issue that was causing problems for OpenOffice users.

Sorry for the second update in two days. I just happened to have some extra free time today and thought it'd be a good opportunity to try to get all the small stuff I've been putting on the back burner into the sheet. This way, 0.5.0 will be focused primarily on my planned overhaul of the cycle models, rather than having a lot of extraneous other stuff to worry about.

If there are any further issues that I've overlooked, even if they're small, they're most likely going to wait until 0.5.0.

Getting the same 508 error, English version.

I'm too getting this error, according the the value of the error its a bracket problem. Opened bracket without closing or vice versa. So im sure excel users will be getting the same problems too?

Unhide the various "DPS Calc" and "Cycles" sheets and screenshot where else those errors are occurring, if you can.

(edit) Also does the error occur right off the bat before you make any changes to the sheet at all, or did you change something to yield the error?

Random question, does anyone know if OpenOffice supports INDIRECT()?

It happens immediately upon load. Without doing anything at all to anything. I doubt you will need screenshots with what Aldriana has said now will you?

(Edit) According to the OpenOffice help, it does support "INDIRECT()"

You would be correct, as I just updated the download link in the first post to version 0.4.7. Changes:

- Really fixed the naming errors for OpenOffice users.

And hoo boy do I hope I'm right this time.

Well, I used INDIRECT() to reference named cell ranges. Hopefully that doesn't share the same pitfalls as indirect references to specific cells. I sort of wanted to switch to something like this already, because the code to determine which cycle table to reference on the Cycles sheets was getting more and more unwieldy, adding any more cycle types would have resulted in badness.