It's more like always .
Your optimizer should tend to go slightly above Exp/Hit cap instead of below.

I mentioned this on the BiS thread, but I think it was lost in the midst of specific gear discussions:

Wouldn't crit rating have a different stat weight depending on the presence of 4 pc T9 bonus? Without the bonus, all crit would be valued less than it would with the bonus. I'm not sure that I'm smart enough to model it, but does anyone else share my view that a single weight for crit will not work?

Edit: I suppose this is dealt with by using the T9 bonus EP to represent the added value of crit, but then that bonus should have a sliding value dependent on your total crit rating, rather than a fixed EP number.

Zerack, I think there's an error in the stats for Shoulderplates of Trembling Rage. It should be 107 Str, not 115 (that's the Sta value).

I just ran the optimizer a few times. I used the Frost DW preset stats. I also ran using the stats from the first post on the revenge of the offhand thread. I found that unless I forced melee/spell hit it equipped me with ZERO +hit. As well as very little Expertise.

Is there anything I can PM/email you to help figure this out? Or was I doing something not quite right?

I also found the "Band of Draconic Guile" was not listed.

I also have a question about the weapon selections. It chose 2X bloodcrush cudgel over 2x Aledar's Battlestar. Is weapon speed wighting set up or enterable anywhere?

I am also curious if I can do anything to speed up the calculations? Is there a way to make the app multi-thread aware?

If you look at the gear.txt file that accompanies the application that's where he appears to pull the item data. In there I cannot find any weapon speeds which leads me to believe that his app does not handle them. Weapon speed is important of course, so this leads me to question the applications other hidden logic?

Opening up the source would help answer some of these questions if the author is willing to do so.

I don't think the program makes allowances for weapon speed. For the BiS lists I've just been including the slow weapons in my calculations and not bothering with the fast ones. Slow/slow is right for DW Frost, yeah?

To start out I love the program so thanks a lot for the hard work you've put into this. The question I have is when running the program after selecting a decent amount of items (both current and 10 man normal items from Ulduar and ToC) I continue to get a "Run Time Error '7' Out of Memory" message. When i watch the process in Task Manager the memory usage just goes threw the roof and then times out. Was wondering if you had any thoughts on how to fix this.

I encountered the same problem when selecting a large amout of gear (5 pieces per slot), mem usage goes through the roof and the app crashes. When i select just 1 - 2 pieces per slot, it can get all possible gearsets pretty quickly, but then hangs at the "gemming gearsets"calculations. The mem usage at that point is fine, it just doesnt seem to do anything. I've tried selecting large amounts of possible gems and just gem per color, nothing seemed to help.

And btw, thnx for making a application like this.

Zerack, unless you plan on selling this software, I don't see any reason to keep it closed source. I personally would be interested in contributing to the project if you were to host it on Secure source code hosting and collaborative development - GitHub or a similar code collab site.

I'll be posting a new version later today with some updates, but let me try and address some of the issues that have come up:

@dr_AllCOM3 - As discussed, there was a problem where the region wasn't being set to 1 after it did the region check. I think this should work in the new version without trouble, but my region checking is a hack at the moment that I'm not happy with. Let me know in the future if it continues to cause trouble. Regarding the optimizer tending to go over the hitcaps rather than under - that's not the nature of an optimization like this. Tendency would be to end up slightly under, which is technically optimal from a numeric point of view. I'm slowly getting around to fixing the hitcap / expcap forcing options, so that should suffice when they are available.

@elf-boy - If you are still having the issue where it generates sets with no +hit, please upload and PM me a text dump of the results of a calculation. That contains information I can use to determine what exactly is going on. Regarding speeding up the calculations, I'm working on it. I'm talking with someone about helping me make the program multi-thread aware which should result in good time savings, but it's not ready yet. Hang tight.

@radunio - The trinket issue was fixed. It is likely you are using the release that briefly contained a trinket error. Download again and reinstall and you should have no problems. Let me know if the issue persists.

@EvilNuff - The current version does not support weapon speeds, but I've added it in the next version. This should assuage some of your fears that the program is doing something mystical and / or arcane to derive set values. I assure you it is not.

@advocate70 - I'm unable to reproduce this error either on my development machine or on my two personal machines running the most recent code. Is anyone else having this problem?

@ deathsythe / orathar - I'll look into dealing with this. Can you give me an idea of how large the program is growing before crashing? So far I've optimized primarily for speed, but there are ways that I can make the program use less memory. In fact if speed wasn't an issue I could keep memory usage ridiculously low, but I don't think anyone would like those calculation times.

@Anathem - I'll consider making the source public as I've no plans to attempt to profit from this. My hesitation is that I do not by any means know what I am doing, and I'm fairly certain I'd be the laughing stock of the EJ community if anyone halfway competent looked at the code Regardless if there's something specific you are interested in helping with please let me know and perhaps we can get something set up.

I think that covers most of what was said in the thread since I last checked in. There's been some discussion about weights so I'm going to double check that they are all up to date with the respective threads before posting the next version, but hopefully that won't take long and I can get up a new version this evening. With apologies, Norg, this version will support weapon speed so you may have to do some recalculating. Please don't hurt me.

You won't be laughed at . You can be glad, if there are five people who at least understand the code. If helps a lot at bugfixing though, judging from my experiences from the sim. Afabar and me always find stuff to correct.