As some people roaming the official DH forums might have seen already there is a project running to create the ultimate user-friendly D3 calculator. We have named this calculator in honor of our good friend: ERR37.
It is currently very much a work in progress, slowly building it up piece by piece. But we are getting there, having most basic implementations in there. These currently include:
Basic damage calculation for Demon Hunter ( including archery, sharpshooter and steady aim )
Adding items to a character, building them up stat by stat ( not all stats implemented yet )
Saving and Loading of characters
A seperated calcuator from the main application, allowing us to develop a Silverlight and possible a Mono for Android version in the future
Passive Skill damage modifiers implemented for all classes
Follower Buff support, for when you run with your Scoundrel or Enchantress
Dual Wield support
Better error handling
Should you run into an exception, you have the option to send us a report of the error.
This report includes data from the application namely:
The exception message.
Stacktrace of the exception.
Character data that you were working with.
Possible extra notes that the user would give us about what he was doing.
A lot of UI changes, though minor, that should make handling the application easier
We have an icon!
Known issues of 0.4:
You will be unable to load in save files from 0.3 without manually editing the save file! If you want to do this you can do the following:
Open the .e37 save file with notepad
Find the line where it says
You can find our project, and the source for it aswell, over at our Google Code page. You are very much free to grab the source and mess around with it. Even better if you wish to contribute to the project, we are always on the lookout for help from other devs.
For a bit of technical information:
The application is written in C#. The current front end of the application is done in WPF. The Calculator itself is a class library with a Portable Class Library to communicate in between. This iwll allow us to add Silverlight and Mono for Android, any other .net front end to the calculator using the same code. The WPF client is using the Caliburn.Micro framework in conjuction with Ninject.
Why not make it purely online? that way it will work from iOS and WP as well
The online version will be done through Silverlight. The reason for this is simply because neither of us two project starters ( me and pdluke ) are Obj-C devs but we are both C# devs. We realise this will exclude iOS from the the possible targets, for now. However because Silverlight -is- supported on Mac OS atleast that will in the nearby future be supported.
If we can find a developer that has knowledge of Obj-C then we will not hesitate to take on the prospect of making this fully mac compatible
We have a bunch of issues sorted in v0.3, with just one nagging one left. We hope to rectify that issue today and hopefully push v0.3 out tonight. This version will include basic support for all classes and a bunch of UI fixes
The basic implementation for all classes have been put in. This does not include passive of active skills just yet, it will only calculate the damage from your gear alone. While we realise this is not perfect yet, it will help people identify upgrades at least.
Various UI fixes and improvements
Stability gain obtained
Saving and Loading of character sheets has been improved
Our current plan is to release v0.4 in multiple parts.
This means that v0.4 will include the core improvements to the application. v0.4.1 will be released shortly after and will include all active and passive skills of a class, if this is not in the core v0.4 yet, which it probably will. If that is the case then v0.4.1 will be a different class. The same goes for v0.4.2 etc until all classes have their skills included.
It will take time for us to implement such amount of data, hence we choose for this segmented release. We realise this might dissapoint people who are playing class numero 5 and wish to use our calculator, we can only apologize. Time is limited for us too : )
As always, if you find any issues or wish to make suggestions please do so on our issues page on google code. It helps us keep track of it and allows other players from different sources than D3Fans to chip in!
I went through it quickly before heading off to bed and my guess is that your weapon has not got a minimum and/or maxmimum damage attached to it.
In v0.4 we will have better error handling to allow us for better bug tracking.
Thanks for your report, though there is no need to copy over the error onto the thread here. We check the issue page often enough and will spot your problem when we start working on it again. : )
Ruilo, please save your character ( if you have not already ) and attach the save file to the issue post on our tracker. It will make it much easier for us to track down why you are getting this result : )
We shall be cleaning up the build up tumbleweeds in this thread in the near future. Please bear with us for a bit longer for the next update! Remember that we are eager to hear suggestions. So if you wish to add one; please do so on our issues page : )
Correct. There is a margin of error because we don't know the exact values from in-game data due to rounding, as you said. Perhaps when the D3 API is released we get more accurate values, atleast from items worn by players. It would reduce the margin of error.
Our current developer version has a nice and shiny error reporting function in it that dumps exceptions straight to our google issue page, no longer is it needed to have you as the user do it manually. I am hoping to expand this feature to allow for suggestions and manual error reporting ( For issues that are not erroneous code-wise ) from within Error37 itself too however that is for v0.5 at it's earliest point.
Our backend developer is currently a bit time constraint and such our next version will likely not come out until late this weekend if not early next week. We'll see how far we can get it.
Since you released to public, here are some comments/suggestions.
1. Typos on About page: Artwork not Artword and Entertainment not Entertainement
2. Re-order all the dropdowns to be sorted ascending by name. It is very difficult to find items
3. Get yourselves an icon! I hate the default .Net icon.
4. When viewing the Add Item Stats popup, please add which item you are adding stats for in the header. IE: "Add Item Stats for Gloves"
Nah, far from 1.0. We have a lot of things planned before we bump it out of beta!
But please, if you could be so kind, put this on our issues page as a suggestion. It keeps it sorted and clean and people from different sources besides D3Fans will see the suggestion too! : )
Edit: Apparently I cannot post links anymore because I need 10 posts..? o.0
Anyway... just copy paste it then >.> : code.google.com/p/dh-dmg-calc/issues/list
We are in need of some user input currently on what to do with the buttons that represent the character item sheet. Right now they are very dull looking buttons that don't really serve any purpose but to be able to click on them to edit the stats.
I would like to know from you guys what you think would be a good idea to put on those buttons that would both make sense and be usable. Remember that for items like the Neck and both rings the space is limited!
I will sit down this weekend and give it a run - I will be sure to send my thoughts and suggestions your way
Awesome, thanks for the interest!
Please file any of your suggestions over to our issues page, keeps things organized! : )
We would still like to have some suggestions about what to do with the worn items buttons.
I planned on taking a look at it yesterday afternoon after work, but I completely forgot. If you want to remind me, post here around 5 EST (8 hours from now) so I see it after work. Otherwise it's up to my brain to remember, and that's not likely.
As some people roaming the official DH forums might have seen already there is a project running to create the ultimate user-friendly D3 calculator. We have named this calculator in honor of our good friend: ERR37.
It is currently very much a work in progress, slowly building it up piece by piece. But we are getting there, having most basic implementations in there. These currently include:
You can download the latest version here by clicking this shiny yellow link!
Changes that include in this version:
This report includes data from the application namely:
The exception message.
Stacktrace of the exception.
Character data that you were working with.
Possible extra notes that the user would give us about what he was doing.
Find the line where it says
and change it with:
next for every item you wear you need to change every line where it says
to this
Save the file and you should now be able to load it just fine in 0.4+.
-------------------------------
You can find our project, and the source for it aswell, over at our Google Code page. You are very much free to grab the source and mess around with it. Even better if you wish to contribute to the project, we are always on the lookout for help from other devs.
The project is currently maintained by:
The application is written in C#. The current front end of the application is done in WPF. The Calculator itself is a class library with a Portable Class Library to communicate in between. This iwll allow us to add Silverlight and Mono for Android, any other .net front end to the calculator using the same code. The WPF client is using the Caliburn.Micro framework in conjuction with Ninject.
The online version will be done through Silverlight. The reason for this is simply because neither of us two project starters ( me and pdluke ) are Obj-C devs but we are both C# devs. We realise this will exclude iOS from the the possible targets, for now. However because Silverlight -is- supported on Mac OS atleast that will in the nearby future be supported.
If we can find a developer that has knowledge of Obj-C then we will not hesitate to take on the prospect of making this fully mac compatible
Ha. Bagstone.
We are pleased to announce our release of version 0.3, which will pave the way for 0.4; a version scheduled to bring the difference.
You can get it by clicking this shiny long link
The release notes for v0.3 are as follows:
This means that v0.4 will include the core improvements to the application. v0.4.1 will be released shortly after and will include all active and passive skills of a class, if this is not in the core v0.4 yet, which it probably will. If that is the case then v0.4.1 will be a different class. The same goes for v0.4.2 etc until all classes have their skills included.
It will take time for us to implement such amount of data, hence we choose for this segmented release. We realise this might dissapoint people who are playing class numero 5 and wish to use our calculator, we can only apologize. Time is limited for us too : )
As always, if you find any issues or wish to make suggestions please do so on our issues page on google code. It helps us keep track of it and allows other players from different sources than D3Fans to chip in!
In v0.4 we will have better error handling to allow us for better bug tracking.
Thanks for your report, though there is no need to copy over the error onto the thread here. We check the issue page often enough and will spot your problem when we start working on it again. : )
tldr;
bump
Our backend developer is currently a bit time constraint and such our next version will likely not come out until late this weekend if not early next week. We'll see how far we can get it.
1. Typos on About page: Artwork not Artword and Entertainment not Entertainement
2. Re-order all the dropdowns to be sorted ascending by name. It is very difficult to find items
3. Get yourselves an icon! I hate the default .Net icon.
4. When viewing the Add Item Stats popup, please add which item you are adding stats for in the header. IE: "Add Item Stats for Gloves"
Good work so far guys, looks ready to be a 1.0.
But please, if you could be so kind, put this on our issues page as a suggestion. It keeps it sorted and clean and people from different sources besides D3Fans will see the suggestion too! : )
Edit: Apparently I cannot post links anymore because I need 10 posts..? o.0
Anyway... just copy paste it then >.> : code.google.com/p/dh-dmg-calc/issues/list
I would like to know from you guys what you think would be a good idea to put on those buttons that would both make sense and be usable. Remember that for items like the Neck and both rings the space is limited!
Where has everybody run off too? D:
Awesome, thanks for the interest!
Please file any of your suggestions over to our issues page, keeps things organized! : )
We would still like to have some suggestions about what to do with the worn items buttons.