SRL Archive - Help

I'm always at 90-100% cpu usage. Just now the bot stopped working because of it. Minimizing simba takes some ram and cpu so as I was doing it, runescape froze and the script said shutting down.

I have MINUMUM SETTINGS in runescape, cpu usage at very low. I also used disable graphics, made no difference. Computer is pretty crappy, got 500mb ram (and simba uses 400mb of it while botting).

Yeah mine uses about the same, there's not much you can do about it as it needs to run java, the rs client and the script all at once.
If you want games these days to run smoothly your going to have to get at least 1-2 GB RAM.
One suggestion might be to reduce the priority of the process and not run anything else in the background (going through processes and shutting off everything that is not needed).
Not sure how much that would help you though.

~Caotom

Best way to lower CPU is move the slider on SMART down, which lowers the FPS on rs (Frames per second). Besides that no much else you can change besides low RS settings, and set CPU usage to low on rs.

I found the most effective way to lower CPU is to buy a new cpu.

MoMo! Baneling! Hell yeah! +rep!

From: mormonman
I found the most effective way to lower CPU is to buy a new cpu.

This does work very well!

updating to simba 0.99 and smart v7.2 instead of simba 0.984 and smart v6.9c will increase CPU usage. Now smart and simba will appear separately in task manager and both uses CPU. Anyone experiencing the same issue?

Open task manager, see what process is using all the CPU, kill it, enjoy having 5% CPU usage.

From: Arepirpi
updating to simba 0.99 and smart v7.2 instead of simba 0.984 and smart v6.9c will increase CPU usage. Now smart and simba will appear separately in task manager and both uses CPU. Anyone experiencing the same issue?

I don't think CPU usage should have increased. Previously SMART was living inside the Simba process, now it's outside the process. There should hardly be a difference. If you add up the usage of both it'll be like 984 in which it was already combined.

Try minimizing and normalizing the SMART window. E.g. click SMART's 'Minimize' button and then restore the window by clicking the SMART button on the Taskbar. From my experience, that frees up about 30% of CPU usage on a single-processor virtual machine.

From: Karpov
Try minimizing and normalizing the SMART window. E.g. click SMART's 'Minimize' button and then restore the window by clicking the SMART button on the Taskbar. From my experience, that frees up about 30% of CPU usage on a single-processor virtual machine.

I have no idea how in any universe minimizing a program would affect CPU usage.

Minimizing/normalising SMART causes the canvas to flash black (refresh?) and this seems to take a load off the CPU. I don't know if this is a bug or not but it definitely happens on all my virtual XP machines.

From: Wizzup?
I don't think CPU usage should have increased. Previously SMART was living inside the Simba process, now it's outside the process. There should hardly be a difference. If you add up the usage of both it'll be like 984 in which it was already combined.

Yea, I saw they were different - and it doesn't seem to be making any difference.. which makes sense, it really shouldn't be much different.



The minimizing programs thing maybe has some effect on the system as - windows tries to sleep the program when it is minimized to save resources, but obviously smart/simba have to run so maybe they keep "waking" themselves?

http://support.microsoft.com/kb/293215
idk if that helps some people, I don't really feel like reading that

From: Joe
I have no idea how in any universe minimizing a program would affect CPU usage.

It does work. Reason being that the DC in windows get cleaned and set to size 0 when a window is minimized.

Smart gets around this but I'm not sure that it still draws to the canvas. I think it just provides a buffer to Simba to read from instead of drawing. I remember it being impossible to draw on the canvas via GDI while minimized. You can try it by minimizing a window and taking a DC screenshot, it'll just contain the titlebar.

With that being said, since it isn't drawing it's canvas while minimized (hopefully it isn't), it's possible that it lowers CPU usage/memory usage.

I doubt it's still drawing, because of the fact that linux multiple desktop.. moving to a desktop without smart on it will improve cpu power by like 10-20%, I was testing giving a vm 1,2,3,4 and 6 cores to use.. it seemed to always significantly show better performance when smart wasn't on the actual screen.

From: Wizzup?
I don't think CPU usage should have increased. Previously SMART was living inside the Simba process, now it's outside the process. There should hardly be a difference. If you add up the usage of both it'll be like 984 in which it was already combined.

Are there any ways to combine the two processes just like it was in 984? Why do SMART needs to be separate when living inside was good? I'm just curious :)

From: Arepirpi
Are there any ways to combine the two processes just like it was in 984? Why do SMART needs to be separate when living inside was good? I'm just curious :)

Living inside isn't really good.. there are benefits from being two processes, there are only bad things that happen when living inside!

such as - to dump the java memory smart holds.. you have to close simba too (I believe I read that from benland or wizzup) because simba is the "parent" process, now that smart is its own, when it is closed, it will dump the java memory so it isn't using ram for no reason

From: Arepirpi
Are there any ways to combine the two processes just like it was in 984? Why do SMART needs to be separate when living inside was good? I'm just curious :)

Benefits on the user end is that you can restart Smart without closing Simba. You know that annoying 6 hour thing that says Please close your client you game session ended? Well it gets around that.

Also you can have multipe Smart's per simba. So instead of opening 3-4 Simba's to run 3-4 Smart's, run one simba with 4 smart's.

Lots of others but meh cba to mention every single detail.

It uses the same CPU even though it's outside simba and looks like more. It isn't more. Yes there is a way to have it inside Simba. Just load LibSmart32.dll instead of LibSmartRemote32.dll. You'll notice the CPU is still the same.

From: Brandon
Benefits on the user end is that you can restart Smart without closing Simba. You know that annoying 6 hour thing that says Please close your client you game session ended? Well it gets around that.

Also you can have multipe Smart's per simba. So instead of opening 3-4 Simba's to run 3-4 Smart's, run one simba with 4 smart's.

Lots of others but meh cba to mention every single detail.

It uses the same CPU even though it's outside simba and looks like more. It isn't more. Yes there is a way to have it inside Simba. Just load LibSmart32.dll instead of LibSmartRemote32.dll. You'll notice the CPU is still the same.

Thanks for the suggestions :) will try them out now