Rawr (v2.3.23 released on 9/12) - Page 130

zimira · 03/16/09, 5:13 PM

From the 3.1 druid thread, which is what i saw last night on ptr as well. Ptr down right now so i cant confirm it again right now.

bamina · 03/18/09, 5:07 AM

As i tried to optimize m ypaladin for retribution i got the following errormessage with 2.2.0b4

System.Collections.Generic.KeyNotFoundException: Der angegebene Schlüssel war nicht im Wörterbuch angegeben.
   bei System.ThrowHelper.ThrowKeyNotFoundException()
   bei System.Collections.Generic.Dictionary`2.get_Item(TKey key)
   bei Rawr.Optimizer.ItemInstanceOptimizer.InitializeItemCache(Character character, List`1 availableItems, Boolean overrideRegem, Boolean overrideReenchant, Boolean templateGemsEnabled, CalculationsBase model)
   bei Rawr.FormOptimize.buttonOptimize_Click(Object sender, EventArgs e)
   bei System.Windows.Forms.Control.OnClick(EventArgs e)
   bei System.Windows.Forms.Button.OnClick(EventArgs e)
   bei System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   bei System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   bei System.Windows.Forms.Control.WndProc(Message& m)
   bei System.Windows.Forms.ButtonBase.WndProc(Message& m)
   bei System.Windows.Forms.Button.WndProc(Message& m)
   bei System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   bei System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

I've no idea why that happens. Optimizing my healgear works without any problems.

Astrylian · 03/18/09, 11:58 AM

Please attach the character file that reproduces that to a new issue on our Issue Tracker.

Munorion · 03/18/09, 12:51 PM

Silly question:
Rawr (latest beta) rates The Egg of Mortal Essence (slightly) higher for me (Moonkin) than Embrace of the Spider. Now, both give a passive 98 spelldamage, but with the latter I should actually get the benefit of the proc. So, that seems a bit fishy to me.

• Adoriele · 03/18/09, 1:18 PM

Originally Posted by Munorion

Silly question:
Rawr (latest beta) rates The Egg of Mortal Essence (slightly) higher for me (Moonkin) than Embrace of the Spider. Now, both give a passive 98 spelldamage, but with the latter I should actually get the benefit of the proc. So, that seems a bit fishy to me.

Rawr (as far as I know) doesn't have a difference between healing and damage spells. Sometimes you have to sanity check stuff like that.

Munorion · 03/18/09, 1:46 PM

Hm, fair enough, but then it should still rate the two exactly the same? FWIW, the tooltip (in Rawr) includes the proc for Embrace, but only shows "98 spelldamage" for the Egg.

thedopefishlives · 03/18/09, 2:34 PM

Originally Posted by Munorion

Hm, fair enough, but then it should still rate the two exactly the same? FWIW, the tooltip (in Rawr) includes the proc for Embrace, but only shows "98 spelldamage" for the Egg.

Latest beta has some broken code for trinket procs. I'm still trying to math out the final equation that I need to use, so bear with me.

Kris · 03/19/09, 3:30 AM

TBC gems are missing in the beta. I tried manually adding Eternal Earthstorm Diamond, copied everything from the WotLK version, it's still not appearing in the meta gems list.

Astrylian · 03/19/09, 10:04 AM

What do you mean by 'copied everything from the WotLK version'? Rawr is never missing any items, of course, but yeah, I dropped TBC items from the default itemcache. Is there something stopping you from using that item?

Kris · 03/19/09, 11:02 AM

Eternal Earthsiege Diamond
+21 Defense Rating and +5% Shield Block Value
Requires at least 2 Red gems
Requires at least 1 Blue gems

Eternal Earthstorm Diamond
+12 Defense Rating and +5% Shield Block Value
Requires at least 2 Blue gems
Requires at least 1 Yellow gems

Since my tanking gear has 0 red slots, I'd gain more by using the TBC gem, instead of wasting 2 slots for red gems. The problem is, when I added Eternal Earthstorm Diamond, Rawr correctly imported the 12 def rating and 5 SB from armory, but the gem itself is not available anywhere in the program. I can't select it in the default gem settings, can't see it in the Meta section.

Astrylian · 03/19/09, 11:23 AM

Ah hah, OK, found the bug. The charts aren't updating with newly added items immediately. Just relaunch Rawr, after adding it.

Astrylian · 03/22/09, 6:33 PM

Download (BETA) - Rawr - Release: Rawr 2.2.0b5

NEW! Tour of Rawr Movie! - YouTube - Tour of Rawr

Recent Changes:
v2.2.0b5
- PLEASE NOTE: This is a beta of Rawr 2.2. It has not received the same level of testing that we normally put into releases, but we're releasing it in its current form, due to the large number of changes. If you do run into bugs, please post them on our Issue Tracker. Please use the current release version, Rawr 2.1.9, if you encounter showstopping bugs in Rawr 2.2.0b5. Thanks!
- Fixed a bug where relevant items and gemmings wouldn't be updated immediately upon switching models.
- Fix for the Direct Upgrades chart being broken in some models.
- More performance improvements to the Optimizer
- Added 'Load Possible Upgrades from Wowhead' feature. Check the 'Use PTR Data' item inside of it to load upgrades from the PTR Wowhead, as they're discovered on the PTR.
- Rawr.Bear: Fix for a minor issue with Savage Defense. Support for more 3.1 changes.
- Rawr.Cat: Support for more 3.1 changes.
- Rawr.Moonkin: Support for more 3.1 changes.
- Rawr.Mage: Support for more 3.1 changes.
- Rawr.HolyPriest: New Custom Role feature (please test this!)
- Rawr.Retribution: Support for more 3.1 changes.
- Rawr.Healadin: Support for more 3.1 changes.
- Rawr.Tankadin: Support for more 3.1 changes.
- Rawr.Warlock: Fixes for several more talents, pets, and glyphs.
- Rawr.RestoSham: Support for more 3.1 changes and some bugfixes.
- Rawr.Hunter: Fix for a display bug with AP.
- Rawr.ProtWarr: Support for more 3.1 changes.

Astrylian · 03/23/09, 11:46 AM

When I first released v2.2.0b5, I accidentally left the default data files marked as read-only, which makes Rawr throw an error when you try to close it, and it tries to save the data files to disk. I've updated the v2.2.0b5 zip file to fix this, but for any of the first 500 of you to download it, you can either re-download it, or just do the following:

1) Goto the Rawr folder, where you unzipped it.
2) Open the Data folder.
3) Select all, right click, Properties.
4) Uncheck 'Read-Only', click Apply, then click OK.

That should fix it. Sorry about that.

Kris · 03/23/09, 1:09 PM

Quoting a issue I posted on Codeplex, I feel it requires a little discussion here:

Beta 5 of Rawr suggests +32 sta +2% armor to be 2.5 times more valuable than 21 def, 5 blv meta. It also lists 104 AP, 15 crit to be much better than 15 def, 20 dodge shoulder patch. Same for most enchants and item upgrades. All recommendations suggest I replace def rating for str, agi and crit. And since I'm sitting on 541 defense atm, all those suggestions would take me under the def cap and make me crittable. Something sounds terribly wrong here, when DPS parts are placed higher than def ones.

The issue was explained partially and I can understand why going below crit cap is possible with current beta. What I cannot understand is why Master's Inscription of the Axe is rated higher than [Greater Inscription of the Pinnacle]. Are the default threat values so off bounds, that they make dps parts better than defensive ones? And if yes, what are the correct values I should work with? I know I can sort things by avoidance and such, but what I'm mostly interested is really "Overall" balance and that's where the Tankadin module is currently most unbalanced.

Astrylian · 03/23/09, 1:39 PM

I'm not totally familiar with the Tankadin model, but I'm sure that you can adjust the value of threat, to match how much you need it. Threat is very subjective; depending upon your raid group, and content, you may need more or less of it.

As for uncrittability, that's up to the user to watch for (and why it's clearly displayed on the stats tab whether you're crittable or not). It's expected that you'll probably use an Additional Requirement of "% Chance to be crit <= 0" when optimizing.

EDIT: Also, in your example comparison, keep in mind that you're comparing a Master's enchant (inscriber-only) to a Greater enchant. It's quite likely that a *ton* of thread will be more valuable than a relative *little* bit of mitigation/survival. Comparing an Inscriber-only enchant to an anyone-enchant isn't something you're likely to do though, you're probably looking to compare Master's to Master's, or Greater to Greater.