There seems to be a constant stream of questions about Rawr.Mage that are a result of not using the tool correctly. Hopefully this thread will be of help to those seeking answers related to Rawr.Mage. This thread will be dedicated mostly to the use of the tool and is not meant to be a place for reporting bugs.
That said, let's start at the beginning.
Rawr.Mage is a module for Rawr which can answer several theorycrafting questions related to mages.
You can download the program from
Rawr - Home
There is a thread here dedicated for any general Rawr questions not specific to the mage module:
http://elitistjerks.com/f31/t21713-r...eased_11_27_a/
If you have a bug to report, please utilise the bug reporting tools at
Rawr - Issue Tracker
A lot of questions are answered in the Rawr.Mage wiki, so if you haven't read it, please take a loot at
Rawr - Home. There are some questions that aren't answered there and these I'll try to answer here. I'll start with some common questions, the rest will come as a result of further discussion in the thread.
Why does Rawr.Mage value int and mana regen so high?
There is a very good chance that you have not set up Rawr properly. If you haven't yet, I advise you again to look at the Rawr.Mage wiki. The most common reason for this problem is that you forgot to select buffs. If you are sure that you selected everything correctly then most likely this means you have actually specified fight conditions where you are mana starved. Rawr.Mage optimizes total damage done given the fight parameters and it will utilize whatever means it has. With default settings it will try to compensate with potions, gems, evocation, less mana intensive rotations. It will not optimize your talents, so it might be possible that a better alternative to regemming your gear is changing your spec for a particual encounter if you've indeed modeled it correctly. If you've tried everything and it still doesn't make sense as a last resort there is an option under fight parameters to assume unlimited mana. This however will do exactly what it says and don't be surprised when it says to use molten armor and when you try that in practice you run out of mana.
How to use Rawr.Mage in combination with WWS reports to improve your game play?
This answer is adapted from a guide I made preexpansion so some things might be out of date.
First thing you should get from a WWS report is the fight length which you can get at the top after the date and enter that in options under Fight tab. Next look at your external mana regen. If you received Mana Tide or Innervate you can enter that on "Spells & Buffs" tab and you can specify Replenishment and Judgement of Wisdom under Buffs.
Next thing to look at is your dps time. In WWS you'll have a line like this:
Dmg. Out to foes : 1,161,580 (13 %) to friends: 0 DPS time : 12'30'' (69 % of presence) DPS : 1548
Your dps time in this case would be 0.69. There are a few things to keep in mind here. The way WWS computes this is to divide the whole fight in 5 second intervals and in each interval if you did any damage they mark you as dps active in that interval. Number of intervals in which you did damage over total number of intervals would then be your dps time. Especially for fire specs you have to be careful as dots will skew this number. For Rawr.Mage the dps time is time where you were able to cast at mob, i.e. not running around moving out of fire. So you have to be careful to identify how much of downtime was due to environmental/fight requirements and how much was due to you being slow switching targets. This is best done comparing to another player of same spec to see if you're too low. Main reason why this can be low is due to slow targetting, being slow in reacting to events and similar. When you run out of fire it's important to do it fast and clean and get back to dps as soon as possible without wasting time on turning around.
Next thing to find out, which is almost the most important I think, is to figure out how much effective latency you have. Look at your tooltip in game to see the cast time of your spells after haste (or check in Rawr). Now go to WWS and click on browse log file. This will give you a list of all damage events you did. Take a large stretch where you're chaincasting and look how much time it took you to cast them. It's important to take a large stretch since there are quite some fluctuations in individual casts due to how combat log works. Now divide this total time by number of casts you did and compare to the tooltip cast time. The difference between the two is effective latency which you can enter in Rawr under Spells & Buffs. The default there is 0.05 second which is very low. Anything from 0.1-0.2 would still be considered normal. If it is anything more than that then you have serious trouble. This is called not pressing the button enough. Try some new casting methods, get some cast bar latency mods.
Now you should have all the fight parameters set in Rawr and be able to compare your raid performance with optimum possible for your gear/spec.
Go to Stats tab in Rawr and check the Solution and Spell Info panel. If you look at Abilities in WWS you have a list of all spells you cast including average damage, number of casts, crits, misses and so on. A large reason for variation is crit percentage. This is random and not under your control. Compare crit% in WWS with crit% in Spell Info for all the spells. If there is a difference here then you should take this into account when evaluating your performance. This can be for better or for worse. Similar to crit is miss. This is also completely random and not under your control.
Again at the end is mitigated% which is the partial resists. On average it should be around 6%, but WWS does not compute this accurately so it'll more often show figures around 4-5%.
Now it's time to look at your spell selection. If you mouse over spell cycles in Rawr you'll see a breakdown of which cooldowns should be ideally used with each other and with which spell. You also have a breakdown by spell which will show you how much damage should come from each spell and number of times each should be cast. This is especially useful to compare with the total column in WWS. For number of hits be careful because WWS only shows number of non-crits. To get number of all casts in WWS expand the Columns button and in first "Nb" row check Crit and All Miss. Hits + Crit + Miss = number of all casts. If this doesn't match with Rawr that could be because you entered wrong dps time or latency. If could also be because you used a bad mix of spells or bad ratio between them. If number of casts match you can still have a missmatch in damage which can be caused by ineffective use of cooldowns.
First thing to check is mana pots/mana gems and evocation and compare with WWS. Did you use more than necessary or not enough? Did you evocate when you shouldn't? Did you use haste potion when you should have used mana potion? In WWS you'll see this under Gains, Buffs & Debuffs.
Next you should check your use of activatable effects and talents. First thing to check is how many times you used them. You can see this in WWS again under buffs gained. Compare it to suggested number of uses in Rawr and figure out what you did wrong. Did you forget to use a trinket? Should you be desyncing your 2 min cooldowns from 3 min cooldowns or not?
Finally you should check if you're using cooldowns effectively and pair them correctly. To check this in WWS you have to click on browse log file and for filter select "Both". Look for lines like:
45141 20:57'45.076 Kavan gains aura Mojo Madness
45142 20:57'45.076 Kavan gains aura Arcane Power
45143 20:57'45.076 Kavan gains aura Icy Veins
Compare this with pairings that Rawr is suggesting. Are you using Icy Veins with Heroism when you should have desynced it? Are you using comustion at the right time? Which trinket did you use with Arcane Power?
To get more accurate results in Rawr you can go to Advanced tab, enable Global Optimizations, check Segment Cooldowns and Integral Mana Consumables for Display (not for Comparison) and enable Reconstruct Sequence. If it takes a long time and you get a message box that under the computation limit it wasn't able to find a solution then you can either increase the limit (not more than 1000-1500) or change SMP Search Method to DepthFirst. After you've done this the cooldown pairings will be more accurate and you can also check the Sequence which will show you the complete timeline of when you should have used the cooldowns.