I get it when trying to open the program it self and the detail section of it is LONG. Im at work atm, when i get home i will post what it says under detail section.
I get it when trying to open the program it self and the detail section of it is LONG. Im at work atm, when i get home i will post what it says under detail section.
I've been using KParser lately to parse my groups Einherjar runs. What I've noticed is that a lot of the time certain mobs that I'm fighting show up as Players. Because of this I can't select that mob to see the specific parse for that mob. Most of the time its the Einherjar boss who is counted as a Player.
The first time it occured was during a run where we got a wave of Poroggo's so I figured it got confused due to some Players being charmed but since then it has also happened when I'm absolutely sure that nobody has been charmed. Is this a known issue, I saw it on one of the posts above in a screenshot too when someone who did Odin had some of the Einherjars in his parse.
It has happened to me too; in fact, it happened just last night. We had leeches, bats, spiders, and the golem boss. The golem (well, one of them? idk) was listed as a player, and I couldn't tell our guy who has new-found love for his RNG how much he did on the boss. I mostly parse it to check people's acc, who is sleeping what, etc. though.
I also had an issue with one parse where I could select Ouryu to be isolated, but doing so would crash KParser. I need to get the latest version, pull up that parse, and see if it still happens.
A friend of mine seems to be having some trouble making his parser work. It's his first time using one and i wasn't with him when he installed so i cant say what went wrong.
I do however have a screenshot of his error.
http://i66.photobucket.com/albums/h2...ersererror.jpg
Same issue as above. Using KParser V 1.4.2.0
Error code spoiler-ed. Hope it helps and thanks in advance.
Spoiler: show
it turned out the exe file didnt install the sql. It supposedly works now.
I used to use verizon 1.4.0 fine, until last Tuesday. I usually hit "Begin parse and save data", but somehow I hit "Begin dafualt parse" by accident and it stopped working since then. I don't know how to fix it. Tried getting rid off the old version and downloaded the 1.4.2 one, nothing works still. Help please.![]()
Am I the only person who can't do things from live memory?
that happens to me at random. I'm not sure what causes it. but if it happens i just parse from log for a bit then randomly retry to parse from live memory and it works for seemingly no reason.(I blame vista)
There is a problem with the last few releases when it comes to Vista 64 and possibly other architectures. If you roll back / download the 1.3.8 version (and update the offsets) It will work fine (if you did everything correctly in the first place). I tried every trick posted to get 1.4.0-2 to work and just gave up and went with 3.8 GL!
Link for 1.3.8 is posted on the windower.net website under approved programs k-parser
New version out: 1.4.3. Zip archive and installer versions both available.
I have pretty much a brand new computer (most parts replaced) after the previous one failed, and am running Windows 7/64-bit, so I'll have more direct contact with any issues on Vista/Win7 and 64-bit systems now.
Changelog:
1.4.3 (November 2, 2009)
- Fix (?) issue regarding presence of SQLCE. Finally just including the files directly in the .zip, and including some redirects in the program's manifest. Can hope that this eliminates the SQL problem.
- Fix issue with needing administrative rights to run in Vista and Windows 7. Don't have to set it manually anymore.
- Fix bugs in parsing 'no effect' enfeebles.
- Fix bug in parsing use of Feather Tickle by blue mage mobs.
- Fix bug in parsing certain ability names.
- Fix bug in error logging.
- Fix bug in handling the Recent Files list.
* Compact long file names in the Recent Files list. Added tooltips for full path.
+ Started to revise Damage/Minute plugin, ended up creating an entirely new one: Performance. D/M will be deprecated.
-- Note: the calculations to reach DPM (or DPS) are done differently in the two plugins, and probably will not match. I believe the new version is more accurate.
Can download at kparser - Project Hosting on Google Code
Older versions are, as always, available on the Downloads page if you have trouble getting the new version to work.
Cool, maybe this one will fix the random not parsing. Maybe not.
Any plans to add Dread Spike damage in? As far as I can tell they don't count for anything.
Thanks for the good work.
I ran a parse of a full Salvage run before releasing the new version, and it seemed to work fine. But then, there's several other things that were problems for other people but worked fine for me, so we'll see.
On Dread Spikes, yes, I noticed they were missing yesterday as well. Need to get some parse samples for it to make sure it works correctly (where drk is self, is in party, is in alliance, or not in party).
I dont get that KParser. its my first parser and it doesnt seem to do anything ... all i get is an empty field when i quit parse.
i am missing the total basics of it. (english is not my main language).
I click "Begin parse and save data" then kill a few mobs and click "Quit parsing" thats all i have to do right? i have a few pages open like "FIghts, offense, offense detail" but those pages are all empty.
Is there something i dont get? or is there a step-by-step guide for beginners anywhere?
Thanks for help
As English is not your main language, are you running FFXI in a different language (French/German/Japanese)? KParser can't parse the other versions of FFXI yet.
The logging fixed? It wasn't recording full damage before. I was doing Ejar w/ both KP and DP up and DP had more total damage at the end. Some players matched up perfectly with both parsers, but a good number of player had more total dmg on DP than KP
I'm trying to get KParser 1.4.3.0 going under Win 7 x64 but not having any luck. Gone through the readme, check all the patches. Nothing.
It's not throwing up any error codes just every window is blank. The Unparsed Data window is greyed out in the drop down menu and cannot be displayed.