Jump to content
Sign in to follow this  
TRiLeZ

TRiBot Release 9.302_0 [More Performance Improvements]

Recommended Posts

Changes include:

  • The non-LG client automatically added 5 miliseconds of paint delay on top of the user specified paint delay. This has been removed.
  • Any paint delay of less than 5 milliseconds was "corrected" behind the scenes to 5 milliseconds. This "correction" has been removed. Before, setting your paint delay to 0ms would make the client sleep the mandatory 5ms, and a 5ms "corrected" paint delay. Now, the client will sleep for 0ms instead of 10ms in this case.
  • Before, clients which were minimized or not in focus because of another tab were made to have a minimum of 35ms paint delay plus that 5ms mandatory delay for non-LG clients. This has been removed. If you notice an increase in CPU usage when using multiple tabs, this may be why. Consider increasing your paint delay.
  • Client painting is a lot more smooth now because much less calculations and small sleeps are performed each game frame.
  • CPU usage is lower for LG, and especially for non-LG.
  • I couldn't re-produce the typing bug with LG and OSBuddy, but I made some changes which might make a difference.
  • Like 18

Share this post


Link to post
Share on other sites
16 minutes ago, RedHawkLuffy said:

cpu usage went from 15 to 30 percent after update o-o

Close and re-open the client, it should go back to normal.

16 minutes ago, ksppgs said:

I can't collect the coordinates after the update

Try above ^ if that doesn't work, delete hooks.dat in .tribot\settings and then open a new client

Share this post


Link to post
Share on other sites
4 minutes ago, FALSkills said:

Close and re-open the client, it should go back to normal.

Try above ^ if that doesn't work, delete hooks.dat in .tribot\settings and then open a new client

thank you

Edited by ksppgs

Share this post


Link to post
Share on other sites
Just now, FALSkills said:

On your tribot client try increasing the paint delay under File->Settings. I'm not sure how much (or if it does) affect performance from OSBuddy / whatever you are hooking, but it should reduce CPU usage significantly.

my script doesnt work as well by increasing paint delay :(

Share this post


Link to post
Share on other sites
Just now, FALSkills said:

On your tribot client try increasing the paint delay under File->Settings. I'm not sure how much (or if it does) affect performance from OSBuddy / whatever you are hooking, but it should reduce CPU usage significantly.

He can't use LG since he's a VIP and not a VIP-E.

Share this post


Link to post
Share on other sites
2 hours ago, FALSkills said:

Close and re-open the client, it should go back to normal.

Try above ^ if that doesn't work, delete hooks.dat in .tribot\settings and then open a new client

spent over an hour trying to fiqure out why .isonScreen() would not return false if it wasn't there instead it would throw an error and quit... delting hooks.dat fixed it 

 

thanks!

Share this post


Link to post
Share on other sites
2 hours ago, RedHawkLuffy said:

my script doesnt work as well by increasing paint delay :(

This update makes the client FPS increase as things on TRiBot's end have been made more efficient. So this increase in FPS will increase CPU usage (by the RS client). So it's as if client paint delay has been lowered even though you didn't change any settings. You'll have to increase the client paint delay to get the FPS to the same as it was before.

Share this post


Link to post
Share on other sites
9 minutes ago, thermsen1 said:

scratch that.... im having a problem and it just started happening when i updated so i guess ill post here and script help... but ive simplified my script to this small code and cant get it to work.... but when the object is not on the screen Salt[0].isOnScreen should just return false (i believe as im new to scripting and it was working before) but instead i get the error 

  • [17:16:42] java.lang.ArrayIndexOutOfBoundsException: 0

 

 

any ideas? i tried deleting hooks.dat and didn't help and restarted client

Try the Scripting Help section, people will be more than willing to help you.

https://tribot.org/forums/forum/125-scripting-help/

Share this post


Link to post
Share on other sites
19 hours ago, ohParadox said:

Still getting white screen after awhile. 

LG? Non-LG?

3 hours ago, justpixels said:

Thanks for the improvements! My botting rigs will appreciate it!

Notice any improvements in CPU/memory usage?

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 includes:

      Fix updater bug which was causing a bunch of issues


      TRiBot will no longer require manual hook fixes every time the RS client updates - the updater has been fully patched for objects


      Hooked login fields


      Improved the login bot


      Ability to recognize the banned/locked messages again


      Ability to read the current input for username and password fields


      If the username or password is already entered correctly, it won't be erased


      If only part of the username or password is already entered correctly, it won't be erased. The login bot will fill in what's missing.


      If there are a few invalid characters after a valid substring of your username/password, only (approximately) those invalid characters will be erased. The login bot will then proceed to fill in the missing characters.





      Coming soon:

      Skull icon fix


      Improve screen rate and responsiveness of the RS client (both regular client and LG)


      Much more
        • Thanks
        • Like
      • 21 replies
    • This release includes:

      Fix shift clicking option selecting


      Fix high paint delay settings saving


      Update prayer IDs for the quick select menu


      Remove RS3 support


      Fix hooks



      RS3 Support Removed

      The RS3 client hasn't been updated since our Old-School version of TRiBot was released, as many of you may have noticed. Keeping all of the RS3 code in the client made the client as a whole harder to maintain, larger, slower, and messier. As hardly anyone still uses the RS3 client, and since the RS3 API was hardly functioning, we made the decision to completely remove it from TRiBot.

      For the average user, this means that the client will be smaller, cleaner, and faster. Future updates will also take less work meaning there will be more frequent updates.

      If you were one of the few users still using the RS3 client, we apologize for the inconvenience. No future support for RS3 is planned. There are many other botting clients which has support for RS3, so we recommend finding an alternative if you wish to continue botting on RS3.
        • Thanks
        • Like
      • 25 replies
    • Please welcome our new developers, @JoeDezzy1, @erickho123, @Encoded, and @wastedbro.

      These members will be responsible for working on, maintaining, and improving TRiBot.

      This means that bug fixes and improvements will now come at a much faster pace! We're committed to providing users with the best botting experience possible!
        • Thanks
        • Like
      • 30 replies
    • This release includes:

      More 3rd party libraries for script writers to use


      Apache Commons Codec


      Apache Commons Collections


      Apache Commons Configuration


      Apache Commons IO


      Apache Commons Lang


      Apache Commons Math


      GSON


      Guava


      JFoenix




      Hint arrow API


      Game#getHintArrowX


      Game#getHintArrowY




      Fix player hooks including Player#getSkullIcon and Prayer#getPrayerIcon
        • Thanks
        • Like
      • 49 replies
    • This update includes:

      Fix broken hooks


      Fix login bot for the message "No reply from login server. Please wait 1 minute and try again."


      Fix bug relating to which bot tab is sent human input


      General#randomLong bug fix involving negative numbers


      Fix GE API



      Please note: There are still some issues with the login bot due to a change in the game mechanisms handling the login screen. We're working on a fix and will upload it when ready.
        • Thanks
        • Like
      • 37 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×