Working Parser?

[Cream Soda]

Get net framework

[Motenten]

Hmm. Problem there is that it's technically not possible to have an unhandled exception unless the exception is generated by the framework itself, and not the program. In fact it even says that - Exception has been thrown by the target of an invocation. Now I have to go digging and see if I can find anything that's being marshalled at startup. However it's definitely outside KParser, and there's apparently no way for me to trap for it, which will make this difficult to debug.

[LinktheDeme]

is dvs parser working again? ;o

[Amele]

is dvs parser working again? ;o

direct parse was never not working >.> you do need the latest memloc, it's on the previous page of this thread.

[Zhais]

is dvs parser working again? ;o

Been working, just update your memloc

edit: amele beat me by like .01 seconds

[Amele]

Been working, just update your memloc

edit: amele beat me by like .01 seconds

story of my nm camping life ^^v

[Shinsei]

I give up on KParser

where can i get the new memlocs for DvsParser?

[Leolai]

The new memloc was posted just on the last page (works for both Direct Parse and Kparse)

The number Viena quoted is the current memloc for both directparse and kparse. For directparse, put the following into DVSconf.txt:

MEMLOC=0x576D58

[Kaope]

Is Kparser supposed to not to work with timestamp? I can't seem to get it to work with timestamp on....

[Motenten]

KParser should work fine with Timestamp; it just strips that information out. However it seems like every couple months they change the format for how the timestamp gets encoded into the message and I have to fix how it gets handled. I'll see if it's been changed again recently.

[Motenten]

Just double-checked, and it seems to be handling the current version of Timestamp (2.1) properly.

[Motenten]

Version 1.1.3 released. http://code.google.com/p/kparser/

Including changes in 1.1.2:


Several significant speed improvements.

Complete rewrite of the Extra Attacks plugin to fix several issues.

Fix bug in parsing from log files that duplicated entries.

When parsing from log, will use Windower Timestamp values to timestamp messages, if present.

Consolidated some DLLs. If you normally extract the .zip into an existing folder, would suggest deleting all files in the existing folder first.

[Wenslydale]

Error message when attempting to parse Extra attacks.

Error while Processing Plugin:
The given key was not in the dictionary

Log Here;

[rithridan]

Maybe this is the wrong place to ask but, what is the difference between KParser and DirectParse (DvSParse)? Is there something that KParser can do that DirectParse can't or is just whatever feels most comfortable to use?

[Zhais]

Maybe this is the wrong place to ask but, what is the difference between KParser and DirectParse (DvSParse)? Is there something that KParser can do that DirectParse can't or is just whatever feels most comfortable to use?

KP is more detail and expanded parse oriented,

DP is summary oriented. I do believe DP ends up being more lightweight? I haven't really had the time to check against them.

I keep getting myself into busier and busier situations so haven't had time to do jack with the parser yet other than make releases with releena's commits lol ><

[nekura]

DP definitely feels more lightweight, but I love KParser's information overload and ability to select the FFXI process to parse from.

[Amele]

KP is more detail and expanded parse oriented,

DP is summary oriented. I do believe DP ends up being more lightweight? I haven't really had the time to check against them.

I keep getting myself into busier and busier situations so haven't had time to do jack with the parser yet other than make releases with releena's commits lol ><

this is pretty accurate.

if you're looking for alot of raw data to do testing with, kparser is probably better. if you're looking for a quick summary of 'what's my acc? who's doing the most damage? are my ws hitting ok? what's my average hit? what's my evasion rate?' etc then direct parser is better.

direct parser is the lighter-weight app so if your machine is slower, then dp will probably work better for you than kp.

[Motenten]

1.1.4 release of KParser @ http://code.google.com/p/kparser/

New plugin for Items. Shows details of items used, and when.

Fixed (hopefully) the dictionary error and null reference reading error.

Framework is in place for exporting data to Excel. Now I need to start updating the plugins so that they'll generate the info in the proper format to be saved.



On the difference between KParser and DirectParse, Zhais and Amele pretty much got it. KParser was specifically designed for datamining to answer any sort of question I could possibly think of. Rather than just "how much damage am I doing?", answering things like "what's the distribution on the damage that my hits have done?". The more elaborate plugins I've done recently have been less accurate (but hopefully will improve), but more interesting to try to figure out.

On the other hand, it is definitely not lightweight. I've got a pretty good system at home, but even I don't keep more than 2-3 tabs open at a time while parsing (though partly because I'm only interested in a few things at a time).

[Valyana]

1.1.4 release of KParser @ http://code.google.com/p/kparser/

************** Exception Text **************
System.Reflection.ReflectionTypeLoadException: Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.
at System.Reflection.Module._GetTypesInternal(StackCr awlMark& stackMark)
at System.Reflection.Assembly.GetTypes()
at WaywardGamers.KParser.ParserWindow.FindAndLoadPlug ins()
at WaywardGamers.KParser.ParserWindow.ParserWindow_Lo ad(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Mes sage& m)
at System.Windows.Forms.ContainerControl.WndProc(Mess age& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.O nMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.W ndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

[Valyana]

Looks like my problem was old plugins; installing 1.1.2 and then 1.1.4 fixed the crash, as did deleting the plugins that aren't in 1.1.4.