Rawr.Mage - Page 109

Loevty · 07/17/11, 5:05 AM

Originally Posted by Maje

Rawr was valuing 4t12 at around 80* dps, assuming 4t12 works as recently discovered the dps increase should be around 240 instead of 80. For comparison 4t11 is worth around 1352 dps.
(* with a specific set I checked, your results may vary).

In summation: 4t12 is slightly better than before, it doesn't become good it just becomes slightly less awful, as to which set of gear is better depends on each mages gear.

I understand that what I mean is, to clarify; in a 'BiS list', is 4P Tier 12(minus hands) superior to 2P T12 (three off pieces)? Or do the secondary stats on the off pieces outway the aprox 240 dps gain plus tier secondary stats.

Raymeo · 07/30/11, 6:59 PM

Is there a way to filter out Spirit/Resilience gear from showing in the item list when using Rawr.Mage? Or Agility/Strength gear from showing in slots that don't have armor types, like the Back slot?

Kavan · 12/13/11, 2:01 AM

It has come to my attention that many players are scared of the number of options available in Rawr, so I've decided to make a very short list of the advanced settings I would recommend you to try out if you're ready to go beyond the default settings.

Cycle Level Haste Procs: Recommended for Fire spec, should make haste thresholds more accurate if you have haste procs, which will be everyone with T13.

Simple Stacking: Recommended for Arcane spec, in general this will make stat weights more stable (doesn't work for other specs).

Gaws · 12/13/11, 11:48 PM

When I check the option for Cycle Level Haste Procs as Fire, even with T13 normal 4 set(ilvl 397) and I run the optimizer, it chooses to go back to T12 HC 4 set. Why is that?

Kavan · 12/14/11, 3:27 AM

Actually just found a bug with the cycle level haste procs where it will assume you have 2T13 even if you don't. That is very likely the reason for what you're seeing. Will try to get a fix out as soon as possible.

Maje · 12/14/11, 5:39 AM

There is still something odd going on there, I used 4.3.2, enabled Dark Intent and used the BiS gear to optimize. Rawr chose a haste rating of 2722 which with DI translates into 35.07% i.e. slightly over what's needed for the 4th tick of combustion.

However in 90% of the cases that's actually over the needed amount since 2t13 gives 500 haste rating at the time of combustion, which seems like it isn't taken into account (Cycle level haste procs were enabled).

At that point Rawr suggests a value of 4.19 for crit and 3.02 for haste, however reforging from crit to haste lowers the estimated DPS which is a clear sign of a haste breakpoint, which though I'm at a loss to explain.

EDIT: If I check the Proc Uptime graph, the 10x 50 haste shows an uptime of 0 not sure if it's indicative of something.

EDIT2: Also unrelated to the above Insignia of the Corrupted Mind is on 115s ICD rather than the 100s used by Rawr.

Kavan · 12/14/11, 10:07 PM

There was indeed another more hidden bug related to T13 and combustion. I posted a new download that should fix it. From what I tested under your conditions it's now going for +2 ticks on LB and Pyro. Let me know if you find anything else that doesn't seem right.

Beldia · 12/15/11, 7:43 PM

I am trying to determine if the goblin racial is automatically applied since I am trying to optimize my reforging (kind of low on crit for fire)? Also I think I have seen it mentioned that there is a way to find a stat priority for my gear set in RAWR?

Kavan · 12/15/11, 9:36 PM

Goblin racial is automatically applied, yes. If you need stat priorities you can check the Stat Values->Relative Stat Values chart, but I think the Mage Specific->Stats Graph will give you a better overall picture.

zimzamzoom · 12/16/11, 4:37 PM

Would it be possible to add crit rating to the additional requirements dropdown in the optimizer? Currently it seems the only stat ratings are hit and haste (among many other options). This is in version 4.3.2b.

Perhaps I'm missing something, is there another way to optimize with a specific amount of crit?

Astrylian · 12/16/11, 4:50 PM

Originally Posted by zimzamzoom

Would it be possible to add crit rating to the additional requirements dropdown in the optimizer? Currently it seems the only stat ratings are hit and haste (among many other options). This is in version 4.3.2b.

Perhaps I'm missing something, is there another way to optimize with a specific amount of crit?

Why would you want to?

Kavan · 12/16/11, 6:22 PM

Ok time to dispel some confusion about what Cycle Level Haste Procs does exactly. The way Rawr operates without that is it computes the uptime of each haste proc and averages them for each spell. So for example for T13 it might find that it results in 450 haste on average. Then it computes all spell statistics with that specific averaged haste and finally combines it into cycles.

What Cycle Level Haste Procs mode does is instead it computes spell statistics for each possible combination of haste procs. So for T13 for example it would count both 0 haste and 500 haste, similar for haste trinkets and all combinations of what you have. It will combine these into cycles for each haste proc combination separately. Finally it will compute the uptime of each haste proc combination and average at the end.

This makes a difference specifically for dots, because there haste isn't linear. The way you're getting extra dot ticks is very discrete so if you average at the start you'll just get number of extra ticks at the averaged haste, which isn't necessarily the same as averaging the number of extra ticks at each possible haste proc combination.

I'll also enable this setting by default in next release since most are playing Fire at the moment to give better results by default.

Skorp · 12/18/11, 6:35 PM

question retracted

Turwok · 12/21/11, 6:08 AM

Rawr (4.3.3) is pointing a haste cap for combustion tick at 1340~1360 for me. I set full raid buffs without DI, goblin race. According with this chart the cap should be 1858 (500 haste ahead).

Is it considering that I am using 2pcT13? Which I´m not.

Kavan · 12/21/11, 6:20 AM

What exactly makes you think that it is pointing out a haste cap there? This kind of questions are better suited to be posted as an issue on the codeplex site so that you can also provide your character xml without which it is very hard to know what is going on.