LogWatcher by syn

[Lastone Yusee [SL]]

Ok, I'll look back through. Don't have an ATI card though, and as much Alt-Tabbing as I've done hasn't availed me yet, but maybe I am missing something.

Thanks

[onesock]

Very nice app Syn! Kudos for the product, and thanks for taking the time to build it.

I tried it out on a Thids run last night - but about halfway through the run it stopped logging damage (it kept logging xp, monitoring fugue timer, etc). After the run I looked in the watcherrlog.txt and noticed:

12.03.08. 00:48:25 Traceback (most recent call last):
File "C:\nwn\NWN\logs\logwatcher.py", line 379, in idle_func
check_action(line)
File "C:\nwn\NWN\logs\logwatcher.py", line 290, in check_action
srs = lajn[4][1:3]
IndexError: list index out of range
(Last line: [CHAT WINDOW TEXT] [Wed Mar 12 00:48:25] Illithid Fieldmaster : Spell Penetration : *immune*)

and

12.03.08. 02:05:28 Traceback (most recent call last):
File "C:\nwn\NWN\logs\logwatcher.py", line 379, in idle_func
check_action(line)
File "C:\nwn\NWN\logs\logwatcher.py", line 290, in check_action
srs = lajn[4][1:3]
IndexError: list index out of range
(Last line: [CHAT WINDOW TEXT] [Wed Mar 12 02:05:27] The Surrogate : Spell Penetration : *immune*)

Would that have anything to do with it not logging?

Cheers!

[synan]

Certainly would, thank you very much for reporting this!

I will be fixing it in the next version, didn't know things can be immune to spell pen

[synan]

Finally made some progress with running this thing on linux, and am finally able to use the app myself lol

Anyways, still getting info on various window managers, but here's the trick to get it to overlay the game on linux. First of all, edit your nwn.ini and add AlowWindowedMode=1 to your [Display] section, then change the FullScreen from 1 to 0. That will run the game in a window, but if you run the game in the same res as your desktop it will be full screen actually, but having the window decorations (border, titlebar with buttons). On kde you can rightclick on the titlebar and under advanced choose "No border", that will effectively make the game "true" fullscreen and you can make _any_ window overaly it, logwatcher included. Since I'm finally able to actually use the thing and I made a desert run with it I found some "issues" that will be addressed in the next update (yes, the damage counters will finally be fixed so they don't push themselves out of the window) and some minor linux tweaks are due (problems with log switching for some reason).

I'm wondering how many linux users are actually using this, I seem to recall at least one?

I'll be adding all details for various window managers to the original post when I gather them for the most common wms (btw, openbox/fluxbox and I'm guessing *boxes have the option to turn off window decorations on right click too).

I would like to shout a big Thank You to deepscout999 of WNx for his help and effort testing the thing out in various scenarios. Thanks man

EDIT: I just figured the same method might be used to run it on Vista too, not sure tho, if someone tests it lemme know please!

[thirddeep]

Adding my voice for support of Linux !

Thanks.

Thd.

[ferghus]

I'm using your logwatcher in Linux with KDE 3.5.6. Use it all the time (for about the last month and half or so). Worked great, 'out of the box', so to speak. Didn't have to tweak anything to get it to stay on top, be the right size etc. except I did have to start playing in window mode instead of full screen. That was a little adjustment in play style, but now I'm used to it.

Only two issues I've noticed with it. First is that the window needs to be resizable or bigger or something, since as damage accumulates, it fills up the small window and then the rightmost displayed damage type - divine - is no longer visible. Resizable would be most useful, but not sure how hard that would be to implement.

Second is that after a while, it just stops logging data. Pretty much hangs. So, I can usually get through 2 maps of a Hells run, or maybe three maps into something like DB, Thids or such before this happens. Usually thats ok, since I'm using this mostly for monitoring damage types in order to manage rings and items better. Though, it is nice to have the deathclock functioning.

Either way, it's all good. I've really learned a lot about various runs while using it and it's clarified and helped with a lot of confusion. Thank you very much for your efforts on this great utility.

Ferghus

[synan]

ferghus said:

I'm using your logwatcher in Linux with KDE 3.5.6. Use it all the time (for about the last month and half or so). Worked great, 'out of the box', so to speak. Didn't have to tweak anything to get it to stay on top, be the right size etc. except I did have to start playing in window mode instead of full screen. That was a little adjustment in play style, but now I'm used to it.

Well, I would consider that severe "tweaking" haha, anyways, as I said earlier, if you run the game in the same resolution as you have your desktop you can remove the border on the window and it is basically normal fullscreen.

Only two issues I've noticed with it. First is that the window needs to be resizable or bigger or something, since as damage accumulates, it fills up the small window and then the rightmost displayed damage type - divine - is no longer visible. Resizable would be most useful, but not sure how hard that would be to implement.

Not hard to implement at all, one option really, I actually forced it to be nonresizable. However I did notice some font issues on kde being it's actually a GTK window, you can set the font size in yout gtkrc file, I can give you the details if you need it. However I have also noticed that the div damage gets pushed out even with smaller font, and will be adressing the issue somehow, rounding stuff to tens of thousands as suggested and with some other tweaks. Bare with it just for a little bit more

Second is that after a while, it just stops logging data. Pretty much hangs. So, I can usually get through 2 maps of a Hells run, or maybe three maps into something like DB, Thids or such before this happens. Usually thats ok, since I'm using this mostly for monitoring damage types in order to manage rings and items better. Though, it is nice to have the deathclock functioning.

I discovered this yesterday and also with some poking around the terminal while playing I found the issue and fixed it. For some reason completely vague to me the linux version of the game rotates logs on 2500000 bytes and the win version goes up to 2520000, as I was going as close as possible and people only tested it on windows the problem was silent till now. I will implement an OS check that will solve it for now, untill the planned redesign of the log rotating detection is in. Btw, you can fix this yourself with just replacing the 2 occurances of "252" with "250" in the logwatcher.py file, open with any text editor and search and replace.

Either way, it's all good. I've really learned a lot about various runs while using it and it's clarified and helped with a lot of confusion. Thank you very much for your efforts on this great utility.

Ferghus

Glad it's useful, I have many more features planned for it, just a bit short on time.

[maxekist]

I've been trying to use the logwatcher, installed everything right in the right place, started it, but once in game, i can't stop it from flashing. Been able to start it on and it seems to work, but it flashes and so, it is absolutely horrible to use! Been alt-tabing 20+ times just as said by CataclysmicDeath when talked with him, but still, it flashes and flashes again!
Would really appreciate to be able to make it work though!

Edit: just seen what said on last page(didnt go through all the 11 pages before to post)
But i don't have an ATI card. My card is a intel mobile 945GM but it flashes too.
If you have any idea...

[icevvind]

I'd like a command with which i could switch the SR and SP lines to something like mortal strike / called shot kills and DC, or the enemie's save against that. (Or anything else that would fit in that space) Mainly as i don't really have a use for the SR/SP lines as non-caster.

[ankorite]

Hello I've been using the logwatcher on my OLPC laptop laptop.org for a little while now while I play on my other computer. The OLPC laptop comes with python installed and is built on fedora core 7 so it worked out of the box. I export my nwn log directory using nfs and mount it locally in a temp directory on the laptop. The only thing I did was change the "width_request" and "height_request" property's in nwn.glade to better fit the laptops 1200x900 display. I'm gonna give overlaying it a try now that you've figured it out.Thanks for making this sweet program!

Ank

[synan]

maxekist said:

I've been trying to use the logwatcher, installed everything right in the right place, started it, but once in game, i can't stop it from flashing. Been able to start it on and it seems to work, but it flashes and so, it is absolutely horrible to use! Been alt-tabing 20+ times just as said by CataclysmicDeath when talked with him, but still, it flashes and flashes again!
Would really appreciate to be able to make it work though!

Edit: just seen what said on last page(didnt go through all the 11 pages before to post)
But i don't have an ATI card. My card is a intel mobile 945GM but it flashes too.
If you have any idea...

Well, as I don't really know what's causing it (guessing it's a battle between game/logwatcher for the top layer) I can't fix it. Does it overlay and then flicker or does it appear over the game every second and then vanishes?

[synan]

icevvind said:

I'd like a command with which i could switch the SR and SP lines to something like mortal strike / called shot kills and DC, or the enemie's save against that. (Or anything else that would fit in that space) Mainly as i don't really have a use for the SR/SP lines as non-caster.

An ini file is already on my TODO, will add a way to define what is shown where.

Btw, the SR/SP works for turners too, and AA (bigbie arrows). Prolly for something else too.

[scarabamassa]

well i tried this, installed in the exactly way it is described but im gettin an error message like this :
"python.exe - Point of Entry not Found"
"Not Possible to Find The point of entry of procedure g_assert_warning on dinamic bound library lidglib-2.0-0.dll."

sorry.. tried to translate this cause here the message appears in portuguese

Scaraba

[synan]

With some googling it seems to be a GTK problem, you probably have something else using GTK libraries and the versions missmatch, like Gimp or Gaim/pidgin or something. Anyways, this supposedly fixes the problem:
"renamed libglib-2.0-0.dll in C:\WINDOWS\system32 to -libglib-2.0-0.dll"

I would suggest you check the other GTK apps for possible breakage after that.

[scarabamassa]

synan said:

With some googling it seems to be a GTK problem, you probably have something else using GTK libraries and the versions missmatch, like Gimp or Gaim/pidgin or something. Anyways, this supposedly fixes the problem:
"renamed libglib-2.0-0.dll in C:\WINDOWS\system32 to -libglib-2.0-0.dll"

I would suggest you check the other GTK apps for possible breakage after that.

well thanks.. this worked.. aparentelly the dll files went to system folder not system32.. i renamed on system32 and didn't worked but when i renamed in system it worked.

Scaraba