Hi,
I had been playing Diablo 3 for a while today and when I turned my Bot on I noticed it would go to screen flashing and when I clicked the Diablo 3 window it would crash DB. Then I have to wait for my key to time out because I would get max sessions message. I immediately did a clean install of DemonBuddy and manually updated and made sure I had the most up to date GilesTrinity and RadsAtom, the only two plugins i use. After the clean install I got it up and running first try.
Now after this it played perfect for a while and crashed diablo and DB to desktop, and now DB crashes at the Flashing screen part of login. I have attached the log file to this post in hopes that someone could please help me out. Thank you in advance, very much appreciated.
Just fyi, I am able to play Diablo 3 for hours manually, its just when I try to run DB that it crashes.
Most of my Log files look like this:
[02:55:09.115 N] ========== Grid segmentation resetting!!! ============
[02:55:10.053 N] Demonbuddy v1.0.1094.279 started
[02:55:11.054 N] Logging in...
[02:55:12.332 N] Attached to Diablo III with pid: 3104
[02:55:12.349 N] Flashing window
But the latest one looks like this:
[02:53:44.204 N] ========== Grid segmentation resetting!!! ============
[02:53:45.158 N] Demonbuddy v1.0.1094.279 started
[02:53:47.594 N] Logging in...
[02:53:48.847 N] Attached to Diablo III with pid: 3104
[02:53:48.857 N] Flashing window
[02:53:50.265 D] Executable Path: C:\DB Clean\Demonbuddy.exe
[02:53:50.265 D] OS Architecture: AMD64
[02:53:50.267 D] OS: Windows 7 Service Pack 1 64-bit
[02:53:50.267 D] OS Language: English (United States)
[02:53:50.284 D] Reloading AssemblyLoader<Zeta.CommonBot.ICombat> - Initializing
[02:53:52.691 N] Current bot set to Order Bot
[02:53:52.692 N] Loaded profile [A2 - Inferno] Keyhunting Profile 2
[02:54:58.895 D] Cannot stop a bot when it is not running.
[02:54:58.895 D] Forcing closed all current windows.
My log files below.
View attachment 1984 2012-10-19 22.11.txt
View attachment 936 2012-10-19 22.53.txt
View attachment 3748 2012-10-19 22.10.txt
View attachment 4476 2012-10-19 19.01.txt
I had been playing Diablo 3 for a while today and when I turned my Bot on I noticed it would go to screen flashing and when I clicked the Diablo 3 window it would crash DB. Then I have to wait for my key to time out because I would get max sessions message. I immediately did a clean install of DemonBuddy and manually updated and made sure I had the most up to date GilesTrinity and RadsAtom, the only two plugins i use. After the clean install I got it up and running first try.
Now after this it played perfect for a while and crashed diablo and DB to desktop, and now DB crashes at the Flashing screen part of login. I have attached the log file to this post in hopes that someone could please help me out. Thank you in advance, very much appreciated.
Just fyi, I am able to play Diablo 3 for hours manually, its just when I try to run DB that it crashes.
Most of my Log files look like this:
[02:55:09.115 N] ========== Grid segmentation resetting!!! ============
[02:55:10.053 N] Demonbuddy v1.0.1094.279 started
[02:55:11.054 N] Logging in...
[02:55:12.332 N] Attached to Diablo III with pid: 3104
[02:55:12.349 N] Flashing window
But the latest one looks like this:
[02:53:44.204 N] ========== Grid segmentation resetting!!! ============
[02:53:45.158 N] Demonbuddy v1.0.1094.279 started
[02:53:47.594 N] Logging in...
[02:53:48.847 N] Attached to Diablo III with pid: 3104
[02:53:48.857 N] Flashing window
[02:53:50.265 D] Executable Path: C:\DB Clean\Demonbuddy.exe
[02:53:50.265 D] OS Architecture: AMD64
[02:53:50.267 D] OS: Windows 7 Service Pack 1 64-bit
[02:53:50.267 D] OS Language: English (United States)
[02:53:50.284 D] Reloading AssemblyLoader<Zeta.CommonBot.ICombat> - Initializing
[02:53:52.691 N] Current bot set to Order Bot
[02:53:52.692 N] Loaded profile [A2 - Inferno] Keyhunting Profile 2
[02:54:58.895 D] Cannot stop a bot when it is not running.
[02:54:58.895 D] Forcing closed all current windows.
My log files below.
View attachment 1984 2012-10-19 22.11.txt
View attachment 936 2012-10-19 22.53.txt
View attachment 3748 2012-10-19 22.10.txt
View attachment 4476 2012-10-19 19.01.txt