Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
Sign in to follow this  
TRiLeZ

TRiBot Beta 7.30_0

Recommended Posts

Having the same problem as tatiko since 7.03_0 (05/08/13): for me i'm pretty sure (may be 1-2 versions off but it was definately around here). Used to be able to run 8 at around 50% cpu now I can barely run 4 without it hitting 100%

 

 

 

client paint delay 16
tribot sleep modifier 0.5 (used to be 1 but i changed it to this to see if it uses less cpu%)
 You have the recommended Java installed (Version 7 Update 25).
64 bit
max heap size 256mb (hasn't been changed)

Edited by Mikkolol

Share this post


Link to post
Share on other sites

 I have an update to the loader which addresses this issue coming soon.

 

Could you answer some questions for me?

If you go to File->Settings, what is your:

  • Client Paint Delay
  • TRiBot Sleep Modifier

Also, what version of Java are you using? Is it 32 bit or 64 bit? What are you setting the max heap size to?

 

 

 

TriLez is there any chance in the future you can somehow implement a feature where if a bot fails a random or logs out when not on a break, that a message is sent to our email or txt or something like that? I am just wondering if that is at all possible. 

Share this post


Link to post
Share on other sites

 I have an update to the loader which addresses this issue coming soon.

 

Could you answer some questions for me?

If you go to File->Settings, what is your:

  • Client Paint Delay
  • TRiBot Sleep Modifier

Also, what version of Java are you using? Is it 32 bit or 64 bit? What are you setting the max heap size to?

 

Does increasing the max heap size decrease CPU usage?

 

And is running two accounts on one client (tabbed) use less CPU than two separate clients?

Share this post


Link to post
Share on other sites

Does increasing the max heap size decrease CPU usage?

 

And is running two accounts on one client (tabbed) use less CPU than two separate clients?

 

The way the JVM works is that when the heap fills all the way up, the garbage collector will do a full cleanse to get rid of all the garbage. This can be quite CPU intensive. So if you set the max heap size too small, CPU usage will increase. However, setting it too large will allow for a build up of wasted memory space.

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.
Sign in to follow this  

  • Our picks

    • This release will:

      Fix LG for both OSBuddy and RuneLite


      Fix issue where the resizable client isn't able to be made smaller (Thanks @JoeDezzy1)


      Fix detection of the logout game tab when resizable mode and side panels are enabled (Thanks @JoeDezzy1)


      Add initial support for Sentry to allow us to identify and easily debug exceptions happening with all TRiBot users


      Add methods to determine if the bank is actually loaded, and not just the overarching interface (Thanks @wastedbro)



      Upcoming updates:

      Improved CLI support


      Full Sentry support


      Much more
      • 53 replies
    • This release will:

      Fix NPE in Camera API (Thanks @wastedbro)


      Update deposit box interface ids (Thanks @Encoded)


      Add various bank methods (Thanks @wastedbro)


      Banking#getWithdrawXQuantity


      Banking#getDefaultWithdrawQuantity


      Banking#arePlaceholdersOn




      Fix resizeable minimap bug (Thanks @wastedbro)


      Remove Java 8 requirement


      Please note: TRiBot is not yet fully compatible with Java 10+




      Fix the break handler issues by ensuring the break handler thread never gets paused


      Fix broken settings hooks



      Upcoming updates:

      Improved CLI support


      Much more



      Note: If you are using LG, please restart both the RS client and TRiBot
      • 68 replies
    • This release will:

      Add support for using custom F key bindings to switch between game tabs (Thanks @erickho123)


      Fix tab opening for "Skills" and "Kourend Tasks" (Thanks @erickho123)



      Note: If you are using LG, please restart both the RS client and TRiBot
      • 34 replies
    • This release will:

      Fix an issue where breaks would stop firing


      Fix Combat#getWildernessLevel, use dynamic search for text and cache ID for later calls


      Fix an NPE in the Combat API


      Fix Mouse#leaveGame bug where the mouse wouldn't actually leave the game screen
      • 21 replies
    • This release will:

      Add LG support for Runelite


      Fix NPCChat issues


      Fix a bug where the camera angle setter would just hold down a key for 5 seconds (the timeout)


      Slightly adjust the rotation via keys to be more accurate


      Add the ability for asynchronous camera movement via keys


      Make Camera rotation via mouse more fluid, with more antiban, and work much better in resizable mode


      Add a "Camera#setCamera" method, allowing the rotation and angle to be set in parallel


      Increase the likelihood of using the mouse for camera movements


      Add support for adjusting the camera to positionable entities (Positionable#adjustCameraTo)



      Upcoming updates:

      Improved CLI support


      Much more



      Note: If you are using LG, please restart both the RS client and TRiBot
        • Like
      • 59 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×