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

Deninkle · 05/15/08, 11:28 AM

I'm getting two repeatable errors with Rawr.Mage.

The first doesn't really seem to matter at all:

If I select any two handed weapon, then try to click on the off hand slot I get an error. I can continue on without further problems if I press "continue".

************** Exception Text **************
System.OverflowException: Overflow error.
at System.Drawing.Graphics.CheckErrorStatus(Int32 status)
at System.Drawing.Graphics.FillRectangle(Brush brush, Int32 x, Int32 y, Int32 width, Int32 height)
at System.Drawing.Graphics.FillRectangle(Brush brush, Rectangle rect)
at Rawr.ItemSelectorItem.get_PrerenderedImage()
at Rawr.ItemSelectorItem.OnPaint(PaintEventArgs e)
at System.Windows.Forms.Control.PaintWithErrorHandling(PaintEventArgs e, Int16 layer, Boolean disposeEventArgs)
at System.Windows.Forms.Control.WmPaint(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

The second is a bit more irritating. If I select an item and decide I don't like the gem in it, I press edit and change the gem. If I then left click on the same item as if I were to select a new one, I get another error. If I press continue, the selection menu for items goes behind Rawr. I also get the same error thrown up each time I click on it.

************** Exception Text **************
System.ObjectDisposedException: Cannot access a disposed object.
Object name: 'ItemButton'.
at System.Windows.Forms.Control.CreateHandle()
at System.Windows.Forms.Control.get_Handle()
at System.Windows.Forms.Control.GetSafeHandle(IWin32Window window)
at System.Windows.Forms.ToolTip.Hide(IWin32Window win)
at System.Windows.Forms.ToolTip.HideAllToolTips()
at System.Windows.Forms.Form.OnDeactivate(EventArgs e)
at System.Windows.Forms.Form.WmActivate(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Thanks for continuing to develop this excellent program!

Astrylian · 05/15/08, 11:35 AM

Ah, found the bug on your first issue. Thanks

The second one, I was hoping b14.1 would fix. Still perplexed with what's causing it, but I'll keep working on it.

Eyegore · 05/15/08, 4:35 PM

Does the ProtWarr model give any avoidance/mitigation value to expertise, in that it reduces parry hasted attacks from bosses? If not, and I get the feeling this is more likely the case (SoC apparently has 0 mitigation value), can we expect that soon? An option to enable/disable that would be nice as well, for bosses that are or are not subject to parry feedback.

Edit* Oh and thank you for this cool new tool of course. Also I am glad to see that faster weapons are scoring better on threat this version, that was bothering me and making me question what assumptions this thing was running under.

Althir · 05/15/08, 5:23 PM

Anybody started looking at Shadow Priests for Rawr?

Astrylian · 05/15/08, 5:27 PM

Nope. Would love it if someone did. If there are any C# devs that love spriest theorycraft around, ping me.

ezweb · 05/15/08, 5:39 PM

Boss parry haste is not modeled yet. I honestly haven't found enough information to make a good model in Rawr.

Information found for modeling so far:
http://elitistjerks.com/717512-post1371.html
http://elitistjerks.com/f31/t15257-m...cs/#post459820

If you have other links I may have missed on my first pass please let me know.

The value of expertise in reducing boss parry haste is affected by: hasted attack speed, threat cycle, windfury procs per cycle, player parry rate, boss attack value, boss attack speed and probably some others I haven't thought of. I could make a simple model without taking all those into account, but I was hoping to get some other features in first (custom HS's per cycle, better boss modeling: like attack speed) so that I could make a better expertise as mitigation model.

In b14, threat points were based solely on the limited threat cycle, and thus heroic strike threat didn't matter, in b14.1 I changed it to average limited threat and unlimited threat to get a better average. I hope to change that again for the next version to make the number of heroic strikes per cycle a user configurable setting and use that to determine threat points.

Binkenstein · 05/15/08, 6:37 PM

Originally Posted by Astrylian

Nope. Would love it if someone did. If there are any C# devs that love spriest theorycraft around, ping me.

Or are there any C# devs that want to do the coding part of modules, with help from theorycrafting non-dev types?

Spazzball · 05/15/08, 8:02 PM

In the Mage model for Rawr, after using the Optimizer it'll use two weapon enchants, and so I'll have a Sunfire enchant on my main hand weapon, but then another Sunfire on my off-hand. Is there any way to have Rawr fix it automatically, or are there any plans for it to be fixed? I suppose it's from the Warrior function, so I'm not sure if that's possible.

Edit: Ah, I'm sorry. Disregard my message. After using Rawr some more I've found that the second enchant to off-hand doesn't actually do something, but it's still checked.

Delrain · 05/16/08, 10:17 AM

Just noticed this this morning with both 14.0 and 14.1, the improved scorch debuff in Rawr Mage isn't modifying the fire damage as far as I can tell. When clicked, there is no change at all on the dps numbers from any gear. In comparison, if I check CoE+improved (+12.73% fire dmg) there is a noticeable jump in all numbers. This is under both 2/48/11 and 10/48/3 models. Bugged? or am I missing something obvious?

Suesse · 05/16/08, 10:21 AM

Trying specing out of imp scorch then toggling the debuff again. It could be that it's assuming you are applying it if you're speced into it.

Astrylian · 05/16/08, 11:51 AM

I don't think the talent matters, I think it's the Maintain Scorch checkbox on Options tab that matters as well. Is that correct, Kavan?

Kavan · 05/16/08, 11:58 AM

Yes if maintain scorch is enabled and you have the talent the buff is enabled automatically.

Saltycracker · 05/16/08, 12:06 PM

I have a question about the Healadin module; Is there any way to enable all types of armor besides just plate. It seems that the item comparator is only looking at plate and some cloth options. I added [Worldstorm Gauntlets] to the item database and they are not showing up as well as other mail items.

Eyegore · 05/16/08, 1:15 PM

Originally Posted by ezweb

Boss parry haste is not modeled yet. I honestly haven't found enough information to make a good model in Rawr.

Information found for modeling so far:
http://elitistjerks.com/717512-post1371.html
http://elitistjerks.com/f31/t15257-m...cs/#post459820

If you have other links I may have missed on my first pass please let me know.

The value of expertise in reducing boss parry haste is affected by: hasted attack speed, threat cycle, windfury procs per cycle, player parry rate, boss attack value, boss attack speed and probably some others I haven't thought of. I could make a simple model without taking all those into account, but I was hoping to get some other features in first (custom HS's per cycle, better boss modeling: like attack speed) so that I could make a better expertise as mitigation model.

In b14, threat points were based solely on the limited threat cycle, and thus heroic strike threat didn't matter, in b14.1 I changed it to average limited threat and unlimited threat to get a better average. I hope to change that again for the next version to make the number of heroic strikes per cycle a user configurable setting and use that to determine threat points.

Personally I would prefer an imperfect, if reasonable, approximation over completely leaving a relevant impact of a powerful stat out completely. If it is better from a programming standpoint to proceed with a more detailed model, or you just don't have the time and want to spend what time you have doing it right, that's cool. It might at least be reasonable to note somewhere that expertise gear may be somewhat undervalued in the current model, forgive me if i missed it, but I did not see that warning anywhere. From what I have seen and experienced it is generally considered a very desirable stat, not just for aggro, but specifically because the avoidance component of it's behavior specifically mitigates the most dangerous type of incoming damage: the unexpected spike. I wish I could be of more help in actually finding a solution, but those links you have are where I would have looked myself and are the best resources I have seen on the issue. Thank you for your effort in putting this together; I don't mean to find fault, but I would also love to see this become the best tool it can be.

Astrylian · 05/16/08, 1:21 PM

We will, Eyegore. It's just out first version, still lots of features to implement.