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

baldeagle · 02/06/09, 3:02 PM

Are there plans to include the Titan-forged leather helm of triumph and the boots?

Astrylian · 02/06/09, 3:04 PM

See the readme, Baldeagle, about missing items.

jonny · 02/07/09, 3:51 PM

I realise that a lot of the announced changes for 3.1 are still rather fuzzy, but once the PTR appears are there plans to add a 3.1 mode to the various models so we can see the effects on gear for ourselves?

Astrylian · 02/07/09, 6:45 PM

Of course.

Sengiratolom · 02/08/09, 7:12 AM

After selecting the "download upgrades from armory" option while running the enhancement module the tool gives an error and stops listing the values of items

here is the dialogue i get

************** 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.ToolTip.BaseFormDeactivate(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnDeactivate(EventArgs e)
at System.Windows.Forms.Form.set_Active(Boolean value)
at System.Windows.Forms.Form.WmActivate(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(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)

Astrylian · 02/08/09, 9:26 PM

If you get a 'Cannot access a disposed object' error, that's a bug in an old version of the .NET Framework. Uninstall all versions of .NET Framework that you have, and reinstall the latest from Microsoft (3.5SP1)

thedopefishlives · 02/09/09, 3:54 PM

I'm proud to announce the beta release, if you will, of Rawr.Moonkin Spell Calculation Engine 3.0. Now powered by Adoriele's WrathCalcs spreadsheet math, Rawr.Moonkin should provide a more accurate reflection of your moonkin's DPS for a given gear set and what defines "upgrades" for your moonkin. I have checked in the mostly complete work-in-progress, for those of you who have a mind to download and compile source code and give it a spin. The discussion thread on Codeplex has more information.

jula · 02/09/09, 8:58 PM

I'm trying to find the optimal tanking set for my tankadin alt. What I would like Rawr to do is find the best set it can from all items in game (highest "overall rating"). However i want to add two constraints:
1. uncrittable.
2. every hit must be either be fully avoided (for example dodged) or blocked. It is not very hard for a paladin to reach this while holy shield is up, and i wish to assume 100% uptime on that.

How can i do that ?

I noticed in the feral tank module under "optimize" you can add the requirement of "chance to be crit <= 0%" to meet the first constraint. However this does not exist for the tankadin module, and I still don't know how to add the second constraint.

Astrylian · 02/09/09, 10:58 PM

We're working on adding constraints like that to the Optimizer for the next version.

badhairday · 02/10/09, 4:49 AM

I'm puzzled why the optimizer constraints are per-model.

Tanks share a common set of desired constraints (uncritability at a minimum, %avoidance, %mitigation), casters share another (sp, regen), and melee/hunters another (AP), plus some stats everyone love: hit, crit. Seems odd that some models have these constraints and others don't.

Why not have every model have every constraint? It may not make any sense to have a Warlock be uncrittable, or a Prot Warrior to have spellpower>2000, but it seems like the code to check these could be shared across all models.

Then I wouldn't have to request an update to the Tank DK optimizer constraints, because there's no uncrittable option.

(or +hit, or expertise, or %mitigation, or anything else)

ebolad · 02/10/09, 5:45 AM

Originally Posted by badhairday

Then I wouldn't have to request an update to the Tank DK optimizer constraints, because there's no uncrittable option.

(or +hit, or expertise, or %mitigation, or anything else)

Those are per model because models have to calculate the values and not all models do it and/or do it the same way as the others.

And TankDK has the possibility to optimize for uncritability. Just set the Crit constraint to <= 0. I'll put the rest on the todo list.

Zurgat · 02/10/09, 7:45 AM

Looks quite good, most our mages are very happy with the tool.

However, what are the plans regarding implementation of these two models?

•Rawr.Rogue: Not functional for 3.0.
•Rawr.Warlock: Not functional for 3.0.

v2.1.7:
Rawr.Rogue/Warlock: Nothing new, yet, but wanted to mention that we have a ton of active development on these models lately, and new versions are coming soon.

Astrylian · 02/10/09, 11:43 AM

There's active development on both of those. Warlock is looking like it'll be ready for our next release. Rogue might be, but not sure yet.

badhairday · 02/12/09, 7:21 AM

Originally Posted by ebolad

Those are per model because models have to calculate the values and not all models do it and/or do it the same way as the others.

After pondering this for a while, I think I see your point. It does no good to optimize defense/resil to make a bear uncritable, for example, when they could have the talents, and just about every stat is affected by some class mechanic. Ok, stupid user educated.

And TankDK has the possibility to optimize for uncritability. Just set the Crit constraint to <= 0. I'll put the rest on the todo list.

Awesome. The crit constraint wasn't there when I looked, which is what inspired me to write. In fact, there were no constraints for TankDK aside from the main overall/survival/threat ones (I might have the names wrong here, at work right now).

I'll look again and try reinstall/redownload/nuke the site from orbit if still not there. Thanks for the heads up.

Edit: The crit constraint is there. Turns out it was a UTS error - user too stupid. I'm happily enjoying it now. Thanks again.

Squishypants · 02/12/09, 10:05 AM

When optimizing with the Holy Priest module I've noticed that, after I optimize it's been giving several T7.25 pieces really over the top values. For example, normally Mantle of Dissemination is > T7 but after optimizing the T7 is given a higher rating by far than any other shoulders. I've been able to get the values back to normal by unequipping all T7 but again when optimizing it does the same thing.

I'm assuming this has something to do with the value of the Set bonus's but some people really don't care about those and it's doing it with 3 pieces sometimes. Not sure if this is intended but it seems buggy to me, I don't mind it trying to get a 2pc bonus not the 4pc (or 3?!)in but would rather have the option.