Working Parser?

[Hakamaru]

Someone who has a TTL of 11266 has 31.52% of total damage done while someone with 118207 has 28.02% of total damage done.

In that case, I'd like to see the dump for that parse. Attach it to a PM or a reply to this thread please.

Did you observe the total during the course of this parse? Did it simply get stuck at 11266? Or was it doing something else entirely?

Edit: nvm the underlined part... you say you're resuming a previous parse. I'd still like to run the dump through the parser with the debugger going.

[Xrave]

we use a series of accumulators; Due to issues with non-nm's sharing mob names, if such a feature were implemented it wouldn't be accurate except in parties that were similar to the setups of parties in 2004 (like when spyle's was popular) if people are doing damage at the same time to two mobs of the same name, the parser has no way to distinguish which is which.

and doing weird things with multiple mobs can lead to strange results (like colibri with 0 hp) or two deaths while someone records all the damage on one mob and none on the other but getting counted as two fights instead of one.

I mean, it'd be possible to write the feature (you'd just add a few more value to each player: last_damage_total, accumulate TTL - LDT into another accumulator field, divide by kill count (which might need to be created? I don't remember if we track.) and display. increment LDT to TTL each time a kill is recorded. test for TTL = LDT to check for afk fights.

I realize the instances where it wouldn't be accurate (would only really happen if you were fighting 2 different mobs with the same name at one time, not just mobs with different names). You can look for the "X defeated by Y" to reset the damage/fight.

Even with the inaccuracy of that in the one instances where you are attacking the same mob type at the same time (don't think there's an issue with 2 different mob names at the same time), it's a feature I'd like very much as it's something that would remove inaccuracies such as the wyvren pets being used to inflate total damage. You could also go back in FFXIP and choose which mobs you didn't want included in the total results...so as you're parsing you could write down what fight number you're on when things like the wyvern pet is added, or a Sleepga goes off and only 1 person does damage for 25% of the mob's HP due to slow mages, etc.

[Breemer]

Whenever I try to open a saved parse (from any version) the parser screen is totally blank and won't update.

[Wizerd]

I read through the thread but couldnt find a solution to the problem. Has anyone figured out how to get the loot to be parsed? I was running it last nite parsed battle data and how many monsters were killed just fine, but it did not list their drops.

//unload timestamp (I realize the response is late but figured I'd post it anyway )

[Fallso]

Someone who has a TTL of 11266 has 31.52% of total damage done while someone with 118207 has 28.02% of total damage done.

In that case, I'd like to see the dump for that parse. Attach it to a PM or a reply to this thread please.

Did you observe the total during the course of this parse? Did it simply get stuck at 11266? Or was it doing something else entirely?

Edit: nvm the underlined part... you say you're resuming a previous parse. I'd still like to run the dump through the parser with the debugger going.

I'll send you it in a PM, just a note aswell, any parse I load up has the same value for TTL "11266".

[Hakamaru]

I'll send you it in a PM, just a note aswell, any parse I load up has the same value for TTL "11266".

Seems like something odd with your system or files since I'm getting something reasonable when I load your dump.

http://i77.photobucket.com/albums/j7...allsoTotal.png

I'm not quite sure what to suggest. Make sure your .NET is set up and all that. Maybe download the package again from SourceForge.

Are you only having problems resuming old dumps? Or are you seeing any live parsing bugs as well? One thing you might try is loading a dump, then going out and swinging at something once. See if it rights your problems when the screen is updated.

[ASG]

I read through the thread but couldnt find a solution to the problem. Has anyone figured out how to get the loot to be parsed? I was running it last nite parsed battle data and how many monsters were killed just fine, but it did not list their drops.

//unload timestamp (I realize the response is late but figured I'd post it anyway )

Works like a charm now. what does the timestamp do to stop it from parsing the loot?

[Amele]

I read through the thread but couldnt find a solution to the problem. Has anyone figured out how to get the loot to be parsed? I was running it last nite parsed battle data and how many monsters were killed just fine, but it did not list their drops.

//unload timestamp (I realize the response is late but figured I'd post it anyway )

Works like a charm now. what does the timestamp do to stop it from parsing the loot?

modifies the chatlog. I thought it had been fixed for all lines but I guess there's something about the loot tracking that isn't quite right yet.

[eva00r]

I'd like to have some new colums called spells damade high/low/avg and a special report on spells. That's a suggestion tho.

[Xrave]

A problem that I'm getting that wasn't apparent in DVS is that when I'm parsing full alliance damage, the game will lag up every second or so when it appears that the parser is reading information from memory.

On DVS I could parse an entire DL with alliance and outside damage not filtered and get no lag at all.

[Amele]

A problem that I'm getting that wasn't apparent in DVS is that when I'm parsing full alliance damage, the game will lag up every second or so when it appears that the parser is reading information from memory.

On DVS I could parse an entire DL with alliance and outside damage not filtered and get no lag at all.

applications are basically the same. did anything else change? parser also checks alot faster than once a second so if it's regularly once a second I doubt it's direct parse.

[Xrave]

Well it does happen faster than 1 time a second, but basically just used once a second to describe it.

It only happens when DP is running, and only when an alliance or more of people are unfiltered for the parser to read it. No lag at all meritting at mamools, dynamis, any area with lots of people doing damage with the parser running with filters on so only party damage is checked. Also no stutters in the same situations with filters off and DP not running.

[Hakamaru]

Well we've added more regular expressions to the parse engine for new features. This has a multiplicative effect on computation, so it's possible that we're simply taxing your system too much.

One thing you might try is turning off all the reported columns while you're parsing since that will save a bunch of screen-update routines from running. You can turn on reporting fields later, after you've collected the dump.

[Anakron]

I just start the parser program before I'm about to parse whatever it is, not before I log in, but when I log out to a mule and come back I have to restart the program to get it to work, so its probably due to you starting the parser before your char is logged in.

I can look into it to be sure, but I believe the application will fail if there's no chatlog in memory (because the pointers won't dereference correctly.) since the chatlog isn't created until you actually log in (why would it exist before then?) it fails.

this is, of course, correctable - but it would take alot of work relative to the severity of the problem.

just don't start the parser until you're logged into the game *shrugs*

I start DirectParse (v2.1.1) after I login, but I seem to have the same problem with the parser basically not reading anything. I've tried closing and re-opening several times while logged in but it doesn't work. I'm using Vista, running the official Windowed version and also installed WoTG using the EU torrent copy while everything else was US. Would any of these cause this problem?

I searched for "vista" and "window" throughout this thread but didn't catch anything related. Thanks in advance for any help.

[SamanosukeShiva]

which folder should i unzip the directparse to? does it matter? how do i parse?

sorry kinda newb to this whole parsing thing, just recently switched from PS2>PC

[Fallso]

I'll send you it in a PM, just a note aswell, any parse I load up has the same value for TTL "11266".

Seems like something odd with your system or files since I'm getting something reasonable when I load your dump.

http://i77.photobucket.com/albums/j7...allsoTotal.png

I'm not quite sure what to suggest. Make sure your .NET is set up and all that. Maybe download the package again from SourceForge.

Are you only having problems resuming old dumps? Or are you seeing any live parsing bugs as well? One thing you might try is loading a dump, then going out and swinging at something once. See if it rights your problems when the screen is updated.

only happens when I resume the parse, I'll try downloading the package again.

[Amele]

I just start the parser program before I'm about to parse whatever it is, not before I log in, but when I log out to a mule and come back I have to restart the program to get it to work, so its probably due to you starting the parser before your char is logged in.

I can look into it to be sure, but I believe the application will fail if there's no chatlog in memory (because the pointers won't dereference correctly.) since the chatlog isn't created until you actually log in (why would it exist before then?) it fails.

this is, of course, correctable - but it would take alot of work relative to the severity of the problem.

just don't start the parser until you're logged into the game *shrugs*

I start DirectParse (v2.1.1) after I login, but I seem to have the same problem with the parser basically not reading anything. I've tried closing and re-opening several times while logged in but it doesn't work. I'm using Vista, running the official Windowed version and also installed WoTG using the EU torrent copy while everything else was US. Would any of these cause this problem?

I searched for "vista" and "window" throughout this thread but didn't catch anything related. Thanks in advance for any help.

make sure you run it in xp compatibility mode.

[SamanosukeShiva]

for vista, run the parser as administrator.

[Hakamaru]

which folder should i unzip the directparse to? does it matter? how do i parse?

sorry kinda newb to this whole parsing thing, just recently switched from PS2>PC

It doesn't matter where you put the files for this parser since it's not concerned with your file system. Just make sure you leave DirectParse.exe in the same folder as all those .dll files and DvsConf.txt. You can make a shortcut to DirectParse.exe, place that on your desktop and things will work just fine.

[Xrave]

One thing you might try is turning off all the reported columns while you're parsing since that will save a bunch of screen-update routines from running. You can turn on reporting fields later, after you've collected the dump.

Tried it again on a DL yesterday. This suggestion worked, it looked like it was just a window refresh issue.