Anyway to make DB run smoother 4 bots?

[Tkay]

So my pc is beast af, gtx980ti, 6700k cpu, but once I went from 3 -4 bots at once, it started to take a pretty heavy toll on my pc. I have settings and res low, any other way to make it run easier?

edit: Having huge trouble running 4, just crashes.

EDIT:: Overclocked my CPU, runs perfectly now.

 

[FreakyBart]

yo.
nope, it take a lots of ressources.
just disable sound & set graphics to low throught nvidia panel, and not only diablo settings

 

[Tkay]

Good idea!

 

[xzjv]

In trinity settings > Advanced limit your (Ticks per Second) TPS to around 10. At 30+ TPS DB uses 10-30% CPU per instance. at 5-10 TPS its more like 2-5% CPU.

 

[Tkay]

What happens to the bot itself if under 10?

 

[boynextdoor]

with 4 accounts I found myself utilizing 16 / 16 gb of my ram. I purchased another 16 bringing me to 32 but havent run anything yet. Might try it again this season but might not considering the ban waves. Run the 4 bots again and check your ram usage, once you run out of ram your computer will start using your HD to serve as memory and it will slow things down considerably.

 

[mishmear]

with 4 accounts I found myself utilizing 16 / 16 gb of my ram. I purchased another 16 bringing me to 32 but havent run anything yet. Might try it again this season but might not considering the ban waves. Run the 4 bots again and check your ram usage, once you run out of ram your computer will start using your HD to serve as memory and it will slow things down considerably.

Must be something else using all your memory D3 doesn't use that much

 

[FreakyBart]

4 D3&DB does, and xzjv posted a working solution

 

[looser7k]

im using isboxer to rum my 4 accounts on low graphic settingin in d3. it works very smooth on my 3000 euro pc. i think isboxer is worth the money never tried muliboxing though.

 

[xzjv]

What happens to the bot itself if under 10?

TPS controls how long it sleeps for between each 'tick' - which is a pass at thinking/processing. During a tick actors (monsters/switches/barrels etc) are refreshed so we have their current hit-points/location etc. During a tick there is usually an opportunity for a spell to be cast, an instruction to move somewhere. You get the idea.

At 10 TPS it will do a tick - then go to sleep and do nothing for 1/10 second. Then tick (for however long that takes maybe 10-100ms), then sleep again for 1/10 of a second and so on.

So impacts of a low setting? it will be slightly slower to react. You probably wont notice a difference unless you set it really low.

Most of the time there is no need for it to think really fast, as in 30 times a second, because 90% of those ticks nothing has changed, and its just wasted effort and CPU.

But for some builds it does matter, a couple seasons ago when generator monk was the rage the attack speed of the build was fast enough to make use of the faster processing. I think it could attack (potentially different targets) somewhere in the 100-200 ms range.