Recent Posts

Pages: 1 ... 4 5 [6] 7 8 ... 10
51
Thanks for the PM.  Nothing is changing very much from the variable world.  I recommend you going through all your Rules in the "Rules" tab and de-selecting everything that has a "Log?" checked.  This will prevent the "History" tab from getting too large and this might slow things down.  You can also check your history tab and see how many items have been cataloged over time.  If the number is large, then removing the logging might speed things up a bit. 

Actually, there's a variable at the top of the script called "%use_history" that you can change to #FALSE to turn off all history collection.  You might try that first instead of unchecking everything to be logged.

If that doesn't work then I'm at a loss.

I had sent you a pm, anyway I will try to use set %use_history #FALSE and see if it helps. I will keep you posted, thanks a lot for your help. I realized noone else is having the issue as I did not see anyone replied in the post or because noone is using long enough to notice the issue?
52
Thanks for the PM.  Nothing is changing very much from the variable world.  I recommend you going through all your Rules in the "Rules" tab and de-selecting everything that has a "Log?" checked.  This will prevent the "History" tab from getting too large and this might slow things down.  You can also check your history tab and see how many items have been cataloged over time.  If the number is large, then removing the logging might speed things up a bit. 

Actually, there's a variable at the top of the script called "%use_history" that you can change to #FALSE to turn off all history collection.  You might try that first instead of unchecking everything to be logged.

If that doesn't work then I'm at a loss.
53
How many rules in total do you have?  Also, are you running any other scripts in parallel with the looter? 

I have seen sometime when loot time increases as run time also increases, but not nearly what you're experiencing.

The real only thing that we have control over is the size of the variables that are accumulated over runtime.  You might want to take a snapshot of your vardump (Tools/VarDump) when you first start the script, and then take one when you start experiencing slowness.  Then compare the sizes (in bytes or lines) of the 2. 

It's been a while since I did an analysis like this.  Feel free to PM me your results, but don't post the actual vardumps because there's account specific information.

Also, there's an older version still posted.  You might want to try that and see if it works differently.

I had tested the old version too. They are both about the same after 1 to 2 hours of nonstop looting. I had pm you my vardump files. By the way, how can we control the size of the variables that accumulated over runtime? Is there a way to clear easyuo cache while running it or the namespace data?
54
How many rules in total do you have?  Also, are you running any other scripts in parallel with the looter? 

I have seen sometime when loot time increases as run time also increases, but not nearly what you're experiencing.

The real only thing that we have control over is the size of the variables that are accumulated over runtime.  You might want to take a snapshot of your vardump (Tools/VarDump) when you first start the script, and then take one when you start experiencing slowness.  Then compare the sizes (in bytes or lines) of the 2. 

It's been a while since I did an analysis like this.  Feel free to PM me your results, but don't post the actual vardumps because there's account specific information.

Also, there's an older version still posted.  You might want to try that and see if it works differently.

Thanks for your reply, TM. I'll try using vardump before and after running the script for a few hours. I'm also running another script that calls CLAW to check loot. Additionally, I'll test an older version to see if the scan time increases over time with that as well. Actually, I noticed this issue a while ago, but since I wasn’t running it for long periods, I just lived with it until now, lol.
55
How many rules in total do you have?  Also, are you running any other scripts in parallel with the looter? 

I have seen sometime when loot time increases as run time also increases, but not nearly what you're experiencing.

The real only thing that we have control over is the size of the variables that are accumulated over runtime.  You might want to take a snapshot of your vardump (Tools/VarDump) when you first start the script, and then take one when you start experiencing slowness.  Then compare the sizes (in bytes or lines) of the 2. 

It's been a while since I did an analysis like this.  Feel free to PM me your results, but don't post the actual vardumps because there's account specific information.

Also, there's an older version still posted.  You might want to try that and see if it works differently.
56
I’m noticing that scan times are increasing over time. Initially, scanning 3 Omit rules and 9 Active rules takes around 1.5 to 1.9 seconds for 5-7 items. However, the scan time gradually increases. After an hour, the same rules take about 23 to 27 seconds, and it continues to rise. The last time I tested it, after 2 hours and 30 minutes, each scan was taking 39 to 45 seconds. The only way to reset it is to stop the script, reload it in EasyUO, and start again, but eventually, the scan time increases again with each scan per corpse.

Anyone had encountered this issue and is there a fix for that? I am using the version 0.783.
57
Are you using large containers in the client? It may require a change to the gump size that the script is expecting.
58
Hello, I am having a problem with the bank.  It does not recognize it open and keeps opening bank and not placing anything in the secure
59
lets try it out

Hello! If you are curious about this script, I would suggest going to the new member section. Read the stickied "good intros" and then make your own "good intro" so you can have your restricted access removed.
60
lets try it out
Pages: 1 ... 4 5 [6] 7 8 ... 10