[A3 Inferno] Alkaizer RUN Gnome Proof - Unstuckable

im still on 1.7.1.9

gonna try this out.

 

After some testing, ive had my bot kinda fixed, if i run him myself to Azmodan checkpoint and then leave the game and load Gnomestart instead of Jumpstart he is doing the runs fine, and he is going for few hours. but then there is a problem when he can, after few runs just log out in FoS and when he is starting next game he spawns in FoS instead of Core. he tps back to city and load Core profile and leaves game. and then start to go in and out as mantioned before.

E. Just noticed that after resetting he starts at The second heart, instead of kill azmodan.

 

n1 profile thanks alot gnome! 2.8a runs great for me with 13 trinity

I was impressed by ur high gph guys, can some1 pls advice me optimized loot settings for trinity? what should my bot pick up to achieve these high results?..

 

I get this stuck too.
Trinity 1.12
gnome 2.8a
Trinity unstucker deals with it, usually takes few min to get back on track.

 

Minutes.... dont want that wasted fixing tower today.

 

So fos need on game entry stuck handling? thats what i am determining.

 

OVER NIGHT TEST RESULTS = .13 TRINITY IS CURRENTLY A FAILURE.

So until rrrix gets and runs some real profiles over here, I am at the mercy of this 299! BUG THAT IS OVER 3 MONTHS OLD! what the heck?

all 3 bots down this morning.

Alkaizer ran for 18 hours then loooped into Core 1 Core 2 file, after being at FOS I beleive, some how it got to core1 after it should never be there, probably due to leave game on so many deaths. THIS 299 BUGGED OUT CRASHED DIABLO AND DEMONBUDDY! fooooooook joy! happy new year! 3 month old bug.

1-60 level profile with trinity .13
Decided to magically stop bot........ @ lvl 34

last bot running the same
1-60 level profile with trinity .13
Decided to magically stop profile @ lvl 12

So, these are isolated complete different accounts different areas, different profiles.. but yay trinity .13

other than the HUGE overhead with the new mesh thing (I had to turn it off on all test machines, it's overbearing completely) I am rating .13 as near garbage that may need full attending.

TOWER 1 FIX

THERE is 3 hot spots commented out 18 19 20 or to that matter, just re-uncomment those, you should never stick in tower again.

 

I will try .13 for one more day, after that I am going back to .10 which was many times smoother. Only have to use UnstuckMe!


.10 reports good for barbs
.10 reports not good for wizards (crash related)

 

Oh also before anyone gets me wrong, Okay, the stuck crash, Quest change thing, is happening due to leave game on death counter. And depending which area or which profile it resumes to that same profile which if it hit a checkpoint it can change the start location resulting in terrible things happening.

When I changed over to NON RADS, I stopped testing on death and resume. I will retest all of that today, and correct resume game bugs for everyone.

I was kind of hoping trinity would be-able to handle this type of behaviour but it doesn't there is way to much mesh touch stuck work going on for whatever reason, and leaving in old bugs like the 299! one. Why we need mesh any ways, is beyond me.

 

I will personally assist you in fixing this issue, please contact me via skype and refer to this post.

Did you delete the rads folder from your plugins folder... possibly the cause.

 

This is due to RadsAtom 1.5.1
use ATOM and it shouldn't happen.

never seen this issue when running trinity as only plugin (on any profile including your one).

 

Top Profiles by average GPH
Job2k9 Champ Hunt
523.50k
Core + FOS By Limpice
490.47k
04 v2.5O.6 RC ARC - debug version [Galkaizer] Fields of Slaughter
480.53k
03 v2.8 Pro Only [Galkaizer] TotD Level 1
441.28k
Core of Arreat+Fields of Slaughter-Long Private By: Fragmam, Thank you for donate-me.
409.04k
06 v2.8 public [Galkaizer] Fields of Slaughter
399.81k
[A3 - Inferno] Ultimate SkyHigh Farm
398.90k
Tinnkaizer v0.4
396.63k
05 v2.5O.6 RC ARC - debug version [Galkaizer] The Keep Depths Level 2: Random SEARCH
391.61k
Tinnkaizer v0.5

 

I am shaking my head still as I reply to this, knowing that you read NOTHING on the OP post, which declares WE DO NOT USE RADSATOM ANYMORE !

justify the unjust, 3 completely different scenarios, 3 different bot levels, 3 different servers areas..

ONLY THING SAME TRINITY.13

failed all 3.

 

in 24 hours, I will apply a .10 trinity test, of course results, won't be exactly the same, but we will see what happens during sleep test.

 

What we are working on 'TODAY'

- bringing you fix to optimize AC2 even further (maximize XP)
- fixing Tower 1 to never stick

- writing stuck handling, for those mysterious stucks ... due to death and profile restart at wrong spot (easy fix just a bit of time to do hope to have done today)

 

The memory reading error "299" you speak of is not Trinity 1.7.1.13. If you look at the stack trace, it clearly says it's coming from RadsAtom. It would also be helpful to point out in the leveling profile where the two bots got stopped, maybe attach a log?

Oh, and I am " running real profiles"...

cheers,

rrrix

 

Which part of, we have removed deleted RadAtom from Plug folders was misunderstood?

" clearly says it's coming from RadsAtom. "

 

Hmm. Can you attach a log into the Trinity section? I haven't seen a memory read error on any of mine in ages... Usually people get pretty noisy about that one.

thanks!

 

be a bit more friendly ..

running 17 bots overnight with ur profile and trinity 1.7.13 not a single stuck and nearly 600gph.

delete ur whole folder for 1.7.13 it has to be a problem on ur side, or maybe i m mega lucky but 1-60 works for me, ur profile works and never got this error ur saying.

 

Keep it up Gnome!