Maxi

That space will be used to express some more information about OSBot.

Dark background variant: http://i.imgur.com/KfGS2A5.png

Concepts / basic empty layouts: Light background: http://i.imgur.com/Rw27Hd8.png Dark background: http://i.imgur.com/KfGS2A5.png I say yes.

Will be looked into this weekend and an update for it will be pushed.

I have updated the post to link to our Store as it all works now.

Random solvers are easy to do (most of them). We are waiting for our SDN to be deployed so we can distribute them to you without you needing any updates manually.

We should do this once the SDN is up and running. This way they won't get leaked, otherwise there would be no point.

We obviously are a new bot and didn't base our bot on any other bot, so we're worked from grounds up. If we want to become one of the major bots out there, we will have to do so ;).

Health checking does already work. @Xavier: it's on the list ;)

Food can be used now already, it's really easy to do. You just have to write more than one line, not simply something like eat(id)

Dear community, For the end of this weekend we have planned the release of BETA v1.4.1. With the previous update of v1.3.3 we managed to greatly improve the stability, memory and cpu usage of OSBot. This update will focus on how the current API works. Features/updates you can expect: Fixed area's Completely renewed mouse movement with much higher accuracy (no miss clicking) Improvements on the walking algorithm, also support for paths Improvements on the interaction methods New/improved camera rotation methods Support for local and global area's Fix of the onActivate method from the Login random Food API functions Prayer API functions Magic API functions Anti Ban API functions and more... Stay tuned! OSBot.org

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)?