Leaderboard

Hi all, I have been working since wednesday on the promised engine overhaul. I took a day to completely map out the design on paper and whiteboard, and finished it yesterday. After that Zach and I have been profiling the OSBot lots and made major adjustments to its memory usage. Whilst running a script, the entire application never goes over 200mb of memory usage anymore and after garbage collection is even drops down to 130mb. It's averaging around 150-160mb, running Peter his chicken murder (with some adjustments). I thought I would show you a picture as well. The memory usage you see, is the OSBot client, script and the Runescape client. OSBot itself without running a script or a Runescape client, uses 82mb. So you can do the math yourself ;)! This is a major improvement. The engine overhaul also got rid of any freezes and other glitches. We still have some last things to do before we can tie up our next release, but I think you will all be pleased with it. Sincerely, Maxi

We are glad to announce that BETA v1.3.1 has been released! We have been hard at work optimizing, stabilizing and fixing bugs inside the bot client. We have accomplished the following things in v1.3.1: Improved memory usage. Currently, our tests show that memory usage ranges from approximately 130MB to 200MB whilst running OSBot with 1 script. Obviously, this depends on the situation. In either case, this is a significant reduction from the crazy numbers we would sometimes get in the past, reaching up to 700-800MB. A completely redesigned threading/concurrency system that has shown significant promise and improvements in overall stability. Improved CPU usage. The bot now creates a lower CPU footprint. Of the amount of CPU time the entire application spends including one Runescape client, only around 6 - 10% is spent by the logic of the script/bot. The rest of the CPU time is the Runescape client itself. On my own machine, I run one bot and script with approximately 10-15% CPU. Freezes of the loop and the graphics rendering should be completely in the past now, thanks to the top notch fresh threading system. The hooks we originally had that were not working (i.e. some of the skill hooks, in combat, facing etc) should all be fixed and working now. Laz forgot to push his git so the updates are not included. We will push them once he comes back home. A fresh new GUI theme that will fix cross platform problems, i.e. make it the GUI work perfectly on Mac OSX and Linux as well. Fixed any bugs that had to do with multiple bot tabs. Multiple bot tabs work a 100% now. Slight changes to the API here and there, however due to the above updates we did not have time for the API. All together, this gives us a fresh start without stability issues. Now these are out of the way and we have a very efficient bot, we will go back to our API and randoms to make its quality match its engine it's running on. The SDN continues to be worked on, however as we are outsourcing this we can't tell an exact date for when we will have the first barebone version of it running publically. The new API documentation has been updated: http://osbot.org/api/ The new OSBot download is found here: http://osbot.org Make sure you update your Java to the latest version: http://www.java.com/en/download/manual.jsp If you experience FPS issues, make sure you run 64bit java if you have a 64bit machine! If you're one of the people experiencing FPS issues, post your machine specs (cpu, 32/64 bit, java version + 32/64bit, os etc etc) and you can still use 1.2.2. Refresh your page (CTRL + R) in case it's still showing 1.2.2. Thanks for reading, The OSBot team

After some research I've found that the FPS issue is caused by one our new obfuscation techniques, which some CPU's have little to no trouble with and some do have a lot. Furthermore, 64bit seems to perform MUCH better than 32bit JVM's. We will think about our options to change obfuscation in a way it's acceptable for both parties.

I don't think you should have opend a new topic for this, but thats just me... Love your .gif!

Fix the varrock east banking issue asap please.

Crashes when trying to execute a random solver. Too many bugs in this version, I'm just gonna use 1.2.2. You should consider do it like other bots and provide beta access of new versions to script writters so they get tested instead of deploying buggy releases.

Ok, stop derailing this thread. This is the Graphics section where we discuss GRAPHICS, not trading matters. I'll lock this thread if anyone posts again about scamming/anything unrelated to the thread.

can anyone help me I'm getting the error ''invalid or corrupt jarfile''

2 fps for me wtf

I know, right? Mine was really good until this update. Now it is running 4 or 5 FPS.

It just went down for me.

There is an API called Twinkle, nuff said.

How far have these anti-randoms been developed atm ?

Honestly don't expect this script from you at this point. You basically copied a script and re-released it previously and you've gone on and on about releasing this one "soon." Stop making excuses. This script is probably not coming and if it does, it'll probably be a re-release of a different script.

this board is open to all members of the forum. every member has the right to express their opinion as long as it does not break any rules. don't try to be smart about it, if you can't accept criticism the internet is not for you. and it doesn't matter if you comment on things I post? I don't know what you are getting at

sorry but this is an unnecessary tutorial. if people want to learn Java they should go by a book written buy professionals (or torrent one). following an online guide teaches you incorrect techniques and only the very basics, plus you won't learn anything about the language it self.