Jump to content
  • Wotlk Wrobot crashes after the last update


    eafa
    • Version: All Product: WRobot General Type: Bug Status: Fixed

    Like it says, it crashes after starting any grinder/quester profile, had to roll back to 35712, latest backup I had :(



    User Feedback

    Recommended Comments

    Sorry for the confusion, my problem was caused by a .dll plugin which was compiled with the previous version, all good without it.

    But ! I still have another problem - my PC may get BSOD and reboot accidently while running 3+ wrobot+wotlk instances, it also seems that it happens on mass relog/restart, for example when server goes down or works unstable, I've also noticed that relogger doesn't "lock" wow executable while loading, hbrelog does such thing and it lowers to minimum any loading collisions. Can you add a checkbox for "loading lock" to allow only 1 wow instance to load at once ?

    Link to comment
    Share on other sites

    1 minute ago, eafa said:

    Sorry for the confusion, my problem was caused by a .dll plugin which was compiled with the previous version, all good without it.

    But ! I still have another problem - my PC may get BSOD and reboot accidently while running 3+ wrobot+wotlk instances, it also seems that it happens on mass relog/restart, for example when server goes down or works unstable, I've also noticed that relogger doesn't "lock" wow executable while loading, hbrelog does such thing and it lowers to minimum any loading collisions. Can you add a checkbox for "loading lock" to allow only 1 wow instance to load at once ?

    what is the code BSOD gives? 0x0--- something

    Link to comment
    Share on other sites

    no idea, turned off auto-reboot to look at it next time and let you know, also noticed that I have DEP on in my system settings, which I remember may cause problems with bot programs

    Link to comment
    Share on other sites

    BSOD again, no driver module or anything, just this : 

    STOP: 0x000000F4

    Also there is big wow mouse pointer in the middle of the screen which means that wow was full screen 800*600 or 1024*768 - default setting, which happens exactly when I try to launch more than 1 wow instances at the same moment. Wow just goes default probably coz Config.wtf is busy at that moment.

     

    Link to comment
    Share on other sites

    On 02/09/2016 at 11:53 AM, eafa said:

    Sorry for the confusion, my problem was caused by a .dll plugin which was compiled with the previous version, all good without it.

    But ! I still have another problem - my PC may get BSOD and reboot accidently while running 3+ wrobot+wotlk instances, it also seems that it happens on mass relog/restart, for example when server goes down or works unstable, I've also noticed that relogger doesn't "lock" wow executable while loading, hbrelog does such thing and it lowers to minimum any loading collisions. Can you add a checkbox for "loading lock" to allow only 1 wow instance to load at once ?

    I have added relogger option "Lock relogger when launch Wow or WRobot (to launch one by one):" (wait next update)

    Link to comment
    Share on other sites



    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now

×
×
  • Create New...