Nothing jumps out to me as weird in your log, but then it probably wouldn't. The only things I can see that are different on your end than on mine are the fact that A) You choose North America as your navigation server whereas I leave it at Best Latency. Regardless, we still both connected to the NA server at 192.99.20.72. B) you're using the beta and I'm just using the 1.1.530.0 release version. And C) I just let Trinity auto-detect my routine, you force selection of a specific monk rotation.
And yet, something is clearly different. Mine does not lock up that severely. I do have occasional lock ups, but I haven't had one while rifting today. My only issue today has been the gem upgrade glitch where the bot doesn't find Urshi. Spent like 4 hours standing in town waiting for a portal to close magically by itself.
I do notice a couple of Exceptions get thrown very early on into your session:
Code:
2018-08-02 02:09:34,006 [1] DEBUG DefaultLogger (null) - [Trinity 2.6.448] System.Exception: Only part of a ReadProcessMemory or WriteProcessMemory request was completed, at addr: 00000097, Size: 4
at GreyMagic.ExternalProcessMemory.ReadByteBuffer(IntPtr addr, Void* buffer, Int32 count)
at GreyMagic.MemoryBase.Read[T](IntPtr addr)
at Zeta.Game.Offsets.StaticsEncrypted.?????????????????????????????????????????(IntPtr )
at Zeta.Game.Internals.Actors.DiaObject.????????????????????????????????????????()
at Zeta.Game.PerFrameCachedValue`1.get_Value()
at Zeta.Game.Internals.Actors.DiaObject.get_SceneId()
at Zeta.Game.Internals.Actors.DiaObject.get_CurrentScene()
at Zeta.Game.ZetaDia.get_CurrentLevelAreaSnoId()
at Trinity.Components.Adventurer.Adventurer.OnWorldChanged(ChangeEventArgs`1 args) in C:\Demonbuddy\Plugins\Trinity\Components\Adventurer\Adventurer.cs:line 43
at Trinity.Framework.Objects.Module.WorldChanged(ChangeEventArgs`1 args) in C:\Demonbuddy\Plugins\Trinity\Framework\Objects\Module.cs:line 37
at Trinity.Framework.ModuleManager.<>c__DisplayClass20_0.<WorldIdOnChanged>b__0(Module m) in C:\Demonbuddy\Plugins\Trinity\Framework\ModuleManager.cs:line 121
at Trinity.Framework.ModuleManager.SafeExecuteOnInstances(Action`1 action, String caller) in C:\Demonbuddy\Plugins\Trinity\Framework\ModuleManager.cs:line 163
and:
Code:
2018-08-02 02:09:34,248 [1] DEBUG DefaultLogger (null) - [Trinity 2.6.448] System.Exception: Only part of a ReadProcessMemory or WriteProcessMemory request was completed, at addr: 000001AF, Size: 12
at GreyMagic.ExternalProcessMemory.ReadByteBuffer(IntPtr addr, Void* buffer, Int32 count)
at GreyMagic.MemoryBase.Read[T](IntPtr addr)
at Zeta.Game.Internals.Actors.DiaObject.get_Position()
at Trinity.Modules.SceneStorage.get_CurrentScene() in C:\Demonbuddy\Plugins\Trinity\Modules\SceneStorage.cs:line 33
at Trinity.Modules.SceneStorage.Update() in C:\Demonbuddy\Plugins\Trinity\Modules\SceneStorage.cs:line 147
at Trinity.Modules.SceneStorage.OnWorldChanged(ChangeEventArgs`1 args) in C:\Demonbuddy\Plugins\Trinity\Modules\SceneStorage.cs:line 50
at Trinity.Framework.Objects.Module.WorldChanged(ChangeEventArgs`1 args) in C:\Demonbuddy\Plugins\Trinity\Framework\Objects\Module.cs:line 37
at Trinity.Framework.ModuleManager.<>c__DisplayClass20_0.<WorldIdOnChanged>b__0(Module m) in C:\Demonbuddy\Plugins\Trinity\Framework\ModuleManager.cs:line 121
at Trinity.Framework.ModuleManager.SafeExecuteOnInstances(Action`1 action, String caller) in C:\Demonbuddy\Plugins\Trinity\Framework\ModuleManager.cs:line 163
And those were it. Nothing else shows up in the log until the time gap where DB hangs and you clearly had to manually kill the process. I get tons of exceptions during a botting session, but not right at the beginning like that. They tend to happen like clockwork every 5-10 minutes. Also at the 00000097 memory address similar to your first thrown exception.
I have Windows Defender and Norton Security Suite running, both with exclusions set for the Diablo3 and DB folders. I completely disable audio for diablo 3 in game settings. And when I'm leaving it to run unattended I let DB sit on top of the Diablo 3 window.
I have no clue, man. I could guess but it would be like throwing a dart at a dictionary and hoping you spell out an intelligible sentence. I sympathize. I really do. Hopefully someone far more knowledgeable will be able to help, or have a good recommendation for something to try. I'm just a typical end-user. Most problems I can solve on my own are of the shut it off and turn it back on variety. Windows does like a good restart every now and then.
But anyway, I am glad you were able to get some use out of the Bounty Fix. It's still horrible, but it's like driving a car with three working tires instead of none.
