Jump to content
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 update will:

      Fix GE inventory item positioning bug


      Fix broken object hooks
        • Like
      • 23 replies
    • This release will:

      Fix some ClosedChannelException bug


      Fix bug in RSObject#getAllTiles


      Add game tab support for "Kourend Favour"
        • Like
      • 15 replies
    • This release will:

      Fix Settings UI placement bug


      Fix game object location bug


      Fix small layout bug making the client shift up and down


      Fix client crashing bug where loading the client with a small display area will cause the client to crash


      Fix annoying Linux bug relating to painting events and peers


      Fix settings saving bug where settings are saved to disk more often than they should


      Fix RSInterface#isBeingDrawn bug affecting a limited amount of people


      Drop Java 1.7 bytecode version for 1.8


      Important: Since the downloadable RS client uses Java 7, it will no longer be compatible with Looking Glass. To make up for this, we will add support for using other clients such as RuneLite (at a later date).


      This change was necessary to allow us to use Java 8 syntax. It also paves the way for Java 9/10/11 support.
        • Like
      • 40 replies
    • This update will:

      Fix the RSMenuNode bug which also fixes the bug with bank opening


      Fix the incorrect object positions bug


      Fix and re-enable the LG Objects API Accelerator


      Fix the RSObject#getAllTiles bug
        • Like
      • 22 replies
    • Try our development release by checking "Development Release" on the TRiBot Loader. Note that these new features are currently in beta.

      This release features:

      Re-sizable mode support for both LG and the regular client


      Slightly improved login bot


      Removed final access modifiers from API classes


      Added RSServer hook wrapper to get the client's cached list of server/world info


      [NEW] Bug fix for intelligent banking


      [NEW] Improvement to the stability of LG over time


      [NEW] Vastly improved the reliability and speed of Screen#getColorAt on both LG and the regular client


      [NEW] Fix LG login problems


      [NEW] Fixed re-sizable mode container bug


      [NEW] Fixed re-sizable mode mouse bug


      [NEW] Use of public constants in the Banking API


      [NEW] Use of other various constants such as Projection#NULL_PT and Screen#EMPTY_COLOR



      More features to come very soon!

      Please test it and let us know here if there are any new bugs introduced in this release.
        • Thanks
        • Like
      • 12 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×