The changes we are making in 0.5 are requiring more rewriting of earlier code than anticipated, on top of that development time from some of the project members has been low the last week or so. We are still working on this project, but it is going slow.
Apologies for those wanting the proposed functionality, it will take longer than we hoped
That is really strange, why it would load the page but not send the report.. Some security issue perhaps preventing applications from connecting to the internet?
Oh dear.. then it has trouble connecting to my server
Edit:
Just tested my server and it is online and operational as it should. I don't know why it would not connect to the service. Could you see if this page loads for you? http://nensec.no-ip.org:1337/ErrorReporter.svc
Another suggestion, one I'm guessing you guys already have plans for...but seeing all the stats that you are using to calculate the DPS would be nice. Things like Primary Stat Total, Crit / Crit Damage, Weapon Speed (for each weapon and then weapon average maybe).
Shouldn't be too much coding, it's simply displaying the cumulative values you're already using in the DPS calculation.
Yes, 0.5 is going to be a version mainly focussed on the UI. This will be part of it.
Also, the DPS calculation is off by about 200 DPS for me, not sure why that would be.
EDIT: Just upgraded an item (increased primary stat by 130) and now it's off by 660.
Calculations are always going to be off because you don't know the exact values that D3 uses. You just see rounded values in-game. We decided that an error margin of about 500 DPS above or below is acceptable. However 660 is a bit much. Do you think you can create an issue on our google code page and attach your save file to it? That way we can look where the inflation is going on.
If you do, please be so kind to include your in-game stats too. Thanks!
I have an error margin of 20,000 damage with sharpshooter on and 30,000 with sharpshooter off... I cant save you the file because when i save my character it crashes the program...
There's clearly a math issue somewhere as i rechecked my stats a dozen times.
That makes me think you added in your +elemental damage too. Don't do that, it is already incorporated in the weapon damage values you see itself. If this is not the case then please let us know
Alright let me start off by saying I love this project and hope for the best with it. My issue is a two fold one downloaded v4 no issues there. Input all my data again because I didnt feel like editing saved files coding. Calculate for my dh and get a dps variance of 6500 too much. Checked all my stats several times over everything was right. I didnt add in a follower and didnt have one summoned at the time ingame. So heres part 2 of the issue go to save so I can post the saved file on the google code part. Upon saving or trying to it crashes. So back to square one reinputing the stats.
Skills that were checked off archery and steady aim not sure if that makes a difference or not.
Unless the app crashed due something supernatural you should get a dialog stating that an error occured. That dialog has a button to send the error to us so we can examine it. Please go and reproduce the problem, and hit the send report button when it encounters the error. It will help us immensely tracking down the issue at hand : )
Another suggestion, one I'm guessing you guys already have plans for...but seeing all the stats that you are using to calculate the DPS would be nice. Things like Primary Stat Total, Crit / Crit Damage, Weapon Speed (for each weapon and then weapon average maybe).
Shouldn't be too much coding, it's simply displaying the cumulative values you're already using in the DPS calculation.
Yes, 0.5 is going to be a version mainly focussed on the UI. This will be part of it.
Also, the DPS calculation is off by about 200 DPS for me, not sure why that would be.
EDIT: Just upgraded an item (increased primary stat by 130) and now it's off by 660.
Calculations are always going to be off because you don't know the exact values that D3 uses. You just see rounded values in-game. We decided that an error margin of about 500 DPS above or below is acceptable. However 660 is a bit much. Do you think you can create an issue on our google code page and attach your save file to it? That way we can look where the inflation is going on.
If you do, please be so kind to include your in-game stats too. Thanks!
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
Dual wield is coming in the next version (0.4), which is RC right now. A minor bug in the calculator code is preventing a release and our calculator coder is having difficulty finding the time to fix it.
0.5 will bring a lot of changes to the UI overall, making the app more visual friendly too.
You can always visit our roadmap on the wiki to see what we plan to bring each version, the aim is exactly what you want and what we advertise for: A one stop program that calculates everything as if you never left D3 : )
Not yet, no. This is in the works for 0.5. 0.4 is in it's final testing phase, everything is taking a bit longer due to pdluke's limited time and a bug in the calculator code ( which is his baby )
Apologies for those wanting the proposed functionality, it will take longer than we hoped
Clicky here on the shiny golden link for your golden reward
Edit:
Just tested my server and it is online and operational as it should. I don't know why it would not connect to the service. Could you see if this page loads for you? http://nensec.no-ip.org:1337/ErrorReporter.svc
That makes me think you added in your +elemental damage too. Don't do that, it is already incorporated in the weapon damage values you see itself. If this is not the case then please let us know
Unless the app crashed due something supernatural you should get a dialog stating that an error occured. That dialog has a button to send the error to us so we can examine it. Please go and reproduce the problem, and hit the send report button when it encounters the error. It will help us immensely tracking down the issue at hand : )
Currently we do not, no. Unsure whether we will either : )
Yes, 0.5 is going to be a version mainly focussed on the UI. This will be part of it.
Calculations are always going to be off because you don't know the exact values that D3 uses. You just see rounded values in-game. We decided that an error margin of about 500 DPS above or below is acceptable. However 660 is a bit much. Do you think you can create an issue on our google code page and attach your save file to it? That way we can look where the inflation is going on.
If you do, please be so kind to include your in-game stats too. Thanks!
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.
Have fun all of you guys in using our app and we hope you all look forward to version 0.5!
Dual wield is coming in the next version (0.4), which is RC right now. A minor bug in the calculator code is preventing a release and our calculator coder is having difficulty finding the time to fix it.
0.5 will bring a lot of changes to the UI overall, making the app more visual friendly too.
You can always visit our roadmap on the wiki to see what we plan to bring each version, the aim is exactly what you want and what we advertise for: A one stop program that calculates everything as if you never left D3 : )