Kharma

Okay! This got me thinking... and I tried starting the game and combat/IM logging BEFORE starting the LotroLCD client. Viola! I now have a working DPS meter! I just had to give it files to read BEFORE it found none and created it's own.

vindalfur

The client should periodically check for newer log files and if they are found it should switch to those, thanks for the debugging, it gives me a great place to start tracking down the fault.

Can you verify that you have the latest version of the client (1.0.5), I've tried downloading the X86 client from this page and the dallur.com links and on my machines and virtual machines it always picks up new files automatically so I'm at a loss as to why this is happening.

Regards

Jarl

vindalfur

Fyndir, it sounds like your having the same issue as Kharma, can you try starting the LotroLCD client after you start combat logging and see if that is a valid workaround until I'm able to fix the issue?

Regards

Jarl

Kharma

Well, I reinstalled the program, to be sure that I had the latest version. Started the client, then started Lotro, start logging, then started the plugin. It's working perfectly now. I'm not sure what the issue was, or how it was resolved... but it's working fine now, without the work-around.

Thraxz

I've an issue while running this plugin on Windows7 64 bit. When first loaded it works perfectly and continues to do so. After a few hours of play my computer's performance in game grinds to a crawl. Like from 100-50 FPS down to 30-10FPS. If I restart the client or disable the plugin performance returns to normal.

Hardware is an i7 920 @ 4.0Ghz, 6gb ram, an ATI 4870 and an SSD.

Thanks.

vindalfur

Thanks for alerting me to this issue, just to clarify you mean you have to restart the LOTRO client not the LotroLCD.exe right? Sounds like an issue with the way the LUA code loads data, I copied the methodology for data loading from DPSMeter and although it's brilliant in allowing realtime data loading it uses a method which is a bit hackish and I suspect it's this form of data loading that causes a memory leak in the Lotro client.

If this happens again do you think you could help me verify this by opening up the Windows Task Manager and checking how much Memory (working set) the Lotro.exe client is using before restarting the client?

In the meantime I'll try to find a way of releasing the memory but It's quite possible it can't be done in LUA and I don't have access to the Lotro client code to fix it in there.

I've added it to my issues list:
http://code.google.com/p/lotrolcd/issues/detail?id=18

Jarl Stefansson
Vindalfur @ Brandywine
[email protected]

Thraxz

My 'just booted up' memory usage on the client is 1.333Gb (1920x1200 resolution and everything on does that). I'll load up the plugin in a bit and get back to you.

Thraxz

Hi, I ran the game again and then turned on the plugin after a few hours of being normal. Ram usage was at 1.8GB. After another hour of using the plugin the performance took its usual dive and I checked the ram usage on the the client and plug in. Ram usage of the client was still ~1.8GB and the lotrolcd was only at ~18MB, up from about 2MB at start up. My free ram was over 50% (6GB). I don't think this will help.

vindalfur

Ok, sounds like it's not a memory leak, I'm thinking it might be a file handle leak instead, I'm having a hard time reproducing it over here, I can keep it running several hours without issues, perhaps you could check the file handle count instead of the memory usage?

R.

Jarl


Hi, I ran the game again and then turned on the plugin after a few hours of being normal. Ram usage was at 1.8GB. After another hour of using the plugin the performance took its usual dive and I checked the ram usage on the the client and plug in. Ram usage of the client was still ~1.8GB and the lotrolcd was only at ~18MB, up from about 2MB at start up. My free ram was over 50% (6GB). I don't think this will help.

Thraxz

Well here's some SS of what happens. Note the FPS just above the travel window.

Before turning off lotroLCD plugin.
http://i283.photobucket.com/albums/kk319/Nazgulofminasmorgul/ScreenShot00059-1.jpg

After turning off lotroLCD. (literally 5 seconds later)
http://i283.photobucket.com/albums/kk319/Nazgulofminasmorgul/ScreenShot00060-1.jpg

vindalfur

Was turning off the plugin enough to fix the FPS?
If so does the FPS drop again if you start the plugin again?

Jarl

Thraxz

Yes, it returned it back to normal ending the lotroLCD plug in. LotroLCD can continue running in the background fine, so perhaps it's with the plugin itself. Have you tried alt tabbing in and out of the game to try and replicate my problem? It seems to happen more quickly when I'm alt tabbing in and out.

vindalfur

I think I have now been able to reproduce this, after a couple of hours I see a drop in the fps, I've gone through the code to try to find the cause but it's hard to pinpoint, I still suspect the code block that imports the stats (the one that originated in DPSMeter).

The problem is definitely in the LUA plugin, for now I guess the workaround is to restart the plugin every couple of hours (/plugins unload and /plugins load lotrolcd).

I'll try isolating the cause over the course of the next few days, and keep you posted.

Jarl

vindalfur

Just released version 1.0.6 which has a new data element called hdps (history dps), this element shows the average dps since LotroLCD (the exe) was started.

Due to time constraints I left the reset/clear and settings buttons for the next release but the UI is a lot better and LUA performance has been improved by a factor of 1000 or so and any performance issues should be history.

You can use the same links as before to download the new version.

Feedback is encouraged as usual.

Jarl Stefansson
Vindalfur @ Brandywine
[email protected]

Thraxz

Oh, awesome thanks. So far it's working like a charm. I really like the historical DPS too. Great addition.

Wish List:
I wish I could set the transparency level on the window, I don't know if this is possible.
I eagerly await the clear buttons.