Looks like its trying to meet the old chaotic meta requirement (more blue then red gems). Does the chaotic meta still have the old requirements in the version that you are using, and is it the only meta marked as available?

That looks very strange. I would expect Int/Haste or Int/Hit gem to be stronger in each of those spots where Hit/Haste was used. What do you see in the gem charts for those specific sockets if you try to change the gem? I'd need to see the character xml to say for sure what is happening, but it looks like a bug to me.

Is there a reason why Rawr .NET 4.0.20 seems to want me to end up with 13.77% hit as arcane? Have to force the optimizer to add 1740 hit rating.. and then it wants to consider getting the needed hit rating..

Think the Rawr4 repository profile did get uploaded: EU.Turalyon.Hanshi.Mage.4020b1
Alt armory - Hanshi @ Turalyon - Game - World of Warcraft

Have not bothered to reforge/regem after getting T11 shoulders. And rawr seems to be giving me conflicting information between optimizations. Especially on reckless vs artful ember topaz

The EU.Turalyon.Hanshi.Mage.4020b1 does not appear to be present on Rawr4 repository. I tried loading your character from armory. Upon loading it shows a score of 21698.96. After optimization I get a score of 21832.86 dropping hit to 16.99%.

EDIT: Nevermind. I am dumb and didn't realize cogs had to be added to the gemming template.

Noticed today that Rawr was valuing the 359 [Bell of Enraging Resonance] higher than the 372 version as it had the internal cooldown on the 359 at only 75 seconds. So I went and tested on the target dummies and it appears that the 359 ICD is 100 seconds - same as the 372 - and following the 5x proc duration pattern.

I'm having some unexplainable result in Rawr with my current stats:
- At 7433 SP, 716 haste rating, 1716 hit rating, 1285 crit rating, Rawr returns my dps ~ 18800. The relative stats value of mastery rating: spellpower: haste rating is 1.07: 2.04: 0.99.
- With the same stats, I reforge 75 crit rating -> 75 haste rating, my dps jumps to 19800 dps, a 1000 dps increasement. Furthermore, the relative stats value of mastery rating: spellpower: haste rating is 2.33: 2.18: 1.21.

After spending some more times with Rawr, the above results seems to happen when I'm using the following weapon enchants: mighty spellpower (63 sp), hurricane, and those +sp enchant to weapon. When the weapon enchant is changed to power torrent or black magic, the above abnormality disappears.

I'm wondering whether if it's a rawr bug, or it has something to do with cd line up that results in some "magic number" for haste rating?

You can load the character "US.Weird.Mage.Result.Hurricane1" From Rawr repository and reforge the pants 75 crit-> haste to see the result.

I get a very different result from Arcane Light vs setting 1740 hit as need.

If you just set hit requirement and ignore the mastery bug you'll obviously get a different result. It'll still be wrong though. Here's an explanation of what is happening so it'll be easier to understand why in some situations the mastery becomes overvalued. Under the hood the arcane solver is basically a constraint system. It is asking given some constraints which cycles and cooldown combinations to pick to maximize the damage. The problem comes from the fact that the mana restrictions are underconstrained and allow the solver to pick a solution that gets mana above 100% in some situations. The solver basically exploits this by using regen cycles to get very high mana % which in turn is why mastery is valued so high in this bugged situation. Currently the only places where constraints on max mana are placed are between switching from regen to nonregen cycles and somehow after the hotfix mana changes it can get higher damage from doing this even at expense of burst phases. By enabling Arcane Light or disabling regen cycles you'll prevent the conditions under which it's able to go above 100% mana.

Could someone please explain to me as to why I get the warning whenever I try to use the optimizer?

The following currently equipped items are not available

Rigid Cogwheel in not available
Smooth Cogwheel is not available

Do you want to continue with the optimization?

Any and all help with this issue would be greatly appreciated.

Thanks

Mhalzorn

Alternatively go to Gems->Cogwheel chart and mark those with a green diamond. Gemming templates are a bit awkward for cogwheels because they assume that the same gem is placed in all sockets of the same type which doesn't really work with engineering helms since there's two cogwheel sockets, but the cogwheels are unique equipped.