Does anyone know about the performance impact on this parser? I play on a laptop, and although it's a really good one, I can't parse 20 man raids because of the FPS drop I get there with ACT. On 5 man instances I don't see a difference, so I guess it's my CPU limitations. Would this new parser be any better?
So far I'm really liking it. Just a couple of suggestions, similar to what was said earlier in the thread, it would be nice to be able to just overwrite old combat logs within the parser and not have to do it manually. Some more details within the damage breakdowns would be awesome too, like dps for each skill and max/min hits.
Last edited by darklcd; 08-14-2011 at 09:30 AM.
Captaincrook/darklcd <Best in Slot>
Thanks all for the comments!
There is live parsing. In the last release I had a 15 second threshold before I considered it a "valid" encounter (I didn't want critter encounters). I have an implementation to start the live updating sooner, but I want to test it out before I release it. I also plan on making this number configurable in the future, it just hasn't bubbled up to the top of my list (the list is long).No live parsing? I have the tool on my 2nd screen and I only see the results after the fight is finished + treshold.
I intentionally made it so that it parses the existing encounters, largely because sometimes you want to go back the next day and re-evaluate (I also have another long-term plan for this, depending on the level of acceptance this gets). However, I expect that this is going to be a feature many people are going to want so I'll look into making it a user-defined option.Also, make it so when you click "Start Parsing" it doesn't pull all the data from your Combat Logs, and it starts loading data from the time you clicked "Start Parsing" until you clicked "Stop Parsing". Would make it SO much better and would prevent these freezes.
DPS for each skill is a tricky wicket...what does it actually mean? Philosphical debate ensues. If someone can provide a reasonable definition that I can agree with I'll see what I can do.Some more details within the damage breakdowns would be awesome too, like dps for each skill and max/min hits.
I plan on adding more data to the tables, stay tuned!
I run on an i7 with 8gb ram, so I can't really answer that question. I need someone with a "lesser" computer to give me performance impact feedback as well. One thing to note, you can adjust how often the data is processed (1 second to 15 seconds, default of 5).Does anyone know about the performance impact on this parser? I play on a laptop, and although it's a really good one, I can't parse 20 man raids because of the FPS drop I get there with ACT. On 5 man instances I don't see a difference, so I guess it's my CPU limitations. Would this new parser be any better?
On the note of large combat logs, this is my next top priority (I actually noticed this today). I have a scalable plan but I need to work out some details.
To my knowledge (someone correct me if I'm wrong please), you can tell how much was absorbed but cannot tell why there was an absorb. If you can't tell why then you can't tell who caused it, and therefore you can't assign credit.Hey,
Is this parser able to handle the purifier shields?
I hate it how you allways end up last on HPS because your shields aren't added to the heals you do
I haven't tried it out yet but I did DL it, I notice I can't move the overlay or if I can I'm doing it wrong.
looks good recommending it to my guild so far
Drakkars - Warrior - Warcry - FaeblightGuild Leader3/4 GA, 1/3 IG, 1/5 PBRecruiting a baller warrior dps! Need more red names of awesomeness!
seems promising gonna watch out for more progress
Agility- Female Bahmi Rogue
Raider of Art of War Born on Shivermere, Living on Bloodiron
Greenscale Blight 5/5 ¯\_(ツ)_/¯ River of Souls 5/5 ¯\_(ツ)_/¯ Gilded Prophecy 4/4 Drowned Halls 4/4 ¯\_(ツ)_/¯ = Raid Tier 1 Completed
HammerKnell 3/10 (World 2nd Kill on Murdantix)(2 Shard firsts)
OK, update incoming!
- Significantly reduced the memory footprint which *should* stop the freezing problems and allow almost indefinitely large combat log parses.
- Added the ability to lock/unlock the overlay position, so you can move it around.
- Added the option to skip all existing encounters and go straight to the end.
I've tested this out on my saved combat logs, so now to live! Unfortunately I've got a 20 minute queue so, assuming I don't find a problem there will be an updated link in about 30-45 minutes.
Hey, Just wanted to give you some feedback:
This is definitely replacing my RJ parser. I can do things with it that I can't with RJ. Some of my friends have started using it because they were legitimately impressed by it. Good job, and keep refining it.
Don't make Dahanese sad. Behave yourselves.
i wonder if this is compatible with rift raids, or if the person who made rift raids made it working with a specific parser.
I had to make some adjustments at the last minute because I completely broke the live update...awesome! Anyways fixed now. There were a few really big changes to the code in this update, so I tried to test it pretty thoroughly.
Is there any way to modify my original post so the link stays up to date? I'm not seeing any edit functionality.
Does this track absorption shields and cures?