^This. Everytime you restart SMART you increase your mem usage by ~200M? So running multiple clients will cause loads of errors.Quote:
Originally Posted by Harry
Printable View
^This. Everytime you restart SMART you increase your mem usage by ~200M? So running multiple clients will cause loads of errors.Quote:
Originally Posted by Harry
We talked about this on the SMART thread. If we can't find a solution, I'll make an option for restarting SMART. The user can choose whether or not to do so.Quote:
Originally Posted by KingKong
E: Harry, I still get this error after RS says it's updated.
http://img39.imageshack.us/img39/29/captureaei.png
I'm actually getting it even after I load RS in my browser.
I've read on other forums that this happens when you are logged in for 6hours.. Jagex sure knows how to annoy botters!
I don't think it's even being logged in for any amount of time - I've had it happen a few times recently where I've left the applet open (in a browser) and come back a few hours later to get that message.
Same man. I changed the SMART_World or w/e it is, and that fixed it.Quote:
Originally Posted by Coh3n
We'll be doing a system update in about 20 minutes to try and fix the problem with log-in timeouts for some people.
Keep an eye out for the timer!
Could this be the fix hmm?
That error will only happen if you're trying to load an invalid world. If you load a valid world now without updating it doesn't error, at least not for me.
This. I think the default for SMART_world in the include is random() every time its ran. With my scripts I always set SMART_world := 1 or 160 that way SMART doesn't have to reload.Quote:
Originally Posted by Harry
Happened to me after 2 hours.Quote:
Originally Posted by Fire Monkey
Me too.Quote:
Originally Posted by A G E N T
Let's hope so. :)Quote:
Originally Posted by Kave
Yeah, I got it to work now, thanks.Quote:
Originally Posted by Harry
How do you know you'll never get it with those worlds?Quote:
Originally Posted by Narcle
The actual build number isn't any more frequent than normal: http://www.moparisthebest.com/rs/update.log interesting...
This announcement says they're aware of the issue, I think. I'm assuming anyway as I'm not aware of any other type of login issue.
I think it's purposely there as an anti-ban measure. If it was some kind of bug then our players won't be getting kicked out of the game right around 6 hour mark.Quote:
Originally Posted by Coh3n
I have encountered this problem also, I have been running my personal M1D1 Powerminer for long periods of time on my main and every time I come back a few hours later RS has been updated, I definitely think its to catch bots and whatnot
I find that hard to believe simply because if I was a legit player I would find that rather annoying.Quote:
Originally Posted by insanomano
But not many legit players play for 6 hours straight.Quote:
Originally Posted by Coh3n
It doesn't always happen after 6 hours. A few people, including me, had it happen after only a couple hours.
Yes, I have seen that too. I have had session of 6 hours 54 minutes. But also 2 hours 45 minutes.Quote:
Originally Posted by Coh3n
Maybe it is at regular GMT/EST times?
EDIT:
BTW: are you too noticing a long lag (freeze) when re-entering the game after a random?
This and clicking on the quest/music/emotes tab. The bigger the list it has to load, the longer the lag...Quote:
Originally Posted by WT-Fakawi
I suspect when returning from a random they do some code-shuffling :)... why would it otherwise all-of-a-sudden take so long?
Yes, I've noticed it as well, sometimes it takes up to 3-5 seconds, can be very annoying nad yes, after coming back from random it will lagg much aswell. :(Quote:
Originally Posted by Flight
~Eerik.
There are a lot of areas atm that encounter large lag spikes when doing. They are actually trying to address that issue too (according to them).
About the "RS updating" stuff, I only have it happen to me when I log out of the game and try to log back in. It doesn't automatically "kick"/take me out of the game SOLELY to do this. So when your scripts go to switch players, that is probably when this comes up.
That would be pretty smart if that's what they were doing. IDs snuffled after every time that map region changes? Teleports/random events/walking to a different area.Quote:
Originally Posted by WT-Fakawi
Ya know if you hadn't said it I wouldn't have realized it. Click on your quest tab and after the long lag click to another tab, then back to the quest tab. It won't take any time at all to load it the second time, right? Now walk to a different area and try clicking on the quest tab again, another huge pause?
Hmm...now that yous guys are talking about those updates, I'll have to take a closer look when I play Runescape for long hours. And then, I'll see if post some stuff at this thread.
Thanks for you guys having me know..
Yes that's when it happens to me. I'll be running one player soon so we'll see how that goes.Quote:
Originally Posted by HyperSecret
I am running a single player script as well and it gets kicked near the 6 hour mark.Quote:
Originally Posted by HyperSecret
*You will be automatically logged out after 6 hours of continuous play. This is to stop someone who has hacked an account to stay on it, which helps the original owner recover it once they have changed their password. This can also stop bots, however, most bots are advanced enough to re-login. *Quote:
Originally Posted by kingarabian
Yes before they would kick you out of the game and you would have to re-log. BUT it now kicks you out, tells you Runescape has updated, and you have to reload the game. Don't forget some people have been getting this at the 2-3 hour mark as well.Quote:
Originally Posted by Kave
What makes it really suspicious is that as you reload the game, something is being updated or downloaded to either the cache or client because the loading takes its time...
Runescape is gay... what's really happening is ... they lose $$$ since bot accounts dont buy p2p anymore ... less players ... item stock will be lowered = more expensive (yews/food/runes/etc....)
RS should just let it be... either way, all these communities will find a substitute. Players will get irritated from these lags and what not and more people will quit ... since it is quite hard to make $ and get those 99's legitly. oh well that's Runescape or we are just too spoiled/use to the easy money income haha.
logged me out @ around 5 hours requiring me to refresh.
I played legit yesterday just to see what happens, I had been online for 5h and 53 min and got kicked, had to refresh aswell. :(Quote:
Originally Posted by kingarabian
~Eerik.
apparently its a pointless method to stop botting :/
Just to prove that the client indeed updates every 4-6 hours is that my bot logged me out @ just 1 hour of run time. 6 ours later I try to login to my account and it tells me Runescape has updated. Ofc Jagex really didn't update. So logged in our logged out the client updates in 6 hours. Which is a good time frame because not many legits play for 4-6 hours-ish straight.
My bot is about to come up to 5 hours total running. I have it setup to bot for 2 hours, then take an hour break, and repeat. I wish there was a way around it :/Quote:
Originally Posted by kingarabian
SMART just needs to be reloaded. IIRC you just have to call SetupSmartEx again when an update has been found. I've never tried this so I don't know if it works, but it's worth a shot.Quote:
Originally Posted by Camo Developer
Also, Ben said by doing that you could run into memory issues if you restart SMART several times because RS doesn't free the JVM properly (I think).
no because the RS memory is held in the program running it (in this case simba) meaning the memory doesnt get free'd and to free it you need to close and reopen simba, which would stop the script (i can remember pointing this out before and said it was a memory leak :p)Quote:
Originally Posted by Coh3n
lemme find it...
~shut
Yeah there are definitely problems with reloading SMART. I am running 6 SMARTS right now, imagine if I restart them all and the previous memory is not released? My memory would be 6x2 = 12 while I'm only running 6 SMART's.Quote:
Originally Posted by Coh3n
Just get wizzup to create something to somehow free only SMART memory and we will
Love Him Forever!!!!
It's the way SMART works which is the problem, and also the JVM.Quote:
Originally Posted by Yago
I just got back after several months off autoing/Runescape. I just started using my fighter the script yesterday again, works fine but after about 5 hours my game "Updated" and got me disconnected. When i woke up I set it up again about 1 hour and 30 minutes into this session I read a message as I walk by, "Runescape will be updating in 1 hour".
2 Updates so soon? :confused:
If you play longer than 6 hours continously...they "update" runescape.Quote:
Originally Posted by obx420