First global screenshot

bass

Guardian
Joined
Jan 30, 2009
Posts
259
Location
Italy
Society
NBK Elite Miners
Avatar Name
Bass Rockabilly Master
On both PC I run ET on, the screenshot of the first global is taken considerably too late (I'm talking about seconds). That's probably (I guess) because some DLL/libs are loaded upon first use, the first time a "grab" is performed.

What about taking a "fake" screenshot at startup, so that any dependency is loaded and then cached by the system for later use (real screenshots)?

Just FYI, I've observed the same behaviour (and posted the same advice) on ESG.
 
Can you please tell me your specs.
As well as chat.log size?


The reason why it could take a fair bit of time is that the tracker takes 1.5 seconds to do "one loop" (read the chat.log)... If you then have selected 500 ms as delay.
It could in theory take 1.5 + 0.5 - 0.0001 seconds after your global, for the program to take the screenshot.

The "brutal" solution to this would be to scan the chat.log every 0.2 second - but unless you are running SSD disks on a small chat.log, i think your computer will tart complaining. :)
 
Uhm, 2.5Mb, with fast enough HW (dual procs, 4Mb RAM, SATA).

Note that only THE FIRST global is taken late, not the following ones. Hence my consideration (better, my guess) on DLL loading... But just a guess.

The following globals are taken correctly enough (they catch the swirl).

Just another 2 cents ;)
 
Back
Top