Trinity 1.7.2.2

[plzdontban]

Do you have all stash slots and tabs bought out? I didn't and had this problem, solved it by buying all. Not ideal I know but worked

 

[tesslerc]

hmm this would be a problem when leaving the bot alone for a week or so

is there any reason why db is in control of townrun/stashing? with trinity everything was fine ;-(

Nesox made it work well
Just report this bug on support section.

If trinity would be in charge then every time nesox changes anything - trinity would need an update too.
This way (since db does it ok now) it is a lot cleaner.

 

[demonnbuddy]

when bag is full at position A, bot will kill mobs for TP, and bot may run to position B for killing, then bot find more mobs, and run to position C for killing, then TP at position C.
after townrun, all loots at position A will be ignored, bot start from position B.

 

[Mammon]

demonbuddy, disable extend combat range...

 

[Eisenberg]

Wouldnt be then to much to ask for "pickup legendary plans only" fsetting included in some future trinity release ? Because on the one hand number of yellow worthless plans being picked up by bot is abysmall right now, but on the other, some legendary plans are worth tens of millions.

 

[id_dorin]

my bot doesn't pick Demonic Essence, how could i change this?

 

[quadrotony]

but on the other, some legendary plans are worth tens of millions.

for example

 

[jiznadj]

Anyone come up with any settings to reduce CPU usage? Testing this out, getting about 25-30 percent CPU on a 4ghz i5 with a single bot. BTW 1.7.2.2 is still trying to path through walls in the keep dungeons.

 

[lostsk8r]

If we increase the cache timer limit, so it essentially holds the cache longer before making a new one, this will help with the CPU usage until it resets the cache?

 

[Mammon]

For better perfomance, use these d3prefs settings and use the program advanced care

d3prefs.txt :
PreferencesVersion "44"
PlayedCutscene0 "15"
PlayedCutscene1 "15"
PlayedCutscene2 "23"
PlayedCutscene3 "143"
DisplayModeFlags "0"
DisplayModeWindowMode "1"
DisplayModeWinLeft "343"
DisplayModeWinTop "207"
DisplayModeWinWidth "800"
DisplayModeWinHeight "600"
DisplayModeUIOptWidth "800"
DisplayModeUIOptHeight "600"
DisplayModeWidth "800"
DisplayModeHeight "600"
DisplayModeRefreshRate "75"
DisplayModeBitDepth "16"
Gamma "1.000000"
MipOffset "1"
ShadowQuality "0"
PhysicsQuality "0"
ClutterQuality "0"
Vsync "0"
Letterbox "0"
Antialiasing "0"
LowFX "1"
LimitForegroundFPS "1"
MaxForegroundFPS "15"
LimitBackgroundFPS "1"
MaxBackgroundFPS "15"
DisableTrilinearFiltering "1"
ColorCorrection "1"
MipBias "9.999000"
ReflectionQuality "0"
TonemapExposure "1.900000"
TonemapContrast "1.500000"
TonemapSaturation "1.000000"
TonemapGain "1.000000"
HardwareClass "1"
PCIVendor "4098"
PCIDevice "26392"
MasterVolume "1.000000"
EffectVolume "0.800000"
MusicVolume "0.800000"
NarrationVolume "0.800000"
AmbientVolume "0.800000"
ChannelsToUse "16"
SoundDriver "0"
SpeakerMode "0"
ReverseSpeakers "0"
QuestSubtitlesEnabled "0"
CinematicsSubtitlesEnabled "0"
MuteSound "1"
MuteEffects "0"
MuteAmbient "0"
MuteVoice "0"
MuteMusic "1"



I've tried actually on lower (8bit graphic and 150x100 reso) but doesn't notice any difference in cpu load (using 11 currently)

 

[jiznadj]

For better perfomance, use these d3prefs settings and use the program advanced care

I've tried actually on lower (8bit graphic and 150x100 reso) but doesn't notice any difference in cpu load (using 11 currently)

My D3 prefs are already tweaked. Went from 15-20 percent with two bots to 75-90. Something is really wrong.

 

[Occ]

when bag is full at position A, bot will kill mobs for TP, and bot may run to position B for killing, then bot find more mobs, and run to position C for killing, then TP at position C.
after townrun, all loots at position A will be ignored, bot start from position B.

I am the same
+1

 

[Mammon]

Originally Posted by demonnbuddy
when bag is full at position A, bot will kill mobs for TP, and bot may run to position B for killing, then bot find more mobs, and run to position C for killing, then TP at position C.
after townrun, all loots at position A will be ignored, bot start from position B.
I am the same
+1

Update DB Beta.

 

[Mammon]

My D3 prefs are already tweaked. Went from 15-20 percent with two bots to 75-90. Something is really wrong.

Did you mean you went to 75% after trying out my d3prefs or do you mean you suspect it's due to resource handling by trinity or db in later releases?

 

[jiznadj]

Did you mean you went to 75% after trying out my d3prefs or do you mean you suspect it's due to resource handling by trinity or db in later releases?

Went from 15-20 on older trinity to 75-90 with the new trinity, I really wish rrrix would update the older 1.6 version until the bugs are worked out of the new 1.7x version.

 

[Mammon]

I request also a "low cpu/stripped" upcoming for trinity!
With some perfomance consuming functions disabled, such as ALL logging (If possible, rrrix?) and no prawl, and a character-tuned edit with only settings for the current class.

Such as "Trinity low-cpu-edit with a very simple gui layout and smaller load for each character"

This wouldn't only reduce cpu but probably perfomance in general.. Agreed?

 

[rrrix]

Went from 15-20 on older trinity to 75-90 with the new trinity, I really wish rrrix would update the older 1.6 version until the bugs are worked out of the new 1.7x version.

I'm not going to touch 1.6.3.4 with a ten foot pole. However I will continue to improve the latest versions.

Can I ask you to enable Debug System Performance, and zip and attach a log while you're having this extreme CPU utilization?

 

[Mammon]

Also requesting some double check for molten core explosions, they seem to be the only thing that could potentially kill you - when it's absolutely not neccessary.

 

[rrrix]

Also requesting some double check for molten core explosions, they seem to be the only thing that could potentially kill you - when it's absolutely not neccessary.

Yeah avoidance in general hasn't gotten any love lately.

 

[jiznadj]

I'm not going to touch 1.6.3.4 with a ten foot pole. However I will continue to improve the latest versions.[/IMG]

I don't really blame you there, I was talking about 1.7.1x but it would be nice if when a new version of DB is released that it does not break all the old versions of trinity so there would be something to go back to in case there is a problem.

Can I ask you to enable Debug System Performance, and zip and attach a log while you're having this extreme CPU utilization?

Not sure the logs will tell you anything since it is not crashing or anything but I'll see what I can do, it doesn't go that high all the time but it is always at a minimum of 60 percent or so which is triple what it was.