What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

Trinity 1.7.1.16

Status
Not open for further replies.
RockyRoadIceCream said:
the betas always have more features for some reason, like displaying the going rate of tps on front Main tab

the problem is i dont want to use a non stable release of demonbuddy, its a beta for a reason so i feel for some odd reason its not as stable or safe as the current release

my tin foil hat but a beta is a beta, im curious as to what is making the old trinity show pause button and the .16 removing it, if i just use a different version im not figuring out my problem.

bandaids cover wounds but cleaning them fixes them :P
Click to expand...

No bandaids needed: read the changelog in the 1st post of this thread (the buttons were added into Demonbuddy itself, and are no longer a feature of this plugin).
 
rrrix said:
Did the bot/profile continue to kill monsters and just not pickup items or gold? How long did you let it run for?
Click to expand...
Yes, bot continue to kill mobs + dont use shirines and destroy. 1-2 Hours
 
rrrix, I need your help badly!

I'm running 12 vms with d3 on a server and I messed all previous day with bot build and diff trinity's.
I ran beta 115 and trinity .12 before the update and it was going pretty smooth. Then I decided to upgrade to newest bot (140, also tried .295) and trinity 16 and I'm getting hardest lags on aoe (molten, arcane) elites, sometimes the game freezez up to 1 sec. so it is 100% death to my monks, sometimes bot succesfully casts serenity during the lag, but not very often. IMO there is an issue with heavy calculations while avoiding aoe, crazy lags when molten explodes, when several underground dicks drill you, when there's a lot of arcane etc. CPU load isn't the problem, same lag on 1 vm of 12 working. Increasing tics to 20 and chache refresh to 50 does not help, I also tried setting high cpu priority to d3 and it also doesnt help. Editing avoiding section helped a bit (I lowered the triggered health to avoid certan aoe types from 100 to 60), but my bots still die A LOT. They are geared very well (3500+ ar, 650-750 @res, 35k hp, 80k+ dps, 5% lifesteal) and I expect 0-1 deaths on mp1 act 3 and now I get 4-10 :(

Trinity 12 worked much better, there is a lag too, but it is much shorter and does not trigger lots of deaths. Is there a solution for me? I want to use latest beta and trinity <15 doesn't start with beta 140.
Maybe there is a way to copy avoiding section from .112? Or edit some settings inside trinity 16?
 
Few suggestions... :)
1. Change format of logs to HTML (atleasts stats and stash), or add this, i changed it for myself, cause i use webserver to be able to see logs when i'm not at home :)
2. Change Mobile for Prowl and NotifyMyAndroid to pushover.net - 1 site for both Android and iOS.
3. Fix ItemNames when using nonEnglish localization fo game, mistake is, itemsreallname identifying as itemclass.
 
IGG said:
rrrix, I need your help badly!

I'm running 12 vms with d3 on a server and I messed all previous day with bot build and diff trinity's.
I ran beta 115 and trinity .12 before the update and it was going pretty smooth. Then I decided to upgrade to newest bot (140, also tried .295) and trinity 16 and I'm getting hardest lags on aoe (molten, arcane) elites, sometimes the game freezez up to 1 sec. so it is 100% death to my monks, sometimes bot succesfully casts serenity during the lag, but not very often. IMO there is an issue with heavy calculations while avoiding aoe, crazy lags when molten explodes, when several underground dicks drill you, when there's a lot of arcane etc. CPU load isn't the problem, same lag on 1 vm of 12 working. Increasing tics to 20 and chache refresh to 50 does not help, I also tried setting high cpu priority to d3 and it also doesnt help. Editing avoiding section helped a bit (I lowered the triggered health to avoid certan aoe types from 100 to 60), but my bots still die A LOT. They are geared very well (3500+ ar, 650-750 @res, 35k hp, 80k+ dps, 5% lifesteal) and I expect 0-1 deaths on mp1 act 3 and now I get 4-10 :(

Trinity 12 worked much better, there is a lag too, but it is much shorter and does not trigger lots of deaths. Is there a solution for me? I want to use latest beta and trinity <15 doesn't start with beta 140.
Maybe there is a way to copy avoiding section from .112? Or edit some settings inside trinity 16?
Click to expand...

Hey IGG,

Can you try these things:

1) On Trinity Combat Misc tab, disable "Use NavMesh for targetting" option - see if that helps at all
2) Go to the Trinity Advanced tab, and enable "Debug System Performance", reproduce the problem, and zip the log file (it may be large) and attach the log to this thread.
** I've added a ton of performance logging to all components of Trinity, so this will help me diagnose what went wrong.

nZaO9yC.png


4seti said:
Few suggestions... :)
1. Change format of logs to HTML (atleasts stats and stash), or add this, i changed it for myself, cause i use webserver to be able to see logs when i'm not at home :)
2. Change Mobile for Prowl and NotifyMyAndroid to pushover.net - 1 site for both Android and iOS.
3. Fix ItemNames when using nonEnglish localization fo game, mistake is, itemsreallname identifying as itemclass.
Click to expand...

Good stuff, will look into it!
 
rrrix said:
Good stuff, will look into it!
Click to expand...


Actually, i already did all those changes for myself, but the problem is :) i have to change it everytime u release new version of Trinity:(
I can give u changes files so u can look into it.

In NotificationManages there is "hack" for messages (take a look at code near POST requst generation), pushover uses 2 API keys and device name if needed to identify users and APP to send for. Finally it looks like screenshot i attached.
2013-01-20_10-37-07.webp
For example UI of bot can be changes to: USER key (cause now its 1 key for both devices), and APP key, also device name if needed.
View attachment changes.zip

upd. about Monk combat, how about to change Inna's set timer from 5 sec to 4,8 sec + random(500)? cause of bot tracking by blizz?
 
Last edited:
1 - Bot keep try to TP under Fire pic. - Could you add this Flamethrower into the list that bot have to avoid


2- (TrinityMoveTo - question) How to turn ON *names* in the DB log window ? pic. ATM its <TrinityMoveTo questId="1" x="1091.752" y="1135.849" z="0.1727592" pathPrecision="10" name="Heart of the Damned-01" /> in my XMLs
 

Attachments

  • TPunderFire.webp
    TPunderFire.webp
    20.3 KB · Views: 91
  • TrinityMTlog.webp
    TrinityMTlog.webp
    28.7 KB · Views: 86
IGG said:
Here are my logs
https://www.dropbox.com/s/c0uxz0wgxhu3faq/trinity logs.rar
Click to expand...

Looks like you have performance problems across the board, there's something systemic wrong with your setup i think.

Try these things:

  • Make sure you have enough free memory for each bot, including D3+DB combined (it needs at least 1.5GB, 2GB is ideal). Swapping will kill performance (and your monk :)).
  • Set TPS lower, not higher (5-7 maybe) - higher TPS will consume more CPU/resources
  • Set cache refresh rate to a higher number (400-750 maybe) - a faster (e.g. lower number) refresh rate will consume more CPU/resources
  • Disable "Use NavMesh for targetting" (this is not necessarily the problem you're having, but it may help)
  • Make sure you can get at least 20 FPS WITHOUT the bot running - just playing manually (Ctrl-R in the game to see FPS rate in lower right hand corner)
  • Try a minimal D3Prefs.txt setup (search forums for how)

I noticed your bot is having serious performance trouble just reading simple variables from game memory. Either your system is way underpowered for what you're trying to do, or there's a configuration problem in your VM setup. What usually takes most machines 5ms is taking yours over 100ms.

For example, these steps should never take take longer than ~0.10ms, if even that:

[07:00:52.254 V] [Trinity][Performance] Execution of the block RefreshCachedType.4 took 96.43ms.
[07:00:13.272 V] [Trinity][Performance] Execution of the block RefreshUnit.6 took 96.31ms.

This step should also never take more than ~ 25ms, even with a screen full of monsters and AoE:
[07:01:21.419 V] [Trinity][Performance] Execution of the block RefreshDiaObjectCache took 99.97ms.

Let me know if any of this helps!

rrrix
 
it is posible to do stash logs starting from newest drop not for oldest, at now trinity gather a lot of information, so i dont like remove full folder as i used to before. Its really aning to scroling it al the time after 100+ hours of boting

oh and yesturady got 2 or 3 time situation that bot try to town run in front of flame thrower in ToD, flame always itercept teleporting. Maybe after 2 or 3 fails bot should move a bit or something
 
Last edited:
I'd like to request a stats improvement for the next version, average game length and possible games per hour calculated from this
 
Tinnvec said:
I'd like to request a stats improvement for the next version, average game length and possible games per hour calculated from this
Click to expand...
Not possible to calculate with random profiles, as i can get it...

Small update for ItemHanding script which allows you to get bot stats log in HTML format. will looks like:
Безымянный.webp

DL and replace: View attachment ItemHandling.zip
 
Last edited:
trinity .15 working good , .16 seems to have some problems with destroying doors in depths (lvl 2) ...he just stay there and watch the door...sometimes in skycrown too area...watching at baricades..im i doing something wrong..? is the same setup from .15
 
Last edited:
With Trinity 1.7.1.16 boat began often die during the battle to stop until he was killed.
 
I love those engrish words "boat" "boot" "get banhammer" (lvl 64 laser rifle 500% crithitdamage). :P
 
Hey rrrix, I need your help now badly.

Please, please tell me how to completely disable trinity logs, it keeps makining it (loglevel: normal), I get bad lags with many vm turned on! PMed you already.

I continued the tests, doing them 3-4 hours, already reached my goal - stable smooth botting process :)
 
IGG said:
Hey rrrix, I need your help now badly.

Please, please tell me how to completely disable trinity logs, it keeps makining it (loglevel: normal), I get bad lags with many vm turned on! PMed you already.

I continued the tests, doing them 3-4 hours, already reached my goal - stable smooth botting process :)
Click to expand...

Demonbuddy logs can't be disabled, but, to disable Trinity logs, just uncheck all the 'Debug System' checkboxes in the advanced tab. It's safe to leave the 'Debug Info in Status Bar' on (that doesn't actually *log* anything)
 
Status
Not open for further replies.
Back
Top