Imgshack some pics for me, DPS is # untill the 2nd log file is read usually within 5-10 seconds if your in any normal boss fight. Just make sure you have the correct log file selected.
Imgshack some pics for me, DPS is # untill the 2nd log file is read usually within 5-10 seconds if your in any normal boss fight. Just make sure you have the correct log file selected.
*GARUDA* new parser for 1.22 updates
New parser: http://www.bluegarterls.com/home-mai...id=8&p=8#p4071
DMG-dealt to clipboard (not just dps)
Start/Restart button updated for simplified starting/restarting of parser
Fixed for magic resist rates (updated to parse for "partial evades")
Ability to save log folders to a set directory of users choice after each fight for easy re-parsing
History DPS added for every saved log (click new "Save Logs" button after event/fight/run and save the logs), this lets you reparse those saved logs quickly
History DPS added to clipboard menu for all the runs of the night at a glance
Fixed the stop button: NEVER CLOSE THE PARSER AGAIN =)
You're awesome, thanks Tachi.
i got a question. The Parser is not reading damage from my party. How can i fix that.
Do you have the right log directory selected?
You need to select the correct log file, in the link above go to the first page's op and it has the setup instructions.
i selected the correct log file. i get every thing but damage all 0.
do i have to be in party for this to work? how long do i have to wait for something to be written in log?
i tried couple times using this but everytime i get nothing or just old data, today i deleted all my log folders to be sure it wasnt something there, started ffxiv, opened bg parser on the only log folder that was created, started parser, killed few coblyns outside uldah and got nothing =/
edit: after few minutes it appeared, i was just impatient =)
Ya when solo its not a very good tool for measuring DPS, but for stat collection and testing setups its great. And in a full party situation on a boss fight/instance the DPS is very accurate vs what is happening in real time.
Its handy to make a single macro with:
"/echo ." on each of the 10 lines. This lets you force clear out a log file at any point in time. Just pop the macro a few times and the dps will update showing the file was written out.
Parser seems broken after the update. Tried running it on twice and all my results came up 0.
can you please take some SS's and post links to them so I can see what your getting? I used the parser all last night on many runs and I have never had the "all zero's" issue ppl talk about from time to time.
I bet its either "you have the wrong log selected" or "you have a target mob selected that is not what your fighting" or "you have an old version of the parser".
Seems to be working fine now. Not sure why it was acting that way the other night.
Are NM filters saved in any way if you close it? I had the parse filtered for Gardua the night before, but looked like my filter list was empty.
yes if you pick an NM it saves the NM's name, and shows it on the parsers upper left corner next-to "BG Parser" it would say "BG Parser: Garuda" etc. If you click the
Setup>NMs then it clears them all out and lets you re-select what you want. So yes if you click that it makes it seem like you had nothing selected prior its just my personal preference for how I use it. I only change NM's when I know I don't want the current one selected and usually i'm changing targets in a hurry so anything to reduce my mouse clicks.
I am having the same problem. When NM file is checked the damage output is displayed with NP (which means log file path is correct). But, for instance, if I wanted to parse anything else that is not in the NM file (e.g. moogles) the damage output will always be 0 even though other tabs display values correctly.
Any thoughts?
So you can see the dmg taken/ breakdowns etc correctly in all the tabs except the DPS tab? If so try unchecking this, I found it can cause issues on some machines especially EU players:
Please take a screenshot of the parser not displaying properly and imageshack it so I can see.Show DMG Tool Tips check box is for EU users or anyone who has issues when running the parser where the main Damage done panel is glitching/lagging.
Why doesn't the parser detect attacks for 0-1 dmg?
I'm trying to do some tests using broken weapons so I don't have to run away and let mobs regen but it's not acknowledging the hits at all.
Tachikoma:
Here's an image of my parser acting up and being all damn crazy in the damage dealt tab.
ht tp://images.bluegartr.com/bucket/gallery/70c0eeee5cd819d57bc57d39b6146394.jpeg
And while I was working on this post it acted up even more spectacularly:
ht tp://images.bluegartr.com/bucket/gallery/5934ce1b561bdd9a8ebe7e20dc206272.jpeg
Hope this helps, signed up just for this XD (trrrrying to break the url so the forums will accept)
Mine does the same thing. As soon as i select the log file, or do anything else from the menu, the parser window goes blank until i roll the mouse cursor over it which reveals a garbled UI. The folder it makes in my log directory is always empty too. Does it matter if i have Java 7 instead of Java 6? And does 32 or 64 bit windows matter?
Since my ls no longer uses my parser as they want to use one that reads ram and has 100% accuracy in dps where my parser is only 95%accurate I have stopped supporting and updating it. Also 2.0 is supposed to have an API to make developing addons in the future easy and robust. Till then good luck and thanks to all who used my parser.
Tachi