VGInterface : Fabled Damage Meter : Fabled Damage Meter

		VGInterface > Vanguard Tools & Utilities
Fabled Damage Meter

Category: Vanguard Tools & UtilitiesFabled Damage Meter

Interface Information

Name:

Fabled Damage Meter Updated this week!

Author:

rgagnier06 [List rgagnier06's interfaces]

Date:

05-08-2008 01:15 AM

Size:

445.02 Kb

Version:

1.9a

Rate Addon:

Pictures

Click to enlarge

Views: 0
Size: 39.26 Kb
Dimensions: 475 x 500

Raid Damage Reporting

Click to enlarge

Views: 0
Size: 31.08 Kb
Dimensions: 475 x 500

Group Damage Reporting

Click to enlarge

Views: 0
Size: 46.40 Kb
Dimensions: 811 x 574

Manage Group/Raid Participants

Click to enlarge

Views: 0
Size: 62.37 Kb
Dimensions: 811 x 574

Main Graphical Damage Display

Description

An easy to use (Graphical) Damage Meter. Allows you to import a log file, define who was in your Raid/Group (Who you want to show up) and see it on a Graphical chart/easily report it back to your VG group! -Flamor (Xeth)

Bug Report: http://www.vginterface.com/portal.ph...876&a=listbugs

Feature Requests: http://www.vginterface.com/portal.ph...a=listfeatures

Main Features

- Easily load and view VG log files in a graphical chart!
- Very easy tool for reporting your data back to your group/raid/guild, etc.
- Made to get the data you want on your screen as quickly as possible without too much messing around (In an easy to interpret graph!). Easily getting that data from the program into VG has also been a huge driving force in the programs dev.

Installation
----------
Unzip & Install
----------

Setup (Windows Vista - V1.8+)
----------
After the program is installed you will need to set the access level of the program in order for the updater to function correctly.

#1- Navigate to C:\Program Files\Fabled Damage Meter\

#2- Right Click on Fabled Damage Meter.exe
--> Go to the Compatibility tab.
--> Check "Run as Administratior" at the bottom.
--> Click Ok/Done

#3- Right Click on Updater.exe
--> Go to the Compatibility tab.
--> Check "Run as Administratior" at the bottom.
--> Click Ok/Done

Thats it!
----------

Recommended Macros
----------

*Starting Macro* (Starts logging to the Vangaurd Bin Folder)

-----------------------------------------------

/g Starting Fabled Damage Meter
/log

------------------------------------------------

*Stopping Macro* (Stops logging)

------------------------------------------------

/g Ending Fabled Damage Meter
/log

------------------------------------------------

Operation
----------
-Open program.
-Create a new tab in VG and select every checkbox (Damage,Others' Damage,etc).
- Type /log.
-When done fighting either close VG or type /log again to stop logging.
-Click the Browse button in the Damage Meter program and select your corrosponding log file.
-Click ok.

**NOTE**
-Go to the "Participants" tab in the Damage meter software and remove any unwanted participants in the log file (NPC,etc) or specify who to show. Doing this will automatically update the graph.
----------

V1.9 **CURRENT VERSION**

----------

-Auto-Updater moved to an optional tool: You can choose to continue to manually update your software if the auto-updater is not working properly. (Now under the participants tab)

- DPS Parsing: Added functionality to display DPS!

- Made several bug fixes.

----------
V1.8

----------
- Introducing Automatic Updating! No Longer will you need to un-install your old version, download the new version and install it. After this update, the auto-updater will offer to check for new versions upon loading and download/configure each update with very little user-interaction!

- Heal Parsing! You will now have the option to easily swich betwean Healing and Damage parsing. Please continue to test this and leave feedback so I can continue to improve its features and accuracy.

- Fixed a bug within the "Highest Hits" sorting algorithm that was assigning hits to the wrong participants.

-Sorted the Hardest Hits.

- Added functionality to view participants if your participant count is 25+.

----------

V1.7(Modified)

----------
-NEW! The guild "Fabled" (Xeth) has officially adopted this Damage Meter and as such it has been renamed and modified to fit the guild (Graphically).

-->What does this mean to you? Everyone still has complete access to this program; the program is just under a different name and has changed slightly (graphically).

- Added a "Hardest Hits" page that allows you to see each participants hardest single hit.

-Please post comments with any suggestions/concerns.

Have fun and Enjoy!
----------

V1.7(Raid Improvements)

----------
-Fixed a bug that would be triggered if you hit the con button while the log was running.

-Added a new "Raid" tab on the Damage Totals window. Did alot of re-working to make this new tab work as planned. Only a max of 6 participants are visible on the "Group" tab. A max of 24 participants are visible in the "Raid" tab and they are broken into 4 groups for easier insertion into a macro. (Macro's only allow aprox 6 participants worth of data)

-Enjoy!
----------

V1.6(Code Revamp)

----------
- Did a complete revamp on how the program loads, reads, sorts and saves log information. I was forced to make these changes because the old system began to take 20-60+ seconds to parse a log or completely crash with larger logs.

- Update Summary
--> Old parse time with med-large logs:
Best case: 20+ secs, Worst: Crash

--> New parse time with all logs:
Best case: Less than 1 second, Worst: 3ish seconds.

The code efficiency changes I made have increased the speed and reliability of the program by leaps and bounds. Please continue testing and reporting back! Thanks

----------

V1.5.3(Bug Fix Part 2)
---------------
- Configured the software to reset the log when you add a group participant. This will make the program sort the names all at one time when you load the log file, instead of each time you add a new name to the participants list. (Much faster)

-Changed the graph to show a (%) next to the participants name instead of a (#) damage number.

-Other minor fine tunings.
---------------

V1.5.2 (Bug Fix)
---------------
- Fixed a pretty large bug inside my participant removal code that was not allowing you to remove desired participants properly. This has been fixed. (Thanks techywarrior!)

- Please note that now that the participants are correctly sorted by damage output, the program takes a little more time to process the parse. Adding group/raid participants prior to loading the log file is much faster then doing it after.
--------------

V1.5
---------------
-Fixed an oversight where "OpenFileDialog1" was displayed in the log directory textbox if you canceled the file browse after clicking "Ok". Now if you cancel the file browse, the "Ok" button is not displayed and the textbox is cleared. (Thanks Avooca!)

-Fixed a bug where the "Top 10" where not being sorted correctly. (Was only actually being sorted inside the "Damage Reporting Tool", not in the charting area itself) - Fixed

-Moved the legend into the extreme top right of the charting area so it dosent cover up pie chart labels.

-As requested on the forums, i have added the damage totals next to each name on the pie chart. Is this prefered?

-Doing more testing to identify other possible bugs. Please keep me posted! Please submit feature requests as you think of them too, there very helpfull.
---------------

V1.4 c (Bug Fix part 2)
---------------
-Performed further testing and found a bug that would reject the log file if you gained a level during the time you where logging. This bug has been resolved.

-Removed the redundant reporting label from the left side of the pie graph, allowing more room for the graph's labels.
--------------

V1.4 b (Bug Fix)
---------------
- After doing extensive testing on V1.4 I found the below "possible" bug/problem.
---> For some reason (but rarely), Vangaurd will write a completely blank line to the Log file. The parser was reading that blank line and trying to interpret it, resulting in an error message. I have inserted code into V1.4b that will handle this (rare) accurance without any problems.

-Added an uninstall button in the programs folder, making it easier to update to newer versions.

-Added a link to VgInterface in the programs folder, making it easier to update to newer versions.

**Please help this program to become what it is truly capable of by submiting bug reports on this website and submiting feature requests so I will know what everyone wants added. Thanks as always! **
---------------

V1.4
---------------
-Added a Log Viewing Tool.

-Tweaked the parsing code to be even more accurate.

-Fixed the Damage Reporting tool to correctly add the (/group,/say,/guild,etc) text in front of "Damage Report" at the top.

-Modified the Damage reporting tool to make it more user friendly with pasting into a VG macro.

-Added code to the parser that rejects rediculous ammounts of damage from the log (When VG bugs and says you hit "John Doe" for 503849234 damage). As of now that line will be completely skipped/ignored, which is ALOT more accurate than adding the outragously bugged damage figure.

-Fixed a bug where the graph becomes obviously inaccurate under specific conditions.

-Reworked the Participants tab to be more user friendly and easier on the eyes.

-Add new functionality to the Participants tab. Now instead of removing unwanted participants you can also explicitly state what participants you (only) want to be shown. (Excludes everyone but those on your list of participants) Both options are available to you now, in the participants tab.

-Did a semi-overhaul on some of the parsing code which resolved a bunch of bugs from the previouis version. If you found V1.3 to not display your data correctly, give V1.4 a shot, it should resolve the problem.

(Please provide me with Feature requests, Bug reports and other feedback! Thanks!)
--------------

V1.3
----------------
-More tooltips/labels to avoid confusion.
-Easy group/raid reporting tool to copy + paste into a macro and report damage results.
-Added percentages (%) next to each name in the Damage Totals window for clarification.
-Corrected the parsing code to correctly account for Critical hits.
----------------

V1.2
----------------
-Fixed a bug where the "Others" element was not displaying on the pie graph when there are more than 9 people in the group/raid.
----------------

V1.1
----------------
-Re-uploaded in a setup file so the required .dll file was attached.
----------------

V1.0
---------------
-Uploaded Initial beta compilation.
---------------

Archive List (Old Versions)
File Name	Version	Size	Author	Date
Fabled Damage Meter	1.9	445.10 Kb	rgagnier06	05-08-2008 01:03 AM
Fabled Damage Meter	1.8	444.26 Kb	rgagnier06	04-23-2008 10:43 AM
Fabled Damage Meter	1.7a	432.70 Kb	rgagnier06	04-11-2008 08:27 PM
Vanguard Damage Meter	1.7	366.98 Kb	rgagnier06	04-09-2008 10:14 PM
Vanguard Damage Meter	1.6	364.47 Kb	rgagnier06	04-04-2008 11:12 PM
Vanguard Damage Meter	1.5c	365.30 Kb	rgagnier06	04-02-2008 05:15 PM
Vanguard Damage Meter	1.5b	365.35 Kb	rgagnier06	04-02-2008 12:29 AM
Vanguard Damage Meter	1.5	364.96 Kb	rgagnier06	04-01-2008 09:54 PM
Vanguard Damage Meter	1.4c	364.54 Kb	rgagnier06	03-31-2008 01:12 PM
Vanguard Damage Meter	1.4b	364.34 Kb	rgagnier06	03-29-2008 11:16 PM
Vanguard Damage Meter	1.4a	364.83 Kb	rgagnier06	03-29-2008 04:43 PM
Vanguard Damage Meter	1.4	362.83 Kb	rgagnier06	03-28-2008 04:01 PM
Vanguard Damage Meter	1.2	360.45 Kb	rgagnier06	03-28-2008 01:02 AM
Vanguard Damage Meter	1.1	360.45 Kb	rgagnier06	03-27-2008 11:46 PM
Vanguard Damage Meter	1.0	13.88 Kb	rgagnier06	03-27-2008 11:33 PM

File Statistics

User Rating:

Downloads:

745

Views:

2626

Favorites:

Uploaded By:

rgagnier06 [More interfaces by rgagnier06]

Last Modified:

N/A

Author

Comments

Comment Options

Today, 08:24 AM

avooca

Junior Member

Forum posts: 0

File comments: 2

Uploads: 0

I just installed the latest release on a fresh XP SP3 Pro workstation. Does not launch

Event Type: Information
Event Source: Application Popup
Event Category: None
Event ID: 26
Date: 5/12/2008
Time: 8:24:19 AM
User: N/A
Computer: WOOT
Description:
Application popup: Fabled Damage Meter.exe - Application Error : The application failed to initialize properly (0xc0000135). Click on OK to terminate the application.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

05-01-2008, 09:29 PM

rgagnier06

Junior Member

Forum posts: 16

File comments: 9

Uploads: 1

Re: Re: didn't run under xp anymore

Version 1.9 is ready!

Last edited by rgagnier06 : 05-10-2008 at 01:01 AM.

04-26-2008, 10:24 AM

rgagnier06

Junior Member

Forum posts: 16

File comments: 9

Uploads: 1

Re: didn't run under xp anymore

I'm re-releasing the software either today or tommarow to allow people to bypass the updater if you are having trouble with it. Until then you can run the previous version.

For anyone having problems with the software:

-A good description of the problem (Specifics/Details) and/or screenshots would help tremendously in fixing any problems.

This update (V 1.8) is (logistically) by far the largest update so far. Therefor I expected to run into problems and complications with some people and their clients. This being said, I am working on fixes to any problems that have and may arrive. If you run into a problem, simply report it to me and you WILL get a reply and a fix. Thanks a ton, Flamor.

Last edited by rgagnier06 : 04-26-2008 at 10:31 AM.

04-26-2008, 08:14 AM

thesparxinc

Junior Member

Forum posts: 0

File comments: 2

Uploads: 0

didn't run under xp anymore

I cant run it under windows xp anymore

it shows i should run as adminstrator, but didnt work either.
updater too.

v1.8

04-22-2008, 12:32 AM

rgagnier06

Junior Member

Forum posts: 16

File comments: 9

Uploads: 1

I did some extensive testing on the Highest Hits page and found a major flaw in the sorting code that wasent assigning the damage to the correct participants after it was sorted. This bug has been fixed. Thanks again (thesparxinc) for pointing this out to me! Thanks a ton and keep the feedback coming! - Flamor

P.S- This fix will be in Version 1.8 which will be release within the next 1-3 days.

Last edited by rgagnier06 : 04-22-2008 at 12:48 AM.

04-21-2008, 10:43 PM

rgagnier06

Junior Member

Forum posts: 16

File comments: 9

Uploads: 1

Thanks for the feedback as always

As for the Highest Hits page being inacurate, I will have to look into this. I Created the Highest Hits page after all of the normal parsing code had already been made and there is a chance i may have made an error in its implimentation. Thanks a ton for the feedback and I will get back to you soon with my results. -Flamor

04-21-2008, 07:44 PM

thesparxinc

Junior Member

Forum posts: 0

File comments: 2

Uploads: 0

First: Great work!... nice parser.

But!...i think i have a bug report

I currently using 4 Logparser (Yours, YAVLP, VG Logparser [vgmonks, vgdisciples]) and after each raid and i parse the log with all of them.

All 4 have nearby same values (overall dmg and highest hit) but yours showing wrong values at least at highest hits.

for example:
Me (Rogue) - Highest Hit = 3956hp, overall 6.793.812
Guildy (Cleric) - Highest Hit = 42356hp, overall 1.232.354

and at the other parsers show nearby same values EXCEPT for highest hit. seems its flipped!

maybe it helps to fix
good work, and go on developing

(sorry for bad engl. ... im german

)

ps: if you want some logfiles ... contact me! (via pn or email from profile here!)

Last edited by thesparxinc : 04-21-2008 at 07:50 PM.

04-14-2008, 01:44 PM

rgagnier06

Junior Member

Forum posts: 16

File comments: 9

Uploads: 1

Auto-Updater Complete

I just wanted to give you guys an update on the status of the auto-updater I have been promising. As of right now the updater is completed and i am just doing some final tests for bugs. The only thing that is delaying the release of this new version is my search for a reliable and suitable hosting service.

I will be hosting 2 files on the server in order to allow the auto-updater to function correctly.

File # 1: Version file: stores information about the latest released version.
File # 2: Program Update file: the actual updated program that will be replacing your older version.

A suitable file hosting situtation would have to have the following:

-Static download link (Download url stays the same even after I update the file periodically)

-Direct download link.

-Preferably free.

If anyone has any ideas or can help me with this, it would be greatly appreciated. - Flamor

04-07-2008, 12:39 AM

rgagnier06

Junior Member

Forum posts: 16

File comments: 9

Uploads: 1

Working on an auto-updater for the new version. Please keep the feedback/requests coming. -Flamor

04-01-2008, 05:47 PM

rgagnier06

Junior Member

Forum posts: 16

File comments: 9

Uploads: 1

"Browse for a log then Cancel it will leave "OpenFileDialog1" in the log path and when you click ok it generates a dump - Vista x64. I'll start using it now and keep you posted "

-----------------------------------

Thanks! This is a very easy fix, and i'll make it handle the cancelation of the file browse more sharply. The feedback is much appreciated!

-Flamor

04-01-2008, 11:59 AM

avooca

Junior Member

Forum posts: 0

File comments: 2

Uploads: 0

Browse for a log then Cancel it will leave "OpenFileDialog1" in the log path and when you click ok it generates a dump - Vista x64. I'll start using it now and keep you posted

Avooca

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.IO.FileNotFoundException: Could not find file 'C:\Users\Eric\Desktop\OpenFileDialog1'.
File name: 'C:\Users\Eric\Desktop\OpenFileDialog1'
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
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, String msgPath, Boolean bFromProxy)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access)
at VG_DPS_Meter.Form1.loadData()
at VG_DPS_Meter.Form1.Button5_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventAr gs 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.W ndProc(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.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/Microsoft.NET/Fra...7/mscorlib.dll
----------------------------------------
VG DPS Meter
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Program%20Files%20(x86)/V...ge%20Meter.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL...isualBasic.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL...089/System.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL...dows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL...em.Drawing.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL...e.Remoting.dll
----------------------------------------
ZedGraph
Assembly Version: 5.0.9.41461
Win32 Version: 5.0.9.41461
CodeBase: file:///C:/Program%20Files%20(x86)/V...r/ZedGraph.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.

04-01-2008, 11:19 AM

Faiz

Junior Member

Forum posts: 0

File comments: 1

Uploads: 0

Ingame please

Is there any way to get this in-game and hopefully somewhat like WoW-Damage meter... The setup for that is sweet

04-01-2008, 09:28 AM

rgagnier06

Junior Member

Forum posts: 16

File comments: 9

Uploads: 1

As far as i know right now you can't build a functional damage meter into the UI. I am hoping SOE makes changes that will allow this to be possible in the near future, but as of now it is not (as far as i know).

04-01-2008, 06:55 AM

eizen

Junior Member

Forum posts: 2

File comments: 2

Uploads: 0

This looks very interesting =)

Is it at all possible to ehh..get it to 'show up in the game' so to speak? In the UI I mean...without tabbing out.
(Im very unfamiliar on what can and what can't be done when it comes to mods for the UI...does it show?