What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

[Standalone] DB Guard Crash detection and Relog

gexstar said:
Why does he always ask if i want to start Diablo 3 and DB ?
Ofcause i want to start those, what else would i want to do with DB Guard ? :D

And he somehow doesnt notice that the game started... he always thinks im still at charscreen and then restarts everything.

Using Win7 32b on a VM btw.
Click to expand...

I will include this in the next release. :)
VM not supported currently, I am investigating how to implement it.
 
Sangrejoven said:
I need some help with this Plug-in. I am able to the set the DB Guard up but during the restart stage after the first game has completed. 1. D3 will start 2. The DB icon is in the task bar (Blinking) and the plugin does not open it or bring it to the windows mode to be recognized. Then I get this message "DB Not Detected Do you want to start it (Yes or No) Is there a setting I am missing or does anyone else have this problem?
Click to expand...

Please make sure ur screen looks like the image posted in the guide and in the first post.
If you are using a VM, this is currently not supported.
 
hmm i'm having some problems with Ver 1.130,

basically the problem is that although it has no problem reloading D3 and logging in, somehow DBguard is unable to load up DB even though there's no error message popping up this time round. Will test back ver 1.120 to see if the same problem occurs.

Question, when we do an upgrade of version, do we have to delete off all the old .config files or we just replace the .exe file? Maybe that's what causing the problem.
 
hmm just tested ver 1.12 and it has no problem with launching D3 and DB... now monitoring to see if everything runs normally.
 
sfrattini said:
can you try to run it in compatibility mode?
Click to expand...
I tried that but still can not run, I even run in a different PC with windowsXP X86 OS, and got the same result.....

Is that possibly because my OS language is not English?

Thx for reply.
 
update:

v1.12 works great. ran it for close to 40 hours and it helped to relog my d3 and db twice. nice work!
 
gexstar said:
Why does he always ask if i want to start Diablo 3 and DB ?
Ofcause i want to start those, what else would i want to do with DB Guard ? :D

And he somehow doesnt notice that the game started... he always thinks im still at charscreen and then restarts everything.

Using Win7 32b on a VM btw.
Click to expand...

will there be an updated release to address this issue? current ver has some quirks but most of the time it works for me.
 
great software, was looking for something like this for a while... thanks a lot
 
Nice tool.

But always crushes just before starting a new game...
Screen in correct position
 
My anti virus software pops out when I try to run it, says Win32.Troj.Generic.
 
Does DB guard support multiple instances?

edit: it works great for me btw.
 
I am wondering that how is the timeout setting gonna resolve this problem: when using RadsAtom to set break timer, lets say 30-90mins, and DB guard will count that as "inactive" and starts counting too( if I understand it correctly). In this case, I have to set to DB Guard timer for 90mins otherwise DB Guard would close D3 and DB then restart them. However, if D3 went wrong and error window pops out, DB Guard would not restart everything until the 90min timer is up. Then technically, it wastes 90mins.
 
so since patch 1.06 it stopped working... get a message "Line: 660 error - subroutine/label restart not found!" anyone getting this?
 
wenyi289 said:
I am wondering that how is the timeout setting gonna resolve this problem: when using RadsAtom to set break timer, lets say 30-90mins, and DB guard will count that as "inactive" and starts counting too( if I understand it correctly). In this case, I have to set to DB Guard timer for 90mins otherwise DB Guard would close D3 and DB then restart them. However, if D3 went wrong and error window pops out, DB Guard would not restart everything until the 90min timer is up. Then technically, it wastes 90mins.
Click to expand...

Thats correct.
DBGuard cannot make differences between a [crash] and a [RadsAtom] wait time, I might think about adding a feature to do the break directly in Dbguard...
 
You must log in or register to reply here.
Back
Top