Bort's NWN Log Parser for windows

[mishimayukio]

Very nice program, but there are 2 issues I have with it. First, is there any way you can get the log to show TRs? The entries look like this:
[CHAT WINDOW TEXT] [Sat Feb 02 16:58:37] Lemure : Turn Outsider : *success* : (3 + 80 = 83 vs. TR: 68)
[CHAT WINDOW TEXT] [Sat Feb 02 16:59:21] Kocrachon : Turn Vermin : *success* : (6 + 65 = 71 vs. TR: 61)
[CHAT WINDOW TEXT] [Sat Feb 02 16:59:39] Anymental : Turn Elemental : *success* : (8 + 65 = 73 vs. TR: 68)
[CHAT WINDOW TEXT] [Sat Feb 02 16:59:59] Dedicated : Turn Undead : *success* : (7 + 70 = 77 vs. TR: 64)

Second, I run the log parser on a different computer computer than NWN, reading the log file over the LAN. It works fine in this way except for one thing, the fugue timer. The fugue timer only counts down when the parser updates making it extremely unreliable. Is it possible to make the timer run independent of the log reading?

I've really enjoyed using this program over the past 2 days, and it will be a staple of my NWN experience in the future. Thank you!

[secrecy]

(Don't know if this has been brought up before, I haven't read through the entire thread)

BUT!

Could there be added a "against which monster" colomn in the damage window?

This would be very usefull when fighting large hordes of monsters where you don't know precisely which baddie you're hitting.

(quick example: DB run, Sander, Living Sand, Spiked Devil and Sand Elemental in a group. You're hitting one of them, and the log-watcher lists your damage as 0 physical, 0 acid, 0 fire, 68 elec. But it doesn't say which enemy you hit.)

Now, pretty often, you know which enemy you hit due to clicking on it, but very often, at least for me, it would be -very- usefull if the log-watcher would list -which- enemy you're attacking on each line.

Would be appriciated if added, but understandable if not!

(Lastly; 'scouse my spelling if it's off. Fairly tipsy atm, just came home from celebrating my moms grand ole 60. The red wine was particullarily good!)

[bort]

mishimayukio said:

Very nice program, but there are 2 issues I have with it. First, is there any way you can get the log to show TRs?

Done, thanks for the suggestion. Will be in the next version.

Second, I run the log parser on a different computer computer than NWN, reading the log file over the LAN. It works fine in this way except for one thing, the fugue timer. The fugue timer only counts down when the parser updates making it extremely unreliable. Is it possible to make the timer run independent of the log reading?

The timer itself is independent of the log reading. There is one timer which controls how often the parser checks the log file for new entries (every 2 milliseconds) and another (independent) timer which counts down each fugue timer every second (if any are active).
How inaccurate are you finding the fugue timers?
A few seconds or way out?
If there's a uniform delay of a certain number of seconds when reading over LAN on your system I can add an option to automatically modify each timer to compensate...

I've really enjoyed using this program over the past 2 days, and it will be a staple of my NWN experience in the future. Thank you!

Glad to hear! Keep the suggestions coming please

secrecy said:

Could there be added a "against which monster" colomn in the damage window?

I can see this would have its uses when around party kickback critters in large mobs, I'll see about adding it asap. Thanks!

dirk said:

Ideally, I'd like to see a dash (-) in all the columns that were "not applicable" if the attack result was a miss. That would keep all my "rows" in synch and when I scroll back I'll have an accurate record of the damage done on a specific attack.

I guess if you did that, you could also replace all those scroll bars for each column with just one scroll bar for the entire "table".

Done. When you Miss, each damage box will now shift up one.
It's not perfect (for various reasons, such as damage shields and spells cast mid combat - i.e. battle cleric casting earthquake or WoF) but it is nicer i suppose. This'll be in the next update. Thanks!

The information read from the logs isn't currently stored in a table, it's just read line by line from the logs and fed straight into appropriate boxes. I might experiment with linking the scroll bars somehow in future so you can scroll one box back up and the others will follow... There is a cut-off point where the oldest information in each box is removed though, so you wouldn't get a full history after a long run.

dirk said:

Another nice little tweak would be if you could specify a list of character names somewhere in the ini file (or a separate file) and the "Analyze" box would offer the option of a drop-down so you could select a character name from that list. Obviously still be able to type one in.

I'll see about adding this asap, thanks!

[bort]

Version 1.6 uploaded!
--Added Turn Resist
--Minor Tweaks

-Bort

[mishimayukio]

bort said:

How inaccurate are you finding the fugue timers?
A few seconds or way out?
If there's a uniform delay of a certain number of seconds when reading over LAN on your system I can add an option to automatically modify each timer to compensate...

It varies on how much activity there is in my game. When active in a hells run the timer is sometimes still counting down 10-20 minutes after the death, when its not active it is usually right on target, give or take a few seconds.

[bort]

mishimayukio said:

When active in a hells run the timer is sometimes still counting down 10-20 minutes after the death, when its not active it is usually right on target, give or take a few seconds.

Odd.
Sounds like NWN is using up so many CPU cycles that the connection between the two computers is being momentarily interrupted.
I'm not sure what I can change in the parser to fix that..
Are you using the default log directory for nwn and telling the parser to access that over the network using sharing or have you told nwn to write logs over to a network folder on the computer you're viewing the parser on by altering nwn.ini?
In either case it might be worth trying the other method to see if it gives better results.
Hope that helps.

[bort]

Has anyone got the parser running successfully in Vista?
I got a message from Moon saying it wasn't working properly for him and I wondered if anyone else had the same issues or whether it worked fine for them?
Cheers
-Bort

[mishimayukio]

bort said:

In either case it might be worth trying the other method to see if it gives better results.

Tried it and NWN got horrid unplayable graphics lag during hells runs.

[arturus]

I have not been able to get it to work correctly with Vista, but don't think that it is because of the parser app. In dual screen mode I can't get NWN to run on the primary monitor and other apps (Firefox for example) to run on the secondary. Either one apps or the other will display both not both simultaneously. If I switch monitor assignments around run NWN on the secondary monitor, then with some fiddle and much screen blanking during transitions, I can get both NWN and the parser to display, but the the parser doesn't update. I'm not sure if the is card/driver related or not (have nvidia 8800GTX card). I've tried using the parser both with 1 and 2 monitors and in windowed or unwindowed NWN mode. Also locked NWN to a single processor (since I have a dual core CPU) but that made no difference. The parser starts, accepts the character name, log directory, etc but never gets any real-time updates or show stats. It appears that NWN under Vista is not happy about sharing video (or other) resources . I've not spent a huge amount of time on this yet, mostly just poking at it occasionally and waiting to see if others mentioned having problems. I suspect my next step will be to boot into XP to make sure it works on my setup there.

[bort]

mishimayukio said:

bort said:

In either case it might be worth trying the other method to see if it gives better results.

Tried it and NWN got horrid unplayable graphics lag during hells runs.

Thinking about this some more, I might be able to work out something clever to get round the problem, by checking the time that each 'death' message is written to the log and comparing it to the current time.

I'll have a look at it when I get the chance.

[stonewarrior]

I run NWN on Visita (no problems at all) and set the parser up on my laptop which runs XP. I was able to get it to start but then it stops. So, I hit start again and it works...but the data is the same data as it had already loaded. Any suggestions?

Peace, John.

[dodrudon]

Me too. Basically, you hit "start" and it runs through the log, then when it hits the end it stops. And when you hit "start" again it processes the entire thing....

[bort]

Stone: Have you changed nwn.ini to save log files to a directory on your laptop, or did you set the parser to read from your Vista machine?

@dod: What's your setup?

The parser should update as your logs update based on a filesize check every 2 miliseconds... you should only have to hit Start once. Not sure why that isn't working with Vista, I don't have a copy to test on..

[dodrudon]

Exact same as Stone's, and the latter.

[bort]

I'm guessing there's a compatibilty issue with one of the functions in Visual Basic 6 (the program I program the parser in) and Vista.
Trust microsoft to fail when it comes to backwards compatibility ^^

I'm really short of free time at the moment, but will try and research why it's not behaving as it should in Vista (as well as implementing other updates on the todo) when I can.

Cheers
-Bort