Rhadamanthis

Thanks for these values, I'll borrow them for my addon pre-saved scaling values if you don't mind.
I must say though that 2pt9 looks a bit high...

 

Kryptik

But it isn't really when you consider all that the 2pc gives you.

Increased overall pet DPS and crit percentage, thus higher uptime on Empowered Imp

Higher uptime on Empowered Imp then gives you more personal DPS.

 

twistedmage

Lovely little tool to play around with, speeds up the lootrank trawling after calculating equivalence points.

One thing it is missing that would make it more useful for demonology warlocks is a weighting entry box for stamina.

 

P51mus

I went through the gear list and manually added "Heroic" to the end of the names of all the heroic items, so they can be excluded from the calculation without removing the normal version as well.

Is there anywhere I can upload/send this modified file so other people can use it as well?

 

mjball

Post it to this thread, just like how Optigear itself is attached in this post.

 

dukkh

It looks like something is wrong with optimization.
I was trying to find BiS set for 10ppl and needed 446 hit rating.
Surprisingly OG was unable to find such a set – all his set was limited to 400hit.
No items were excluded; latest 0.69a version. All weights and set bonuses were default (see screenshot)
Can anybody check this issue with previous version of OG? I suspect that “adjusted pruning process to speed up app” messed something.

 

jeffason

Seems like the t9 4pc is not being calculated correctly... I removed all kel'thuzads set and left guldan's, then removed the heroic versions from the loot list. t9 2pc seems to be correct but if I crank up 4pc to insane values like 2400 they are still not selected...

 

Kryptik

I was having the same problem sort of. Whenever I wanted to choose JUST the 245 pieces it wouldn't work at all, so when I selected both Triumph from the option (the 245 and the 258) it obviously picks the 258 pieces. So what I did was I went into the Gearlist.xml and changed all the 258 items to Guldan's XXX of Triumph2, but it still didn't work. So then I went into the Excluded.xml and saw there was still two versions of the 245 for each pieces. So I just deleted one of each for all the set pieces. After doing that the 245 pieces are working correctly.

 

mwaf

On the subject of T9 pieces, is there a reason why all of the Kel'Thuzads XXX of Conquest pieces have T9 disabled:

 

VenomByte

There's a hard-coded limit of 400 to the target hit rating. It's been this way since the first release. I'll up it to 500 or something. The idea was to prevent it calculating useless sets with huge amounts of hit, which would never actually be any use. Thinking about it though, a better method might be to set the hit value of any gear combination which is > target value to be equal to the target value.

 

mjball

Why would you set the hit value (of a gear combination which has hit value > target value) to be equal to the target value? I don't see how that would prevent Optigear from calculating sets with uselessly high hit values, so it seems arbitrary. In fact, hardcoding any upper limit on hit (as you said you're currently doing, with a value of 400) seems like a bad idea because it means that you'd eventually have to change that hardcoded value when the level cap is raised.
Instead, my recommendation would be to either (a) provide an additional input field where users can input their own upper limit, either in terms of hit rating or percent, or (b) replace your arbitrary upper limit of 400 with a less-arbitrary hit percent. By option b, I mean that OptiGear would have some hardcoded X% hit rating (I guess it could be stored as value and not a percent if you don't mind updating for subsequent expansions). Then, it would discard gear sets that have more +hit than the target hit rating plus the X% (reasonable values of X might be 1 or 2). If you allowed users to enter X themselves, this would be equivalent to my suggestion (a).

 

jeffason

Thanks for the help, this was definitely a better way to force choosing ilvl245 instead of ilvl258 (which is what I want). However, I'm still having a problem using your method where it does not select 4pc t9 no matter how high I pump up the set bonus value... Are you not having an issue where it will always only select 2pc t9 and then other crafted items?

 

Shayo

First time I got a chance to take a look at your app. Good work so far. In a future release, could you possible include the item level in the gearlist.xml? Wowhead has it in this format:

and since you're already pulling xml from wowhead and parsing it, getting the data from this particular div should be no more work.

This would also allow for individual filter requests, such as "We're a 10 man exclusive guild and not up to heroic yet, I'm going to filter by ilevel 226-239" or "My 25 man guild hasn't downed any of the heroic level mobs, I want to calculate BiS for ilevel 213-245" and similar scenarios. This could seriously help cut down on the number of requests for BiS lists.

If you're not interested in making this modification, is there source code available so I could make the required changes to add this functionality? I'd be happy to contribute to this project.

 

VenomByte

Here is why you would do it:

When you calculate a gear set, you don't care if it has too much hit. You care about every point it has up until your desired cap value, and everything after that is worth zero. When you are discarding gear combinations (or partial gear combinations) you care about hit, dps weighting, meta req, number of Tx pieces, and so forth. Gear pieces are added incrementally, so setting higher values of hit to lower ones allows you to improve the pruning efficiency of the system, thereby preventing almost all of the excess hit sets from being generated in the first place.

For example, lets suppose that after adding gear slot X under the current system we have the following gear sets(assuming only hit and dpsweight are relevant):

Set 1 - 300 hit, 2000 dpsweight
Set 2 - 290 hit, 2100 dpsweight
Set 3 - 280 hit, 2100 dpsweight
Set 4 - 260 hit, 2300 dpsweight
Set 5 - 250 hit, 2350 dpsweight

Set 3 gets discarded because it's inferior to set 2.

Now you combine these sets with gear slot X+1, which has two items:
Piece 1 - 0 hit, 300 dpsweight
Piece 2 - 35 hit, 100 dpsweight

This gives you
S1/P2 - 335 hit, 2100 dpsweight
S2/P2 - 325 hit, 2200 dpsweight
S1/P1 - 300 hit, 2300 dpsweight
S4/P2 - 295 hit, 2400 dpsweight
S2/P1 - 290 hit, 2400 dpsweight
S5/P2 - 285 hit, 2650 dpsweight
S4/P1 - 260 hit, 2600 dpsweight
S5/P1 - 250 hit, 2650 dpsweight

S4/P1 and S2/P1 can be pruned.

If you have a target hit value of 300, and can therefore set all values >300 to 300, S1/P1 becomes superior to S1/P2 and S2/P2, so these two can be eliminated also. As you add each gear slot in turn, this will significantly reduce the exponential growth factor at each stage.

 

jeffason

I'm having issues with the application freezing at "Adding body part 22 of 22" the last few times I've tried using it. I've made some changes to the stat weights, t8/t9 bonuses, and exclusion list. OptiGear 0.69 Alpha

 

P51mus

It'll stay on 22/22 for a long time, that's normal.

Making it look like it's still doing something while it's on that step should probably get changed, but keep in mind it'll take at least several minutes to run through the last step until then.

 

jeffason

It would hang for 3+ hours so I had to restart the app. It wouldn't actually start working again until I changed some gear configuration. I suspect it is possible for the app to fall into infinite loops in some configurations.

 

Inarathra

I can further cite that the data imported from wowhead is kind of flawed, and the app gets very confused by the flawed data. ie. Most of the new "heroic" ilvl 258 stuff is named identical to the ilvl 245, which I am finding more and more absurd on Blizzard's part.

Simply hand editing the gear xml to include anything special on the heroic version (iw. I added (h) for now) until wowhead and Blizz adjust things a bit will work, however.. that is a -lot- of editing, it's not just tier.

Also keep in mind that the tier9 gear is also not labeled as such in the gear list, either, which likely will make the "Use T9 Bonus" not function very well. You can hand edit this, too, and it appears to work. <t9>1</t9>


One thing I cannot hand edit or fix is the staff enchant. It always uses the MH weapon 63sp chant, and, if you 'lock' the staff chant it breaks the entire gearset. Setting the staff I am using to <isStaffEnchant>true</isStaffEnchant> makes no difference. Not that is matters too much in the end, as it is simply a sp bonus over the other and I cannot see it affecting any gear choice except a mh/oh vs staff (which you should be able to eyeball.)


One other thing.. can anyone give a -good- tier9 bonus weight for affliction T9-53/0/18? I have been using ~2p-50/4p-150 though that really is a wild guess. I just can't see an avg boost from the t9 2p being much from an afflic pet, and most of the quibbling in thread is related to the destro emp imp buff, which aflocks do not have.

The 4p t9, however, is quite nice, and will be a pleasure once I can get all 4 pieces. It is such a lame 2p bonus, and, the 4p such a nice one, that it almost does take a nice tool like this to help you work out what pieces to to in what order for tier. According to most simulations, I will be swapping gear and gems around a ton to maintain optimal dps in the 369hit mark. This includes banking new t9 at times, or, swapping from Lifeless touch 248 gloves to t8.5 gloves when moving a t9 head in (unless I get some other nice hit gear in the meantime... )


On a side note: can anyone confirm a sanity check for me... If -not- weighting hit (ie. max dps, trash/miniboss set) would [Firesoul] + [Igniter Rod] beat [Intensity] for an afflock, and, if so.. how much? The BiS tool is saying so if I set hit low. (See the staff chant glitch above, too, )

 

Demondan

Gul'dan's Gloves of Triumph don't seem to be included unless both are in the included list. Also, there's no way to tell which one it is, so adding tooltips would be cool.

 

Inarathra

That is part of the issue that I am posting about. And, obviously, if you include both, the heroic versions, which are vastly superior to the non-heroic, will undoubtedly always be chosen.

The interim "fix", or "hack" rather, is to open your gearlist.xml file (any editor will do fine, even wordpad.. though an xml editor really makes the job easier)... and do a search for "guldan". Find all the items that are there and check their spellpowers, the one with obviously more is heroic.. then tack a little(h) or -Heroic or such in it's name. Note, strangely, the imported data has no ilvl field.

Changing the 0 to a 1 in the t9 field is also probably helpful, as I do not think the Optigear app will know it is t9 to apply the set bonuses. (thats just speculation on my part, but it seems to work for me after doing so).

Also, open the excluded.xml and sear there for guldans, too. Remove any/all entries or the app will get confused.

Finding all the t9 equivalent with a heroic counterpart in the list is a much harder task. I suggest only changing the items you know you have or will be looking at shortly. Again, add h or heroic to the name, and remove them from the exclude.xml.

Keep in mind, this is simply scoring each item and set bonus with numbers. You really need to play around with it and take note of the scores and differences of the scores before jumping to any wild conclusions. It will sometimes also tell you to gem in certain ways as it moves hit around to the least point-degrading spots, but, remember it will always think something 0.0001 point higher is better, you need to use a bit of common logic.

Nicely, is also keeps track of the 2blue gem requirement for you, as well as the socket bonus+multicolor gem choices.

Most of the glitchiness thus far is directly attributed to wowhead's incomplete data and blizz' asinine naming choices. I swear Blizz was asleep at the wheel naming the top gear in the game exactly the same as the non. We have to remind people in raids for ToC to double check what they are bidding on to make sure they didn't spec out the heroic item before they blow a ton of dkp... as I did. Twice. [Sandals of the Mourning Widow] and [Pants of the Soothing Touch]. Both excellent items, but, their heroic counterparts stats made me offer up a lot more dkp than I should have.

 

Xebeche

Are Optigear’s built-in stat-weights still acceptable, or should others be used now? I have been adding the T9 set weights as suggested in this topic, but other than that, I’m using the built-in weights.

I know how to get my scale factors via Simcraft, but it generates them based on the gear I already have equipped (or a gear set I tell it to use). Since Optigear is suggesting an entire gear set based on my scale values, it doesn’t seem to be a good idea to incorporate Simcraft’s values into Optigear.

I apologize for using the phrases “stat-weights” and “scale factors” interchangeably.

 

Celean

Recently I ran into a problem using optigear, concerning the 4 piece T9 bonus. Optigear seems to not take the 4 piece bonus into account for the ilvl 232 gear.

I made sure all the Kel'Thuzad conquest gear is enabled (added to the included gear list). I altered the gearlist.xml file to add T9 to all Kel'Thuzad gear (which is off by default for the ilvl 232 items). Due to this the 2 piece T9 function now works perfectly. However even I if I plug in 5000 as a number for the 4xT9 weight it will not equip 4 items. I understand that the ilvl 232 items are not that great, but with such a dps buff I would expect optigear to equip 4 pieces of T9.

Is this a known bug? Or am I missing something?

Below are the links to the output and the gearlist:
http://img36.imageshack.us/img36/549...raftoutput.jpg
http://img39.imageshack.us/img39/701...atgearlist.jpg

 

Cigaras

Open gearlist.xml and find those items, you'll notice a tag <t9>0</t9> whenever on ilvl 245 and 258 set items the tag is <t9>1</t9>.

However even having <t9>1</t9> I can't force it to "equip" 4 set pieces set whatever bonus weights I enter.

P.S. would love to get a source code

 

Reeshet

It seems like this would fix a large number of the problems if the gearlist xml file had the item level on it. You still wouldn't be able to tell the difference easily between a ToC 25 ilvl 245 item and a TotGC 10 ilvl 245 item, but I don't think that's the point that's causing the confusion. Most of the problems are between gear that's same name as different iLvl gear.

This would also allow a pretty easy filtering mechanism. You could say you want to Exclude all gear below item level 226 and above 245 if you only wanted to look at Ulduar, ToC10 and ToC25 gear.

 

Celean

Like I said I allready altered the xml file, the tag is allready set to 1. This made the 2 pice bonus work, the 4 piece bonus however does not work.