Maxi

For now you can add the randoms released on the forums in your scripts folder. We ourselves are aiming to release all randoms at once through our SDN, that way no one will have to update their randoms manually. We are still waiting for the person who we outsourced the SDN to, to finish the SDN up. Once he has finished it up, we will write the security around it to protect scripts used in the SDN from being cracked, leaked and stolen. All together, this shouldn't be too long anymore.

Really must be your script this time. Run it in command line to see what output it gives.

It's due to the new hooks file that wasn't uploaded to the server. Hold on for a few minutes ;).

The server will be up in a minute.

So we've been looking as to why only some people were experiencing incredibly low FPS, and as to why in general the obfuscated bot was using so much more memory / CPU compared to the non obfuscated version. I am doing these tests on an 8 year old machine, a 32bit machine, which was experiencing the low FPS too. We have found several causes. First of all, apparently some, not all, people who run 32bit java on a 64bit machine get very low FPS. Most of these people could fix this by installing 64bit java on their machine. Second was that we upped the obfuscation to be harder on string encryption. However the additional string encryption was that severe, it multiplies the memory usage by 2 and by that also making the CPU usage higher, and in some cases also low FPS. We have decided that we will reverse this additional string encryption obfuscation. We are still unsure however on the JVM / machine related influence causing low FPS for some people. Some machines, with the same specs or even lower, run 50 FPS without a problem. A third thing I discovered is a small mistake in the state worker, the component of OSBot responsible for updating the state from the client with callbacks. I will do some tests where I'll use some different approaches to achieve the same. We will keep you updated. OSBot.org

Yes we are aware of that, one of the things we missed when doing the overhaul of the engine. Don't worry though, this should be an easy fix. @Xavier, it was probably doing that because of the new string encryption, which also caused significant memory usage. Running with the new encryption gives me 380MB, running without it between 140 and 180MB. We will remove the new encryption from 95% of the files.

Ok, I have done some more testing and played around with the obfuscation on my 8 year old computer and I've managed to get FPS up to averaging 21 FPS, maxing at around 35, whilst being outside the fightcave. Will do some more testing now.

Also, one of our new encryption techniques caused the client to use 380mb at least in obfuscated form, where as without the new encryption technique it's 180mb. We will see what we can do to keep our software as secure as possible whilst keeping that FPS up and memory usage down. I'm not testing on a 8 year old machine, which should give me quite a good comparison. However the FPS is caused by a different obfuscation technique than the encryption, which seems to run fine on certain JVM's or CPU's (not sure where this really relates to yet).

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 think someone swapped npc and players up right there lol. We'll get a fix for that asap.

I think we might have a lead here. Swing (the framework the GUI runs on) uses hardware acceleration if enabled on your computer. The client runs inside the GUI, thus probably needs the hardware acceleration to be set to true. In the case of your laptop, your settings on cord are probably that you enable hardware acceleration as where you don't without cord. I'm going to look further into this, it's most probably not our software. And no, this was added ages ago and has never been used really. I have been reading, hardware acceleration problems can also be cause by using 32bit java on 64bit machines. Looking further into this.

Specifics please about your java installation.

I'm thinking it could be due to the obfuscation, but it's weird it's different for different people. What we need to know is: your EXACT processor and the java version you're running.

Yes obviously. It are not that many people though, just the ones that posted here and that's maybe 6 or 7. But yes I'm clueless as to why. It obviously has nothing to do with computer specs, I'm running a dual core which is 3 years old. We'll figure it out. What happens if you tick your model information and interface debug boxes on and off (leaving them on for a second)?

What happens if you tickle your model and/or interface debug button on and off (keeping it on for like a second)?

Zach, Laz and Kati use Windows like all of you.

Are you running v1.3.1?

I don't see a problem here either:

I just realized Laz did not push his git with the fixed hooks. We'll push the update when he comes back.

It should be faster than ever, not the other way around :p. It is for me, Zach, Laz and a lot of others. Try and reload.

I can't see how it's broken. It types in strings fine.

That's obviously a script error, not an error in our code.

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

The update is not available yet Pike. It will be later tonight. Once we do so, your old version won't work anymore and you will have to download the newest version. I think we need a stable bot with low resource usage first. Your random won't do a thing without it.

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