Working Parser?

[Motenten]

Release 1.3.7

1) Updated the memloc in the default settings. The new memloc location is 0x0057d768 (applicable to both KParser and DirectParse).

However since the program now properly carries over settings from prior versions, getting this new version does not automatically change the memloc. As such you will need to manually update it even with the new version, or use the Reset button in the options dialog to reset to the defaults (since the default for the new version is the correct memloc).


2) Added an Enfeebling tab. This is more experimental than most, as there are a number of known problems. Because of a flaw in the current database structure, it's not possible to track effects that wear off. Even if it was, you wouldn't see effects wearing off if you didn't apply them, or if they were overwritten (eg: Dia by Dia II), or if the mob uses certain moves that clear debuffs (eg: Exuviation).

Regardless, the duration times won't be accurate for long fights. It's mainly for short fights (eg: merits) where you can expect the debuff to last the duration of the fight, and you want to track how long into the fight it is before the debuff gets applied.

When the database structure is revised, this issue is on my list to be corrected.

The Paralyze and TP Move sections are slightly better, but also subject to further revisions.


3) The following is the usual changelog:

1.3.7 (April 8, 2009)
- Fix parsing of Violent Flourish's damage+stun effect.
- Damage+debuff effects (Violent Flourish, stun kukri, etc) should now get reported properly in the Debuff tab.
- Fix same bug as in 1.3.6 (eg: blindna failed to take effect) for alliance members as well as party members.
* Update memloc location for April 8 update.
+ Add Enfeebling plugin tab (experimental, and has known problems).

[Araelus]

Looks good, Motenten, thanks for the update! :D

[xIndustrialxAngelx]

Release 1.3.7

1) Updated the memloc in the default settings. The new memloc location is 0x0057d768 (applicable to both KParser and DirectParse).

this memloc doesn't work when I use it on Directparse...

[Motenten]

You may need to leave off the initial 0x hex value indicator.

[Liquidedust]

this memloc doesn't work when I use it on Directparse...

try 0x57D768 for DirectParse

[xIndustrialxAngelx]

That didn't help =( thanks though

[xIndustrialxAngelx]

try 0x57D768 for DirectParse

Thank god, yes this works! Thanks so much for the help! I really appreciate it!

[Belgaer]

kparser is just waaaay too laggy for me, and DirectParse is pretty laggy in it's own right (though not as much so). I'm on a low end system, so it can be a problem. Is there any parser even less of a memory hog than DirectParse?

[Motenten]

Have you tried running KParser with all tabs closed while you're parsing? (Maybe leave open the Experience tab.) I've noticed a lot of people never close any of the tabs, which would lead to atrocious performance on lower end systems.

[Epical]

Have you tried running KParser with all tabs closed while you're parsing? (Maybe leave open the Experience tab.) I've noticed a lot of people never close any of the tabs, which would lead to atrocious performance on lower end systems.

By no means am I running a low-end system, but I do notice Kparser dropping my FPS. Could that be because I have all tabs open? If I close all tabs during the parse, will the parse still export all the information?

[Motenten]

@Epical: Yes. The parsing is completely independent of the reporting. The parsing is done in the background and all the information is saved to the database. The tabs then query the database for the information that they present. You lose absolutely nothing by having them closed, and you can open and close any of them at any time and they will always have current information.

As for the time it takes, on my system it takes roughly 1 millisecond to parse one line from the chat log. However each time the database is updated (every 5 seconds) all the open tabs reconstruct their data, which can take anywhere from 20 ms to 250 ms per tab depending on the tab and the size of the parse. With 18 total tabs right now, having them all open can take a add up to quite a bit of time.

Personally I only keep the Experience and Offense tabs open during a parse because I never have time to do more than spot-check XP/hr and melee accuracy during a party to make sure things are running smoothly and balanced. Only after a parse has ended will I worry about checking other stuff.

[ringthree]

I am having a problem where I will up my memloc on K-parser and nothing happens. I click ok and then open it again and it hasn't been saved. What can I do to fix this?

[Limlight]

problem as well. I put in the memlock listed a couple posts above and it still isn't working. I'm on vista and just redownloaded the new kparser (tried the same thing with my older version and didn't work their either. I'm a bit of a computer tard lol I'll admit it. I try to right click - properties - Go to the Compatibility tab and check the check box "Run this program as an Administrator" but its grayed out, Is that my problem? it opens but doesn't parse any data!

[Belgaer]

Is there a way to save your report tab settings? Having to close them all out one-by-one every time is very annoying. >.<

[Motenten]

@ringthree and limlight: That problem should have been fixed long ago. It's working fine for me here, though I realize that's not always a guarantee of correctness. Try hitting the Reset button in the options dialog? (and then readjust the save directory) Also, see if an error is being generated in the error.log file (it's a text file).

@Belgaer: There's no way to save preset tab lists, no. It saves the currently open tabs between sessions. However if you're closing the tabs through the menu, it may be quicker for you to use the context menu on the tabs themselves. You can close a specific tab, or close all tabs except the tab you're over. That makes it easy to return to a minimal state.

[Fridell]

Seems Direct Parse broke again after todays update 22th April wrrryyyyy

[Wenslydale]

Aye, and Kparse.

[Viena]

0x57D7E8

[Arximiro]

0x57D7E8

Anyone have a working memloc for Kparse? This one isn't working for mine

[Wenslydale]

Works for me.