Working Parser?

[Motenten]

@CadgerEX:

To bring up the Unparsed Data tab you need to enable Debug Mode in the Options dialog.

Also, check the errors log file. You can bring it up using the button in the About dialog.

@Cream Soda:

That's very hard to say. I am curious, though, if you could test one thing: import the DP data into KParser and see what that looks like compared to the other two parses. There are a few other things I could look at if you could send me copies of the two parses as well.

[Kohan]

Interestingly, I was having awful problems with the second to last version of KParser. Admittedly, I have not tried the newest release. I will once I have the opportunity.

In the interim, I'll describe what I experienced. Previously, KParser worked fine under Windows XP x64 for me (as I posted about it in this very thread, including the measures I took to get it functioning). For a number of months, I was using another OS, and KParser went through an update or two since then.

When I eventually returned to XP x64, which was untouched the entire time, I installed and tried to use the newer version of KParser, but could not. Specifically, once I started a parse, it would rapidly eat up all of the available memory and available CPU on the system, leaving FFXI to practically freeze at 1-4FPS, and rendering the computer nearly unusable. The error log rapidly bloated to several GBs in size, so I could not open it to review.

Of course, since this is related to a now outdated version, it may not matter anyway. Though I do not have a screenshot, KParser was occupying around 2GB of RAM, and the error file was roughly 3GB.

I've since downgraded to 1.3.8, and have no problems whatsoever.

Would there have been any specific reason for this happening?

[Motenten]

There was one bug I found that caused an infinite loop in the error logging routines. I ended up with a 60,000 line log file after just a few seconds. Not sure if that same bug would have caused it to eat up memory, but it's possible that that's what you encountered. That's fixed now.

[CadgerEX]

Tried that, still nothing at all. Tried it from both memory and logs as well. Nothing in errors file either.

Edit: Just tried 1.3.8 and get this error message in the log

04 November 2009 21:22
WaywardGamers.KParser.ParserCore, Version=1.3.8.0, Culture=neutral, PublicKeyToken=null
Error severity level: Info

Memory access
Message: Memory Monitor Thread: ERROR: An exception occured while trying to connect to Final Fantasy.  Message = Access is denied

---------------------------------------------------------------

[Motenten]

Ok, that indicates that the program doesn't have administrative rights. It needs to be UAC elevated to be allowed to read from another process' RAM (and possibly to have access to reading the program files directories where the logs are stored).

For 1.3.8, you need to set that manually on the program/shortcut properties, Compatability tab. 1.4.3 -should- demand administrative rights when you run it, so that you don't need to manually set that flag. If you aren't getting a UAC prompt when running, there's a problem.

[Omnipotent]

I went to the link by google. Downloaded the latest version as well as the x86 thing since I run 32 bit. My parser just remains blank, and when it I hit parse, says parsing on the bottom, but yet again the whole box is blank.

[Motenten]

Do you get anything in your error log? Go to the About box and click the Errors button.

[Motenten]

Release 1.4.4, available at kparser - Project Hosting on Google Code

Name substitution is the most significant change in this one.

1.4.4 (November 4, 2009)
- Fix minor threading bug in Performance plugin.
+ Added ability set a display name for players. With this, photoshopping screenshots should no longer be necessary.
~~ Usage: If player info text starts with text enclosed in square brackets (eg: [war/nin]), then that string will be used in place of the player's name if the option to do so is set in the Edit menu (and can thus be quickly toggled on and off). An asterisk will be prepended to the text to indicate that it is user-defined. Text more than 15 characters long will be truncated to avoid spacing issues compared to real names.
~~ Examples: The war/nin (as used above) would thus have the name of "*war/nin". Other players might be shown as "*Relic sam" or "*Spoony bard".
~~ This does not change the names listed in the player selection drop-downs on various tabs. This also does not change the names listed in the Salvage subsection of the Loot tab.
~~ When the database structure is upgraded, this feature will move to its own field instead of being a fudge in part of the player info field.
* Changed Unparsed Data plugin to Raw Data plugin, with the option to either show only unparsed lines (what was shown before), or all lines logged.
~~ NOTE: Be aware that loading all raw data can take a long time for a large parse. You should generally Not change the type while in the middle of a parse.



@Cream Soda - With this you won't need to send me a copy of the parses. Import the DirectParse database, then view the Raw Data/All Data log for each parse. Copy them into external text files and run a diff on them, or use a program that can compare files.

You want to look for any lines that are present in one parse but not in the other. Particularly look for duplicate or missing lines, where duplicate entries are shown by duplicates in the sixth numeric field (the third 8-hex-digit number).

Note that there can be one quirk: DirectParse saves the original log lines in two separate chunks, and I have to re-combine them on import. It's possible the recombine won't have exactly the same characters as the KParser parse. If that's the case you'll need to do more sophisticated comparisons.

[Cream Soda]

I just run the parse and x out after i compare damages. I'll have to save parses on friday's run. You'll have to explain how to do the importing and ect. I usually just screen shot and paste into paint and save my parses that way.

[Thunder]

I went to the link by google. Downloaded the latest version as well as the x86 thing since I run 32 bit. My parser just remains blank, and when it I hit parse, says parsing on the bottom, but yet again the whole box is blank.

I have the same thing with all the 1.4 versions When parsing on 1.3.8 it says, "Parsing to default file." at the bottom but 1.4.4 yields, "Parsing...".

[Motenten]

@Thunder/Omnipotent

Things for you to check:

1) Check the simplest level of parsing first. Just type something into chat and check the Chat tab. Wait a few seconds, then stop the parse to force a close and refresh. If nothing shows up in the Chat tab, note it here.

2) Check the error log. Go to the About dialog and hit Errors. It should bring up the error.log text file. You can also find it from KParser's directory. If there are any errors, note them here.

3) Check the directory that you're saving your parses to. Are you using the default, or have you changed it to another location? Go to that location and check the file KPDefaultParse.sdf. Does it exist? Also check the timestamp it was modified at. If it isn't there, or the timestamp isn't the time you just ran the test parse, then you may not have permissions to write to that file/directory. Adjust the directory's security settings, or change the default save location.

4) If the file exists, look at the size. Is it 236 KB? That's the size of a brand new empty database. Check any other instances of parses you've run and haven't gotten info for and see if they are 236K or if they are larger. Most typical parses are a few MB.

5) Turn on debug mode in the Options dialog and run a parse. In the directory that you save the parse there should be a file named debugOutput.txt. Examine that to see if it's generating info on parse attempts. Also check to see if it provided an entity list at the bottom of the file.

6) Also in debug mode (after stopping a parse), check the Raw Data plugin tab. See if it shows anything in terms of unparsed data and/or all raw data.

If any of these help you find out what's wrong, please let me know. If none of them let you know what's wrong, also let me know.

[Thunder]

Tried everything.

Files are all 428 KB and time stamp is accurate.
Error shows nothing.
debugOutput.txt. has: Entity List is Empty
Raw data in debug mode after parse was stopped has literally nothing.

Between starting/ending all parses I typed and entered chat.

[Motenten]

Couple more tests, if you wouldn't mind, Thunder.

Go to the Options dialog and hit Reset, then adjust the default save directory back to whatever you have it set as. Then try another quick parse, as above.

Second, change the parse method to By Log, and Read Existing Logs (so you don't have to force a file write-out). Start parse, then end, and check the results. Reset back to RAM afterwards.

[Thunder]

Reset it and retried, nothing's changed, file's still blank and 428 K.

Changed method to log and checked read existing logs. It parsed/recorded everything successfully from.. last night at 10pm to 30 minutes ago(5:00)

[Kailee]

I had the same problem as Thunder/Omnipotent, are you guys using windower? And if so are you guys running in fullscreen/no border? If you are, try resizing the screen so that there is a border, check and see if that works because it did for me.

[Omnipotent]

@Thunder/Omnipotent

Things for you to check:

1) Check the simplest level of parsing first. Just type something into chat and check the Chat tab. Wait a few seconds, then stop the parse to force a close and refresh. If nothing shows up in the Chat tab, note it here.

2) Check the error log. Go to the About dialog and hit Errors. It should bring up the error.log text file. You can also find it from KParser's directory. If there are any errors, note them here.

3) Check the directory that you're saving your parses to. Are you using the default, or have you changed it to another location? Go to that location and check the file KPDefaultParse.sdf. Does it exist? Also check the timestamp it was modified at. If it isn't there, or the timestamp isn't the time you just ran the test parse, then you may not have permissions to write to that file/directory. Adjust the directory's security settings, or change the default save location.

4) If the file exists, look at the size. Is it 236 KB? That's the size of a brand new empty database. Check any other instances of parses you've run and haven't gotten info for and see if they are 236K or if they are larger. Most typical parses are a few MB.

5) Turn on debug mode in the Options dialog and run a parse. In the directory that you save the parse there should be a file named debugOutput.txt. Examine that to see if it's generating info on parse attempts. Also check to see if it provided an entity list at the bottom of the file.

6) Also in debug mode (after stopping a parse), check the Raw Data plugin tab. See if it shows anything in terms of unparsed data and/or all raw data.

If any of these help you find out what's wrong, please let me know. If none of them let you know what's wrong, also let me know.

I just clicked the tab things under windows and it works now . Stupid mistake.

[Motenten]

Hmm... I was trying a borderless version of windower a while back, and that might have also been when I ran into a problem with losing track of chat log data in RAM. I didn't care for the borderless mode, though, and changed back to normal, but I never thought to associate the two things together. I'll try testing that out later tonight.

[Shamaya]

Add in the hit/miss/crit tally table for R.N.G. study!

[Motenten]

Actually, Shamaya, check the Offense Details tab, and check the Show Details option. Doesn't show misses (I can add that), but it does show the sequential order of hits. Just puts non-crits separate from crits. I can add a summary details section to list the full mix of hits, crits and misses.

Edit: Ok, adding in misses will take more work. For now, though, I updated it to show an integrated list of crits and non-crits. Crits are marked with a trailing 'c'. Not sure I like that, since I don't know how easy it would be to get around that if you're importing it into Excel or similar. I'll look into exporting directly to Excel later on.

[Shamaya]

Oh, thanks much for your response and effort :3 I'll go download the new version a bit later. I don't want you ta break you back over making more edits tho if you're busy. Misses would be great. But at the very list, for a lol test on checking into R.N.G., crits vs normals is a good starter. Just now in my log I critted four times after not critting for "ages". And not 3 minutes ago, same thing. Seems so weird.