Yes.
Yes.
Roger, thank you.
Anyone else having problems with Kparser freezing? version 1.1.7 on Vista
Hmm. Looking at the process flow, looks like I fixed one deadlock issue and created another. Pesky multi-threading. I'll work on a fix for it.
Really appreciate the work you've done it's a top notch app.
Just professing my love for this parser, thanks for all your hard work =)
Okay, I'm using Direct Parse 2.2.92 right now. I've never noticed this before, since I never really use Ranged jobs, and decided to parse my Cor at random, but for some reason Ranged TP shots are not registering. I fixed the Memloc to the one a few posts up, and melee and WS dmg work fine, including Ranged WS. But any normal RA I fire isn't showing up in the "Ranged" column, or being added to my total damage score. Being the kind of Cor that TPs entirely on bullets, this skews the parse by a ton. Halp?
Shinsei, I had the same problem as you I think. It was solve after I reinstall lightluggage and timestamp plugins. It didn't work for me before i reinstall them thou.
Sometimes mobs get parsed into the damage, there a reason or solution? Thanks, KParser
?
Sorry, your question didn't make any sense.
I think he means like Tiamat will join the players on the damage done list if you can see other's damage taken?
Not Tiamat, like Motsognir's sons in T3 Einherjar are parsed as players, like Epical said, and also I've never parsed our Rangers before until today's Ixion, it shows them having 100% RACC and I'm pretty sure thats not possible, but I could be wrong >.>
KParser 1.1.7 clears my chat log when I maximize it. :/
Deleted
Anyway i can run kparser from a different pc then the one im running ffxi on?
New version of KParser (1.2.0), available at kparser - Google Code
Significant revision of the threading code and plugin API, so a minor version number upgrade. These changes should remove all threading deadlock issues (if I did it right), so no more lockups.
Complete rewrite of the Defense plugin for more detail.
Started adding unit tests for certain modules to improve regression testing.
A few other bugs fixed.
@Tavo: If you set KParser to parse from logs, then map the directory where FFXI is located to a network drive on the other system and point KParser at the temp directory in there it should handle parsing from the second system without any problem.
what was the deadlock issues? Would this be when it would freeze up and crash? If so, then w0000t!
Am i doing something wrong? say the .zip file is corrupted