1
Forum Settings
       
Reply To Thread

ParserFollow

#52 May 02 2008 at 1:18 PM Rating: Excellent
***
2,236 posts
Sorry, there's no way for me to distinguish kicks from punches, or guarded hits from unguarded, at least not directly. A histogram distribution graph would likely give you a better idea of those individual damage type ranges. I haven't written it into the program yet, though.
#53 Jun 09 2008 at 6:35 PM Rating: Excellent
***
2,236 posts
New base address for KParser (or DirectParse, if you use that) is 0056DA48 00575968. You can update that through the options dialog in KParser, or in the associated text file for DirectParse. No update to the KParser program as I've been bad and not working on it recently. Will get back to it more this summer.

Edited, Jun 12th 2008 7:23pm by Kinematics
#54 Jun 10 2008 at 12:12 PM Rating: Good
Avatar
*****
12,446 posts
my KParser doesn't work. I get errors everytime I open it, or try to start a parse. I changed the thingy like you posted, but that didn't do anything.
____________________________
Theytak, Siren Server, FFXI [Retired]
Amerida Baker, Balmung Server, FFXIV
LOLGAXE IS MY ETERNAL RIVAL!

Reiterpallasch wrote:
Glitterhands wrote:
Am I the only one who clicked on this thread expecting actual baby photos [of Jinte]? o.O

Except if it were baby photos, it would be like looking at before and afters of Michael Jackson. Only instead of turning into a white guy, he changes into a chick!
#55 Jun 10 2008 at 1:27 PM Rating: Excellent
Scholar
***
1,146 posts
update killed kparser, needs to be updated then will work again
#56 Jun 12 2008 at 9:07 AM Rating: Excellent
Scholar
***
1,638 posts
yeah still broken, doesn't seem to work anymore
____________________________
http://ffxi.allakhazam.com/profile.xml?117964
http://ffxi.allakhazam.com/profile.xml?8953
War 75, Mnk 75, Whm 75, Rng 75, Bst 75, Blm 68, Thf 61, Nin 51
#57 Jun 12 2008 at 4:23 PM Rating: Excellent
***
2,236 posts
Ok, finally figured out what's wrong, since the parser is working fine for me. I copied the wrong value into the post above. That's the old memloc. Doh!

Correct memloc is: 00575968. Will edit above post as well.
#58 Jun 13 2008 at 6:25 PM Rating: Excellent
**
390 posts
Thanks Kinematics! Its working now for me.
#59 Jun 20 2008 at 3:51 PM Rating: Excellent
2 posts
Hey, I just started using this recently, and I cant figure out how to make it parse my PT damage, it only shows mine.
I have an idea that it's the fact that I filter most of my PT damage so I don't get spammed, so to get it to display my PT damage, do I have to un-filter it?
#60 Jun 20 2008 at 5:19 PM Rating: Excellent
***
2,236 posts
Correct. It can only parse what actually shows up in your chat log.
#61 Aug 05 2008 at 2:15 PM Rating: Excellent
*
158 posts
Anyone know the updated Memloc, I can't get the parser to read the RAM, I can only get it to read log.
____________________________
-Lilman-

75 WHM
75 BLM
75 WAR
75 THF
64 SMN

348 Merits

CoP - Complete
ZM - Complete
Rank 10 - Bastok and San d'Oria
ToAU - Complete
WoTG - 3
Bonecraft - 66.3

-Sentry-

75 PLD

#62 Aug 22 2008 at 2:29 AM Rating: Excellent
***
2,236 posts
The new memloc from the June update was 00575968. Also, 1.0.8 has been released (http://code.google.com/p/kparser/) and should fix an issue with not being able to update the memloc value properly, as well as a few other enhancements and bug fixes.
#63 Aug 27 2008 at 4:47 AM Rating: Excellent
***
2,236 posts
Another update to KParser (v1.0.9 at http://code.google.com/p/kparser/), though only a couple of additions.

First is the addition of access (via dialog; check the Tools menu) to a small field in the database to store player information. When I originally designed the database I considered putting automated job info there by pulling seacom data or the like, but it never really worked out. Unfortunately I left it fairly small -- just 100 characters. While recording job info for each player in the parse is probably useful, I also recently realized people will probably want to store things like full gear set info as well, and that's just not feasible with its current size. This will be changed in the next database revision.

To go along with that, I added a small little plugin page to show the player info that's been stored for the current parse file.


Second is the addition of detailed data for offense and defense damage per fight. Most people probably won't use it, but it can be handy if you're trying to do a more detailed statistical analysis of the numbers. The Defense Details tab will likely be useful for those studying shield block or guard rates/amounts, while the Offense Details is for those studying random pDiff variance behaviors.

Processing for unrestricted mining of large data sets can get expensive, so it's set on a minimized value while parsing is active.


Also has a fix for totaling -ga spell damage.
#64 Aug 27 2008 at 4:52 AM Rating: Excellent
Avatar
****
7,677 posts
Kinematics,

A friend that I recommended your parser to happened to comment to me that he wanted to export the parser data to an xml file or something similar, but wasn't able to; the export option on the menu is disabled/greyed out. I thought something might have been bugged, but when I checked my client it was disabled on mine too, whether I loaded an old parse or brought in some new information.

Is that something you just haven't added yet or is there some step we're missing to be able to do that? I know the fields are copy/paste capable, but that can make a mess in transition between text fields (and also requires more effort than clicking a button ^^).

Edited, Aug 27th 2008 8:50am by Norellicus
#65 Aug 27 2008 at 5:48 AM Rating: Excellent
***
2,236 posts
Yes, the Save Report menu option hasn't been implemented yet. I should at least put it in so that you can save the current text display data.

As for getting the data in XML format, that's rather trickier. If you're only concerned with the data currently displayed, it's not quite so bad. If you want all the data, you really should just be reading the database itself.

Someone from BG has asked to be able to export to CSV or Excel file format, and either of those might also be viable. Just going to be tricky trying to figure out how to put the data together for it without duplicating everything in the plugin.

If possible, can you get details on exactly what's wanted?
#66 Aug 27 2008 at 6:06 AM Rating: Excellent
Avatar
****
7,677 posts
Really mostly looking for offense/defense stat tables to make it easy to share parse data with others without distributing the database files and exposing the captured chat logs which may contain private conversations; xp/loot information is easy to copy/paste if needed for some other purpose, but trying to copy/paste those tables can get messy, so having a way to just drop the general summarized statistics for damage dealt and such into a file for easy distribution is the main point. Think like the exports produced by spyle's old parser for a basic proof of concept.

Being able to filter what fields are reported to the export on the fly would be a bonus but I don't think it's critical.

Edited, Aug 27th 2008 10:06am by Norellicus
#67 Aug 27 2008 at 7:11 AM Rating: Excellent
***
2,236 posts
Well, I've added two quick things so far that will be in the next release.

First, the ability to save a copy of the database out that is stripped of all chat information for privacy. That way the database itself can be shared without issue.

Second, I've put in the first basic reporting, which will allow you to save the currently viewed page as a simple text file.

More reporting options will require thought on how to implement them.
#68 Aug 27 2008 at 12:30 PM Rating: Excellent
Avatar
****
7,677 posts
<3
#69 Aug 28 2008 at 12:33 PM Rating: Excellent
Was just browsing forums when I saw this as active topic out here. I don't normally come to this forum, but the title caught my eye. I'm going to download it and try it out since I have been interested in getting a parser to see the effects of different builds beyond just eyeballing things - but I was always afraid of getting a virus and my account stolen.

Glad to see this has the endorsement of so many people I know and respect from the forums. Thanks for the tool!


Edit: nevermind. I restarted the parser program and it's all good.

Edited, Aug 28th 2008 6:08pm by TerrainFFXI
____________________________
75 RDM WHM DRK DRG PLD
58 BLM
56 WAR
#70 Aug 28 2008 at 8:57 PM Rating: Excellent
***
2,236 posts
1.0.10 released (http://code.google.com/p/kparser/)

Can select POL process to monitor when parsing.

Can save a copy of the database without any chat information, for privacy when sharing files.

Added additional effects and spikes to the details pages.

First report option finally implemented, allowing saving of the current displayed plugin page as a text file.

Speed improvements on the Offense page.
#71 Aug 29 2008 at 5:33 AM Rating: Excellent
Sage
***
1,220 posts
/wave

I'm the friend Norel was talking to about exports. I wanted to share some parses with friends so they could see how they were doing, as they weren't able to parse themselves. I've not gotten a chance to test that yet (just spamming campaign atm) but I'm quite looking forward to the capability. Much thanks. And the ability to select which POL instance to log from is so much <3 you win at least 3.14 internets.

One crash bug encountered in the new version, not serious I dont think (and totally not a complaint, just want to help track stuff): If you select the "Player Information" menu before any players have been logged, it causes a crash. I can send you the detailed information from it if it'd help. I reproduced it twice just selecting that right after starting parsing, and the third time I just went and killed a rarab and tried again and had the dialog box pop up np.

Edit: There was another bug I had in the last version, but I'm gonna try and reproduce it and get a saved database for it, as I couldnt quite figure what it was doing. XP/HR wasnt calculating properly, and most of our kills were showing as no-xp mobs. I *think* it only happened when I started parsing when a chain was already in progress, but I couldnt exactly ask that we kill the chain just so I can bugcheck sometime :)

Edited, Aug 29th 2008 9:33am by pogle
____________________________
Pogle | Gilgamesh Taru | Windy Rank 10 | ZM 17 | CoP/TAU Complete
75 BLM|WAR|RDM|RNG|BST|SAM|NIN|MNK|SMN|DRG | 56 BRD

Social LS: Icefire, http://becd.net/ffxi/forums
HNMLS: Spoondaggers
Dynamis: Anagram
Salvage: DisposeableHeroes
100+2 Alchemy | 59.0 WW | 40 GS | 25.2 Smithing

I'll try being nicer if you try being smarter.
#72 Aug 29 2008 at 8:19 AM Rating: Excellent
***
2,236 posts
Patch release 1.0.10.1 fixes the crash bug in the player info dialog. And I'm interested in seeing the other bug you found once you have something more solid.
#73 Aug 29 2008 at 8:42 AM Rating: Excellent
Sage
***
1,220 posts
If I merit this weekend I'll definitely try and reproduce it for you.
____________________________
Pogle | Gilgamesh Taru | Windy Rank 10 | ZM 17 | CoP/TAU Complete
75 BLM|WAR|RDM|RNG|BST|SAM|NIN|MNK|SMN|DRG | 56 BRD

Social LS: Icefire, http://becd.net/ffxi/forums
HNMLS: Spoondaggers
Dynamis: Anagram
Salvage: DisposeableHeroes
100+2 Alchemy | 59.0 WW | 40 GS | 25.2 Smithing

I'll try being nicer if you try being smarter.
#74 Aug 31 2008 at 10:21 PM Rating: Excellent
***
2,236 posts
1.0.11 released: http://code.google.com/p/kparser/.

Fixes a bug parsing pups. Getting Overloaded caused a quirk where the pup was reclassified as a mob, eliminating them from showing up in most report pages from that point on (which would of course distort any comparisons made against the job).

Added a somewhat experimental new plugin for Thief data (SA/TA/Hide) at the request of Melphina. This one is very expensive to process (takes about 10 times as long as the entire Offense page), so it gets the same minimal optimization restriction as the Offense Details page while a parse is running. Once I get the kinks worked out I'll see if I can improve the speed.


After this I plan on doing a complete revamp of the plugin architecture to make it easier for both myself and anyone else who wants to write a plugin, and make it easier to add certain features. That will be the 1.1 release line. I may also revise the database structure in that release.
#75 Sep 08 2008 at 2:27 PM Rating: Excellent
***
2,236 posts
1.0.12 released at http://code.google.com/p/kparser/

Uses the new default memloc of 0x00576D58.
#76 Sep 10 2008 at 10:56 AM Rating: Excellent
***
2,236 posts
1.0.13 released. Couple bug fixes, plus updates on the Thief plugin and addition of proper handling of the new weaponskills.
Reply To Thread

Colors Smileys Quote OriginalQuote Checked Help

 

Recent Visitors: 1 All times are in CST
Anonymous Guests (1)