Wanted Posted November 1, 2011 Share Posted November 1, 2011 http://villavu.com/forum/showthread.php?t=67428Version 6.9 was almost version 7.0, but then I decided I just couldn't live with myself if I skipped 6.9. This includes a few minor bug fixes, but adds support for middle mouse buttons. (You'll need a new smart.scar to make use of this, however. It's in the zip, committed to srl-opendev, and on my github). There's also the ability to set the maximum JVM memory directly via SmartSetMaxJVMMem(mb: integer). Call it before anything else, such as with SmartSetJVMPath. Zipped Binaries: http://bland.no-ip.org/files/SMARTv6.9.zip Source (GIT Repos): https://github.com/BenLand100/SMART Changelog v6.9: +Middle mouse button support included +Double buffering fixes flickering/disappearing mouse dot/debug graphics +Ability to set maximum JVM memory +Potential bug in native graphics if using a larger window resolved. http://villavu.com/forum/showthread.php?t=67428It crashes. That being said, the default for Java is 64mb. Jagex tries to ensure that the maximum is set to 256mb, but this is not always honored by the java plugin (ironically) if the JVM is already started. Due to the way I load the JVM, I'm really not sure what the maximum has been set to, but I've received some complaints about out of memory errors. I've set SMART to default to 256mb, but it can be set higher if need be. Pushed to latest OSI. https://github.com/OSI1/OSI1/commit/b56d8b802fb443f1f4e10002ee250fdadb7c1c29 Major difference: You can now use Hold and ReleaseMouseMid with SMART and bug fixes/performance. Make sure you move the SMART plugin and reload plugins. It's also important to reload runescape in your normal browser before trying to use it with SCAR. Quote Link to comment Share on other sites More sharing options...
Bixby Sayz Posted November 6, 2011 Share Posted November 6, 2011 Was going to start a new thread for this, but this might be a better fit? If not Mod please move it. I've been experiencing SMART taking a very long time (90000 ms to be exact) to initialize. After a bit of digging realized what was happening. InitiateSMART makes the assumption the Login screen will be present (because SMART just loaded). If you are logged in already, it sits there waiting until it times out. When testing/developing a script I routinely leave my char logged in, make some changes to the script, run it again, and repeat. Except it takes 1.5 min each time for the check for the login screen to timeout. Perhaps it would be better to check for both conditions (or all 3): login screen, lobby, logged in. Quote Link to comment Share on other sites More sharing options...
Wanted Posted November 6, 2011 Author Share Posted November 6, 2011 (edited) Hmm yea, it only checks for the login screen. I'll have it check for all three.. Edit: Should be fixed now Edited November 6, 2011 by Wanted Quote Link to comment Share on other sites More sharing options...
