Hello, I am having troubles having updated trinkets in my drop-down menu, I have downloaded the latest version multiple times, any help would be appreciated
Sometimes EnhSim GUI will point to old versions of the actual EnhSim application. The path is in the bottom right hand corner of the GUI. Point it at the latest version of the app and you should be good to go.
If you're asking about selecting the latest trinkets, sometimes they're not named so you'll have to export from ShockandAwe or know what the corresponding #'s are.
Nothing from the newly added sets/trinkets will show up in the gui since the source for the gui isn't available thus cannot be edited, so the new stuff can't be added as long as someone manages to decompile it.
Nothing from the newly added sets/trinkets will show up in the gui since the source for the gui isn't available thus cannot be edited, so the new stuff can't be added as long as someone manages to decompile it.
As the poster above you suggested you can type in the item id into the trinket and relic fields. If you export from ShockandAwe or Rawr you'll notice that they both export in this fashion.
If you're having trouble figuring out what the item id for a particular trinket should be, look it up on wowhead and the number in the url will be the id.
I'm an orc with a fist weapon MH and mace OH. when i sim for expertise, i get around 1.14 for expertise when i'm at 26/21 (MH/OH expertise) and 0.6 for 28/23 (Have to call the fist weapon an axe in enhsimgui since it doesn't include "fist" as an option). But I see a lot of well-known top enh orc shamans at 31/26 expertise on wow armory. Would different gear really make that much of a difference? Based on enhsim I was going to forget gemming expertise past 26 on the MH but I would appreciate any thoughts.
I'm an orc with a fist weapon MH and mace OH. when i sim for expertise, i get around 1.14 for expertise when i'm at 26/21 (MH/OH expertise) and 0.6 for 28/23 (Have to call the fist weapon an axe in enhsimgui since it doesn't include "fist" as an option). But I see a lot of well-known top enh orc shamans at 31/26 expertise on wow armory. Would different gear really make that much of a difference? Based on enhsim I was going to forget gemming expertise past 26 on the MH but I would appreciate any thoughts.
Some of them also may be having issues shedding that much expertise as well. See if they are gemmed for that much and if not, then that may be your answer.
I'm an orc with a fist weapon MH and mace OH. when i sim for expertise, i get around 1.14 for expertise when i'm at 26/21 (MH/OH expertise) and 0.6 for 28/23 (Have to call the fist weapon an axe in enhsimgui since it doesn't include "fist" as an option). But I see a lot of well-known top enh orc shamans at 31/26 expertise on wow armory. Would different gear really make that much of a difference? Based on enhsim I was going to forget gemming expertise past 26 on the MH but I would appreciate any thoughts.
Probably the EP calculation in the second case is going beyond the expertise cap for your offhand. I would recommend you check the EP value you have set for expertise.
Probably the EP calculation in the second case is going beyond the expertise cap for your offhand. I would recommend you check the EP value you have set for expertise.
It was true in the 0.66 case, but not in the 1.14 case, and I fixed it so that it would just hit expertise cap on the OH and ran it again, came out to be 1.03. Still doesn't make sense to gem for expertise in that case, so I'm still wondering why some were. I'm just hoping to get a slow axe soon, though.
any info for OSX users? ienhsim (the Cocoa GUI) is still the 3.1 version (should be the same engine of EnhSim 1.7.x)
and the latest EnhSim release doesn't include OSX command line anymore. I tried to dwonload the latest repository revision, but the included executable seems to be out of date, it outputs:
Totem totem_of_electrifying_wind not found.
EnhSim version 1.7.0.3 by Verges: xxxxxxx@gmail.com
A preliminary version of the EnhSimGUI is now available from http://dl.getdropbox.com/u/561320/EnhSimGUI.zip. The new items aren't added yet, but some of Rouncer's requested changes are in since they were easy to do at the same time as the code cleanup. This is just the first step to make sure that the source was decompiled and put back together into a functional application.
If people could please test with their existing config files, rawr and shock and awe and let me know how it works. My testing showed that everything worked well except for some odd things from severely out of date files.
Once I've got some feedback I'll get this added to the official release and start working on additional upgrades/fixes from the community.
Cool that's easy to fix and I'll just put something in for it with the next feature version. I'm just hoping for no crashes or unusual behavior.
Please everyone make sure that the files written out match and provide the same results when run for simulation or EP values. That's the truest test if this whole experiment has been a success.
One other issue I discovered for myself. If you cut and paste in from rawr or shock and awe your rotation will be wiped out. This will be fixed in the next trial version I put out (probably tomorrow).
I'm an orc with a fist weapon MH and mace OH. when i sim for expertise, i get around 1.14 for expertise when i'm at 26/21 (MH/OH expertise) and 0.6 for 28/23 (Have to call the fist weapon an axe in enhsimgui since it doesn't include "fist" as an option). But I see a lot of well-known top enh orc shamans at 31/26 expertise on wow armory. Would different gear really make that much of a difference? Based on enhsim I was going to forget gemming expertise past 26 on the MH but I would appreciate any thoughts.
Many of those shamans with 31/26 are using gear that is T8 BiS (meaning gear that is best in slot prior to CotC T9 content), which include T8.5 shoulders, T8.5 gloves (or the Yogg 10HM leather belt), Godbane Signet and Caress of Insanity, which give a total of ~140 expertise.
Your sim values mean that gemming expertise at the 26/21 level is still better than gemming AP but at 28/23, you're better off just being slightly short of expertise cap and gemming AP. Therefore, I'm guessing that at 27/22 or so, you're already better off not hitting expertise cap on your offhand and simply going for AP (or haste...).
31/26 is just a relic of pre-3.2. I'm sure that we will see more shaman with un-capped expertise on their off-hand (if possible with a fist/axe and then a mace OH), especially since T9 seems to have less expertise than previous sets.
I copied and pasted my enhsim folder to new test folder, then replace enhsimgui.exe and ran it. Loaded up my config file and hit Simulate, no problems at all. Same numbers as the old enhsimgui.exe but when I hit Calculate EP Values I get the following error message. Yes it is pointing to the correct enhsim.exe executable.
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.ArgumentException: Empty path name is not legal.
at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options)
at System.IO.StreamWriter.CreateFile(String path, Boolean append)
at System.IO.StreamWriter..ctor(String path, Boolean append, Encoding encoding, Int32 bufferSize)
at System.IO.StreamWriter..ctor(String path, Boolean append)
at EnhSimGUI.MainForm.writeConfigFile(String filename)
at EnhSimGUI.MainForm.mCalcEPValuesButton_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.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)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///c:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
EnhSimGUI
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/enhsimtest/EnhSimGUI.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
Microsoft.mshtml
Assembly Version: 7.0.3300.0
Win32 Version: 7.0.3300.0
CodeBase: file:///C:/WINDOWS/assembly/GAC/Microsoft.mshtml/7.0.3300.0__b03f5f7f11d50a3a/Microsoft.mshtml.dll
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
Okay so I don't think this has been discussed lately, but given the large number of Off-set pieces in ToC with armor pen on them, I started playing around with my ArP numbers a bit. Of course if we had other options, I wouldn't even bother doing this, but since we're probably going to have to deal with a few pieces with ArP on them, I figured I'd see how much it would take to actually make it good. At 50%ish ArP sims higher than AP and at 60%ish it passes haste (for my config at least).
My question is, has anyone tried fully gearing/gemming for it on live? I only checked by bumping up the value in the sim, I haven't set up a gearset w/ it on chardev, only because most of the pieces aren't in the DB yet.
Next week, when heroic is available, the pieces should be in the DB, and I can sim the gearset, but for now, do you guys think gemming it up to 50% is viable once you have a few pieces?
Well, the question is, was it also nerfed for shamans? We already have a different value of haste rating than other classes, maybe Blizzard now does the same for ArP. Which would make sense, considering our damage composition.
Since we all know the exactness of the enhanced shaman rotation (priority) , why is it not simply standardized into the Enhsim?
Why remove a very useful feature? That would be like setting the AC on all cars to 70 degrees since that is what most people want it set to. Besides that optimum rotation has changed through the course of the expansion and now even includes MW4-LB and even MW3-CL (depending on which totem you are using). For all we know LL could end up moving very high up the priority list when Quaking Earth is fixed and if that feature was removed we would have no way of knowing.
I am going to risk the infraction because the irony is just too sweet...
With regards to ArP, has anyone heard any more information on this? I am reading a 13% nerf to the total amount of armor penetrated by current ArP ratings. Is this a bug on PTR or intended?
For some reason whenever I hit calculate EP values I always get an error unless I uncheck MW_5 and SW in the priority rotation. It gets an "Enhancement Shaman simulator has stopped working" error. Is there a way to fix this?
Is anyone else simming 20/51/0 well? This is with 4 points in Reverb (0.8s reduced cooldown on on shocks) taking a points out of imp. shields, imp. SS, AK and shamanistic focus. I have this coming out almost 50DPS higher.
I don't know how well this works in practice since that appears to be a lot less mana efficiency and while mana isn't an issue at the moment, it might be with this config.
08/26/09, 6:12 PM
Similar Threads
