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

Trinity 1.7.3.2

Status
Not open for further replies.
bizzy1one said:
why is my barb stopping WW and doing a stutter step lol? it looks like he's trying to cast something he doesnt have the fury for or tries to rend but doesnt match criteria for rend cast?

everything else seems to be working great, maybe i have something set wrong?

He stops to cast rend but a high % of the time he doesn't cast it because he's spamming sprint to fast? something is def up with my rend and dunno how to fix.
Click to expand...
My barbs do the same. And strangely, sometimes the don't cast WOTB. Dunno why...
 
Madenaras said:
My barbs do the same. And strangely, sometimes the don't cast WOTB. Dunno why...
Click to expand...

it looks to me like he is spamming sprint non stop which fixes the fury dump problem, but when he tries to cast rend he cant cast it because 734,573 casts of sprint are going off.

i guess it needs a check to stop sprint spam when rend needs to be cast? maybe can get a simple fix soon from rrix or something else capable =)

maybe its not rend, as he stops when he spams sprint regaurdless. he never spams sprint and keeps moving, or maybe its multiple things happening in there.
 
Hey everyone, does anyone know if the initial problems with Trinity 1.7.3.1 / 2 / 3 have been sorted out? It would instantly cause DB and D3 to crash on the original release to the newer version. Thanks in advance if anyone knows.
 
And still Demonbuddy crashes with new trinity. Fresh install, new Folder, all new, i copy
the Trinity folder into the new Plugin folder but if i start demonbuddy D3 and Demonbuddy crashes.

[08:48:18.198 D] Reloading AssemblyLoader<Zeta.Common.Plugins.IPlugin> - Initializing plugins
[08:48:19.144 N] Using SNORecord Table 718
[08:48:19.234 N] Diablo III Exited, Demonbuddy terminating in 20 seconds.
[08:48:19.293 D] System.ArgumentException: The version string portion was too short or too long.
in System.Version.VersionResult.SetFailure(ParseFailureKind failure, String argument)
in System.Version.TryParseVersion(String version, VersionResult& result)
in System.Version.Parse(String input)
in System.Version..ctor(String version)
in Demonbuddy.MainWindow.CheckForUpdate()
[08:48:19.306 D] Cannot stop a bot when it is not running.
[08:48:19.307 D] Forcing closed all current windows.
 
@people with sprint problems: I cannot reproduce the bug, so please provide more info. Watch the fury when he stops. Is it at 0? If so, you are fury starved. I use a Mighty Weapon + Weapon Master, so I'm almost never fury starved. Rend has a higher priority than Sprint, so maybe try to change the variables for Rend:
Barbarian.Rend.MinFury (default 20, especially increase this)
Barbarian.Rend.MinNonBleedMobCount (default 3)
Barbarian.Rend.MinUseIntervalMillseconds (default 1500, try to increase this too)
Barbarian.Rend.MaxRange (default 10)
... I believe that this is a build problem, so you might have to change a few things to generate fury faster or tweak variables (even try the ones for Sprint). You can change them in plugin settings.
 
@people who experience startup crashes: Try unblocking Demonbuddy in firewall. It seems he's trying to check for a new version, and gets an empty response or something (the code is not public): crashes in Demonbuddy.MainWindow.CheckForUpdate(). Also, if you use a *****ed version, it might not work. Check that you use the latest Demonbuddy.
 
FluffyPulsar said:
@people with sprint problems: I cannot reproduce the bug, so please provide more info. Watch the fury when he stops. Is it at 0? If so, you are fury starved. I use a Mighty Weapon + Weapon Master, so I'm almost never fury starved. Rend has a higher priority than Sprint, so maybe try to change the variables for Rend:
Barbarian.Rend.MinFury (default 20, especially increase this)
Barbarian.Rend.MinNonBleedMobCount (default 3)
Barbarian.Rend.MinUseIntervalMillseconds (default 1500, try to increase this too)
Barbarian.Rend.MaxRange (default 10)
... I believe that this is a build problem, so you might have to change a few things to generate fury faster or tweak variables (even try the ones for Sprint). You can change them in plugin settings.
Click to expand...

he doesnt stop and stand there w/o fury to cast rend. he stops ww'ing to dump fury by casting sprint like 5+ times. this barb has 90% crit and full fury almost all the time. i guess when he stops to dump fury it could go under the 20 min for rend.

the barbs im running dont spam sprint and keep ww'ing or even running. they stand still and spam it w/o moving. when this happens nados stop spawning and ww stops hitting, which causes less killing and more dying. this is a problem even w/o the rend problem.

barb needs to dump fury via sprint while maintaining ww.

p.s. every time i try to change variables via trinity it crashes db?
 
Hmph, he should only cast it once (if fury is >= 95%), but I guess there is some problem with caching, so he thinks that he's still at 95%+ while casting sprint multiple times. From what I can tell, he casts it like 2 times for me, but very quickly, so it doesn't really matter. The next thing you can try is to play with TPS and Cache Refresh Rate (the Advanced tab). Decrease cache refresh time and/or increase TPS (watch CPU usage, because this can have a huge impact on performance).

If your barb has tornados generating fury with 90% crit, then maybe the bot doesn't register the fury decrease as it appears he's still at full fury. In that case, the cache tweaks could work, too.

Yea, it crashes when changing variables. Pitty. It also sometimes crashes while reloading item rules. I guess thread synchronization doesn't work all too well.

Also, Test Backpack Scores and Order Stash buttons generate exceptions (even in the old Trinity).

What can I tell you - many bugs to be fixed still, but fortunately, works for me. :D
 
FluffyPulsar said:
Hmph, he should only cast it once (if fury is >= 95%), but I guess there is some problem with caching, so he thinks that he's still at 95%+ while casting sprint multiple times. From what I can tell, he casts it like 2 times for me, but very quickly, so it doesn't really matter. The next thing you can try is to play with TPS and Cache Refresh Rate (the Advanced tab). Decrease cache refresh time and/or increase TPS (watch CPU usage, because this can have a huge impact on performance).

If your barb has tornados generating fury with 90% crit, then maybe the bot doesn't register the fury decrease as it appears he's still at full fury. In that case, the cache tweaks could work, too.

Yea, it crashes when changing variables. Pitty. It also sometimes crashes while reloading item rules. I guess thread synchronization doesn't work all too well.

Also, Test Backpack Scores and Order Stash buttons generate exceptions (even in the old Trinity).

What can I tell you - many bugs to be fixed still, but fortunately, works for me. :D
Click to expand...

i'm testing out the cache rate atm and will post findings.

the other thing that is somewhat frustrating is sometimes it doesnt recast wotb after it drops and comes back off cooldown. not sure what the problem is there either but it is def a problem.
 
bizzy1one said:
the other thing that is somewhat frustrating is sometimes it doesnt recast wotb after it drops and comes back off cooldown. not sure what the problem is there either but it is def a problem.
Click to expand...
I noticed this too, but it's very rare for me. The bot might have tried to cast it, and D3 didn't allow it, but the timer kicked in, so the bot waits for another 2 mins to recast it. This could also be a cache problem. Who knows.
 
higher cache rate makes him stand still longer and cast slower. lower cache rate seems to make him cast more sprints or at least faster. lower cache rate is the better option but still doesnt help much.

the ww code + legendary code + min trash count code all are huge upgrades. if can get fury dump with a fluid ww it will be golden =)
 
I know you guys working hard on trinity. Its a great plugin and we all cant bot without, so big thanks. But both new versions are bugged like hell. Check the comments. Much ppl cant run trinity because it crashs D3+DB instantly. And not everyone here is using the h*** shit. On the other hand, barbs are again broken. And all i read is dont use h* or try this and do that. But not every user here is experienced enough to setup such stuff.

So please try to fix the new trinity and concentrate on a stable and easy to use release instead of pushing more and more options, which not work.

@Fluffy: No firewall activated (not the windows one, no other). Clean Win7 without any updates. Tested on 4 different PCs with different hardware. All crashing, thats weired. Will hope the next version is working again.
 
FluffyPulsar said:
can you upload a video of this behavior? it could help a lot.. you can use Fraps
Click to expand...

he stops to spam sprint instead of continuing to channel ww / move. thats the whole problem. if your barb stops moving to cast sprint twice then its the same behavior. mine just does it more. it kinda looks like first generation tempest rush.

it needs to spam sprint while continuing everything else like it casts overpower w/o stopping ww.
 
bizzy1one said:
higher cache rate makes him stand still longer and cast slower. lower cache rate seems to make him cast more sprints or at least faster. lower cache rate is the better option but still doesnt help much.

the ww code + legendary code + min trash count code all are huge upgrades. if can get fury dump with a fluid ww it will be golden =)
Click to expand...
So, this is what I came up with without understanding the issue fully, so it might not work at all, but please test if it's working better. It should cast Sprint with min 300ms intervals. This should allow WW to be used in between. I would use variables, but those cannot be setup anyway (crash), therefore it is hardcoded for the moment.
 

Attachments

bizzy1one said:
he stops to spam sprint instead of continuing to channel ww / move. thats the whole problem. if your barb stops moving to cast sprint twice then its the same behavior. mine just does it more. it kinda looks like first generation tempest rush.

it needs to spam sprint while continuing everything else like it casts overpower w/o stopping ww.
Click to expand...
My barb runs fine, he doesn't stop, therefore I requested a vid which would show me fury levels etc etc. Since I can't reproduce it, I'm not gonna waste much more time with this, not knowing the root cause. But feel free to try my attempted fix.
 
derico5 said:
I know you guys working hard on trinity. Its a great plugin and we all cant bot without, so big thanks. But both new versions are bugged like hell. Check the comments. Much ppl cant run trinity because it crashs D3+DB instantly. And not everyone here is using the h*** shit. On the other hand, barbs are again broken. And all i read is dont use h* or try this and do that. But not every user here is experienced enough to setup such stuff.

So please try to fix the new trinity and concentrate on a stable and easy to use release instead of pushing more and more options, which not work.

@Fluffy: No firewall activated (not the windows one, no other). Clean Win7 without any updates. Tested on 4 different PCs with different hardware. All crashing, thats weired. Will hope the next version is working again.
Click to expand...
Not many people work on Trinity atm. I for one am a new DB user with a lot of coding experience, so I try to help, but it takes a lot of time to track down some of the issues if I don't have them. I'm sure rrrix has the same problem, so the issues remain unfixed. Be glad that there are options you can tweak, because it is very hard to optimize the bot for all builds. There are guides which help you setup Trinity and other plugins to optimize your run.
 
derico5 said:
@Fluffy: No firewall activated (not the windows one, no other). Clean Win7 without any updates. Tested on 4 different PCs with different hardware. All crashing, thats weired. Will hope the next version is working again.
Click to expand...
Then try installing all updates + SP1. It's the first thing I did. It updates .NET as well. There could be some old .NET on your computer, etc.
 
Status
Not open for further replies.
Back
Top