Rawr.mage seems to have only a 'dps' restriction. Would be really nice if it could have minimum health and minimum shadow resist so that we could optimise alternate gear sets. I remember spending quite some hours figuring out my best gear for Mother Shahraz but since then I've picked up new stuff and would be great to see if I should craft the SR leggings after all... On the other hand SR is really outside the scope of a dps optimiser, perhaps an simpler idea would be if you could force the optimiser to ignore certain slots. E.g. force SR pieces to slots, set minimum spellhit, and generate ideal Mother gear.
Regarding your ponderance on ignoring slots and generating resist sets that way, I think you may already be able to swing that if you don't select ANY gear for optimization in the slots you want to have resist stuff in.
Example: I have SR neck, helm, cloak, bracers, shoes, belt. If I put those items in slots (you will have to add them in via the Add Item tool) and then don't select any gear for those slots in Optimizer, it should theoretically ignore those slots and generate the best gear combos for the other slots.
Well, I tried to do that anyways. Rawr.mage let me add in the item ID's but won't let me select the items for gear slots. I guess if it doesn't have spell dmg or some mage-like stat on it, it gets filtered out.
You could manually add 0.01 spell damage to each item or something.
Good call! I did .001 spell damage to be safe and they showed up just fine. I did that with Void Spheres as well so I could add those in as gems to my SR socketable slots. Then I ignored those slots for Optimizer, ran it, and Optimizer totally ignored those slots and set me up with an ideal set for the rest of my gear. Voila, SR optimized gearset!
A similar issue like the above exists when gemming pure stam in DPS gear (just about every class makes a stam set.)
I want to make a hybrid set, which includes gear that has stam gems in sockets; but I'm really checking out how much DPS the set has. The item isn't cached with the proper gems yet; I have to switch out to the bear model to put the stam gems in the item.
Yeah all you have to do is brute-force it by giving anything without caster stats, caster stats. Put ".001" or some really tiny value in for spell damage in the item editor; it'll show up as 0 spell dmg but it'll be usable in Rawr.mage. I plan on itemizing a sta set this way now that I know it can be done.
Edit: I just noticed you're a druid...if you want to do it for kitty gear, try giving the sta gems like .001 agi or something, see if that works.
Last edited by Rustyshrapnel : 04/10/08 at 4:31 PM.
Optimizer is really great, especially now that you just said that optimizing enchantments isn't broken, just not visible
One small feature request. Instead of the type of damage survival rating, I'd like to be able to tell the optimizer that I need it to enforce a certain number (or range) of resist rating. Thanks!
i'm confused, because in-game it shows that I'm uncrittable.
when i input the exact same items/gems/enchants it tells me that i'm still a few points from uncrittable in RAWR. Just wondering if this is a bug? or some way to work around this?
i'm confused, because in-game it shows that I'm uncrittable.
when i input the exact same items/gems/enchants it tells me that i'm still a few points from uncrittable in RAWR. Just wondering if this is a bug? or some way to work around this?
Well, first make sure that you really have everything exactly the same in game and in Rawr, by just comparing the DefRating and Resilience values. Assuming those match, trust Rawr. The character screen in-game rounds defense, such that it can say that you're uncrittable, when you aren't. The difference is something along the line of 2 def rating or 3 resil, if I recall correctly.
Nothing, at the moment, I believe. Rawr models support multiple ratings to compare gear by. Look at the Bear model for example: gear has both a Mitigation rating and a Survival rating. Overall is the sum of all the sub-ratings for the model. For Mage, there happens to only be one. I think Kavan may add a Survival rating for Mage, as well, not sure. (Though it'd be on a much smaller scale, since DPS is far more important than Survival for mages, most of the time) It'd be there so that it'd accurately rate an item like [100dmg 50sta] as better than [105dmg 10sta].
What exactly is the logic difference in "DPS rating" vs "Overall Rating" for the Mage optimizer?
It is the same.
Also for the next release I'll add sta and resist to relevant stats so that those items show up for selection and add constraints for optimizer based on health and resistances. Let me know if anyone would like to use any other kind of constraints also.
If you're actually having it choose gear out of a given gear-pool to optimize you could add input for minimum HP required for the fight... Anything more complex than that for mage survival is greatly subjective, and best I can think of as an extra is let the user add "stamina rating per stamina point as a function of current stamina" (with that function generally being infinite if HP is below a certain value since you're going to die for sure if you drop that low, and after that minimum value have stamina drop rapidly in value as you increase it until eventually hitting 0). Overall I think adding minimum HP entry is well more than sufficient for DPSers.
jsut tried loading my lock from a save file, and from armory, got this message
************** Exception Text **************
System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
at System.ThrowHelper.ThrowKeyNotFoundException()
at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
at Rawr.Retribution.CalculationsRetribution.GetTalents(Character character)
at Rawr.Retribution.CalculationsRetribution.GetCharacterCalculations(Character character, Item additionalItem)
at Rawr.CalculationsBase.GetCharacterCalculations(Character character)
at Rawr.Calculations.GetCharacterCalculations(Character character)
at Rawr.FormMain._character_ItemsChanged(Object sender, EventArgs e)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at Rawr.Character.OnItemsChanged()
at Rawr.FormMain.set_Character(Character value)
at Rawr.FormMain.LoadCharacterIntoForm(Character character)
at Rawr.FormMain.bw_ArmoryGetCharacterComplete(Object sender, RunWorkerCompletedEventArgs e)
at System.ComponentModel.BackgroundWorker.OnRunWorkerCompleted(RunWorkerCompletedEventAr gs e)
at System.ComponentModel.BackgroundWorker.AsyncOperationCompleted(Object arg)
Has the rawr elemental shaman been finished yet? (or developed). Searched the thread and saw the post saying you had started it but couldn't find any more details.
Console started working on one, but has since decided to create his own application.
I've been working on an updated spreadsheet, but that's going to take a while before it's finished.
Also for the next release I'll add sta and resist to relevant stats so that those items show up for selection and add constraints for optimizer based on health and resistances. Let me know if anyone would like to use any other kind of constraints also.
As mentioned: minimum health, resist stuff if possible (but that workaround with the 0.01 spelldamage is great!), but what would also be nice is minimum/maximum hit rating. E.g. with some configurations of gem choices Rawr.mage suggests I wear my Spellfire Belt over my Belt of Blasting where obviously this leaves me 23 hit short of cap.
As mentioned: minimum health, resist stuff if possible (but that workaround with the 0.01 spelldamage is great!), but what would also be nice is minimum/maximum hit rating. E.g. with some configurations of gem choices Rawr.mage suggests I wear my Spellfire Belt over my Belt of Blasting where obviously this leaves me 23 hit short of cap.
I wouldn't discount non-hit-capped gearsets so quickly. Being hit-capped isn't everything. Hit is certainly the most efficient use of stats, but if you're short by 10 hit rating, and have a choice between an item with 10 hit rating and an item with 50dmg, you surely should take the dmg one.
As mentioned: minimum health, resist stuff if possible (but that workaround with the 0.01 spelldamage is great!), but what would also be nice is minimum/maximum hit rating. E.g. with some configurations of gem choices Rawr.mage suggests I wear my Spellfire Belt over my Belt of Blasting where obviously this leaves me 23 hit short of cap.
You have to be careful with the Optimizer because if you do not select a sufficiently "thorough" search, or if you choose only to use pre-existing gem choices (i.e. the ones you see already in your socketed items) it can give you a not-quite-optimized answer. This is stated in the Optimizer section and I find that it is always worth having a play with any strange gemming options or gear choices.
An example of this that happened to me was with my [Scryer's Bloodgem] in comparison to [Icon of the Silver Crescent]... when I re-jigged some of the gemming options I got a higher dps rating and I remained hit-capped.
EDIT: Funnily enough, the [Scryer's Bloodgem] would probably be easier to co-ordinate Fire spec cooldowns with. Ignoring the destruction potion and the ever unusual combustion, your cooldowns are all multiples of 3 minutes. Although pointless for the higher up mages... it may be useful for those of us who raid Kara and still think that [Scryer's Bloodgem] and [Xi'ri's Gift] are good trinkets.
I know that rawrs use is as a dps spreadsheet, but in the future, will we be able to look forward to anything for healing, to optimize hps?
Rawr currently is used for both dps and tanking. Some healing models have been claimed, but nobody's actually checked in any code for healers yet. As a platform, Rawr certainly supports it.
True of course in terms of DPS dealt, but when you need to be certain to sheep trash that can kill very quickly (Kael trash taught me this lesson) you look on hit cap another way. Sod's Law also messed up one early attempt on Zerevor due to me wearing extra stamina gear; 97% spellhit and I got a resist on the pull. In my shame I felt I should pay everyone's repairs. Of course those random things even themselves out over your whole raiding career, but you always remember the situations where it went wrong.
The Rawr optimizer needs to be able to set stat requirements, and derived requirements... 99% hit rate, 15k health, passively uncrushable, etc. The models should be able to supply derived stats to the main application, as well as the raw stats that the application can easily track itself (like stamina, hit rating, etc). Some people will want to enter their own stats in (600 stamina) while other people will want to base requirements on the derived stats after buffs (15k health).
The Rawr optimizer needs to be able to set stat requirements, and derived requirements... 99% hit rate, 15k health, passively uncrushable, etc. The models should be able to supply derived stats to the main application, as well as the raw stats that the application can easily track itself (like stamina, hit rating, etc). Some people will want to enter their own stats in (600 stamina) while other people will want to base requirements on the derived stats after buffs (15k health).
How much stamina you have doesn't directly matter. How much *health* you have does matter. So, health is a stat available to the optimizer, stamina is not.