I haven't done it before, Cranch, but thanks for beta-testing these things for me!

Bug: Darkweb bindings are missing a formula on their tab, which means they are sorted top.
Bug: Gear Planner is taking iLevel for 2nd trinket slot from the values of the 1st slot.
Bug: I broke racial crit bonuses.

I'm glad it's down to 'trivial' bugs like these, by now. These will be fixed in the next version.

For those interested, the algorithm followed by the gem optimizer is as followed:

1. Clear all gems.

2. First it loops through the following:
- find the prismatic (or yellow, blue, red if others aren't available) socket that has the highest socket bonus when combined with a +hit gem, but doesn't have a gem in it yet.
- put in a full +hit gem or a mixed + hit gem
- repeat

After this loop you should be hit-capped.

3. Next check:
- find the prismatic (or blue, yellow, red) socket that has the best socket bonus combined with the blue gem defined to match meta requirements.
- put in the blue gem

After this loop your meta-gem should be active.

4. Last loop:
- check each empty socket if it would give more dps with a color matching gem than with a red gem
- put in a matching or red gem depending on the answer
- repeat until all sockets are filled

EDIT:
As for your remark about crit%. Are you using the same spec for both beta4 and beta6? I'm getting the same crit% in both versions, but your 59.47% is what your SV spec has (with same gear, buffs, etc..), while 52.xx% is what your MM spec has.
EDIT#2:
Re-uploaded version 6 fixing the things mentioned above. Last update for today (well it is tomorrow here already).

nvm

Indeed that was the problem.

Interestingly enough, the Regemmer improves dps on my gems for MM, but actually gets about 2 dps lower for SV. To see this, load my gear, select SV build, set up shot rotation, then Regem. I'd argue that Regem should never lower your dps (it should just restore the original if it can't find an improvement.)

I've been running some tests in the gem optmizer and found that this part of the loop is actualy considering belt buckle as a prismatic socket that counts for bonus.

My setup in the spreadsheet is using the three color gem on this socket probably because it assumes its the best place to be to achiev the +12ap bonus in Belt of Dragons (which I believe its the best socket bonus in my current gear).

On the gear optmizer I'm getting a setup using 2x Dark Matter, but this is an unique trinket.

Sorting stats on my machine (Core2 Duo E6400, 4Gb Ram) are as follow:
Items checked: 373
Time taken: 44,98s
Per item: 121ms

Other than that I'm really looking forward for a final version of this changes. Great piece of work.

Edit:
I've rerun the gear optimizer and couldn't reproduce the 2x Dark Matter setup. I'll keep trying this until I can get this to report again.

Edit2:
Had that setup again when running the optmizer with only Dark Matter, Darkmoon Card: Greatness and Comet's Trail selected to be optmized (clicked select top3 from gear planner). When I add Mjolnir Stone (which is in my current gear setup), the optimizer selects Dark Matter and Mjolnir Stone for trinkets.

Ah. This is an oversight of my side. It should of course not trigger the bonus AP from the belt.

EDIT:
Also found the problem for double trinkets. Typo into a formula, because I had added a check so it wouldn't double use unique trinkets.

There seems to be an issue with the dual wield vs 2h gear planner comparisons. When looking at the gear planner with my 1hs equipped(bootblade+malice) it gives journey's end a 79 higher delta. That looked unusual to me because the 1hs clearly have superior stats when comparing the two. I put the journey's end in the spreadsheet and it was a 19 dps loss compared to what I use now, despite the much higher delta in the gear planner.

The auto gemming thing doesn't seem to handle well prismatic sockets (Belt Buckle) and Socket bonuses.

It rather place a agi crit gem on a yellow socket and a pure hit on the belt than a hit on yellow and a pure agi on belt.

And when I press regem, even after doing that change, it reverts back to the lower dps one (by 3ish dps).

Also... I don't know if something was changed... but the "CalcAtributes" now takes much longer than before. It took me 1m45s to do it, when it used to be nearly instant.

There's a small bug with the "CalcAtrributes". This will be fixed in the next release.

Same for the prismatic socket issue. They were top priority for gemming +hit, but I've moved them down a little bit, because it doesn't make much sense.

It should now try to socket +hit in the following order:
Yellow sockets, either +16 hit or a mixed +hit gem
Blue socket
Prismatic sockets
Red sockets

So red sockets are the very last possible choice for socketing +hit, with prismatics just above them, which makes sense I hope.

Wouldn't it make more sense for prismatics to be above blue sockets, since you first loop through yellow, then blue, then red?
In your setup, it seems to me it could potentially suggest gemming a yellow in a blue socket, making your blue gem either take up another blue socket or a prismatic (losing a blue socket bonus from your yellow gem suggestion)?

In this case I would have to restrict blue sockets to 'mixed' +hit gems only, then.

Couple things that sent the sheet into processing that lasted several (30+) seconds, that did not happen in past versions.

1) Deleting a profile.
2) Selecting 'No Racial' in the shot rotation.

Currently running Excel 2007 fully patched.

And just as a side note, is there any benefit to shipping the spreadsheet with sample profiles and specs in it? Just seems like unnecessary bloat to me, and could maybe even save you some money on bandwidth not having all of that stuff in there that (presumably) no one uses.

I keep getting "runtime error 91" when I try to read my talents from the armory.

"Runtime error 91 - Object variable or With Block variable not set"

Debugger points to this line in the scrapeTalents block

Set Nodelist = GetSingleDataXLS(URL, "//talentGroups").ChildNodes


This has happend with a couple of different versions.
Yes I can access the armory (when it's up)

The Gear tab can read from the armory no problem when i tried it today (Tuesday) I got the expected message of the Armory being down. However, the Talent tab gave me the runtime error

Are you using the latest PTR version? The pre-PTR versions are unable to access the armory anymore because of the change blizzard made with showing pets and their talents.

I had the same problem with version 90a yesterday.

Is it the pet talents causing an issue?

Blizzard added pet talents to the Armory which broke the talent import. Use the beta versions or wait for me to finish them up and release version 91.

Using the latest Beta with Excel 2007, pressing the CalcAttributes button seems to cause a series of calculations which blink on the bottom of the screen ("Calculating 0%") for quite a while - at more than 5 minutes. I have been able to replicate this behavior several times.

The repetitive blinking and time it takes is such that it appears to me to be a bugged formula, somehow.

Issue: ilvl 245 leatherworking items are included even if my intent is to have the gear planner/optimizer only use gear currently available in 3.1 (ilvl 213-239 items only)

It's seriously taking forever, way more than 5 minutes, when in the past it would take just a few seconds. Anyone else have this issue?

It's a bug, it's fixed in the next version.

I'm currently adding all the new items for 3.2 discovered and once that is done I'll release the next version. The "CalcAttributes" results is used only for the pawn string currently so it's not really critical. It's not needed to run that button for the Gear Planner or Optimizer.

Loading my profile, I get the following warning: '+114 Attack Power is not a supported Wrist enchant.' I have them enchanted with Fur Lining - Attack Power - Spell - World of Warcraft.

Edit: My mistake, I believe the PTR may have changed this enchant.

Correct. Same thing applies to ring enchants, etc. The beta spreadsheet is 3.2 only.

Why does speccing into improved hunter's mark doesn't show a dps increase in the spreadsheet? I'm trying to figure out whether I should put points in focused aim and equip another item or spec into improved hunter's mark.